VB COM, Debugging COM+ Componets -- Runtime error 91- Object variable or with block not set

Debugging COM+ Componets -- Runtime error 91- Object variable or with block not set

Author	Message
Mart #1 / 3	Debugging COM+ Componets -- Runtime error 91- Object variable or with block not set I am trying to debug my com+ components on win2k and vb6 and am receiving the above error when calling GetObjectContext.CreateInstance or GetObjectContext.SetComplete, I know I had to add some registry settings when working on NT4 & MTS. Do I need to do the same thing for Win2k & COM+? If so, what are the additions. There is a knowledge Base article on Microsoft's site but it no longer available. Thanks in advance. Marty
Sun, 12 Oct 2003 05:36:27 GMT

Cale L. Corbet #2 / 3	Debugging COM+ Componets -- Runtime error 91- Object variable or with block not set Without getting into too much detail, have you created your objects with New or CreateObject? There is a well-known bug with instantiating with New in some instances. I get the error you mentioned when I use a New in those instances. A good starting point to get a handle is MSDN Index searching for "New vs. CreateObject in components" Another possibility is that you don't have your COM+ application's Transaction property set to Requires. Good luck! Cale Quote: > I am trying to debug my com+ components on win2k and vb6 and am receiving > the above error when calling GetObjectContext.CreateInstance or > GetObjectContext.SetComplete, I know I had to add some registry settings > when working on NT4 & MTS. Do I need to do the same thing for Win2k & COM+? > If so, what are the additions. > There is a knowledge Base article on Microsoft's site but it no longer > available. > Thanks in advance. > Marty
Mon, 13 Oct 2003 12:08:08 GMT

RemoteDebugger.co #3 / 3	Debugging COM+ Componets -- Runtime error 91- Object variable or with block not set Try Team Remote De{filter}, you'll see it's easier and much more healthy this way. :) Check it out & Test-Drive it here: http://www.--.com/ {filter}.com/Team_Remote_De{filter}.asp Team Remote De{filter*} allows you and your team to trace any number of code units of any kind ( ASP, MTS, T-SQL, COM+, ActiveX Exe, DLL, COM, Thread, CFML ), written in any language ( ASP, VB, VC++, Delphi, T-SQL, VJ, CFML ) residing on multiple shared and dedicated servers at the same time, without ever attaching to process! Good luck and take care, Art A. Software Architect Spline Technologies Corp. Quote: > I am trying to debug my com+ components on win2k and vb6 and am receiving > the above error when calling GetObjectContext.CreateInstance or > GetObjectContext.SetComplete, I know I had to add some registry settings > when working on NT4 & MTS. Do I need to do the same thing for Win2k & COM+? > If so, what are the additions. > There is a knowledge Base article on Microsoft's site but it no longer > available. > Thanks in advance. > Marty
Mon, 20 Oct 2003 23:52:42 GMT

Page 1 of 1

[ 3 post ]