Community discussion forum

Runtime Error-429 ActiveX Component can't create Object". for COM+ Component on Windows2003

• • Reply

  8 months ago

  by Phemphel

  Oufemi Hunjenukon

  , Nigeria

  Joined 10 months ago
  Hi There!
  
  Could anybody please help regarding the below issue.
  
  We had a COM+ component deployed on Windows 2000/NT machine it was working fine, I mean when it was being invoked from other machines it was creating object and was serving the purpose.
  
  Recently as an upgrade we moved all the COM+ component from Windows 2000/NT to WINDOWS 2003 and now when we are trying to invoke that component its throwing "Runtime Error-429 ActiveX Component can't create Object".
  
  Client side machines are running Windows XP with SP2, COM+ component was created as a server application. I doubt that it may be because of Windows 2003 security issue but not sure or am I missing something while building that component.
  
  Please help or provide your suggestions.
  
  Thanks in advance.

   

  Additional Information:

  We have created an application proxy on new server (i.e., Windows2003) and then we did a Export (At Component Services->Com Components->right clicking on our component) to get the .MSI and .CAB file.
  
  These .MSI we installed on the client machine. (Since this is an application proxy, so client will invoke the component on server in this case Windows 2003 server)
  
  When the application is started at login screen itself it is throwing the above error. (Login checking is also happening in a class which is in COM+ component)
  

   
  Report abuse
• Advertisement

  Simply the fastest line-level profiler for .NET ever

  “The low overhead means it has minimal impact on the execution of my program”
  Mark Everest, Development Team Leader, Renault F1 Team Ltd.

  Try out the new ANTS Profiler 4 for yourself. Download your 14-day trial now

• • Reply

  7 months ago

  by Jangac

  Charl Janga

  , Netherlands

  Joined 9 months ago

  I have experienced exactly the same problem moving my COM+ server application from Windows 2000 to Windows XP.  The only hint I have found so far relates to the fact that XP has much tighter security than 2000.  Try setting the security level on the server object to allow unrestricted access.  That may help.

  Tony 

  Report abuse