After installing SP1, we keep getting this error on our RMS. Anyone seen this on their enviornment or know how to fix it? Thanks. Last modified by: System Alert: OleDB: Results Error Source: RMS.xyz.com Path: RMS.xyz.com Last modified time: 7/3/2008 8:57:28 AM Alert description: OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor Instance name: RMS.xyz.com Instance ID: {E8D68465-E771-F04E-2A13-72CB8D0B60B1} Management group: ABC
Is SQL Broker enabled? This query should tell you: select is_broker_enabled from sys.databases where name = 'operationsmanager' If its not (value =0), then enable it: ALTER DATABASE operationsmanager SET ENABLE_BROKER Stop the 3 services on the RMS while setting broker. We added a monitor in SP1 to verify broker is enabled (broker is required for receiving task status). Lenny Wile ------------------------- 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/cpyright.htm "opsmgr" wrote in message news:C805CFB6-7E38-4643-A39F-36D75932A70A@microsoft.com... > After installing SP1, we keep getting this error on our RMS. Anyone seen > this > on their enviornment or know how to fix it? Thanks. > > Last modified by: System > Alert: OleDB: Results Error > Source: RMS.xyz.com > Path: RMS.xyz.com > Last modified time: 7/3/2008 8:57:28 AM > Alert description: OleDb Module encountered a failure 0x80004005 during > execution and will post it as output data item. Unspecified error > > Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor > Instance name: RMS.xyz.com > Instance ID: {E8D68465-E771-F04E-2A13-72CB8D0B60B1} > Management group: ABC >
Hi Lenny, Thank you for your reply. Yes it is enabled. I re ran the query again just to make sure and the result is 1. Any idea? Thanks. "Lenny Wile [MSFT]" wrote: > Is SQL Broker enabled? > > This query should tell you: > > select is_broker_enabled from sys.databases where name = 'operationsmanager' > > If its not (value =0), then enable it: > > ALTER DATABASE operationsmanager SET ENABLE_BROKER > > Stop the 3 services on the RMS while setting broker. > > We added a monitor in SP1 to verify broker is enabled (broker is required > for receiving task status). > > > Lenny Wile > > > ------------------------- > 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/cpyright.htm > > > "opsmgr" wrote in message > news:C805CFB6-7E38-4643-A39F-36D75932A70A@microsoft.com... > > After installing SP1, we keep getting this error on our RMS. Anyone seen > > this > > on their enviornment or know how to fix it? Thanks. > > > > Last modified by: System > > Alert: OleDB: Results Error > > Source: RMS.xyz.com > > Path: RMS.xyz.com > > Last modified time: 7/3/2008 8:57:28 AM > > Alert description: OleDb Module encountered a failure 0x80004005 during > > execution and will post it as output data item. Unspecified error > > > > Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor > > Instance name: RMS.xyz.com > > Instance ID: {E8D68465-E771-F04E-2A13-72CB8D0B60B1} > > Management group: ABC > > > > >
You may want to capture VER etl tracing from the Health Service during the failure to see if we capture the complete error - i.e. the description that goes with the 0x80004005 error. Other than that, if SQL is on a separate server from the Root HS, you could capture a Netmon trace to capture the error. Lenny Wile ------------------------- 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/cpyright.htm "opsmgr" wrote in message news:9951DC20-D170-4651-B7CE-64699035BABB@microsoft.com... > Hi Lenny, > > Thank you for your reply. Yes it is enabled. I re ran the query again just > to make sure and the result is 1. Any idea? Thanks. > > "Lenny Wile [MSFT]" wrote: > >> Is SQL Broker enabled? >> >> This query should tell you: >> >> select is_broker_enabled from sys.databases where name = >> 'operationsmanager' >> >> If its not (value =0), then enable it: >> >> ALTER DATABASE operationsmanager SET ENABLE_BROKER >> >> Stop the 3 services on the RMS while setting broker. >> >> We added a monitor in SP1 to verify broker is enabled (broker is required >> for receiving task status). >> >> >> Lenny Wile >> >> >> ------------------------- >> 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/cpyright.htm >> >> >> "opsmgr" wrote in message >> news:C805CFB6-7E38-4643-A39F-36D75932A70A@microsoft.com... >> > After installing SP1, we keep getting this error on our RMS. Anyone >> > seen >> > this >> > on their enviornment or know how to fix it? Thanks. >> > >> > Last modified by: System >> > Alert: OleDB: Results Error >> > Source: RMS.xyz.com >> > Path: RMS.xyz.com >> > Last modified time: 7/3/2008 8:57:28 AM >> > Alert description: OleDb Module encountered a failure 0x80004005 during >> > execution and will post it as output data item. Unspecified error >> > >> > Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor >> > Instance name: RMS.xyz.com >> > Instance ID: {E8D68465-E771-F04E-2A13-72CB8D0B60B1} >> > Management group: ABC >> > >> >> >>
We get the same error every few days. The broker is enable value 1. The SQL DB runs on a seperate SQL2005 SP2 server but on the same switch so there should not be any networking issues. Also the SQL server is a huge server 8 Quad Cores 64 GB RAM etc etc so it should not be a performance related issue. The RMS is running SP1 and I have only seen this error since the upgrade. OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor Instance name: server.root.local Instance ID: {9BCD0474-327C-70F4-B3AE-2D6692BC64E9} Management group: NoName "Lenny Wile [MSFT]" wrote: > You may want to capture VER etl tracing from the Health Service during the > failure to see if we capture the complete error - i.e. the description that > goes with the 0x80004005 error. > > Other than that, if SQL is on a separate server from the Root HS, you could > capture a Netmon trace to capture the error. > > Lenny Wile > > > ------------------------- > 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/cpyright.htm > > "opsmgr" wrote in message > news:9951DC20-D170-4651-B7CE-64699035BABB@microsoft.com... > > Hi Lenny, > > > > Thank you for your reply. Yes it is enabled. I re ran the query again just > > to make sure and the result is 1. Any idea? Thanks. > > > > "Lenny Wile [MSFT]" wrote: > > > >> Is SQL Broker enabled? > >> > >> This query should tell you: > >> > >> select is_broker_enabled from sys.databases where name = > >> 'operationsmanager' > >> > >> If its not (value =0), then enable it: > >> > >> ALTER DATABASE operationsmanager SET ENABLE_BROKER > >> > >> Stop the 3 services on the RMS while setting broker. > >> > >> We added a monitor in SP1 to verify broker is enabled (broker is required > >> for receiving task status). > >> > >> > >> Lenny Wile > >> > >> > >> ------------------------- > >> 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/cpyright.htm > >> > >> > >> "opsmgr" wrote in message > >> news:C805CFB6-7E38-4643-A39F-36D75932A70A@microsoft.com... > >> > After installing SP1, we keep getting this error on our RMS. Anyone > >> > seen > >> > this > >> > on their enviornment or know how to fix it? Thanks. > >> > > >> > Last modified by: System > >> > Alert: OleDB: Results Error > >> > Source: RMS.xyz.com > >> > Path: RMS.xyz.com > >> > Last modified time: 7/3/2008 8:57:28 AM > >> > Alert description: OleDb Module encountered a failure 0x80004005 during > >> > execution and will post it as output data item. Unspecified error > >> > > >> > Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor > >> > Instance name: RMS.xyz.com > >> > Instance ID: {E8D68465-E771-F04E-2A13-72CB8D0B60B1} > >> > Management group: ABC > >> > > >> > >> > >> > > >
Can you correlate these errors to anything else... such as a cluster failover... or a restart of SQL or a restart of the RMS opsmgr services? "Jon Garrett" wrote in message news:793310D1-BED3-4548-8458-0B26FD168A43@microsoft.com... > We get the same error every few days. The broker is enable value 1. > > The SQL DB runs on a seperate SQL2005 SP2 server but on the same switch so > there should not be any networking issues. > > Also the SQL server is a huge server 8 Quad Cores 64 GB RAM etc etc so it > should not be a performance related issue. > > The RMS is running SP1 and I have only seen this error since the upgrade. > > OleDb Module encountered a failure 0x80004005 during execution and will > post > it as output data item. Unspecified error Workflow name: > Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor Instance name: > server.root.local Instance ID: {9BCD0474-327C-70F4-B3AE-2D6692BC64E9} > Management group: NoName > > "Lenny Wile [MSFT]" wrote: > >> You may want to capture VER etl tracing from the Health Service during >> the >> failure to see if we capture the complete error - i.e. the description >> that >> goes with the 0x80004005 error. >> >> Other than that, if SQL is on a separate server from the Root HS, you >> could >> capture a Netmon trace to capture the error. >> >> Lenny Wile >> >> >> ------------------------- >> 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/cpyright.htm >> >> "opsmgr" wrote in message >> news:9951DC20-D170-4651-B7CE-64699035BABB@microsoft.com... >> > Hi Lenny, >> > >> > Thank you for your reply. Yes it is enabled. I re ran the query again >> > just >> > to make sure and the result is 1. Any idea? Thanks. >> > >> > "Lenny Wile [MSFT]" wrote: >> > >> >> Is SQL Broker enabled? >> >> >> >> This query should tell you: >> >> >> >> select is_broker_enabled from sys.databases where name = >> >> 'operationsmanager' >> >> >> >> If its not (value =0), then enable it: >> >> >> >> ALTER DATABASE operationsmanager SET ENABLE_BROKER >> >> >> >> Stop the 3 services on the RMS while setting broker. >> >> >> >> We added a monitor in SP1 to verify broker is enabled (broker is >> >> required >> >> for receiving task status). >> >> >> >> >> >> Lenny Wile >> >> >> >> >> >> ------------------------- >> >> 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/cpyright.htm >> >> >> >> >> >> "opsmgr" wrote in message >> >> news:C805CFB6-7E38-4643-A39F-36D75932A70A@microsoft.com... >> >> > After installing SP1, we keep getting this error on our RMS. Anyone >> >> > seen >> >> > this >> >> > on their enviornment or know how to fix it? Thanks. >> >> > >> >> > Last modified by: System >> >> > Alert: OleDB: Results Error >> >> > Source: RMS.xyz.com >> >> > Path: RMS.xyz.com >> >> > Last modified time: 7/3/2008 8:57:28 AM >> >> > Alert description: OleDb Module encountered a failure 0x80004005 >> >> > during >> >> > execution and will post it as output data item. Unspecified error >> >> > >> >> > Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor >> >> > Instance name: RMS.xyz.com >> >> > Instance ID: {E8D68465-E771-F04E-2A13-72CB8D0B60B1} >> >> > Management group: ABC >> >> > >> >> >> >> >> >> >> >> >>
The other time I have seen this is when rebooting domain controllers, that the RMS was using for authentication. "Kevin Holman" wrote in message news:eJlMa4c4IHA.3480@TK2MSFTNGP03.phx.gbl... > Can you correlate these errors to anything else... such as a cluster > failover... or a restart of SQL or a restart of the RMS opsmgr services? > > > "Jon Garrett" wrote in message > news:793310D1-BED3-4548-8458-0B26FD168A43@microsoft.com... >> We get the same error every few days. The broker is enable value 1. >> >> The SQL DB runs on a seperate SQL2005 SP2 server but on the same switch >> so >> there should not be any networking issues. >> >> Also the SQL server is a huge server 8 Quad Cores 64 GB RAM etc etc so it >> should not be a performance related issue. >> >> The RMS is running SP1 and I have only seen this error since the upgrade. >> >> OleDb Module encountered a failure 0x80004005 during execution and will >> post >> it as output data item. Unspecified error Workflow name: >> Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor Instance name: >> server.root.local Instance ID: {9BCD0474-327C-70F4-B3AE-2D6692BC64E9} >> Management group: NoName >> >> "Lenny Wile [MSFT]" wrote: >> >>> You may want to capture VER etl tracing from the Health Service during >>> the >>> failure to see if we capture the complete error - i.e. the description >>> that >>> goes with the 0x80004005 error. >>> >>> Other than that, if SQL is on a separate server from the Root HS, you >>> could >>> capture a Netmon trace to capture the error. >>> >>> Lenny Wile >>> >>> >>> ------------------------- >>> 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/cpyright.htm >>> >>> "opsmgr" wrote in message >>> news:9951DC20-D170-4651-B7CE-64699035BABB@microsoft.com... >>> > Hi Lenny, >>> > >>> > Thank you for your reply. Yes it is enabled. I re ran the query again >>> > just >>> > to make sure and the result is 1. Any idea? Thanks. >>> > >>> > "Lenny Wile [MSFT]" wrote: >>> > >>> >> Is SQL Broker enabled? >>> >> >>> >> This query should tell you: >>> >> >>> >> select is_broker_enabled from sys.databases where name = >>> >> 'operationsmanager' >>> >> >>> >> If its not (value =0), then enable it: >>> >> >>> >> ALTER DATABASE operationsmanager SET ENABLE_BROKER >>> >> >>> >> Stop the 3 services on the RMS while setting broker. >>> >> >>> >> We added a monitor in SP1 to verify broker is enabled (broker is >>> >> required >>> >> for receiving task status). >>> >> >>> >> >>> >> Lenny Wile >>> >> >>> >> >>> >> ------------------------- >>> >> 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/cpyright.htm >>> >> >>> >> >>> >> "opsmgr" wrote in message >>> >> news:C805CFB6-7E38-4643-A39F-36D75932A70A@microsoft.com... >>> >> > After installing SP1, we keep getting this error on our RMS. Anyone >>> >> > seen >>> >> > this >>> >> > on their enviornment or know how to fix it? Thanks. >>> >> > >>> >> > Last modified by: System >>> >> > Alert: OleDB: Results Error >>> >> > Source: RMS.xyz.com >>> >> > Path: RMS.xyz.com >>> >> > Last modified time: 7/3/2008 8:57:28 AM >>> >> > Alert description: OleDb Module encountered a failure 0x80004005 >>> >> > during >>> >> > execution and will post it as output data item. Unspecified error >>> >> > >>> >> > Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor >>> >> > Instance name: RMS.xyz.com >>> >> > Instance ID: {E8D68465-E771-F04E-2A13-72CB8D0B60B1} >>> >> > Management group: ABC >>> >> > >>> >> >>> >> >>> >> >>> >>> >>> >
Happened again last night at about 18:15 which is probably one of the quieter times on the network. No failover was happening and the DC's were up! Its just a random error. "Kevin Holman" wrote: > The other time I have seen this is when rebooting domain controllers, that > the RMS was using for authentication. > > > "Kevin Holman" wrote in message > news:eJlMa4c4IHA.3480@TK2MSFTNGP03.phx.gbl... > > Can you correlate these errors to anything else... such as a cluster > > failover... or a restart of SQL or a restart of the RMS opsmgr services? > > > > > > "Jon Garrett" wrote in message > > news:793310D1-BED3-4548-8458-0B26FD168A43@microsoft.com... > >> We get the same error every few days. The broker is enable value 1. > >> > >> The SQL DB runs on a seperate SQL2005 SP2 server but on the same switch > >> so > >> there should not be any networking issues. > >> > >> Also the SQL server is a huge server 8 Quad Cores 64 GB RAM etc etc so it > >> should not be a performance related issue. > >> > >> The RMS is running SP1 and I have only seen this error since the upgrade. > >> > >> OleDb Module encountered a failure 0x80004005 during execution and will > >> post > >> it as output data item. Unspecified error Workflow name: > >> Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor Instance name: > >> server.root.local Instance ID: {9BCD0474-327C-70F4-B3AE-2D6692BC64E9} > >> Management group: NoName > >> > >> "Lenny Wile [MSFT]" wrote: > >> > >>> You may want to capture VER etl tracing from the Health Service during > >>> the > >>> failure to see if we capture the complete error - i.e. the description > >>> that > >>> goes with the 0x80004005 error. > >>> > >>> Other than that, if SQL is on a separate server from the Root HS, you > >>> could > >>> capture a Netmon trace to capture the error. > >>> > >>> Lenny Wile > >>> > >>> > >>> ------------------------- > >>> 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/cpyright.htm > >>> > >>> "opsmgr" wrote in message > >>> news:9951DC20-D170-4651-B7CE-64699035BABB@microsoft.com... > >>> > Hi Lenny, > >>> > > >>> > Thank you for your reply. Yes it is enabled. I re ran the query again > >>> > just > >>> > to make sure and the result is 1. Any idea? Thanks. > >>> > > >>> > "Lenny Wile [MSFT]" wrote: > >>> > > >>> >> Is SQL Broker enabled? > >>> >> > >>> >> This query should tell you: > >>> >> > >>> >> select is_broker_enabled from sys.databases where name = > >>> >> 'operationsmanager' > >>> >> > >>> >> If its not (value =0), then enable it: > >>> >> > >>> >> ALTER DATABASE operationsmanager SET ENABLE_BROKER > >>> >> > >>> >> Stop the 3 services on the RMS while setting broker. > >>> >> > >>> >> We added a monitor in SP1 to verify broker is enabled (broker is > >>> >> required > >>> >> for receiving task status). > >>> >> > >>> >> > >>> >> Lenny Wile > >>> >> > >>> >> > >>> >> ------------------------- > >>> >> 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/cpyright.htm > >>> >> > >>> >> > >>> >> "opsmgr" wrote in message > >>> >> news:C805CFB6-7E38-4643-A39F-36D75932A70A@microsoft.com... > >>> >> > After installing SP1, we keep getting this error on our RMS. Anyone > >>> >> > seen > >>> >> > this > >>> >> > on their enviornment or know how to fix it? Thanks. > >>> >> > > >>> >> > Last modified by: System > >>> >> > Alert: OleDB: Results Error > >>> >> > Source: RMS.xyz.com > >>> >> > Path: RMS.xyz.com > >>> >> > Last modified time: 7/3/2008 8:57:28 AM > >>> >> > Alert description: OleDb Module encountered a failure 0x80004005 > >>> >> > during > >>> >> > execution and will post it as output data item. Unspecified error > >>> >> > > >>> >> > Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor > >>> >> > Instance name: RMS.xyz.com > >>> >> > Instance ID: {E8D68465-E771-F04E-2A13-72CB8D0B60B1} > >>> >> > Management group: ABC > >>> >> > > >>> >> > >>> >> > >>> >> > >>> > >>> > >>> > > > >
I receive the same error. Has anyone figured out a workaround or a fix to this error? "Kevin N. Andersen" wrote: > Exactly the same issue here. Most recent alert was half an hour ago and our > SCOM environment no failovers or anything out of the ordinary was happening. > > -- > Best regards / Venlig hilsen > > Kevin N. Andersen > Windows System Administrator > > "Maekee ." wrote in message news:2008718114039micke_is@hotmail.com... > > Hi, > > I also get this problem, exactly the same message. Have SP1, and our SQL > > Server is 2005 SP2. > > In 30 days this problem has a repeat count of 92. Our Cluster have not > > failed over including restarts of domaincontrollers in that period of > > time. > > > > This problem is reported on Microsofts Feedback page connect.microsoft.com > > with ID 336727. > > > > The case is reported as closed, there is good information about this > > problem on the site. Check it out > > > > Anyone found a solution? > > > > /Maekee > >
I've got exactly the same error....no change in our infrastructure, everything is like usual. Anyone find how to fix this issue ? "kc" wrote: > I receive the same error. Has anyone figured out a workaround or a fix to > this error? > > > "Kevin N. Andersen" wrote: > > > Exactly the same issue here. Most recent alert was half an hour ago and our > > SCOM environment no failovers or anything out of the ordinary was happening. > > > > -- > > Best regards / Venlig hilsen > > > > Kevin N. Andersen > > Windows System Administrator > > > > "Maekee ." wrote in message news:2008718114039micke_is@hotmail.com... > > > Hi, > > > I also get this problem, exactly the same message. Have SP1, and our SQL > > > Server is 2005 SP2. > > > In 30 days this problem has a repeat count of 92. Our Cluster have not > > > failed over including restarts of domaincontrollers in that period of > > > time. > > > > > > This problem is reported on Microsofts Feedback page connect.microsoft.com > > > with ID 336727. > > > > > > The case is reported as closed, there is good information about this > > > problem on the site. Check it out > > > > > > Anyone found a solution? > > > > > > /Maekee > > > >
same error here too.... "Christopher Keyaert" wrote: > I've got exactly the same error....no change in our infrastructure, > everything is like usual. > > Anyone find how to fix this issue ? > > "kc" wrote: > > > I receive the same error. Has anyone figured out a workaround or a fix to > > this error? > > > > > > "Kevin N. Andersen" wrote: > > > > > Exactly the same issue here. Most recent alert was half an hour ago and our > > > SCOM environment no failovers or anything out of the ordinary was happening. > > > > > > -- > > > Best regards / Venlig hilsen > > > > > > Kevin N. Andersen > > > Windows System Administrator > > > > > > "Maekee ." wrote in message news:2008718114039micke_is@hotmail.com... > > > > Hi, > > > > I also get this problem, exactly the same message. Have SP1, and our SQL > > > > Server is 2005 SP2. > > > > In 30 days this problem has a repeat count of 92. Our Cluster have not > > > > failed over including restarts of domaincontrollers in that period of > > > > time. > > > > > > > > This problem is reported on Microsofts Feedback page connect.microsoft.com > > > > with ID 336727. > > > > > > > > The case is reported as closed, there is good information about this > > > > problem on the site. Check it out > > > > > > > > Anyone found a solution? > > > > > > > > /Maekee > > > > > >
I've open a Call to Microsoft Premier Support. I'll keep you if they find a solution. "Andrew" wrote: > same error here too.... > > "Christopher Keyaert" wrote: > > > I've got exactly the same error....no change in our infrastructure, > > everything is like usual. > > > > Anyone find how to fix this issue ? > > > > "kc" wrote: > > > > > I receive the same error. Has anyone figured out a workaround or a fix to > > > this error? > > > > > > > > > "Kevin N. Andersen" wrote: > > > > > > > Exactly the same issue here. Most recent alert was half an hour ago and our > > > > SCOM environment no failovers or anything out of the ordinary was happening. > > > > > > > > -- > > > > Best regards / Venlig hilsen > > > > > > > > Kevin N. Andersen > > > > Windows System Administrator > > > > > > > > "Maekee ." wrote in message news:2008718114039micke_is@hotmail.com... > > > > > Hi, > > > > > I also get this problem, exactly the same message. Have SP1, and our SQL > > > > > Server is 2005 SP2. > > > > > In 30 days this problem has a repeat count of 92. Our Cluster have not > > > > > failed over including restarts of domaincontrollers in that period of > > > > > time. > > > > > > > > > > This problem is reported on Microsofts Feedback page connect.microsoft.com > > > > > with ID 336727. > > > > > > > > > > The case is reported as closed, there is good information about this > > > > > problem on the site. Check it out > > > > > > > > > > Anyone found a solution? > > > > > > > > > > /Maekee > > > > > > > >
I've also create a bug report at Microsoft Connect https://connect.microsoft.com/OpsMgrFeedback/feedback/ViewFeedback.aspx?FeedbackID=371221 "Christopher Keyaert" wrote: > I've open a Call to Microsoft Premier Support. > I'll keep you if they find a solution. > > "Andrew" wrote: > > > same error here too.... > > > > "Christopher Keyaert" wrote: > > > > > I've got exactly the same error....no change in our infrastructure, > > > everything is like usual. > > > > > > Anyone find how to fix this issue ? > > > > > > "kc" wrote: > > > > > > > I receive the same error. Has anyone figured out a workaround or a fix to > > > > this error? > > > > > > > > > > > > "Kevin N. Andersen" wrote: > > > > > > > > > Exactly the same issue here. Most recent alert was half an hour ago and our > > > > > SCOM environment no failovers or anything out of the ordinary was happening. > > > > > > > > > > -- > > > > > Best regards / Venlig hilsen > > > > > > > > > > Kevin N. Andersen > > > > > Windows System Administrator > > > > > > > > > > "Maekee ." wrote in message news:2008718114039micke_is@hotmail.com... > > > > > > Hi, > > > > > > I also get this problem, exactly the same message. Have SP1, and our SQL > > > > > > Server is 2005 SP2. > > > > > > In 30 days this problem has a repeat count of 92. Our Cluster have not > > > > > > failed over including restarts of domaincontrollers in that period of > > > > > > time. > > > > > > > > > > > > This problem is reported on Microsofts Feedback page connect.microsoft.com > > > > > > with ID 336727. > > > > > > > > > > > > The case is reported as closed, there is good information about this > > > > > > problem on the site. Check it out > > > > > > > > > > > > Anyone found a solution? > > > > > > > > > > > > /Maekee > > > > > > > > > >
thanks a lot, i appreciate it "Christopher Keyaert" wrote: > I've open a Call to Microsoft Premier Support. > I'll keep you if they find a solution. > > "Andrew" wrote: > > > same error here too.... > > > > "Christopher Keyaert" wrote: > > > > > I've got exactly the same error....no change in our infrastructure, > > > everything is like usual. > > > > > > Anyone find how to fix this issue ? > > > > > > "kc" wrote: > > > > > > > I receive the same error. Has anyone figured out a workaround or a fix to > > > > this error? > > > > > > > > > > > > "Kevin N. Andersen" wrote: > > > > > > > > > Exactly the same issue here. Most recent alert was half an hour ago and our > > > > > SCOM environment no failovers or anything out of the ordinary was happening. > > > > > > > > > > -- > > > > > Best regards / Venlig hilsen > > > > > > > > > > Kevin N. Andersen > > > > > Windows System Administrator > > > > > > > > > > "Maekee ." wrote in message news:2008718114039micke_is@hotmail.com... > > > > > > Hi, > > > > > > I also get this problem, exactly the same message. Have SP1, and our SQL > > > > > > Server is 2005 SP2. > > > > > > In 30 days this problem has a repeat count of 92. Our Cluster have not > > > > > > failed over including restarts of domaincontrollers in that period of > > > > > > time. > > > > > > > > > > > > This problem is reported on Microsofts Feedback page connect.microsoft.com > > > > > > with ID 336727. > > > > > > > > > > > > The case is reported as closed, there is good information about this > > > > > > problem on the site. Check it out > > > > > > > > > > > > Anyone found a solution? > > > > > > > > > > > > /Maekee > > > > > > > > > >
I'm not sure it is a bug (and I'm usually more than happy to moan at MSFT!). I have seen this regularly and it is usually intermittent. Kevin gave one example above when he spoke about rebooting DC's. I have also seen it when a SQL hotfix has been applied to the SQL Server hosting the OpsMgr databases. The monitor is looking for eventid 11852 in the OperationsManager event log and this event is rather like a London bus. You don't get one coming along regularly. You just get loads at once. So 90 over 32 days doesn't mean anything unless you know when they happened. You could have had 20 occurences in a few minutes ... so the issue might have happened 4 or 5 times in those 3 months. Not really something to worry about in the scheme of things with OpsMgr. I'm not saying it isn't a problem. But a first step to resolving would be to: - close the alert - when the next alert comes long, check the operations manager event log to confirm how many event 11852 you have (or just look at the count in the console) - look at the application and system log on the SQL server to see if that coincides with anything - look at the SQL error logs - check domain controller reboots around that time. Hope it helps Graham "Andrew" wrote in message news:8E788DB0-53D1-4664-91F1-3E774EB26FD4@microsoft.com... > thanks a lot, i appreciate it > > "Christopher Keyaert" wrote: > >> I've open a Call to Microsoft Premier Support. >> I'll keep you if they find a solution. >> >> "Andrew" wrote: >> >> > same error here too.... >> > >> > "Christopher Keyaert" wrote: >> > >> > > I've got exactly the same error....no change in our infrastructure, >> > > everything is like usual. >> > > >> > > Anyone find how to fix this issue ? >> > > >> > > "kc" wrote: >> > > >> > > > I receive the same error. Has anyone figured out a workaround or a >> > > > fix to >> > > > this error? >> > > > >> > > > >> > > > "Kevin N. Andersen" wrote: >> > > > >> > > > > Exactly the same issue here. Most recent alert was half an hour >> > > > > ago and our >> > > > > SCOM environment no failovers or anything out of the ordinary was >> > > > > happening. >> > > > > >> > > > > -- >> > > > > Best regards / Venlig hilsen >> > > > > >> > > > > Kevin N. Andersen >> > > > > Windows System Administrator >> > > > > >> > > > > "Maekee ." wrote in message >> > > > > news:2008718114039micke_is@hotmail.com... >> > > > > > Hi, >> > > > > > I also get this problem, exactly the same message. Have SP1, >> > > > > > and our SQL >> > > > > > Server is 2005 SP2. >> > > > > > In 30 days this problem has a repeat count of 92. Our Cluster >> > > > > > have not >> > > > > > failed over including restarts of domaincontrollers in that >> > > > > > period of >> > > > > > time. >> > > > > > >> > > > > > This problem is reported on Microsofts Feedback page >> > > > > > connect.microsoft.com >> > > > > > with ID 336727. >> > > > > > >> > > > > > The case is reported as closed, there is good information about >> > > > > > this >> > > > > > problem on the site. Check it out >> > > > > > >> > > > > > Anyone found a solution? >> > > > > > >> > > > > > /Maekee >> > > > > >> > > > >
