I just setup a new SBS2011 x64. All OK.

Installed all windows updates. OK.

Installed Visual SourceSafe 2005. OK

Installed Visual SoruceSafe 2005 Update. OK

When I run SourceSafe Administrator, and enable SourceSafe Server Internet connections, it creates the SourceSafe Virtual Directory in IIS, then IIS crashes.

IIS then constantly crashes (several times a minute).

After some hours of fiddling, gave up and blew the server away. I repeated the whole process again and it destroyed IIS again.

(this time, I took bare metal backups of the server between each stage - 20 minutes to restore, not 4 hours ;)

Any suggestions?

Update:

Seems to be caused by the line in C:\Windows\System32\inetsrv\config\applicationHost.config being changed by VSS from:

<applicationPoolDefaults>

to:

<applicationPoolDefaults enable32BitAppOnWin64="true">

Changing it back brings IIS back online immediately.

link|improve this question
Got a bit further...I rolled back the applicationPoolDefaults setting, created a new .Net 2, classic pipeline application pool and assigned it to the site. Client now attempts to authenticate. – Andy Joiner Jan 29 at 21:38
So does VSS run if it is set to <applicationPoolDefaults>? If not, just enable 32Bit for the application pool VSS is using. That shouldn't crash IIS. Do other 32bit web apps run on the same server? – Peter Hahndorf Jan 29 at 21:40
Update: I got a bit further by applying 'preCondition="bitness64"' IIS modules that threw errors, but got stumped when I hit error 500.19, which appears to be due to the 64bit IIS-wide compression. I'm not prepared at this time to disable compression (server wide). I was unable to disable the compression dll using the bitness64 that worked with other modules. – Andy Joiner Jan 30 at 14:53
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown

Browse other questions tagged or ask your own question.