If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

DLL Debuggin'

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

Code:

Dim objContext As COMSVCSLib.ObjectContext

Then a bit later (the first actual line to debug)

Code:

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.

edit -
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 10:33 AM.
Reason: added clarification

Re: DLL Debuggin'

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.

Re: DLL Debuggin'

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??

Under System Application -> Components there is COMSVCS.TrackerServer, which, at least to me, appears to be the one I'm having trouble with. There isn't much I can do here in the way of configuration.

On the System Application I can right click and get a properties page and in the 'Security' tab there are options available to change for 'Authentication Level for Calls'. I have no idea what that does, but I'll look at it. The current setting is on 'Packet Privacy'

Re: DLL Debuggin'

There are 4 resolutions:
The MTS Transaction Mode for the component is set to a value other than 0 - NotAnMTSObject. I tried all available options, nothing worked. Currently set to 1

Visual Basic 6 Service Pack 3 (SP3) or later is installed on the computer.
I'm using SP 6

The authenticating user has the appropriate permissions. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
259725 PRB: Error Occurs When You Debug a COM+ Component Under the Visual Basic IDE with an ASP Client
I went through the steps here and nothing

The component is deployed in a COM+ application.
Not really sure how to check this.

I realized just now that all these solutions are for allowing me to debug. I'm able to debug just fine. The issue is that COMSVCSLib isn't initializing or something.

* The Perfect Platform for Game Developers: Android
Developing rich, high performance Android games from the ground up is a daunting task. Intel has provided Android developers with a number of tools that can be leveraged by Android game developers.

* The Best Reasons to Target Windows 8
Learn some of the best reasons why you should seriously consider bringing your Android mobile development expertise to bear on the Windows 8 platform.