Windows Vista SP1

[CCRussell]

Has anyone upgraded to Windows Vista SP1? I had a Vista system that was the host for the Vault server, working just fine. I made the mistake of upgrading to the production release of Vista SP1, and now the server won't work. I get an error that IE can't display the page when I try to connect to the admin page.

[Beth]

Are you trying to connect while right on the server or from a client machine? Whichever one you've tried, can you try the other?

Are clients still able to connect and get their source code?

Can you post a screenshot of the error?

[CCRussell]

Are you trying to connect while right on the server or from a client machine? Whichever one you've tried, can you try the other?

Are clients still able to connect and get their source code?

Can you post a screenshot of the error?

If I try to connect from a client, I get the following: Unable to connect to http://amd64/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: Unable to connect to the remote server

If I go to the server and try to access the client web page directly with IE, as I have been all along, I just get an IE page that says that the web page cannot be accessed.

I'll be the first to admit, I'm not an IIS guy. I almost never work with this kind of thing, so I'm way over my head. I was able to get the vault server running on Vista Ultimate (32 bit version) by following the instructions on the SourceGear web page, but only because the instructions were detailed.

I would guess that the web site is not running - but I don't know how to tell. I believe that IIS is running...

[Beth]

Some of the things you will want to check initially are detailed out in this KB article: Troubleshooting "Unable to connect to server".

Can you bring up this on your server?
http://localhost/VaultService/ or
http://<vaultserver name>/VaultService/
(ex: http://MyServer/VaultService/)

Then also, check that the IIS settings you initially set up have remained set up that way: Installing Vault on Windows Vista

[Beth]

Also, did you try just a basic iisreset? Go to Start - Run and type iisreset.

Then see if you can connect.

[CCRussell]

None of that works. Essentially, the upgrade on this system to Vista SP1 has clobbered my IIS installation. I am getting a variety of errors in different places when I try to start certain services, etc.

My next step is to reinstall Vista on this system - a drastic step but it's what I think I have to do.

One last question - I cannot make a backup of my vault database through your utilities since I cannot get them to run. I want to preserve the database - what can I back up manually?

[Beth]

The most important thing is your database as that holds all of your code. For that, just go into your SQL Server management Studio and run a backup of the sgvault and sgmaster database (if on 4.x or higher).

Which version of Vault are you on?

Do you have code changes sitting that machine? I'm assuming not since that's usually on a client, but if there are, then you may wish to make a copy of those files.

One of our developers confirmed that installing Vista sp1 on his machine stopped IIS, but an iisreset got it going again for him. What did it do when you tried to run that?

[CCRussell]

The iisreset successfully stopped iis, but the restart failed. The IIS Admin Service or the World Wide Web Publishing Service, or a service dependent on them failed to start. The service, or dependent services, may had an error during its startup or may be disabled.

[Beth]

Can you check your Event Viewer for errors? In order to find out why your IIS won't start, we need to find out what dependent component is having problems.

[micaelk]

Hi all,
I have installed Vista SP1 and the following problem arised: My IIS would not start anymore because the WAS (Windows Activation Process) service could not start. After several hours of research, here is what worked for me:

It turns out that the upgrade process did not properly update my applicationhost.config file. As a result WAS failed to start. I was missing the configHistory section definition from my file.

I diagnosed this problem by looking through TechNet for the various causes of a WAS failure. One of the ongoing themes was to be sure to have a backup of the config file:

http://technet2.microsoft.com/windowsse ... x?mfr=true

Further reading indicated that any changes to the file should generate a backup automatically but it wasn't on my machine.

Here is what I did based on what i found elsewhere: I brought up an elevated rights command prompt (right-click on command prompt icon and select run as administrator)

cd %windir%\System32\inetsrv\config
press enter
notepad ApplicationHost.config
press enter

Locate the following code:

Code: Select all

<configSections>
  <sectionGroup name="system.applicationHost">
     <section name="applicationPools" allowDefinition="AppHostOnly" overrideModeDefault="Deny" />

ADD the following line:

Code: Select all

      <section name="configHistory" allowDefinition="AppHostOnly" overrideModeDefault="Deny" />

Save the file
Try to restart the Window Activation Process Service (WAS). If the service starts, your IIS will then be able to start and your problem is solved.

This is what worked for me.
Good luck

[Beth]

Thanks for the information.

[Nidonocu]

Just had this problem also occur with the latest version of Fortress when upgrading to Vista SP1.

micaelk's fix worked perfectly though and I'm up and running again. Just thought it might be good to bump this topic now that SP1 is live via Windows Update.
I'd recommend sticking or adding this to an FAQ for anyone else who runs in to this problem so they can find this answer quickly.

[Beth]

Thanks for the heads up. I agree adding this as a KB article would be a good idea.