Some other places Greg could try:
http://www.amazon.com/Professional-IIS-7-Kenneth-Schaefer/dp/0470097825/

www.iis.net<http://www.iis.net> (is Microsoft's IIS site, has a very active 
forum. But the advice there will be the same as here IMHO)

Cheers
Ken

From: [email protected] [mailto:[email protected]] On 
Behalf Of Glen Harvy
Sent: Thursday, 6 January 2011 11:53 AM
To: ozDotNet
Subject: Re: 500 - Internal server error

I have found this thread somewhat amusing although I am sure Greg certainly 
hasn't. Amusing to me in the sense that no one can help out with resolving the 
issue although there are a lot of kind people who have tried. I haven't jumped 
in because I've had similar problems in the past and I'm still not sure how I 
resolved them.

Greg, may I suggest you post (if you haven't already) your experience on a 
forum with more far-reaching viewers and with supposedly experience in this 
field. This is after all the ozdotnet forum and could hardly be considered, by 
default, to have regular contributors with experience in managing IIS nor 
SysAdmin generally.

I haven't been following to closely but are you saying that the problem is that 
you can't get it to work on GoDaddy? If that's the case, cough up $5 and get it 
running out-of-the-box on WinHost. I use them exclusively and my web services 
were easier to get running than my CMS websites were. In fact, I don't remember 
needing to configure anything for the web services to work. Are you sure 
GoDaddy even support web services? I wouldn't be surprised if they don't 
considering they concentrate on the cheaper side of hosting.

If it is GoDaddy you are having problems with, try adding this to your 
web.config file:

    <!-- set code access security trust level - this is generally set in the 
machine.config -->
    <trust level="Full" originUrl=".*" />

The above may not work - GoDaddy can override this themselves. No, I don't 
pretend to know what I'm talking about but I'm sure someone at GoDaddy should 
be able to help.

If your not trying to get it to run at GoDaddy, but on your own server then my 
solution to your problem would be, as a start, to not use IIS at all. Use IIS 
Express and see if that works. At least then you won't have a myriad of 
configuration issues to worry about.



On 6/01/2011 11:00 AM, Greg Keogh wrote:
Ken, Folks,

I'm not going as far as using rare tools that I have never seen or used before, 
not yet anyway. I shouldn't have to do this just to get some "hello world" apps 
running under IIS.

This morning I tried using a GoDaddy tool called Plesk to configure IIS, app 
pools and ASP.NET, but it provides meagre and confusing features and after 
another 2 hours or suffering I finished up with ... 500 Server error. What a 
surprise!

New experimental track ... I have a near virgin Win2008 server sitting on my 
left which will become my new web/file server in the coming weeks. I am now 
trying to get my "hello world" apps running in IIS on that clean machine. If 
they work there but not on GoDaddy then I have some more clues.

Pretty bad so far. On a Win2003 server it would take me 20 minutes to get web 
sites and ASP.NET apps all working. I have been working for 2 hours now on my 
clean Win2008 box with little to no success. I couldn't even get a plain htm 
web page to appear on the Default Web Site without giving IUSR modify 
permissions to the web folder (I've never had to do that before). If I don't, 
then I get an authentication prompt to access the htm page. I'm also getting 
permission errors on web.config even though that file is not used.

<rant>Overall ... generally speaking ... something f...@#$ing f...@#$ed up has 
happened to Win2008. All of the familiar steps I've used for years to get IIS 
and ASP.NET working are now worthless and I'm getting conflicting and unhelpful 
errors in unimaginable places.

My income for the last year has probably dropped by 15% due to the time I waste 
configuring and debugging kits, Windows, IIS and frameworks. My productive time 
as a software developer is being swallowed in frustrating never-ending 
"maintenance" tasks. Today is a typical example. I will soon spend more time 
doing unpaid "configuring" that I will writing software. I think there's a 
special black-ops department in Microsoft who have a KOAS style shield on the 
wall which is engraved with (translated from Latin) "Confound the bastards". 
Every product that is released is passed through this secret group who add 
bizarre complexity and gotchas before it reaches the public.</rant>

Greg

Reply via email to