Install 4.12 failed (over 3.53 DB) HttpException

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
Tri
Posts: 288
Joined: Wed Dec 22, 2004 11:10 am

Install 4.12 failed (over 3.53 DB) HttpException

Post by Tri » Tue Jul 15, 2008 3:06 pm

Hi,

I am testing a Vault Server Upgrade from 3.53 and got the following error at the end of the install process:

System.Web.HttpException: The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.

Code: Select all

Stack Trace:
[HttpException (0x80004005): The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
   System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) +3570267
   System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags) +218

[HttpException (0x80004005): The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3465427
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +69
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +279
Here is what I did:

1. New test machine with only Windows 2003 Server standard 32 bits, latest system updates applied.

2. Installed SQL Server 2005 + SP2 + Cumulative Update 8

3. Restored sgvault DB from our current Vault Server 3.53 which is a SQL Server 2000 database. Backup size: 26 GB. SQL Server 2005 didn't report any error so I assume the DB restore was successful.

4. Installed Vault Server 4.12. I don't remember in details but basically, I confirmed all the default options proposed by the installer. I used the same admin pwd than the previous sgvault DB. The installer detected an existing Vault DB and I confirmed to re-use it.

5. DB conversion lasted for about 2 minutes, a screen came up asking to open the web browser to enter the serial number. I hit enter ad got the HttpException error.

6. The Admin Tool GUI as I was used to with 3.5x is no longer installed. Is it removed from 4.x?


Can you please help to diagnose the issue? Thanks very much in advance.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Wed Jul 16, 2008 8:12 am

Your installation steps are fine. Also, you are correct that there is no more admin tool. Instead it's an admin web page.

Can you give the Network Service account permissions manually to the area listed in the error?

After that, then try logging into the web client again.

Tri
Posts: 288
Joined: Wed Dec 22, 2004 11:10 am

Post by Tri » Wed Jul 16, 2008 8:46 am

Just reran the Vault 4.12 installer gain. This time there is no DB conversion dialogs. The install was completed fairly quickly and the Vault Admin Tool is available in Start Menu / SourceGear Vault.

Ran the Admin Tool, login (server = localhost) and got same error message.

Then I manually grant the local NETWORK SERVICE account the permission in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files
- Read & Execute
- List Folder Contents
- Read
- Write

Reran Admin Tool, got error
The Vault Server uses a protocol that is not supported by this client

Reran Admin Web Client, got another error
Server Error in '/VaultService' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested URL: /VaultService/login.aspx

Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433


If you need more log details, please let me know where to get them. Thanks.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Wed Jul 16, 2008 10:12 am

Don't bother with the admin tool. It's never going to connect to Vault 4.x.

Take a look at the settings in your web service extensions and set aspnet 2.0 to allow. Error 404 when accessing vaultservice/vaultservice.asmx page

Tri
Posts: 288
Joined: Wed Dec 22, 2004 11:10 am

Post by Tri » Wed Jul 16, 2008 11:01 am

ASP.NET v2.0.50727 was already allowed in Web Service Extensions.

I rebooted the server just in case. Then opened the link to Vault Web Admin (Start Menu / SourceGear Vault / Admin Web Client)

The very first time: I got the error
URL displayed in browser = http://(ComputerName)/VaultService/admin/
System.IO.FileNotFoundException: Could not find file 'c:\windows\system32\inetsrv\XXXXXXXXVault.config'.

The 2nd time I got the same HTTP 404 than above
http://(ComputerName)/VaultService/login.aspx?ReturnUrl=%2fvaultservice%2fadmin%2fdefault.aspx&message=The%20session%20has%20been%20dropped.%20You%20must%20re-authenticate.%20This%20is%20likely%20due%20to%20a%20reconfiguration%20of%20the%20server.
Server Error in '/VaultService' Application.


Does it has something to do with Windows 2003 and IIS? Can I re-restore the sgvault DB again, uninstall Vault Server 4.12 and reinstall Vault 3.53 just to check that the machine is OK?

Would the presence of Vault 3.53 impact Vault 4.12? I wanted to start on a clean machine with only Vault 4.12.

Tri
Posts: 288
Joined: Wed Dec 22, 2004 11:10 am

Post by Tri » Wed Jul 16, 2008 11:08 am

More info, if I open the page:
http://(ComputerName)/VaultService/Admin/Help.aspx

Then the "Vault and Fortress" help page is displayed. So is the web server working OK?

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Wed Jul 16, 2008 12:27 pm

Does it has something to do with Windows 2003 and IIS? Can I re-restore the sgvault DB again, uninstall Vault Server 4.12 and reinstall Vault 3.53 just to check that the machine is OK?
You can do that if you wish. Your database is probably ok, and mostly your machine is probably fine. I'm thinking that either one spot didn't get quite the right permissions or that there is some IIS setting relating to the 2.0 .NET framework that isn't quite right.

I'd say do what you suggested and then try the upgrade again. If it fails, send an email to support at sourcegear.com (attn:Beth) with a link to this thread and we'll dig a little further together into what's going on here.

Tri
Posts: 288
Joined: Wed Dec 22, 2004 11:10 am

Post by Tri » Wed Jul 16, 2008 1:16 pm

I have uninstalled Vault Server and re-installed 4.12 again. This time I could open the admin page OK. So now I can continue the evaluation.

In the meantime, can you reproduce the test scenario I made above to confirm?

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Wed Jul 16, 2008 3:55 pm

I'll run a test on this and post back results.

Locked