remoteing setup
(Thursday, December 23, 2004)
Found the following interesting discussion in the Newsgroups:
remoteing setup
by:Brian Henry
| I have a server which uses remoteing and it works on a few systems but on
the server we want it to run on it always returns the error "internal server
error" back to the client application as an exception... but when we run the
server app on a windows xp pro box or a secondary windows 2000 server box it
works perfectly... what settings should i check? any security problems i
should look at in the 2000 server box that it wont work on? for a while it
was throwing exceptions back on that box when the app was starting, then i
ran the fix an app wizard and changed the mode to safe mode for the .net app
and it loaded, what should i be looking at to try to trouble shoot this?
thanks
| | | Reply:
by:Brian Henry
| | | also here is the error message from the client.....
"Server encountered an internal error. for mor information, turn on
customErrors in the server's .config file"
how do i do this? what is the correct tag and what level should it be placed
at in the config file? thanks
| | | Reply:
by:v-phuang@online.microsoft.com (Peter Huang)
| | | Hi Bian,
First of all, I would like to confirm my understanding of your issue.
From your description, I understand that you have a remoting server which
will start by reading the config file. The remoting server will run well on
many servers, but on certain server, the remoting server will encounter
error.
I did not understand your meaning very well at the point, when the remoting
server start, will it report any error? Or it will not report error, but
when you start the client on another machine or on the local machine, the
client will get the error?
I think you may follow the instruction you post in another post, that turn
on the customErrors for detailed error information.
<customErrors> Element
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
ml/gnconcustomerrorselement.asp
You may try to check if the port used by the remoting has been used by
other application on the "problem" server?
You may also try to start the remoting server and remoting client by coding
not by the configuration file.
Best regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
| | | Reply:
by:Brian Henry
| | | hello Peter,
we tracked down the problem and it turned out to be a DNS server problem, we
corrected it by changeing the DNS server, thanks for the help
|
|
0 Comments:
Post a Comment