26 Sep 2009
20 Oct 2009
Link to this post
After playing around with the community edition, I desided to create a test website on our production machine.
So I installed an extra sqlexpress 2005 instance on the server to hold the dbs.
Copied all the website files from my local machine to the server.
Created a new website (not a virual directory) in IIS7 with a seperate applicationpool.
Assigned it to run in classic mode, set it to run under LocalSystem and set it to run in x32 mode.
Then I attached the database and log files to the sqlexpress instance.
And finally ran an iisreset to make all changes active. All looks oke so far.
However, If I now start IE and browse to the newly created website I receive an error 503, service unavailible after about a minute and the applicationpool crashes. In windows event logs I have these event id's:
Event ID 5139 Source WAS
A listener channel for protocol http in worker process 8512 serving application pool sitefinity reported a listener channel failure.
followed by Event ID 5002 WAS
Which states the application pool has shut down.
The problematic server is an SBS2008 x64.
I have this running on my development machine which is Win7 x64 with no problem.
Do you have any idea what could be wrong here, or what am I overlooking?