Vault Server not allowing connections

Cullen · Post by **Cullen** » Tue Jul 12, 2005 2:57 pm

Vault Server 3.0.7
Client 3.0.7(2863) - Server
Client 3.0.2 - Dev box
Server Box - Win 2k3, IIS6
Dev Box - XP Pro SP2

I recently moved my vault db to a newly built server. Once the db was up and running, I installed the newest version of the vault server. Installation went fine.

I can access the vault repository through the web interface, everything works smoothly. When I try to access the repo through the client or admin tool, it throws exceptions.

On my dev box, the exception is:
Server was unable to process request. --> File or assembly name yhu-weqo.dll, or one of its dependencies, was not found.

On the server, the exception is:
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.IO.FileNotFoundException: File or assembly name bqq8euwt.dll, or one of its dependencies, was not found.
File name: "bqq8euwt.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.SoapServerType..ctor(Type type, ProtocolsEnum versionsSupported)
at System.Web.Services.Protocols.SoapServerProtocol.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\bqq8euwt.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/bqq8euwt.dll.

--- End of inner exception stack trace ---

The name of the .dll changes each time I run the app, so the exception message changes somewhat each time.

Any suggestions?

lbauer · Post by **lbauer** » Tue Jul 12, 2005 3:52 pm

We've seen this before; it's a pesky error.

Suggestions:

1. Make sure that the account used by Vault has 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
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

Post by **jclausius** » Tue Jul 12, 2005 7:18 pm

Along with the permissions on the

"%windir%\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files" folder. The ASP.Net Process account needs full control to that folder.

check "%windir%\temp" folder. The ASP.Net process account needs Read/Write/Delete

Cullen · Post by **Cullen** » Wed Jul 13, 2005 7:39 am

Ok, thanks for the input. I thought that the installer set those permissions automatically, and I have never had a problem with permissions before. I'll try changing the permissions, and get back to you if it doesn't work.

I just want to reiterate that I really appreciate SourceGear's commitment to customer service. Every time I have had an issue, you guys have responded so quickly it amazed me. Please let Eric Sink know that you two have earned him another rabid fan and customer for life.

Post by **jclausius** » Wed Jul 13, 2005 7:59 am

Cullen wrote:I thought that the installer set those permissions automatically, and I have never had a problem with permissions before. I'll try changing the permissions, and get back to you if it doesn't work.

It is supposed to do just that. However, I've encountered failures when the installation with an account which cannot set folder permissions, or a switch in the ASP.Net process caused issues. I believe the error message you are seeing occurs when the ASP.Net engine tries to compile the MSIL code, and has problems accessing the temp directory.

Cullen wrote:I just want to reiterate that I really appreciate SourceGear's commitment to customer service. Every time I have had an issue, you guys have responded so quickly it amazed me. Please let Eric Sink know that you two have earned him another rabid fan and customer for life.

We're just glad to be of service.

Cullen · Post by **Cullen** » Thu Jul 14, 2005 7:52 am

Ok, that took care of it. Here's what I did:

I checked the appPool settings in IIS, to verify which account the app was using(NETWORK SERVICE).

I went to the temp asp.net files folder, and the NETWORK SERVICE account did not have permissions. I added full control for NETWORK SERVICE.

I went to the temp folder, and once again, NETWORK SERVICE did not have permissions. I added full control for NETWORK SERVICE to the list, and now Vault is working again!

Thanks, I was concerned that I would be losing all my history on this one.

It appears that the directory permissions portion of the installer did not work. I was logged in to the server as Administrator when I installed the Vault Server.

Is there anything I can provide you guys to help you debug the error in the installer? It seems like the installer should have at least not reported the permission-setting as successful, if there was a problem.

Post by **jclausius** » Thu Jul 14, 2005 7:57 am

Can you find a vault_install.log file in your %TEMP% of the account you installed the server?

Cullen · Post by **Cullen** » Thu Jul 14, 2005 8:02 am

Do you want the logs uploaded here, or emailed?

I also wanted to tell you about another problem that this permission caused. I use DragNet as well, and use Vault integration for authentication. I was unable to log into dragnet as any user except admin. I didn't know what was causing that, but the light came on a minute ago; it was caused because the vault service couldn't execute.

Dragnet's error message was just that it couldn't log me in, so I thought something had happened to my dragnet db during the computer switch.

I just wanted to report that, in case you get the same problem from some other customer. Both Vault and Dragnet are working splendidly again.

Post by **jclausius** » Thu Jul 14, 2005 8:13 am

You can email them. Use the email button below my post to send a message. I can reply from there.

Thanks.

DragonDee · Post by **DragonDee** » Wed Oct 05, 2005 3:45 am

I had the same problem when working with mcms. The below command did the trick.

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

Cheers folks lbauer.

SourceGear Support

Vault Server not allowing connections

Vault Server not allowing connections

MCMS error -7 Where-ref bind. Location = C:\WINDOWS\TEMP\