Help w/ RPC_S_PROTOCOL_ERROR... on vista!!! please help
- From: John S <JohnS@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 15 Feb 2007 13:01:13 -0800
Ok I am not sure if this is the correct forum for this or not,
I am getting a RPC_S_PROTOCOL_ERROR when i call my context_handle's open
function, it only happen's from one process, the other client process's can
still connect fine, and if i restart the process in question it will work
again. I need to know what this error actually means and what could be
causing it to start happening. Because seems to work fine for awhile, but
then "breaks" randomly.
Some background info.
1. I have an RPC Client/Server all of the stubs are created from an .idl
file and the rpc protocol being used is ncalrpc.
2. This is not a "com" rpc interface, This is a raw C rpc interface
generated.
3. This rpc interface also uses context handles and "async", on all of its
calls.
4. The server application is a user mode app that helps w/ managing
connections. The rpc server is started up when the application is launched
and shutdown when it exits. During these tests runs i do restart the server
application a few times.
5. The client side is a dll, it is specifically an eappeer dll which get's
loaded up into explorer.exe and svchost.exe (it is loaded into the process
space of the EapHost service).
6. When the client dll whishes to establish a new connection, a new rpc
binding handle is created and a connection is made to the well known endpoint
of the rpc server.I create a new binding for each attempt to open a new
context handle (I also close the binding handle after i close the context
handle, so i am not leaking them).
7. I use [context_handle_noserialize] on the context handles in the .acf
file, there is thread sync + reference counting code implemented on the both
the client and the server side there are no problems w/ that code.
8. I am using vista business edition 6000 (rtm).
Help w/ RPC_S_PROTOCOL_ERROR... on vista!!! please help
Ok,
I am getting a RPC_S_PROTOCOL_ERROR when i call my context_handle's open
function, it only happen's from one process, the other client process's can
still connect fine, and if i restart the process in question it will work
again. I need to know what this error actually means and what could be
causing it to start happening. Because seems to work fine for awhile, but
then "breaks" randomly.
Some background info.
1. I have an RPC Client/Server all of the stubs are created from an .idl
file and the rpc protocol being used is ncalrpc.
2. This is not a "com" rpc interface, This is a raw C rpc interface
generated.
3. This rpc interface also uses context handles and "async", on all of its
calls.
4. The server application is a user mode app that helps w/ managing
connections. The rpc server is started up when the application is launched
and shutdown when it exits. During these tests runs i do restart the server
application a few times.
5. The client side is a dll, it is specifically an eappeer dll which get's
loaded up into explorer.exe and svchost.exe (it is loaded into the process
space of the EapHost service).
6. When the client dll whishes to establish a new connection, a new rpc
binding handle is created and a connection is made to the well known endpoint
of the rpc server.I create a new binding for each attempt to open a new
context handle (I also close the binding handle after i close the context
handle, so i am not leaking them).
7. I use [context_handle_noserialize] on the context handles in the .acf
file, there is thread sync + reference counting code implemented on the both
the client and the server side there are no problems w/ that code.
When I first start out everything seems to work fine. But occasionally
after sometime (note that i am also running the "server" applicaiton from the
debugger.
The eappeer dll contacts the server from the svchost process, and also from
the explorer.exe process. But somewhere along the line I start getting the
RPC_S_PROTOCOL_ERROR protocol error when i call my context handle open
function. I only have this problem in the explorer.exe process. The
svchost.exe can still open and close new context handles w/ my server. The
problem will persist untill i restart the explorer.exe proecess. What is
causing this!!? Am i doing something wrong.
If you need any more info on the situation please let me know, i really
would like to know what is causing this and how i can fix it.
.
- Prev by Date: Re: Loader Behavior (locating the .text section)
- Next by Date: Re: DLL_THREAD_DETACH not called
- Previous by thread: DLL_THREAD_DETACH not called
- Next by thread: NonPaged Pool Memory Leak on Win2k
- Index(es):
Relevant Pages
|
