problem logging in with Client and Web client

[JustinC]

I installed Vault successfully, accepted defaults.

I can hit the url

http://localhost/VaultService/

but can't hit

http://vanderbi-m8r870/VaultService/VaultWeb/login.aspx

I get this error:

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

Access to the path "C:\WINDOWS\system32" is denied

when I try to use the client I get this error


System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction:
http://www.sourcegear.com/schemas/vault ... ceVersions.
At System.Web.Services.Protocols.SoapServerProtocol.Initialize()
System.Web.Services.Protocols.ServerProtocolFactory.Create( Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)


running server, IIS and SQL are local on this machine

I'm logging in as Admin

[jclausius]

Is .Net installed? If you're running Windows 2003 Server, have you configured the Web server to act as an application server?

Can you try to browse to the following page on the server - http://localhost/VaultService/VaultService.asmx

[JustinC]

here is the reply when I browse to that url


http://localhost/VaultService/VaultService.asmx


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

VaultService


The following operations are supported. For a formal definition, please review the Service Description.


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

This web service is using http://tempuri.org/ as its default namespace.
Recommendation: Change the default namespace before the XML Web service is made public.
Each XML Web service needs a unique namespace in order for client applications to distinguish it from other services on the Web. http://tempuri.org/ is available for XML Web services that are under development, but published XML Web services should use a more permanent namespace.

Your XML Web service should be identified by a namespace that you control. For example, you can use your company's Internet domain name as part of the namespace. Although many XML Web service namespaces look like URLs, they need not point to actual resources on the Web. (XML Web service namespaces are URIs.)

For XML Web services creating using ASP.NET, the default namespace can be changed using the WebService attribute's Namespace property. The WebService attribute is an attribute applied to the class that contains the XML Web service methods. Below is a code example that sets the namespace to "http://microsoft.com/webservices/":

C#

[WebService(Namespace="http://microsoft.com/webservices/")]
public class MyWebService {
// implementation
}
Visual Basic.NET

<WebService(Namespace:="http://microsoft.com/webservices/")> Public Class MyWebService
' implementation
End Class
For more details on XML namespaces, see the W3C recommendation on Namespaces in XML.

For more details on WSDL, see the WSDL Specification.

For more details on URIs, see RFC 2396.


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

thanks for your help!!

I am double-checking the .net version (1.1 or not)
will that make a difference?

[jclausius]

When the page is working correctly, it should look like:
http://vaultdemo.sourcegear.com/vaultse ... rvice.asmx


Can you check within IIS that VaultService is a virtual directory pointing to the Vault Server installation? The error message looks as if the VaultService virtual directory is pointing to a VB based web service, not the Vault Server binaries.