Post installation problem, logging as an Admin!

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

djMax

same problem

Post by djMax » Mon Apr 19, 2004 4:48 pm

I'm having the same problem, same config. The details of the error on ping are:

System.IO.FileNotFoundException: File or assembly name -40edl1i.dll, or one of its dependencies, was not found.
File name: "-40edl1i.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)

Given the number of problems I had before this, I'd have to say the disclaimer "Vault does not work with Windows Small Business Server 2003" is in order.

djMax

Post by djMax » Mon Apr 19, 2004 6:15 pm

In the onion of Vault install errors, my previous error has been peeled away. The Windows\Temp directory needs permissions for the user used for process model. It only seems to need List contents permissions.

So the ping tool now works. But, admin doesn't, and the argument to String.Format is still missing somewhere (i.e. I'm still getting "error {0}").

Also, it would be really nice if the admin login window registered itself in the system tray. The behavior of showing up and then disappearing and then coming back is mostly evil.

I really want this to work, I'm recommending Vault to two other companies, but the install is just plain bad at this point.

Dino
Posts: 120
Joined: Mon Apr 19, 2004 8:34 pm

I am having this same problem

Post by Dino » Mon Apr 19, 2004 8:45 pm

Was there ever a resolution?

gdmccarty
Posts: 6
Joined: Wed Apr 14, 2004 4:53 am

Waiting for contact

Post by gdmccarty » Thu Apr 22, 2004 5:57 am

I sent my contact info in, but haven't heard anything.

What should I do next?

GregM
GregM

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Thu Apr 22, 2004 6:25 am

Sorry, it's my fault that you haven't heard anything back. I let it slip down my inbox. I'll contact you today.

-Jeremy

djMaxM

Post by djMaxM » Thu Apr 22, 2004 9:53 am

I believe I know what causes this. If you try to install the Vault web app into companyweb, which is the natural place, it won't work. SBS Sharepoint installs a bunch of custom filters in that website which seem to cause Vault to fail. I created a new web site called "Vault", installed the product there, upgrade the trust in web.config to full, and it works fine now.

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Fri Apr 23, 2004 10:39 am

The cause of GregM's trouble was sharepoint creating a web.config file in c:\inetpub\wwwroot that cleared the httpmodules settings from his machine.config and did not add the System.Web.SessionState.SessionStateModule module back. Fixing the c:\inetpub\wwwroot\web.config file corrected the problem.

Jon Hart

How do I add the session module back?

Post by Jon Hart » Fri Nov 05, 2004 9:04 pm

Rather than just telling us what went wrong, could you also provide a sample on how to fix it?
Im new to .net and have no idea what or where to add to the web.config

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Fri Nov 05, 2004 10:49 pm

Here's an example.

In IIS 5.0, the modules are configured by a file named machine.config in your Microsoft .Net direcotry. See %WINDIR%\Microsoft.NET\Framework\v1.1.4322\config\machine.config

This file will contain elements on how applications are controlled.

Anyway, if you view this file, you will see a section of XML named <httpModules>. In this element, there is a sub element named Session, which tells ASP.Net to handle all session handling by this piece of the .Net framework.

Now Sharepoint goes and installs its own web.config in the ROOT of all web servers. What this does is over-ride the settings in machine.config, and it also gives NEW defaults to any sub folders, including the Vault server.

So Vault then inherits this new setting, which renders it useless as Session handling is a key requirement for the Vault server.

In the post by Jeremy, placing the xml for httpmodules in .Net's machine.config in wwwroot's web.config solved this problem.
Jeff Clausius
SourceGear

Jon Hart

Thanks

Post by Jon Hart » Mon Nov 08, 2004 4:12 pm

Thanks thats exactly what I needed to know.
I also had to modify the trust level to Full, otherwise one of the DLLs from Vault was not being vaildated.

I think it would be appropriate for the installer to validate the operability of the install after it has run. These issues seem to be pretty straight forward, and you could provide immediate help and feedback about configuration issues.

RoboDada

Same problem....

Post by RoboDada » Fri Nov 12, 2004 12:10 pm

I'm also experiencing this problem -- getting the "The server returned an unknown status code ({0})." error when trying to log in to the Admin tool.

I'm running Windows Server 2003 Standard, IIS 6.0. No SharePoint Server installed; however, ActiveDirectory IS set up on this machine; I've made the adjustments suggested in the Microsoft KB article (creating the weak account, setting the ASP.NET process to run under it), though I'm not sure how to check that those settings took hold (I DID reboot the machine).

I can get to the http://localhost/VaultService/VaultService.asmx page, as well as http://localhost/VaultService. I can see the Ping service, but when I try to invoke it, I get a Error 500 from IIS (internal server error).

There IS a sgvault.log file being created in the Windows\Temp\sgvault folder -- but nothing else.

If I try to run the Client tool (never having run the Admin tool yet) from the same machine, I get an error stating: "Server was unable to process request --> File or assembly name _xxxxxx.dll, or one of its dependencies, was not found". The assembly name (shown here as _xxxxxx.dll) changes each time it is run, and is always a seemingly random series of characters.

So, I'm stuck. I've reviews most of the posts in these forums and haven't found the answer yet.

Can anybody point me in SOME direction? We're evaluating for use in our shop and need to decide soon!

Rob Schripsema
Integra Software and Services, Inc.
360-354-0314

Post Reply