locked
Error HRESULT E_FAIL has been returned from a call to COM component RRS feed

  • Question

  • We've recently deployed MIIS and VB to a new server and everything operates fine except for when I try and run my AD_MA to import/export from/to AD.  I get a prompt with the error "Error HRESULT E_FAIL has been returned from a call to COM component".  When i click OK, MIIS shows the error "stopped-server".  My last environment never had this problem.  Does this have something to do with the installation?  The only differences I can think of is that our last environment had SQL Server on the Server and had a full VBStudio whereas our new server has the minimum (see below)  and SQL Server is on a remote server.

     

    Currently on server...

    - Microsoft Visual Basic 2005
    - Microsoft Visual Web Developer 2005
    - Crystal Reports for Visual Studio 2005

     

    Thoughts? 

    Thursday, April 17, 2008 4:22 PM

Answers

  • This actually turned out to be an issue with accidentally pointing MIIS to the Developers edition of SQL Server on a different box.  Since the thread count is so low on the Dev Edition, we kept running into locks and thread issues.

     

    When we pointed it to a Standard Edition of SQL Server on a different box, the errors stopped and the performance was as expected.

    Wednesday, May 7, 2008 2:33 PM

All replies

  • What do you see in the event viewer, related to his error?

    More detail?

     

    Kind regards,

    Peter

    Thursday, April 17, 2008 5:23 PM
  • Thanks for your quick reply, Peter!

     

    The Event Viewer shows two types of errors... (i've received one or the other on the last bunch of runs)

     

    Event ID: 6301

    The server encountered an unexpected error in the synchronization engine:

    "ERR: MMS(5644): sql.cpp(5673): Query (CSession:Surprisepen()) performed with error

    ERR: MMS(5644): sql.cpp(5726): Cannot generate SSPI context

    ERR: MMS(5644): sql.cpp(5734): hrError: 0x80004005, dwMinor: 0

    ERR: MMS(5644): sql.cpp(5889): SQL error: HY000, native: 0

    BAIL: MMS(5644): sql.cpp(497): 0x80004005 (Unspecified error)

    BAIL: MMS(5644): sql.cpp(381): 0x80004005 (Unspecified error)

    BAIL: MMS(5644): sql.cpp(255): 0x80004005 (Unspecified error)

    BAIL: MMS(5644): storeimp.cpp(5247): 0x80004005 (Unspecified error)

    BAIL: MMS(5644): storeimp.cpp(2199): 0x80004005 (Unspecified error)

    BAIL: MMS(5644): mastate.cpp(5667): 0x80004005 (Unspecified error)

    BAIL: MMS(5644): syncprocess.cpp(1758): 0x80004005 (Unspecified error)

    BAIL: MMS(5644): syncprocess.cpp(639): 0x80004005 (Unspecified error)

    ERR: MMS(5644): syncprocess.cpp(820): Retry cs terminated unexpectedly with 0x80004005

    BAIL: MMS(5644): syncprocess.cpp(559): 0x80004005 (Unspecified error)

    BAIL: MMS(5644): syncimport.cpp(393): 0x80004005 (Unspecified error)

     

    Event ID: 6306

    The server encountered an unexpected error while performing an operation for the client.

    "ERR: MMS(5724): sql.cpp(5673): Query (CSession:Surprisepen()) performed with error

    ERR: MMS(5724): sql.cpp(5726): Cannot generate SSPI context

    ERR: MMS(5724): sql.cpp(5734): hrError: 0x80004005, dwMinor: 0

    ERR: MMS(5724): sql.cpp(5889): SQL error: HY000, native: 0

    BAIL: MMS(5724): sql.cpp(497): 0x80004005 (Unspecified error)

    BAIL: MMS(5724): sql.cpp(381): 0x80004005 (Unspecified error)

    BAIL: MMS(5724): sql.cpp(255): 0x80004005 (Unspecified error)

    BAIL: MMS(5724): storeimp.cpp(5247): 0x80004005 (Unspecified error)

    BAIL: MMS(5724): storeimp.cpp(2199): 0x80004005 (Unspecified error)

    BAIL: MMS(5724): server.cpp(3068): 0x80004005 (Unspecified error)

    Thursday, April 17, 2008 6:41 PM
  • Which build of MIIS/ILM are you running?

    What version of .NET Framework?

     

    Kind regards,

    Peter

     

     

    Thursday, April 17, 2008 9:37 PM
  • MIIS: Version 3.2.559.0 (SP2)

    .Net V 2.0.50727 (SP1)

     

    Thanks!

    Friday, April 18, 2008 1:18 PM
  • I'm starting to think that it has to do with the fact that the MIIS database (SQL SERVER) is on a remote box.   Has anyone run into issues with this?

    Friday, April 18, 2008 6:14 PM
  • Yep, you are probably right.

     

    If you look at your error message, it indicates that your system can’t create a SSPI context, which could be an account problem.

     

    You should verify that your service account has sufficient rights to access the database.

     

    Cheers,

    Markus

     

    ///////////////////////////////////////////////////////////////////////
    Markus Vilcinskas

    Technical Writer
    Microsoft Identity Integration Server
    mailto:markvi@microsoft.com.NO_SPAM

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Use of included script samples are subject to the terms specified at
    http://www.microsoft.com/info/copyright.htm
    ///////////////////////////////////////////////////////////////////////

     

     

     

     

    Saturday, April 19, 2008 1:39 PM
    Moderator
  • SSPI failure indicates you have an issue with Kerberos delegation to your SQL Server.  See the following KB for more info on how to troubleshoot:

     

    http://support.microsoft.com/kb/811889

     

    Sunday, April 20, 2008 4:41 AM
  • Thanks for your help, gentlemen.

     

    What rights are sufficient for the MIIS account in SQL Server?  Would owner rights be sufficient?

     

    I'm wondering if this has anything to do with thread counts.  Is there a standard of thread counts per number of transactions of MIIS?

    Monday, April 21, 2008 7:01 PM
  •  

    Also... the reason we seem to be getting these errors is because the MIIS sqlserver database is on a remote server as opposed to its own server.  We never saw these errors when we worked with MIIS and its database on the same server.

     

    I was told that database should be on a different server.  Do you agree with this?  If not, I can just reinstall and create the sqlserver db on the same server and that should be the end of this problem.  If it should be on a different server though, we can still try and forge agead to resolve this issue.

     

    Sincere thanks to everyone for there assistance with this...

    Monday, April 21, 2008 7:19 PM
  • I recommend installing MIIS and SQL on the same box..... You just can't beat the performance..

     

    You can just move the db over to the MIIS box and do a quick reinstall and use the old db...

     

    Just make sure you install sql and give the service account access to the db..

     

    HTH,

     

    Joe

     

    Monday, April 21, 2008 11:23 PM
  • This actually turned out to be an issue with accidentally pointing MIIS to the Developers edition of SQL Server on a different box.  Since the thread count is so low on the Dev Edition, we kept running into locks and thread issues.

     

    When we pointed it to a Standard Edition of SQL Server on a different box, the errors stopped and the performance was as expected.

    Wednesday, May 7, 2008 2:33 PM
  •  

    One thing I forgot to mentions was the use of Network Protocol for SQL.

     

    Most likely you were using TCP/IP...

     

    If you have a remote sql box that is very very close to the ILM box, you can also use Named Pipes...

     

    On very fast networks Name Pipes will help out with performance even on a remote box....

     

    TCP/IP is usually better on slower networks.. When the sql box is far away from the ILM box..

     

    On a local ILM box with SQL installed, I always switch to named pipes as it is much faster and ILM tends to use TCP/IP by default..

     

    HTH,

     

    Joe

    Wednesday, May 7, 2008 2:47 PM
  • I keep Getting this too, with this in the details section..

    ************** Exception Text **************
    System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
       at ShockwaveFlashObjects.xf4f48afd04628564.GetVariable(String name)
       at AxShockwaveFlashObjects.x2799bb92170ccc89.GetVariable(String name)
       at AQ_Elite.xaa4f033827d75b4d.x13d55d1f3018b5bd(Object xe0292b9ed559da7d, EventArgs xfbf34718e704c6bc)
       at System.Windows.Forms.Timer.OnTick(EventArgs e)
       at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    How can i fix this? Thanks.

    Monday, September 5, 2011 6:55 AM