I've got a DLL that I'm trying to debug. I've inherited this code and cannot get in touch with the original developer to find out what to do.
This dll gets called to build a webpage. When I set a break point on the function getting called, the dll breaks just fine.
A bunch of Dim statements get called including
Dim objContext As COMSVCSLib.ObjectContext
Then a bit later (the first actual line to debug)
Set objContext = GetObjectContext
This isn't doing much of anything. objContext is not populated with anything.
The thing is, if I'm not debugging, everything works fine. I'm just trying to walk through the code to get a feel for the way things work. There's a ton of function calls and I do much better if I can walk through, ya know.
Does anyone have any ideas?
Someone suggested permission issues in the Component Services, which I've changed to include the IUSR, but that had no effect.
Thanks for your time.
I've debugged other DLLs for this application, none of them use COMSVCSLib though, so I think that's the main part of the problem.
Last edited by stin; November 11th, 2008 at 09:33 AM.
Reason: added clarification
If you go into the Management console, you should find a number of MTS Package's. If you run the code that calls this Dll, watch the Packages and see which one starts running. If you have load's it might be tricky to see which one it is, however, you should be able to work through the packages to work out which one it is.
If you find my answers helpful, dont forget to rate me
I had to set up my console, but I didn't see MTS in the list of sanp-ins to add. I added 'Component services' Which has a 'Distributed Transaction Coordinator' in it, but I didn't see anything else. Any other ideas??