"Server application unavailable" page

Guest · Post by **Guest** » Wed Sep 29, 2004 11:50 am

When trying to access the http://MYMACHINE/VaultService/VaultService.asmx page I come up with the following error page:

Server Application Unavailable

The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

I am also unable to find the codebehind files that are referenced in each *.asmx, *.aspx file.

Should these *.cs files be in the same directory? Are they created in some step that I missed? When searching for them I was unable to find any of these files.

I'm assuming that the missing files are the cause of the error, if not please recommend alternative solutions to the problem.

mknoll · Post by **mknoll** » Wed Sep 29, 2004 11:52 am

Forgot to log in, I posted the first message.

Post by **jclausius** » Wed Sep 29, 2004 12:25 pm

There is not enough information to provide an accurate solution, so these are "best guesses".

- What OS does the machine have?

- If Windows 2003 Server, are you certain ASP.Net is configured on your server? See the Knowledge Base related to Vault and Win2003 issues.

- If a different OS, is ASP.Net installed/ configured correctly? Does running "aspnet_iisreg -i" from your framework directory help?

mknoll · Post by **mknoll** » Thu Sep 30, 2004 9:45 am

I re-installed IIS and .NET and it seems to be working. Now when I log into the Admin tool I come up with the error in a windows box:

The server returned an unknown status code ({0})

Any idea what could be causing this?

I'm trying to set up Vault on an XP machine until I can get a server box set up for me (the SQL server is on a remote machine). Could my domain controller be an issue?

Post by **jclausius** » Thu Sep 30, 2004 10:16 am

The Domain controller is probably the problem. The Vault server has issues when .Net is installed on a Domain Controller.

You'll need to configure a Custom .Net Account and run the Vault service under identity impersonation or on Windows 2003 server only - create an application pool that is configured to use the Custom.Net account and configure the VaultService virtual directory to use that application pool.

Here is a KB article explaining the process:
FAQ: Running Vault service on a domain controller

Some other forum postings that may help as well:
Vault 2.0.6 on a Windows Server 2003 DC
Post installation problem, logging as an Admin!

mknoll · Post by **mknoll** » Thu Sep 30, 2004 11:37 am

I tried the custom user Identity Impersonation, but came up with the same result. Can the server be installed on an XP OS? This is simply to get familiar with the software until an actual server can be set up.

When I try to run the client, or when I try to ping I get an error saying strange *.dll file not being found in my windows/temp directory.

Error message:
System.IO.FileNotFoundException: File or assembly name vgpkfsrg.dll, or one of its dependencies, was not found.
File name: "vgpkfsrg.dll"
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Boolean isStringized, Evidence assemblySecurity, Boolean throwOnFileNotFound, Assembly locationHint, StackCrawlMark& stackMark)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Boolean stringized, Evidence assemblySecurity, StackCrawlMark& stackMark)
at System.Reflection.Assembly.Load(AssemblyName assemblyRef, Evidence assemblySecurity)
at System.CodeDom.Compiler.CompilerResults.get_CompiledAssembly()
at System.CodeDom.Compiler.CompilerResults.get_CompiledAssembly()
at System.Xml.Serialization.Compiler.Compile()
at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings)
at System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping[] mappings)
at System.Web.Services.Protocols.XmlReturn.GetInitializers(LogicalMethodInfo[] methodInfos)
at System.Web.Services.Protocols.XmlReturnWriter.GetInitializers(LogicalMethodInfo[] methodInfos)
at System.Web.Services.Protocols.MimeFormatter.GetInitializers(Type type, LogicalMethodInfo[] methodInfos)
at System.Web.Services.Protocols.HttpServerType..ctor(Type type)
at System.Web.Services.Protocols.HttpServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)

=== Pre-bind state information ===
LOG: Where-ref bind. Location = C:\WINDOWS\TEMP\vgpkfsrg.dll
LOG: Appbase = file:///C:/Inetpub/wwwroot/VaultService
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===

LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Attempting download of new URL file:///C:/WINDOWS/TEMP/vgpkfsrg.dll.

Let me know if this is familiar.

lbauer · Post by **lbauer** » Fri Oct 01, 2004 1:38 pm

We've seen this error before on other attempted installations on Domain Controllers. There must be a configuration issue we haven't been able to address.

Yes, you can install Vault on Windows XP Professional Edition. Be sure that IIS has been installed and then the .NET Framework.

mknoll · Post by **mknoll** » Fri Oct 01, 2004 2:10 pm

Any further recommendations? I've tried changing the web.config file according to the knowledge base article, I updated the machine.config file for the custom login, I've created the user account and added the appropriate permissions. I'm using XP professional SP1, .NET 1.1, IIS 5.1. Is there any thing I should update and try again? The web server appears to be working fine, but I can't get the admin tools or client to work (I get one of the errors listed in my previous posts).

mknoll · Post by **mknoll** » Mon Oct 11, 2004 2:32 pm

I am now able to get the admin tool and client to work on my machine, but I can't connect to the server from a remote computer. I was able to get the admin tool up and running somehow by doing the following:

1. Uninstall all sourcegear/IIS/.NET framework aps and starting from scratch.
2. Install IIS and all of its components.
3. Install .NET 1.1 redist, and
all components of the sdk pack.
4. Set full permissions for Machine/ASPNET manually in windows/temp, Inetpub/wwwroot/VaultService, Windows/Microsoft.net/framework/v1.1.4322.
5. Install SourceVault under machine config.

This worked for me, the only difference between this method and any other attempt I made was that I installed the full .NET sdk (before I left out sample applications).

Now I have a new problem, I am unable to access the server via a remote machine (inside the firewall). Could this be because I'm under a domain controller? Any helpful posts to look at?

lbauer · Post by **lbauer** » Mon Oct 11, 2004 3:46 pm

When you access Vault from the Vault Server machine, are you using "localhost" as the Vault Server name? Or are you using the machine's name or IP?

Is the "remote" machine on the same LAN as the Vault Server machine?

Review the troubleshooting tips in this KB article and let me know the results:

http://support.sourcegear.com/viewtopic.php?t=736

mknoll · Post by **mknoll** » Tue Oct 12, 2004 9:10 am

I believe most of my problems came from not having the machine/ASPNET permissions set correctly in all applicable folders. The .NET SDK isn't needed.

For the IIS process model I used "machine", and manually gave machine/ASPNET read/write permissions in:

1. C:\WINDOWS\temp
2. C:\WINDOWS\Microsoft.NET\framework\v1.1.4322
3. C:\Inetpub\wwwroot\VaultService
4. C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA

This seems to cure my install problems. Vault is now working fine, thanks for your help!