Groups | Blog | Home
all groups > dotnet remoting > june 2004 >

dotnet remoting : (405) Method Not Allowed


Gilgamesh
6/4/2004 8:57:50 AM
I've got a client application which is using remoting to connect to a remote
object hosted on IIS, and located under a virtual directory. I'm not sure if
it's the configuration problem or not, but I'm getting the error that :
Method Not Allowed.
Does somebody know what's causing this?

Thanks,
Gilgamesh

Sahil Malik
6/7/2004 12:43:25 AM
You might have registered URL's that donot end in .SOAP or .REM, as only
these two extensions are forwarded to the remoting framework by IIS.

Another reason could be that maybe your ASP.NET installation is
misconfigured (maybe by updating from a beta or "release candidate" version
to a release version or due to some choices while running the setup). In
this case, you can try to reinstall the .NET ISAPI mappings (which are also
implicitely used by .NET Remoting) by going to
C:\WINNT\Microsoft.NET\Framework\v1.0.3705 and calling ASPNET_regiis -r" to
reinstall it for all virtual domains running on your machine.

- Sahil Malik
Independent Consultant
You can reach me thru my blog at -
http://www.dotnetjunkies.com/weblog/sahilmalik/


[quoted text, click to view]

(peter.bell NO[at]SPAM visible.com)
6/20/2004 6:55:23 AM
This may be a problem with credentials. If the virtual directory requires authentication then the client side configuration file will need to pass credentials, by default it does not. The following client config file snip passes the default credentials for the current user.

<configuration>
<system.runtime.remoting>
<application>
<channels>
<channel ref="http" useDefaultCredentials="true">
</channel>
</channels>
</application>
</system.runtime.remoting>
</configuration>

Another possibility if you are passing custom types as parameters is that the server is refusing to deserialize them. The default setting does not allow it. In the server application's web.config you need to set typeFilter to Full. Enabling customErrors also provides more useful diagnostics in the exception messages received at the client.

<configuration>
<system.runtime.remoting>
<customErrors mode="On"/>
<application>
<channels>
<channel ref="http">
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full"/>
</serverProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>
</configuration>




**********************************************************************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
AddThis Social Bookmark Button