Admin Client - 405 method not allowed error on login

[kenoyer130]

Platform : Windows 2003 Web Server Edition, patched. .Net 1.1. MSDE database. clean machine.

After installation I launch the Admin tool to complete the setup and type the admin password and the server name in (in this case literally server) and click OK.

Error : "Unable to connect to http://server/VaultService. No server was found at the specified url. Web Exception : The request failed with HTTP status 405 : Method not allowed.

Also, on the test page at http://server/vaultservice when I click the http://server/VaultService/VaultService.asmx http error 404 is returned even though the page does indeed exist.

Thanks for you assistance in this matter

[jeremy_sg]

Could you please verify that you have ASP.Net pages enabled in your IIS manager? I've run into something like this before, and that was the cause.

[Guest]

In IIS Manager - Web Service Extensions node - the Active Server Pages status is Allowed. I assume this indicates they are enabled?

[jeremy_sg]

Another stab would be this article that Jeff just posted on installing Vault on 2003.

http://support.sourcegear.com/viewtopic.php?t=185

If you are still having the same error, then please email me at jeremy@sourcegear.com with your phone number, and we'll try to get this figured out.[/url]

[Sean]

You should also run:

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

this will ensure the asp.net is registered correctly.

[jclausius]

Does anyone know if Windows 2003 Web Server is also a Domain Controller?

I'm not up to speed on all the different types of Win2003 Servers.

[GregM]

http://www.microsoft.com/windowsserver2 ... w/web.mspx

Windows Server 2003, Web Edition, is designed specifically for dedicated Web serving needs, and its functionality has certain limitations as follows:

• Although computers running Windows Server 2003, Web Edition, can be members of a Microsoft Active Directory® service domain, Windows Server 2003, Web Edition, cannot be a domain controller. Consequently, organizations cannot use Windows Server 2003, Web Edition, alone to apply certain management features, including Group Policy, Software Restriction Policies, Remote Installation Services, Microsoft Metadirectory Services, Internet Authentication Service (IAS), and others.

• Organizations cannot use Windows Server 2003, Web Edition, to deploy enterprise Universal Description, Discovery, and Integration (UDDI) services. UDDI is an essential component for enabling discovery and reuse of XML Web services.

• Organizations cannot use Windows Server 2003, Web Edition, to deploy Microsoft SQL Server™.

[Guest]

You should also run:

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

this will ensure the asp.net is registered correctly.

I had this problem, but running aspnet_regiis.exe with the -i switch fixed it. I had installed the .NET Framework before IIS, so perhaps that is why ASP.NET was not registered on my computer.