Entrar
 
HomeBibliotecaWikiAprenderGaleriaDownloadsSuporte ComunidadeFóruns
Recursos para Profissionais de TI >
> 
> 
OleDB: Results Error

Answered OleDB: Results Error

  • sexta-feira, 13 de novembro de 2009 19:53
     
     
    Entrar para Votar
    0

    The server that we have running SCE 2010 Beta is showing a Critical error in the management console.  The error states “OleDB: Results Error”.  Below is the detail from the alert description:

    --------------
    OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error

    : Cannot open database "OperationsManagerDW" requested by the login. The login failed.

    Workflow name: Microsoft.Windows.Client.Vista.ComputerGroup.ShellPerfTrends

    Instance name: Microsoft System Center Data Warehouse

    Instance ID: {16781F33-F72D-033C-1DF4-65A2AFF32CA3}

    Management group: SVSCEB_MG

    -------------

    How do we resolve this issue?

     

    Thank you,

    David

     

Todas as Respostas

  • terça-feira, 17 de novembro de 2009 07:20
    Moderador
     
     
    Entrar para Votar
    0
    Hello David,

    The failure 0x80004005 usually indicates access denied problem. What kind of database are you using? A built-in SQL 2008 Express or a pre-installed SQL 2008 Standard on a remote server?

    Did you modify the SQL Server before the error occured? Did you refresh the run as account on SCE 2010 Beta to access that DB?

    Please also check if any error message was logged in the EventLog on the SCE server.

    Thanks,
    Yog Li - MSFT
     
  • terça-feira, 17 de novembro de 2009 19:46
     
     
    Entrar para Votar
    0
    Hello Yog Li,
    We are using the SQL 2008 Express Edition that was installed by the SCE 2010 Beta install.  The SQL Server was installed on the same server as SCE, which is a virtual server.  We have not modified the SQL Server at all.
    I looked through the event log on the SCE server and found an entry that may be related, but I am not certain.  The error is listed below:

    Report Server (ESSENTIALS) cannot load the XML extension.
    Log Name: Application
    Source: Report Server (ESSENTIALS)
    Event ID: 108
    Task Category: Extension
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: svsceb.shs.loc


    If you need more info, please let me know.
    Thank you!
    David
     
  • quarta-feira, 2 de dezembro de 2009 15:20
    Moderador
     
     
    Entrar para Votar
    0
    Hello David,

    Are you able to open the Report Manager website,.

    To check that, Open Reporting Service Configuration Manager and Report Manager Url. 

    You will find the Report Manager URL there.

    see if you are able to open the report server manager web site.

    Email me the screen shot of the Report Manager website to scedata@microsoft.com

    I am interested to see if any errors found.

    Thanks
    Ranjith A
    SCE 2010 TAP Support.






     
     
  • quinta-feira, 3 de dezembro de 2009 21:01
     
     
    Entrar para Votar
    0

    Hi Ranjith,

    I sent a screen clip of the Report Manager website to the email address you provided.  The error message has not happened again, just the one time.

    Please let me know if you would like any other information.


    Thank you!
    David

     
  • sexta-feira, 4 de dezembro de 2009 20:33
     
     
    Entrar para Votar
    0

    Greetings all,
    I just noticed another error.  Below are the "Alert Description" and the "Alter Contents" from the Alter Properties page:

    Alter Description:
    OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error
    : Login timeout expired


    Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor

    Instance name: svsceb.shs.loc

    Instance ID: {F2F7B4F2-FFB6-9107-36EF-A53B461B4B02}

    Management group: SVSCEB_MG


    Alert Context:
    Date and Time: 12/2/2009 11:44:34 AM
    Log Name: Operations Manager
    Source: Health Service Modules
    Event Number: 11852
    Level: 2
    Logging Computer: svsceb.shs.loc
    User: N/A
     Description:
    OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error : Login timeout expired Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor Instance name: svsceb.shs.loc Instance ID: {F2F7B4F2-FFB6-9107-36EF-A53B461B4B02} Management group: SVSCEB_MG 
     

    Event Data:

    < DataItem type =" System.XmlData " time =" 2009-12-02T11:44:41.9950322-08:00 " sourceHealthServiceId =" F2F7B4F2-FFB6-9107-36EF-A53B461B4B02 " >
    < EventData >
      < Data > SVSCEB_MG </ Data >
      < Data > Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor </ Data >
      < Data > svsceb.shs.loc </ Data >
      < Data > {F2F7B4F2-FFB6-9107-36EF-A53B461B4B02} </ Data >
      < Data > Login timeout expired </ Data >
      < Data > 0x80004005 </ Data >
      < Data > Unspecified error </ Data >
      </ EventData >
      </ DataItem >

    Please let me know if you would like any other information.

    Thank you,
    David

     
  • sexta-feira, 5 de fevereiro de 2010 17:06
     
     
    Entrar para Votar
    0

    Hi Ranjith,

    We upgraded to RC on Tuesday and I noticed when I came in this morning that we have received another OleDB: Results Error message Tuesday afternoon.    The Alert Description reads:


    OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error
    : Login timeout expired


    Workflow name: Microsoft.SystemCenter.CM.AEM.Internal.SystemBucketMachineCountPerfCollection

    Instance name: \\SVSCEB.shs.loc\errordata

    Instance ID: {F4693FB7-67E5-42BB-FEAF-C2C4B8E6E208}

    Management group: SVSCEB_MG



    I am wondering if there is a permissions issue.
    Is there anything else I can provide to help diagnose this error?

    Thank you,
    David

     
  • segunda-feira, 1 de março de 2010 23:07
     
     Respondido
    Entrar para Votar
    0
    Hi David,

    Based on some initial testing, it looks like this issue will be resolved with an updated Management Pack. We haven't finished our testing yet, but I'll send you an e-mail with some additional information.

    Thanks

    Richard
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
  • terça-feira, 6 de abril de 2010 20:10
     
     
    Entrar para Votar
    0

    I'm seeing the same error on a fresh install of SCOM 2007 R2 with a separate SQL install on another server. I get it on both my RMS and MS servers

     

    OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error : Login timeout expired Workflow name: Microsoft.SystemCenter.CM.AEM.Internal.SystemBucketMachineCountPerfCollection Instance name: \\servername\ErrorData Instance ID: {C4E5FAC9-D85F-E3BF-0AEB-0B682BB4D1D4} Management group: ORG

     
  • sexta-feira, 30 de abril de 2010 16:04
     
     
    Entrar para Votar
    0
    And info on this?  I liek the app but these goofy errors are confusing.... having same issue only on teh console server too!
     
  • sexta-feira, 30 de abril de 2010 20:33
     
     
    Entrar para Votar
    0

    For the AEM error and issues with using Management Packs on Operations Manager 2007, please post to the Management Pack forum.

    Thanks

    Richard 

    This posting is provided "AS IS" with no warranties, and confers no rights.
     
  • quarta-feira, 19 de janeiro de 2011 17:39
     
     
    Entrar para Votar
    0
    I am getting this error now and it is January of 2011 so it doesn't seem it was fixed by an updated Management Pack?  What Management Pack would the fix have been in? 
     
  • terça-feira, 22 de fevereiro de 2011 07:00
     
     
    Entrar para Votar
    0

    I also still get that error. I'm running SCE 2010 and DPM 2010 and SQL on the same server, but can't imagine this to be the problem.

    I also get another OleDB: Results Error :

    OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error
    : Login timeout expired


    Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor

    Any news on these??

     

     
  • sexta-feira, 25 de março de 2011 09:57
     
     
    Entrar para Votar
    0
    Somebody got a solution yet? Get a similiar error...
     
  • quinta-feira, 10 de maio de 2012 09:14
     
     
    Entrar para Votar
    0

    I also have this problem and I think that is why I can not perform automatic discovery of computers in my domain and also advanced discovery. Smells like network issue but I do not have a clue what is happening. I have remote SQL Server 2008 SP3 for SCE database and reporting.

    OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error
    : Login timeout expired

    Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor
    Instance name: SCE.credy.com
    Instance ID: {84062819-BE11-4332-A86F-ADA8B65B0E76}
    Management group: SCE_MG
     
  • quinta-feira, 11 de abril de 2013 05:50
     
      Contém Código
    Entrar para Votar
    0

    Hello all,

    I realise that this is an old thread, but I haven't found another poster with the exact same error message as we have, like BoxiKG has reported above ^

    In my case we are running SCOM 2007 R2 which connects to an SQL named instance on a virtual server. This problem only started happening in the last few weeks. No changes have been made to either the SQL server or ops manager around the time the errors started appearing.

    They are also very sporadic in their alert times. Sometimes during server backups, sometimes randomly at 7am on a Sunday morning (when nothing is happening)

    I see no corresponding SQL logs to back up any access issues for ops manager to the SQL server.

    Here is the error:

    OleDb Module encountered a failure 0x80004005 during execution and will post it 
as output data item. Unspecified error
    : Login timeout 
expired


    Workflow name: 
Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor

    Instance name: 
scom-<rest removed for privacy>

    Instance ID: 
{BBB2AF43-BE9D-1BF4-9208-1F9B7A5BCADA}

    Management group: <removed for privacy>