Hi all. I am trying to debug some Vb6 COM+ components under Win2k3 server. I have inherited this code from someone else. I have loaded the components into a COM+ application. I have the com+ app running as the interactive user. When I run the components through the debugger and call them through the web browser, I get an 0x8000ffff catastrphic error. When I don't run the components within the debugger, everything runs normally. I can compile the components fine. The compiled components work properly when called directly,
the problem is when running underneath the debugger.
I am running Win2k3 server, vb6 with sp5, and sql2k with sp3.
Anyone have any thoughts as to how to resolve this issue and to debug the components properly? I have searched the MS knowledgebase and google (sites and groups) with little result. I think that this is a security issue in that some user does not have appropiate access to something, but I am running as the local administrator and everything is configured to run as the Interactive User.
I did a talk on Windows Services in Huntsville, AL in the middle of October. I was shocked that there was more than one person there that knew what I was talking about. I had four people that asked really intelligent questions regarding the security context of a Windows Service. I was shocked because most people have a deer in headlights kind of look when I do my Windows Service talk.
A new version of the Oracle Data Provider for .NET, aka ODP.NET has been posted to the Oracle Technology Network at http://otn.oracle.com/software/tech/windows/odpnet/index.html. Enjoy.