Strange, even stranger errors with my DCOM... (Long MSG)
-
Hi folks... it's me again.... :(( Now approaching wit another strange problem. I just upgraded my systems to Platform SDK Feb '03 to permit me to declare UUIDs in structs in IDL files. I finished redesigning all the project, put the structs in right places, made the appropriate modifies, then I compiled the server and that went OK, compiled the proxy/stub DLL and that was OK again, compiled the client and it went OK. After that I picked up the server executable and the DLL and copied in my folder on client side, and tried to register both of them. The DLL was OK, but not the client. I got a MessageBox that told me of a memory leak, but the title of that MessageBox left me breathless. (LWTCPJSOCKWNDYCLASS: STTRServer.exe - Application Error). I tried to search about that string but don't know what it is. I just can guess that is something about the network, but just nothing more. So I fulfilled the registration part with log statements and I saw that the program executes ALL the instructions (and the return code is ALWAYS S_OK!). So I was stuck. Just to try, I saw that the component registered however, so I tried to start it. Well, it does some strange things. 1) It executes on both client and server (when I configured it to run ONLY on remote machine) and fills BOTH logs:doh: 2) It gives me an error 0x80029c4a: cannot load library/DLL.:doh::doh: The only thing I've not yet done is to rebuild the project on client (since it's an XP Pro machine, while the server is a 2000 Pro machine), but it should work anyway, not event vice versa, but an older engine should work on a newer OS, not? Is there someone that can help me? I can send (not post due of size) code to anyone that would like to analyze it. Thanks again (and I hope this would be the last, for this project! I'm getting crazy!:mad:) Morenz
-
Hi folks... it's me again.... :(( Now approaching wit another strange problem. I just upgraded my systems to Platform SDK Feb '03 to permit me to declare UUIDs in structs in IDL files. I finished redesigning all the project, put the structs in right places, made the appropriate modifies, then I compiled the server and that went OK, compiled the proxy/stub DLL and that was OK again, compiled the client and it went OK. After that I picked up the server executable and the DLL and copied in my folder on client side, and tried to register both of them. The DLL was OK, but not the client. I got a MessageBox that told me of a memory leak, but the title of that MessageBox left me breathless. (LWTCPJSOCKWNDYCLASS: STTRServer.exe - Application Error). I tried to search about that string but don't know what it is. I just can guess that is something about the network, but just nothing more. So I fulfilled the registration part with log statements and I saw that the program executes ALL the instructions (and the return code is ALWAYS S_OK!). So I was stuck. Just to try, I saw that the component registered however, so I tried to start it. Well, it does some strange things. 1) It executes on both client and server (when I configured it to run ONLY on remote machine) and fills BOTH logs:doh: 2) It gives me an error 0x80029c4a: cannot load library/DLL.:doh::doh: The only thing I've not yet done is to rebuild the project on client (since it's an XP Pro machine, while the server is a 2000 Pro machine), but it should work anyway, not event vice versa, but an older engine should work on a newer OS, not? Is there someone that can help me? I can send (not post due of size) code to anyone that would like to analyze it. Thanks again (and I hope this would be the last, for this project! I'm getting crazy!:mad:) Morenz
As soon as I got a Win2k machine, I noticed that i couldn't register ONE out of my FOUR classes. I went in my source code, and I noticed that when I tried to modify project for custom marshaling, I commented out the COM_INTERFACE_ENTRY(IDispatch) for two interfaces, and the third I modified it into COM_INTERFACE_ENTRY (IUnknown). The ONLY class that was right, was the only one that could not be registered. Fixing it, on a 2k machine registers and starts regurlary. Now, it's to try on a XP machine... but I think it will work.... Yesterday was a bad day, you know, I made so many bad things.... Today is a good day, many problems getting away... ;)