HTTP Error 500.19 - Internal Server Error

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
nfa
Posts: 4
Joined: Tue Aug 02, 2011 3:57 am

HTTP Error 500.19 - Internal Server Error

Post by nfa » Tue Aug 02, 2011 4:13 am

Hello,

I've installed Vault Standard 32bit on a Windows Server 2008 R2 64bit with IIS 7.5. When I log in to Admin Web Client and try to run a "Hand Off" it says I must enable 32-bit application. So when I set "Enable 32-bit applications" to true I can't start the web site.

The error is:

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

Module StaticCompressionModule
Notification MapRequestHandler
Handler StaticFile
Error Code 0x8007007e
Requested URL http://ncghypv01.ncg.local:8088/vaultservice/admin
Physical Path C:\inetpub\wwwroot\VaultService\admin
Logon Method Anonymous
Logon User Anonymous



Any help is appreciated.

/Niclas

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: HTTP Error 500.19 - Internal Server Error

Post by lbauer » Tue Aug 02, 2011 1:16 pm

The first thing I would suggest is to make sure the 2.0.x 32-bit framework is registered.

Run this command from a command prompt:

C:\Windows\Microsoft.net\Framework\v2.0.50727\aspnet_regiis -i
Linda Bauer
SourceGear
Technical Support Manager

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: HTTP Error 500.19 - Internal Server Error

Post by lbauer » Tue Aug 02, 2011 2:39 pm

Another thought -- are you sure you installed the 32-bit Vault Server? Could you have installed the 64-bit Vault Server?
Linda Bauer
SourceGear
Technical Support Manager

nfa
Posts: 4
Joined: Tue Aug 02, 2011 3:57 am

Re: HTTP Error 500.19 - Internal Server Error

Post by nfa » Tue Aug 02, 2011 2:55 pm

Hi and thanks for your anser.

I have tried to register and yes, the version is the 32bit...

I will double check tomorrow but I am pretty sure.

It's funny it works fine when 32 bit applikation is disabled.

nfa
Posts: 4
Joined: Tue Aug 02, 2011 3:57 am

Re: HTTP Error 500.19 - Internal Server Error

Post by nfa » Wed Aug 03, 2011 1:01 am

OK, back at work. I've double checked and it was the 32bit that was installed.

Since all I want to do is use Hand off and therefore I need to enable 32bit, is there any other way to (manually) move the files from VSS to Vault? I've tried to get latest from VSS and add the files manually to Vault. I realize that the history is gone but that I can live with. The problem when I do that I can't make a .NET solution to be opened. It complains about wrong SourceControl, I've tried to rebind in Visual Studio, tried to remove all *.vssscc, *.scc, *.vspscc files but nothing seems to work.

Either I need to get the 32bit to work so I can use the Hand off or a step-by-step how to manually "deattach" files from VSS so I can add them to Vault.

Thanks.

nfa
Posts: 4
Joined: Tue Aug 02, 2011 3:57 am

Re: HTTP Error 500.19 - Internal Server Error

Post by nfa » Wed Aug 03, 2011 7:10 am

Hello again,

I've successfully manage to manually rebind a Visual Studio project to Vault and it works as expected. I think it's good enough even if it's lots of work and the history is gone.

One question though. We also have lots of old VB6 projects and as I understand it you have a plugin for VB6 also (don't have the time to investigate it further today) but you don't support rebinding of VB6 projects? Can you explain how I in the simplest way do that or is it just to add the files to Vault and open the project in VB6 and it's automatically works?

Thanks.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: HTTP Error 500.19 - Internal Server Error

Post by lbauer » Wed Aug 03, 2011 10:19 am

VB 6 doesn't have an "unbind" command. To unbind you would delete any source control files in the project in your working folder, particularly the MSSCCPRJ.SCC file. This has the path to the source control provider.

Next make Vault your default SCC provider. This setting is in the Vault Client under Tools->Options->General.

Next, after you have deleted the MSSCCPRJ.SCC file, you can open the VB project. You may get a prompt asking if you want to add the project to Vault, or you can use the command in VB under Tools->SourceGear Vault->Add Project to SourceGear Vault.

This should create a new MSSCCPRJ.SCC file with Vault as the SCC provider.

If another user wants to open the project from Vault, they can use the command in VB 6 under Tools->SourceGear Vault->Create Project from SourceGear Vault.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply