Expression > Forums Home > Feedback and Discussions Forums > Off-Topic Posts (Do Not Post Here) > Creating an instance of the COM component with CLSID Error
Ask a questionAsk a question
 

AnswerCreating an instance of the COM component with CLSID Error

  • Tuesday, June 02, 2009 1:30 AMKalentalis Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

       I am trying to develop a module in Neverwinter Nights 2.  I am running Windows 7 RC with DirectX 11.  Originally I had a problem with the Terrain Menu.  It was displayed improperly ( the text was garbled by overlapping ).  I found the solution was to open the properties window of NWN2ToolsetLauncher file and select "Disable visual themes".  After doing so, the Terrain Menus displayed properly, but I can no longer open or save modules and get above mentioned error.  Can anyone help resolve and report this so it can either be fixed or easier to find for others with this problem?  Below you will see the full details if it helps anyone.

    Thanks.
    Kalentalis

    Unhandled exception has occurred in your application.  If you click Continue, the application will ignore this error and attempt to continue.  If you click Quit, the application will close immediately.

     

    Creating an instance of the COM component with CLSID {C0B4E2F3-BA21-4773-IDBA-335EC946E88I} from the iClass Factory failed due to the following error: 80040111.

     

     

    See the end of this message for details on invoking

    just-in-time (JIT) debugging instead of this dialog box.

     

    ************** Exception Text **************

    System.Runtime.InteropServices.COMException (0x80040111): Creating an instance of the COM component with CLSID {C0B4E2F3-BA21-4773-8DBA-335EC946EB8B} from the IClassFactory failed due to the following error: 80040111.

       at System.Windows.Forms.SaveFileDialog.CreateVistaDialog()

       at System.Windows.Forms.FileDialog.RunDialogVista(IntPtr hWndOwner)

       at System.Windows.Forms.FileDialog.RunDialog(IntPtr hWndOwner)

       at System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner)

       at System.Windows.Forms.CommonDialog.ShowDialog()

       at NWN2Toolset.NWN2ToolsetMainForm.()

       at NWN2Toolset.NWN2ToolsetMainForm.(Object , EventArgs )

       at TD.SandBar.ToolbarItemBase.OnActivate()

       at TD.SandBar.ButtonItemBase.OnActivate()

       at TD.SandBar.

    .(TopLevelMenuItemBase , Boolean , Boolean , Point )

       at TD.SandBar.TopLevelMenuItemBase.Show(Boolean select)

       at TD.SandBar.TopLevelMenuItemBase.Show()

       at TD.SandBar.ToolBar.OnItemPush(ToolbarItemBase item, Point position)

       at TD.SandBar.ToolBar.OnMouseDown(MouseEventArgs e)

       at TD.SandBar.MenuBar.OnMouseDown(MouseEventArgs e)

       at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)

       at System.Windows.Forms.Control.WndProc(Message& m)

       at TD.SandBar.ToolBar.WndProc(Message& m)

       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

     

     

    ************** Loaded Assemblies **************


    It goes on to with a list of the loaded assemblies which is too long for this form, but I hope this is enough info, if not, I can add the rest of the information.

    • Moved bynobugzMVPTuesday, June 02, 2009 1:35 AMbeta software, use connect.microsoft.com (From:64-Bit .NET Framework Development.)
    •  

Answers

All Replies