Unable to crank up Visual Basic COM+ IDE Debugging

I am developing a Desktop application that uses several layers of COM components which are written in VB6 (SP5) (W2K SP4 platform). The client application is making a call to 2 levels of COM, both of which are in seperate VB projects. I am attempting to debug an issue that I'm certain resides in the 2nd layer, and am trying to traverse through the VB projects while running them in memory by starting up the underlying VB apps and having the debugger jump from my client app to the COM. (I have been able to do this in the past without any problems). When I attempt to start the VB projects that house my COM apps, I receive the following VB error:

"Out of Memory"

When I click "OK" to clear the message box, it goes away and the project doesn't start up. It would be nice to be able to debug in this manner without having to use tedious conventions...

Thanks a million to whomever figures this out...




wgyger12Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AzraSoundCommented:
See if Microsoft KB article 241896 applies to your problem at all...
0
wgyger12Author Commented:
This KB article seems to be geared more towards what happens once the .DLL is compiled, and threading issues associated with toggling various project settings. My issue pertains more to using the VB IDE to debug between ActiveX dll projects while running them in memory. (But thanks for the very informative article.)

In my initial inquiry, I should have added the fact that the VB project that I am not able to crank up and access in memory has a local COM+ Application package which points to a remote MTS server (Using DCOM).

This probably wouldn't be such a tough issue to track if the error message had a few more details.
0
AzraSoundCommented:
Are you truly utilizing COM+ capabilities or can you take your DLL out of the COM+ package and test it?  How is the COM+ package set up security wise?  Logged on user credentials or are you specifying the account to run under?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AzraSoundCommented:
Delete
0
wgyger12Author Commented:
This was indeed a security issue. The user settings were being retrieved from the registry deep in the code. Thanks for pointing me in the right direction...
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Development

From novice to tech pro — start learning today.