hi,
I am now working in a project which has the following environment.
OS : windows 2000 server
Platform : .net 1.1
language : vc++.net
currently this project is in vc++ 6.0 (rpc server) and a vb 6.0 (rpc client) app will communicate to this thru rpc calls. now i have successfully (of course after having MANY number of errors) compiled it into VC++.NET. for some reasons, the vb 6.0 app will remain as it is.
my problem is , i cannot make vb 6.0 app to communicate vc++.net application IN ALL OF MY MACHINES. in one machine, i can run the project successfully. but when i copy all them , register all components into another computer, it won't run. when the vb app communicates vc++.net component, it stops saying "NULL reference pointer was passed to stub...". the error no. is 1078. i cannot find ANY USEFUL information both in msdn and other sites. Can any genius help me regarding this if those genius come from VC++ team, i will really be happy about that.
regards,
ganesh.p
1780 null reference pointer was passed to server - is there really anyway to get rid of this????
Mike Reese
I don't think there's any general knowledge to be gained other than the advice to use the debugger to track down the bug and get more information. The likelihood that this is an ordinary null pointer bug. See if you can at least isolate this null pointer issue to the VB client or C++ server side. You can use attach to process feature of the debugger to step through a debug build of the server. If it's the fault of VB component, you'll need to post your question in one of the VB newsgroups here: http://msdn.microsoft.com/newsgroups/.
XP is self aware
Sorry, I can't offer any more because I can't see/debug your code. Read my last reply for my best answer. Maybe you need to set the values for argc and argd always.
Brain
PiotrP1
You shouldn't be bounced around; you should be led to the group that can most effecively help you. As I said, if the bug is on the C++ side, then you should talk to C++ people. If VB, VB. Also for further reference, this forum is for general IDE issues, not Windows dev issues.
I think you probably discovered the solution. Are argc and argd declared as "out" parameters in your type library or IDL file This is needed by the RPC stub to marshall the result when the function "func" returns and control is given back to the VB component. I'm guessing that the C++ server is reneging on its responsibility to populate argc and argd (RPC expects that, regardless of argb).
Brian
John Dieter
hi,
Sorry for the delay in reply. actually i still cannot figure where my problem is. All i can say is, when the vb function is calling a function through rpc, this error occurs. Can you please tell me what are all the possible reasons for this error. or can you give the url which could help regarding this.
Thanks for your effort.
regards
Devi
hi,
thanks for your reply. i have debugged my application. following is my situation.
1. a vb 6.0 app communicates a vc++ component (which is compiled in .net).
2. a function in the vc++ is as follows
func( arga, argb, argc, argd);
3. in the above, argc and argd depends on the value of argb. if argb is "no", i am sending empty strings from vb application.
4. if argb is "yes", then no problems, values will be populated in argc and argd and it works fine.
5. if argb is "no", then the stated error occurs.(null reference pointer blah blah..)
6. if i pass some values in the c and d args eventhough argb is "no", then also no problem.
7. one of the most worrying thing is, in one of my machine, in all cases, the application works fine. but in another machine, the above occurs.
any suggestions
also, initially i posted this above thread in one of the vb forum and i have been redirected to this forum. now you are telling me go to vb forum.