HighTechTalks DotNet Forums  

System.Net.WebException: The remote server returned an error: (400) Bad Request exception

Dotnet Framework (Remoting) microsoft.public.dotnet.framework.remoting


Discuss System.Net.WebException: The remote server returned an error: (400) Bad Request exception in the Dotnet Framework (Remoting) forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
Stephen Barrett
 
Posts: n/a

Default System.Net.WebException: The remote server returned an error: (400) Bad Request exception - 05-31-2006 , 01:13 PM






I am having problems getting remoting working in a new environment.

I have an existing environment with a webapp tier, an application server
tier, and database tier.

The webapp talks to app tier via remoting using a serverfactory/inteface
design approach. The app tier is hosted in IIS and we use the binary
formatter.

Everything works fine in an existing environment. We are setting up a
disaster recovery environment that is a duplicate of the working production
environment.

We are not using the GAC for any of our components.

In this new environment, when ever we try to call a method on our server
factory (hosted as singleton), we get a System.Net.WebException: The remote
server returned an error: (400) Bad Request exception.

A coworker and I have both checked the config files at least 10 times to
make sure everything is configured properly. In fact, the only change of
the config file from the working production environment is the ipaddress of
the app server tier in the webapp's web.config file. Everything else is
exactly the same from what I can tell.

I am guessing that the server itself was staged a little differently by the
IT group, but I cannot tell a difference. I have tested a self contained
ASP.NET application on the appserver and web server and it runs fine so I
believe asp.net is configured properly.

Anyone have any ideas?

This is framework 1.1



Reply With Quote
  #2  
Old   
Stephen Barrett
 
Posts: n/a

Default Re: System.Net.WebException: The remote server returned an error: (400) Bad Request exception - 05-31-2006 , 01:35 PM






Here are the webapp's and app server apps' remoting sections from the config
files in case it helps. I have intentionally changed the ip addresses to
bogus addresses.

WEBAPP
<system.runtime.remoting>
<application>
<client>
<wellknown type="PenProPlus.Remoting.IServerFactory,
PenProPlus.Remoting"
url="tcp://111.111.111.111:8090/Server.ServerFactory" />
</client>
<channels>
<channel ref="http">
<serverProviders>
<formatter ref="binary" />
</serverProviders>
</channel>
</channels>
</application>
<customErrors mode="off"/>
</system.runtime.remoting>

APPSERVER
<system.runtime.remoting>
<application>
<service>
<wellknown type="PenProPlus.Remoting.ServerFactory,
PenProPlus.Remoting"
objectUri="Server.ServerFactory.rem" mode="Singleton" />
</service>
<channels>
<channel ref="http" />
</channels>
</application>
<customErrors mode="off"/>
</system.runtime.remoting>

"Stephen Barrett" <stephen_barrett (AT) aon_nospam (DOT) com> wrote

Quote:
I am having problems getting remoting working in a new environment.

I have an existing environment with a webapp tier, an application server
tier, and database tier.

The webapp talks to app tier via remoting using a serverfactory/inteface
design approach. The app tier is hosted in IIS and we use the binary
formatter.

Everything works fine in an existing environment. We are setting up a
disaster recovery environment that is a duplicate of the working
production environment.

We are not using the GAC for any of our components.

In this new environment, when ever we try to call a method on our server
factory (hosted as singleton), we get a System.Net.WebException: The
remote server returned an error: (400) Bad Request exception.

A coworker and I have both checked the config files at least 10 times to
make sure everything is configured properly. In fact, the only change of
the config file from the working production environment is the ipaddress
of the app server tier in the webapp's web.config file. Everything else
is exactly the same from what I can tell.

I am guessing that the server itself was staged a little differently by
the IT group, but I cannot tell a difference. I have tested a self
contained ASP.NET application on the appserver and web server and it runs
fine so I believe asp.net is configured properly.

Anyone have any ideas?

This is framework 1.1





Reply With Quote
  #3  
Old   
Bluesky25
 
Posts: n/a

Default Re: System.Net.WebException: The remote server returned an error:(400) Bad Request exception - 06-28-2006 , 04:59 AM



Stephen Barrett a écrit :
Quote:
I am having problems getting remoting working in a new environment.

Everything works fine in an existing environment. We are setting up a
disaster recovery environment that is a duplicate of the working
production environment.

Hi,

I am having the same problem and I cannot find any solution. The only
difference between our working environment and the one which raises the
Exception is the domain we use.
If you have solved this problem or have any clue, I am really
interested since I have to make it work quickly and I have no idea
anymore...

Thanks a lot,

Alexandre.


Reply With Quote
  #4  
Old   
Bluesky25
 
Posts: n/a

Default Re: System.Net.WebException: The remote server returned an error:(400) Bad Request exception - 06-28-2006 , 07:01 AM



Bluesky25 a écrit :
Quote:
Stephen Barrett a écrit :
I am having problems getting remoting working in a new environment.

Everything works fine in an existing environment. We are setting up
a disaster recovery environment that is a duplicate of the working
production environment.


Hi,

I am having the same problem and I cannot find any solution. The only
difference between our working environment and the one which raises the
Exception is the domain we use.
If you have solved this problem or have any clue, I am really
interested since I have to make it work quickly and I have no idea
anymore...

Thanks a lot,

Alexandre.
Framework 1.1 SP1 fixed the problem WITH this registry tweak :
http://support.microsoft.com/default...b;EN-US;826437

The error has changed ! Requested service not found...


Reply With Quote
  #5  
Old   
rajeesh t ravi
 
Posts: n/a

Default Re: System.Net.WebException: The remote server returned an error: (400) Bad Request exception - 01-31-2007 , 05:03 AM





Actually this error occured for me also, i can found out that this error
is due to the from session authentication using session variable,just
remove the authentication part and try it
eg)
If dCompanyId = 0 Then
'Response.Redirect("\odms/login.aspx?sErrorMsg=
You Must Login")
'Else
If Page.IsPostBack = False Then
------------------code here----------------
just remove the part mentioned here
If dCompanyId = 0 Then
'Response.Redirect("\odms/login.aspx?sErrorMsg=
You Must Login")
'Else



Rajeesh T Ravi
Software Engineer
Keys Infotech
Cochin

*** Sent via Developersdex http://www.developersdex.com ***

Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.