Upgrading 4.1.3 to 5.0.2 fails

[stevek2]

I have a 64-bit Win2003 server that was running 4.1.3.

After upgrading to 5.0.2 (64-bit), now Vault is broken. I can access http:/<server>/vaultservice and get the 'Vault Home Page' but if I access http://<server>/VaultService/VaultWeb/login.aspx or http://<server>/VaultService/Admin/, I get the following error:

Could not load file or assembly 'DragnetControlsLib, Version=5.0.2.18753, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.

The complete error message and stack trace is below. I have tried an iisreset, and it still fails in the same way. In searching for this error in the forum, it seems some people saw this error during the Vault 5/Fortress 2 beta, but (a) it says it was fixed before the release, and (b) there is something about turning off 32-bit support for the VaultAppPool, but I can't find where to do that.

Also, the 5.0.2 installer said it needed .NET 3.5, so I installed that (and all its service packs) before running the vault installer.

Please help quickly, I was hoping this would be a painless upgrade!!!
Thanks.

--------------------------------------------------------------------------------


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

Could not load file or assembly 'DragnetControlsLib, Version=5.0.2.18753, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
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: Could not load file or assembly 'DragnetControlsLib, Version=5.0.2.18753, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.

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: Could not load file or assembly 'DragnetControlsLib, Version=5.0.2.18753, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.]
System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0
System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +43
System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +127
System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +142
System.Reflection.Assembly.Load(String assemblyString) +28
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +46

[ConfigurationErrorsException: Could not load file or assembly 'DragnetControlsLib, Version=5.0.2.18753, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.]
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +599
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +193
System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +45
System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +178
System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +56
System.Web.Compilation.ApplicationBuildProvider.GetGlobalAsaxBuildResult(Boolean isPrecompiledApp) +235
System.Web.Compilation.BuildManager.CompileGlobalAsax() +53
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +406

[HttpException (0x80004005): Could not load file or assembly 'DragnetControlsLib, Version=5.0.2.18753, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.]
System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +60
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +506
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +779

[HttpException (0x80004005): Could not load file or assembly 'DragnetControlsLib, Version=5.0.2.18753, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +549
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +78
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +257




--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3082

[Beth]

Did you install the 64-bit version of the installer or the 32-bit version? The only way you'd need to put IIS in 32-bit mode is if you were running the 32-bit installer. If you were running in 32-bit mode with Vault 4.1.3, then IIS would already be set to run in 32-bit to make that version work.

[stevek2]

I installed the 64-bit version of the installer. I'm pretty sure I was running the 64-bit version of 4.1.3, as well.

[stevek2]

More info...

Would I get this error if I was running 4.1.3 in 32-bit mode, and then tried to install 5.0.2 in 64-bit mode? I thought I had installed 4.1.3 in 64-bit mode, but I could be wrong. I just now tried to run aspnet_regiis.exe -lk in order to display the ASP.NET bindings, and I found I have to run this from the Framework directory, not Framework64 (ie, I have to run the 32-bit version of aspnet_regiis.exe, if I run the 64-bit version it says IIS in in 32-bit mode).

[stevek2]

More info...I tried the following commands and this seems to have gotten Vault running:

1. Disabled IIS 32-bit mode with the following:

c:\>cscript \inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 False

2. Reset ASP.NET to use the 64-bit v2.0 version:

c:\windows\microsoft.net\framework64\v2.0.50727>aspnet_regiis -i

I can only conclude that I previously ran the 32-bit installer, and then erroneously ran the 64-bit installer this time. Is there any reason I need to use 32-bit mode? I'm not using IIS for anything except Vault.

[Beth]

Thanks for the update. Unless some other program is using 32-bit mode, there's no reason to use it. Based on the little information I have in this thread, I'd say you did the right thing.

[stevek2]

All's well, except when I navigate to 'Shadow Folders' in the Admin tool -- I get


Shadow Folders - Default Repository
The Shadow Folder Service has a configuration error. A valid Cache Path was not specified, and the Shadow Folder Service was unable to create the cache in the default location. Please specify a valid "shadowfolder_cachepath" in the appSettings of the Shadow Folder Service's web.config file.

Now, I've never used Shadow Folders before -- but I wanted to make sure, is this because I haven't setup Shadow Folders properly (since I've never used it before) -- or is this a result of some 32- vs 64- screwup?

How do I get Shadow Folders working (the above-mentioned shadowfolder_cachepath is commented-out in the web.config file).

[Beth]

We have a KB article on what to do for that error posted here: http://support.sourcegear.com/viewtopic ... 13&t=11576.