[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.remoting

405) Method Not Allowed

Gilgamesh

6/4/2004 3:58:00 PM

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
2 Answers

Sahil Malik

6/7/2004 4:43:00 AM

0

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/s...


"Gilgamesh" <gilgamesh4ever@aol.com> wrote in message
news:OGceIykSEHA.3728@TK2MSFTNGP11.phx.gbl...
> 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
>
>

PeterJ.Bell(peter.bell

6/20/2004 1:55:00 PM

0

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.fuzzysof...
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...