Vault server fails to work on 64-bit Windows Server (x64)

[gsmalter]

We just installed Vault 3.1.6 on Windows Server 2003 Standard x64 Edition. We can successfully hit the web page (http://location/VaultService), so we know the web service is running, but logging on through the web page or through the Vault Client results in the error shown at the bottom of this post.

From recent experience, I can tell you that this error is a symptom of a web application running in a 64-bit process trying to invoke 32-bit COM in-process.

The only solution to this is to configure IIS to server in 32-bit processes, but that is not an option for us.

It's critical that we're able to host Vault on our 64-bit server. When will this be supported?

The error encountered was the following:

Server Error in '/VaultService' Application.
--------------------------------------------------------------------------------

is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.BadImageFormatException: is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[BadImageFormatException: is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)]
System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0
System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +495
System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +192
System.Reflection.Assembly.Load(String assemblyString) +42
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +182

[ConfigurationErrorsException: is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)]
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +1259
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +388
System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +145
System.Web.Configuration.AssemblyInfo.get_AssemblyInternal() +30
System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +227
System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +76
System.Web.Compilation.ApplicationBuildProvider.GetGlobalAsaxBuildResult(Boolean isPrecompiledApp) +323
System.Web.Compilation.BuildManager.CompileGlobalAsax() +64
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +785

[HttpException (0x80004005): is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)]
System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +76
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +1168
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +906

[HttpException (0x80004005): is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +709
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +317
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +595
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

[lbauer]

It's critical that we're able to host Vault on our 64-bit server. When will this be supported?

It's on our list of things to do. I'll bump it up in priority, but we don't have a timeframe as yet.

We haven't tested Vault on 64-bit Windows, but we do know the registry in 64-bit systems is different, and our current Vault installer doesn't take that into account. More info here:

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

[gsmalter]

I appreciate the New Year's response.