File or assembly name not found

[darthg8r]

I installed vault 2.06 on a windows 2003 server machine about a month ago and started using it. After using it for a while, and then upgrading that machine to domain controller, vault stopped functioning. When I try to connect to it, I get an error when logging into it using the 2.06 client.

Server was unable to process request. --> File or assembly name 37eoxaa7.dll, or one of its dependencies, was not found.

The assembly name is different every time you try to connect and appears to be a random set of chars. I've reinstalled the application multiple times without any luck.

Anyone have any ideas?

[jeremy_sg]

A couple of ideas,

1. Make sure that the appropriate accounts have full control to C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files

2. Try having the .net framework reregister with IIS. Run the command

Code: Select all

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe  -i

[darthg8r]

Re-registering ASP.NET seemed to work. Thanks

[Paulm]

Tried it, now same error but a different dll "Server was unable to process request. --> File or assembly name erjvuk4k.dll, or one of its dependencies, was not found."

As far as I can see I've gien the right permissions following the article in the knowledge base. All I want is for users to authenticate using AD to log into Vault. I gather I need to have this domain account impersonation to make that possible ?

[bvsoftware]

Could this be related to an install of the 2.0 .NET Framework? I'm getting the same error now.

[akeck]

Hi!

A little hint:
We upgraded our Server in a, let's say, bold way...
We took the disks out of the old P4/2,4 GHz machine and put it into a brand new Dell PowerEdge 1800 (Dual P4 Xeon 3.0 with 2GB RAM...)
We did a repair on Windows (did not start because of the new SATA Controller and other Chipset,...)

Before you call me stupid: we keeped a complete mirror set of the disks in the old server, so going back was a matter of plugging the network cable into the old server... just to be sure...
...and keeping in mind that I want to have a second child and my boss would take some important parts from me making this impossible when our data are lost...

Server worked fine, so I wanted to do a final check with Vault...
guess what: NOTHING worked...

But looking here gave me the solution! Re-Registering .net Framework did the Job, but: I had to re-install Vault Server completely. Only re-registering didn't work!

So if someone hates his live and does a Server Upgrade as we did: Re-Register AND Re-Install!

Thanks alot! Now I will get a chance to watch my son tomorrow searching for his easter eggs!

Alex

[lbauer]

Yeah, we've not tested re-arranging computer parts with Vault on them to see what works and what doesn't. If you're going to do major surgery to your Vault hardware, we'd recommend uninstalling Vault, keeping the database, then reinstalling Vault.

Your boss and your heirs will be happier.