March 7, 2005 at 10:23 am
Hardware: 2000 Sql Server on a 2003 windows server not a DC. Domain is a native 2000. The sql server is only 2003 server.
The application server is running on the same box as the sql server.
Problem: A thread within a user's session will drop out. There will be no error messages on the server or client machine. Sometimes there will be a general rpc error, but not always.
March 7, 2005 at 12:16 pm
Sounds like client side setting issues. Are you running any antivirus on the server? Which is the rpc error you are experiencing?
* Noel
March 8, 2005 at 7:26 am
No AV on the server, not stable enough yet.
Rpc error code rpc_s_invalid_level
March 8, 2005 at 12:56 pm
Sounds like the remote client is holding on the session after it's work is done. The RPC session can drop due to inactivity, the client doesn't know it, and tries to use it. The referenced error could be from trying to access a connection that is no longer active.
Clients should close when (logically) completed processing and going idle, and reopen session when needed. When using ActiveX and DCOM, putting the middle-tier component in Component service package automatically handles that by giving the client a proxy id to hold onto, but not allocating a session until explicitly needed, and dropping it as soon as it can.
Mark
March 8, 2005 at 2:13 pm
Good thought, those who use that section the least get the most errors. Is there a good tool to monitor the RPC connection on the client?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply