Service Check Data Source Module Events
Hello,
I seem to keep having this alert   the event number is 11771, i could really use some help here on how to fix this issue if possible.... these errors are being generated from SCE BY SCE
Thanks,
Danny
Date and Time:   2/4/2010 5:19:14 AM
Log Name:   Operations Manager
Source:   Health Service Modules
Generating Rule:   Collect Service Check Data Source Module Events
Event Number:   11771
Level:    Warning
Logging Computer:   sce01.xxxxxx.com
User:   N/A
Description:
Error getting state of service


Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.



One or more workflows were affected by this.


Workflow name: Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor

Instance name: ESSENTIALS

Instance ID: {023CAC69-7B83-207A-5F48-D808815B4919}

Management group: SCE01_MG


Event Data:  View Event Data
< DataItem type =" System.XmlData " time =" 2010-02-04T05:19:14.0140371-06:00 " sourceHealthServiceId =" 5B7CC866-45FF-A2AE-8D33-0AC661F68861 " > < EventData >   < Data > SCE01_MG </ Data >   < Data > Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor </ Data >   < Data > ESSENTIALS </ Data >   < Data > {023CAC69-7B83-207A-5F48-D808815B4919} </ Data >   < Data > 0x8007007b </ Data >   < Data > The filename, directory name, or volume label syntax is incorrect. </ Data >   </ EventData >   </ DataItem >

 


February 4th, 2010 6:29pm

Also having the following alerts that i do not understand:
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

The process started at 2:01:28 AM failed to create System.Discovery.Data, no errors detected in the output.  The process exited with 0


Command executed: "C:\Windows\system32\cscript.exe" /nologo "ManagedVMClient.vbs" {E99A6599-1D4B-7568-C6A1-8D301BE2F90E} {40F2558C-A56A-9275-D50D-E61F07E290CC} sce01.xxxxxxxxxx.com Server
Working Directory: C:\Program Files\System Center Essentials\Health Service State\Monitoring Host Temporary Files 8\7325\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.Essentials.Internal.ManagedVMServer.Discovery

Instance name: sce01.xxxxxxxxxxx.com

Instance ID: {40F2558C-A56A-9275-D50D-E61F07E290CC}

Management group: SCE01_MG



:::::::::::::::::::::::::::::::::

Error getting state of service


Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.

 

One or more workflows were affected by this.


Workflow name: Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor

Instance name: ESSENTIALS

Instance ID: {023CAC69-7B83-207A-5F48-D808815B4919}

Management group: SCE01_MG



Any insight on this would be great!!!
Thanks again,
Danny

Free Windows Admin Tool Kit Click here and download it now
February 4th, 2010 6:41pm

Hello Danny,

It seems that this is the known issue in the RC version and should be fixed in RTM.

You can refer to the similar thread:
http://social.technet.microsoft.com/Forums/en-US/systemcenteressentials/thread/6c42380e-80af-4a6b-a9b3-08db757780ef

Please let us know if you have any other questions.

Thanks, Anshu
February 4th, 2010 9:56pm

hey anshu,

thanks for letting me know...
i have several other errors that i keep finding that for the life of me i can not figure out why they are there...
like this one:

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: sce01.xxxxxxxxxxxxx.com

Instance ID: {5B7CC866-45FF-A2AE-8D33-0AC661F68861}

Management group: SCE01_MG

Free Windows Admin Tool Kit Click here and download it now
February 4th, 2010 10:24pm

Hi Danny,

Also have a look at this post for resolving the alert in your first posting. The full text search service isn't included in SQL Express but the SQL management pack attempts to monitor it by default.

Thanks for letting us know about the SQL Broker alert too - this is one we're looking into.

Thanks

Richard
February 5th, 2010 1:46am

thanks Richard...
in the future if i encounter any more errors what do you recomend i do with them ?
i am trying to be as active as i can and help you guys make this product as good as you guys can... and i want to add that i really love SCE as a whole...
and would love to continue with the feedback! please let me know how i can help....
Thanks,
Danny
Free Windows Admin Tool Kit Click here and download it now
February 5th, 2010 1:56am

Hi Danny,

We love your reports, so please keep them coming :-).

If you're interested in some activities other than just providing feedback and answering questions on the forums, drop me a note via the contact form on our blog - http://blogs.technet.com/systemcenteressentials/contact.aspx.

Thanks

Richard
February 9th, 2010 3:22am

Hey there! 
here's this weeks errors and alerts
for one week i would like to have everything green and ok
hopefully one day this will happen, in the meantime I will just put them here for thoughts and insight and hope that it helps anyone or helps fix issues...These are from SCE by SCE I am not including any other alerts from other computers here


 Script or Executable Failed to run  Alert Description (there are 5 of these....)
  
Source:  sce01.xxxxxxxxxx.com  The process started at 10:00:59 AM failed to create System.PropertyBagData. Errors found in output:

C:\Program Files\System Center Essentials\Health Service State\Monitoring Host Temporary Files 8\10046\GetOpsMgrDBPercentFreeSpace.vbs(42, 2) Microsoft OLE DB Provider for SQL Server: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation.

 


Command executed: "C:\Windows\system32\cscript.exe" /nologo "GetOpsMgrDBPercentFreeSpace.vbs" SCE01\ESSENTIALS SystemCenterEssentials
Working Directory: C:\Program Files\System Center Essentials\Health Service State\Monitoring Host Temporary Files 8\10046\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.OpsMgrDBPercentFreeSpaceMonitor

Instance name: sce01.xxxxxxxxxx.com

Instance ID: {AEA1BBAE-0F81-99E9-3FF0-80661584C703}

Management group: SCE01_MG
 
Path:  sce01.xxxxxxxxxxx.com\sce01.xxxxxxxxxxxx.com  
Alert Rule:  Alert on Failed Batch Responses  
Created:  2/4/2010 10:02:38 AM

 

Logical Disk Fragmentation Level is high  Alert Description
  
Source:  C:  The disk C: (C:) on computer sce01.xxxxxxxxxxxxxx.com has high fragmentation level. File Percent Fragmentation value is 18%. Defragmentation recommended: true.
Path:  sce01.xxxxxxxxxxxx.com\C:  
Alert Monitor:  Logical Disk Fragmentation Level  
Created:  2/6/2010 3:02:56 AM

 

Service Check Probe Module Failed Execution  Alert Description
  
Source:  sce01.xxxxxxxxxxx.com  Error getting state of service


Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.

 

One or more workflows were affected by this.


Workflow name: Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor

Instance name: ESSENTIALS

Instance ID: {023CAC69-7B83-207A-5F48-D808815B4919}

Management group: SCE01_MG
 
Path:  sce01.xxxxxxxxxxx.com\sce01.xxxxxxxxxxxx.com  
Alert Rule:  Service Check Probe Module Execution Failure  
Created:  2/5/2010 2:02:23 AM


 Logical Disk Fragmentation Level is high  Alert Description
  
Source:  E:  The disk E: (E:) on computer sce01.xxxxxxxxxxxx.com has high fragmentation level. File Percent Fragmentation value is 99%. Defragmentation recommended: true.
Path:  sce01.xxxxxxxxxxxxx.com\E:  
Alert Monitor:  Logical Disk Fragmentation Level  
Created:  2/6/2010 3:02:56 AM

 

WMI Probe Module Failed Execution  Alert Description
  
Source:  sce01.xxxxxxxxxxxx.com  Module was unable to connect to namespace 'root\cimv2'


This has happened 1 times since this instance was loaded.


HRESULT: 0x80010002
Details: Call was canceled by the message filter.

 

One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.Essentials.ComputerManufacturerDetails.BiosSerialNumber.Discovery

Instance name: sce01.xxxxxxxxxxxx.com

Instance ID: {40F2558C-A56A-9275-D50D-E61F07E290CC}

Management group: SCE01_MG
 
Path:  sce01.xxxxxxxxxxxxxxx.com\sce01.xxxxxxxxxxxxxxxx.com  
Alert Rule:  WMI Probe Module Execution Failure  
Created:  2/4/2010 12:10:13 PM


Service Check Data Source Module Failed Execution  Alert Description
  
Source:  sce01.xxxxxxxxxxxx.com  Error getting state of service


Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.

 

One or more workflows were affected by this.


Workflow name: Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor

Instance name: ESSENTIALS

Instance ID: {023CAC69-7B83-207A-5F48-D808815B4919}

Management group: SCE01_MG
 
Path:  sce01.xxxxxxxxxxxx.com\sce01.xxxxxxxxxxxxxx.com  
Alert Rule:  Service Check Data Source Module Execution Failure  
Created:  2/4/2010 9:43:13 AM

 

Free Windows Admin Tool Kit Click here and download it now
February 10th, 2010 6:05pm

hey guys ok more errors to report, mainly this one from many machines: If anyone knows how to resolve this error or warning without just clearing
them please let me know
Thanks,
Danny


The process started at 11:39:49 AM failed to create System.Discovery.Data, no errors detected in the output.  The process exited with 0


Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "ManagedVMClient.vbs" {047A6852-C282-151B-5A0F-6B33D623C23C} {979F2C02-77FF-A615-69AF-D482C4067D17} eomis07.xxxxxxxxxx.com Client
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 17\299\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.Essentials.Internal.ManagedVMClient.Discovery

Instance name: eomis07.xxxxxxxxxxxx.com

Instance ID: {979F2C02-77FF-A615-69AF-D482C4067D17}

Management group: SCE01_MG

February 25th, 2010 12:56am

also here's this weeks critical errors from SCE by SCE


Date and Time: 2/24/2010 9:55:44 AM
Log Name: Application
Source: Windows Server Update Services
Event Number: 13002
Level: 1
Logging Computer: sce01.xxxxxxxxxx.com
User: N/A
 Description:
Client computers are installing updates with a higher than 25 percent failure rate. This is not normal. 
 

Event Data:

< DataItem type =" System.XmlData " time =" 2010-02-24T09:55:44.1666165-06:00 " sourceHealthServiceId =" 5B7CC866-45FF-A2AE-8D33-0AC661F68861 " >
< EventData >
  < Data > Client computers are installing updates with a higher than 25 percent failure rate. This is not normal. </ Data >
  </ EventData >
  </ DataItem >


Date and Time: 2/24/2010 4:25:43 PM
Log Name: Operations Manager
Source: Health Service Modules
Event Number: 11852
Level: 2
Logging Computer: sce01.xxxxxxxxxxxxxxxx.com
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: sce01.xxxxxxxxxxx.com Instance ID: {5B7CC866-45FF-A2AE-8D33-0AC661F68861} Management group: SCE01_MG 
 

Event Data:

< DataItem type =" System.XmlData " time =" 2010-02-24T16:25:54.2642632-06:00 " sourceHealthServiceId =" 5B7CC866-45FF-A2AE-8D33-0AC661F68861 " >
< EventData >
  < Data > SCE01_MG </ Data >
  < Data > Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor </ Data >
  < Data > sce01.xxxxxxxxxxx.com </ Data >
  < Data > {5B7CC866-45FF-A2AE-8D33-0AC661F68861} </ Data >
  < Data > Login timeout expired </ Data >
  < Data > 0x80004005 </ Data >
  < Data > Unspecified error </ Data >
  </ EventData >
  </ DataItem >

 

Date and Time: 2/24/2010 10:47:13 AM
Log Name: Operations Manager
Source: Health Service Script
Event Number: 4001
Level: 1
Logging Computer: sce01.xxxxxxxxxxxxxxx.com
User: N/A
 Description:
GetSQL2008BlockingSPIDs.vbs : Cannot login to database [sce01.xxxxxxxxxxxxxxx.com][ESSENTIALS:master] . 
 

Event Data:

< DataItem type =" System.XmlData " time =" 2010-02-24T10:47:15.8121021-06:00 " sourceHealthServiceId =" 5B7CC866-45FF-A2AE-8D33-0AC661F68861 " >
< EventData >
  < Data > GetSQL2008BlockingSPIDs.vbs </ Data >
  < Data > Cannot login to database [sce01.xxxxxxxxxxxxx.com][ESSENTIALS:master] . </ Data >
  </ EventData >
  </ DataItem >

 

Date and Time: 2/24/2010 10:46:05 AM
Log Name: Operations Manager
Source: Health Service Modules
Event Number: 11852
Level: 2
Logging Computer: sce01.xxxxxxxxxxxx.com
User: N/A
 Description:
OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error : [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation. Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor Instance name: sce01.xxxxxxxxxxxxx.com Instance ID: {5B7CC866-45FF-A2AE-8D33-0AC661F68861} Management group: SCE01_MG 
 

Event Data:

< DataItem type =" System.XmlData " time =" 2010-02-24T10:47:14.1579111-06:00 " sourceHealthServiceId =" 5B7CC866-45FF-A2AE-8D33-0AC661F68861 " >
< EventData >
  < Data > SCE01_MG </ Data >
  < Data > Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor </ Data >
  < Data > sce01.xxxxxxxxxxxxxxxxxxx.com </ Data >
  < Data > {5B7CC866-45FF-A2AE-8D33-0AC661F68861} </ Data >
  < Data > [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation. </ Data >
  < Data > 0x80004005 </ Data >
  < Data > Unspecified error </ Data >
  </ EventData >
  </ DataItem >

 

Date and Time: 2/24/2010 3:50:12 PM
Log Name: Operations Manager
Source: Health Service Modules
Event Number: 31400
Level: 1
Logging Computer: sce01.xxxxxxxxxxxx.com
User: N/A
 Description:
An exception occured processing a group membership rule. The rule will be unloaded. Subscription ID: 1ac6ba80-bb85-4699-82a2-f3c584b06965 Rule ID: bb91657f-32db-4f72-2ed6-e7ac94f0e167 Group ID: b20e0f37-c8d3-afcc-e21e-473b019fd826 Group type name: Microsoft.Dynamics.AX.Management.Pack.DynamicsServer.Group Exception: Microsoft.EnterpriseManagement.Common.DataAccessLayerException: Invalid property name: IsDynamicsInstalledAttribute_CE6F4AC6_0A15_BE42_323A_65A3BC8AB307 at Microsoft.EnterpriseManagement.Mom.DataAccess.ParameterizedCriteriaBuilder.GetColumnDefinitionForProperty(String propertyName, QueryDefinition queryDefinition) at Microsoft.EnterpriseManagement.Mom.DataAccess.ParameterizedCriteriaBuilder.ParsePredicateWithProperty(SqlCommand sqlCommand, QueryDefinition queryDefinition, Nullable`1 typeContextId, XmlReader criteriaReader) at Microsoft.EnterpriseManagement.Mom.DataAccess.ParameterizedCriteriaBuilder.ParsePredicate(SqlCommand sqlCommand, QueryDefinition queryDefinition, Nullable`1 typeContextId, XmlReader criteriaReader) at Microsoft.EnterpriseManagement.Mom.DataAccess.ParameterizedCriteriaBuilder.ParseCriteria(SqlCommand sqlCommand, QueryDefinition queryDefinition, Nullable`1 managedTypeIdContext, XmlReader criteriaReader) at Microsoft.EnterpriseManagement.Mom.DataAccess.ParameterizedCriteriaBuilder.CreateCriteriaTextAndParameters(SqlCommand sqlCommand, QueryDefinition queryDefinition, XmlReader criteriaReader, XmlNamespaceManager xmlNamespaceManager) at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlCommandBuilder.CreateCriteria(SqlCommand sqlCommand, QueryDefinition queryDefinition, String criteriaXml, Dictionary`2 parameterValues) at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.CreateSqlCommandForSelectType() at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.Execute(SqlNotificationRequest sqlNotificationRequest) at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.QueryGenerator.ExecuteSnapshotQuery(MembershipRule membershipRule, DatabaseConnection databaseConnection) at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.ExpressionEvaluatorForSnapshot.EligibleBySnapshotResults(MembershipRule membershipRule, DatabaseConnection databaseConnection) at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.ExpressionEvaluatorForSnapshot.GetRelationshipChangesForSnapshot(MembershipRule membershipRule, Guid groupInstanceId, Guid groupTypeId, Guid relationshipId, IList`1 groupKeyNameValuePairs, DatabaseConnection databaseConnection) at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.MembershipRuleEvaluator.EvaluateSnapshot(MembershipSubscription subscription, DatabaseConnection databaseConnection) at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.MembershipCalculationManager.SnapshotCalculation(MembershipSubscription membershipSubscription, DatabaseConnection databaseConnection) 
 

Event Data:

< DataItem type =" System.XmlData " time =" 2010-02-24T15:50:12.2844774-06:00 " sourceHealthServiceId =" 5B7CC866-45FF-A2AE-8D33-0AC661F68861 " >
< EventData >
  < Data > 1ac6ba80-bb85-4699-82a2-f3c584b06965 </ Data >
  < Data > bb91657f-32db-4f72-2ed6-e7ac94f0e167 </ Data >
  < Data > b20e0f37-c8d3-afcc-e21e-473b019fd826 </ Data >
  < Data > Microsoft.Dynamics.AX.Management.Pack.DynamicsServer.Group </ Data >
  < Data > Microsoft.EnterpriseManagement.Common.DataAccessLayerException: Invalid property name: IsDynamicsInstalledAttribute_CE6F4AC6_0A15_BE42_323A_65A3BC8AB307 at Microsoft.EnterpriseManagement.Mom.DataAccess.ParameterizedCriteriaBuilder.GetColumnDefinitionForProperty(String propertyName, QueryDefinition queryDefinition) at Microsoft.EnterpriseManagement.Mom.DataAccess.ParameterizedCriteriaBuilder.ParsePredicateWithProperty(SqlCommand sqlCommand, QueryDefinition queryDefinition, Nullable`1 typeContextId, XmlReader criteriaReader) at Microsoft.EnterpriseManagement.Mom.DataAccess.ParameterizedCriteriaBuilder.ParsePredicate(SqlCommand sqlCommand, QueryDefinition queryDefinition, Nullable`1 typeContextId, XmlReader criteriaReader) at Microsoft.EnterpriseManagement.Mom.DataAccess.ParameterizedCriteriaBuilder.ParseCriteria(SqlCommand sqlCommand, QueryDefinition queryDefinition, Nullable`1 managedTypeIdContext, XmlReader criteriaReader) at Microsoft.EnterpriseManagement.Mom.DataAccess.ParameterizedCriteriaBuilder.CreateCriteriaTextAndParameters(SqlCommand sqlCommand, QueryDefinition queryDefinition, XmlReader criteriaReader, XmlNamespaceManager xmlNamespaceManager) at Microsoft.EnterpriseManagement.Mom.DataAccess.SqlCommandBuilder.CreateCriteria(SqlCommand sqlCommand, QueryDefinition queryDefinition, String criteriaXml, Dictionary`2 parameterValues) at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.CreateSqlCommandForSelectType() at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryRequest.Execute(SqlNotificationRequest sqlNotificationRequest) at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.QueryGenerator.ExecuteSnapshotQuery(MembershipRule membershipRule, DatabaseConnection databaseConnection) at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.ExpressionEvaluatorForSnapshot.EligibleBySnapshotResults(MembershipRule membershipRule, DatabaseConnection databaseConnection) at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.ExpressionEvaluatorForSnapshot.GetRelationshipChangesForSnapshot(MembershipRule membershipRule, Guid groupInstanceId, Guid groupTypeId, Guid relationshipId, IList`1 groupKeyNameValuePairs, DatabaseConnection databaseConnection) at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.MembershipRuleEvaluator.EvaluateSnapshot(MembershipSubscription subscription, DatabaseConnection databaseConnection) at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.MembershipCalculationManager.SnapshotCalculation(MembershipSubscription membershipSubscription, DatabaseConnection databaseConnection) </ Data >
  </ EventData >
  </ DataItem >

 

 

Free Windows Admin Tool Kit Click here and download it now
February 25th, 2010 1:38am

For what it's worth, I can confirm Danny's findings.  I've recently implemented SCE2010RC here in our environment, and I'm getting the exact same errors, also using the default sqlexpress 2008 install with SCE.  If you want me to post them I certainly can, but personally I think it's a waste of electricity. =)
February 25th, 2010 5:53pm

this is becoming a nuisance.  One of my servers constantly reports this error, which seemingly prevents from installing or even downloading for that matter, any updates from the SCE server.  Is there any work around for this?


Basically getting this error (copied from above):

Path:  sce01.xxxxxxxxxxxxxxx.com\sce01.xxxxxxxxxxxxxxxx.com  
Alert Rule:  WMI Probe Module Execution Failure  
Created:  2/4/2010 12:10:13 PM


Service Check Data Source Module Failed Execution  Alert Description
  
Source:  sce01.xxxxxxxxxxxx.com  Error getting state of service


Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.

 

One or more workflows were affected by this.


Workflow name: Microsoft.SQLServer.2005.DBEngine.FullTextSearchServiceMonitor

Instance name: INSERT INSTANCE NAME

Instance ID: {023CAC69-7B83-207A-5F48-D808815B4919}

Management group: SCE01_MG
 
Path:  sce01.xxxxxxxxxxxx.com\sce01.xxxxxxxxxxxxxx.com  
Alert Rule:  Service Check Data Source Module Execution Failure  
Created:  2/4/2010 9:43:13 AM

Free Windows Admin Tool Kit Click here and download it now
February 25th, 2010 10:03pm

ok so perhaps I was a bit hasty, but applying an override to this rule seems to let an install actually happen.  Is this a bad practice or basically am i just telling the system to ignore this error?
February 25th, 2010 10:06pm

tom,
i am doing this "ignore" function on a regular basis,   from what i can understand they are working on the errors, i am and will continue to post up the errors i find,  the errors are certainly annoying though,  my biggest issue isn't really the fact of me having to clear the errors out, just more so of why they are happening,  mainly from what i see it's comunication errors, and having to do with sql database, but that's all i know, and all i have been told is that they are working on it.... thanks for backing me though, i was begining to think that i was the only one getting errors...
Danny
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2010 12:51am

on a side note, i would love to see more people posting their errors too...  i think if enough people were having these errors they would be more inclined to fix them... or at least help to find a solution for them....
as of now it's a shot in the dark, but i am hoping that something will come of it...
these guys are certainly busting their butts for us on a regular basis, and with that said i am a patient man...  so i wait... :)
February 26th, 2010 12:55am

Here are some of my entries out of the active alerts list on the Monitoring Pane (I'm listing the most common ones):

____________________________________________________________________________________________________

Forced to terminate the following process started at 8:17:14 AM because it ran past the configured timeout 300 seconds.


Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "ProxyConfigurationDetection.vbs"
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\338\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.Essentials.WUAgent.ProxyConfigurationDetection

Instance name: Microsoft.SystemCenter.Essentials.WUAgent

Instance ID: {2B55C412-05BE-ACB8-B17F-A0B8131C672C}

Management group: ***SYSCENTER_MG


_______________________________________________________________________________________________________________

The process started at 8:30:31 AM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 0


Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "ManagedVMClient.vbs" {047A6852-C282-151B-5A0F-6B33D623C23C} {4C72E748-C6DE-8BB4-2402-523EEC68E382} *************** Client
Working Directory: C:\Program Files\System Center Essentials\Health Service State\Monitoring Host Temporary Files 4\163\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.Essentials.Internal.ManagedVMClient.Discovery

Instance name: ***********

Instance ID: {4C72E748-C6DE-8BB4-2402-523EEC68E382}

Management group: ****SYSCENTER_MG
__________________________________________________________________


The process started at 5:59:54 PM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 1


Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "DiscoverWindowsComputerProperties.js" 0 {114E4510-2789-ECC5-AC91-1F7DB6C49998} {505D8178-50EC-9584-AF80-1AFFF58A815D} *********
Working Directory: C:\Program Files\System Center Essentials\Health Service State\Monitoring Host Temporary Files 6\1399\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.DiscoverWindowsComputerProperties

Instance name: ******************

Instance ID: {505D8178-50EC-9584-AF80-1AFFF58A815D}

Management group: ****SYSCENTER_MG

____________________________________________________________________________________________-


Error getting state of service


Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.



One or more workflows were affected by this.


Workflow name: Microsoft.SQLServer.2005.DBEngine.FullTextSearchServiceMonitor

Instance name: BKUPEXEC

Instance ID: {90ADC7A9-31B2-B1CF-21B6-727BF9F9E255}

Management group: ****SYSCENTER_MG

____________________________________________________________________________

Error getting state of service


Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.



One or more workflows were affected by this.


Workflow name: Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor

Instance name: ESSENTIALS

Instance ID: {EE861B36-B3A8-0685-05A5-EB3DD1AB0757}

Management group: *****SYSCENTER_MG

________________________________________________________________________


Error getting state of service


Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.



One or more workflows were affected by this.


Workflow name: Microsoft.SQLServer.2005.DBEngine.FullTextSearchServiceMonitor

Instance name: *****************

Instance ID: {90ADC7A9-31B2-B1CF-21B6-727BF9F9E255}

Management group:*******SYSCENTER_MG

________________________________________________________



There are more if you really want me to post them, again, these are the most common that i've run across.

Thanks,
Tom
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2010 6:09pm

Hey tom,
thanks for posting the errors,
i was told the SQL errors are supossed to be fixed for the actual release, 
but i think they need to be aware of all of them, and the other warnings and errors... 
seems to me that your having just as many of the SQL errors as i am, this definetly needs to be addresed,  so far i am not comfortable pairing SCE up with my actual SQL server,  and even once it's fixed i am not sure if i will want to pair it up with the database,
the many other errors are a concern as well, i know there are several people out there having these same isssues,
maybe if we can get enough people with the same errors, we could get some fixes for them...  :)   (one can hope!)

Danny  
February 26th, 2010 6:34pm

Hey guys,
here's this weeks errors/alerts
please bear in mind these error/alerts are from SCE by SCE
i figure once we can get the kinks worked out with SCE we can move on to the errors and alerts for the other servers and workstations
 i do have a question though, is anyone out there having a issue with the updates ?
i have close to 80GB of updates on the SCE server now,
But actually getting the updates to the machines in a timely matter is a whole new bag of worms....
i have also done several tests on my network that i would love to share if anyone cares,
the first test was with about 50 total machines,
19 servers and 31 workstations,
some of them had vista, others had xp sp2, xp sp3, windows 7
and the servers were a mixed bunch, 2003, 2008, 2008 r2
this test was simple... add 50 machines see what happens...
what happened was simple too! my bandwith dropped to nothing !
and stayed that way untill i made some changes...
the conclusion was this; SCE will eat all your bandwith if the machines you are managing are not up to date,  it does everything it can to apply all the updates it can at the same time, with no regard of anything else,
the solution to this was easy,
number one, make sure SCE is fully up to date and the server it's running on is up to date as well
two, before you add a machine, make sure it's as up to date as you can first,
three, do not auto approve for your servers, my company can not have our servers rebooting on their own, and auto approving pretty much will do that for you.  if you want to use auto-approval and your servers automaticaly rebooting is not an issue, go for it!
and finally four, have tons of patience, this software is powerfull and can do many things, but understand that SCE in reality is many programs shoved and stuffed into one big package!
there are many things going on here, and many programs all running together to make all this possible, and they have a few issues they are still working on.
with that i will leave you with a fav. quote of mine

"The two most powerful warriors are patience and time"  Leo Nikolaevich Tolstoy

Ok! on to the alerts/errors!!!!
---------------------------------------------------------------------

   Script or Executable Failed to run

The process started at 2:01:26 AM failed to create System.PropertyBagData. Errors found in output:

C:\Program Files\System Center Essentials\Health Service State\Monitoring Host Temporary Files 47\42701\GetSQL2008DBSpace.js(67, 12) Microsoft JScript runtime error: 'Databases' is null or not an object

 


Command executed: "C:\Windows\system32\cscript.exe" /nologo "GetSQL2008DBSpace.js" sce01\ESSENTIALS
Working Directory: C:\Program Files\System Center Essentials\Health Service State\Monitoring Host Temporary Files 47\42701\


One or more workflows were affected by this.


Workflow name: many

Instance name: many

Instance ID: many

Management group: SCE01_MG

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

 

   Script or Executable Failed to run

The process started at 2:01:14 AM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 0


Command executed: "C:\Windows\system32\cscript.exe" /nologo "ManagedVMClient.vbs" {E99A6599-1D4B-7568-C6A1-8D301BE2F90E} {40F2558C-A56A-9275-D50D-E61F07E290CC} sce01.xxxxxxxxxxxx.com Server
Working Directory: C:\Program Files\System Center Essentials\Health Service State\Monitoring Host Temporary Files 47\44210\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.Essentials.Internal.ManagedVMServer.Discovery

Instance name: sce01.xxxxxxxxxxx.com

Instance ID: {40F2558C-A56A-9275-D50D-E61F07E290CC}

Management group: SCE01_MG

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

 

Service Check Probe Module Failed Execution


Error getting state of service


Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.

 

One or more workflows were affected by this.


Workflow name: Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor

Instance name: ESSENTIALS

Instance ID: {023CAC69-7B83-207A-5F48-D808815B4919}

Management group: SCE01_MG

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


Service Check Data Source Module Failed Execution


Error getting state of service


Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.

 

One or more workflows were affected by this.


Workflow name: Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor

Instance name: ESSENTIALS

Instance ID: {023CAC69-7B83-207A-5F48-D808815B4919}

Management group: SCE01_MG



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

Freethinkers are those who are willing to use their minds without prejudice and without fearing to understand things that clash with their own customs, privileges, or beliefs. This state of mind is not common, but it is essential for right thinking

Danny....

Free Windows Admin Tool Kit Click here and download it now
March 4th, 2010 8:29pm

After updating to RTM, and updating all the agents, I still see tons of warnings:

Error getting state of service

Error: 0x8007007b

Details: The filename, directory name, or volume label syntax is incorrect.

One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2005.DBEngine.FullTextSearchServiceMonitor

Instance name: SQL_READ

Instance ID: {2A14FE5E-571F-B214-CD9D-983E7BFB54D8}

Management group: LASCE_MG

and

 

Command executed: "C:\WINDOWS\System32\cscript.exe" /nologo "C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 11\1452\DiscoverVirtualMachineComputer.vbs" {EE4C9857-3C24-A2F5-48D5-49EED1DB7BF9} {DD5AD8AB-E4F9-5DC6-E340-EF2B73095F62} LAWEBCAM165.LA.Cryobank.com
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 11\1452\

 

I thought these were known issues that were supposed to be fixed in RTM?


April 22nd, 2010 9:07pm

wow that sucks...  i am not happy to hear that at all....

do have a question though... was your upgrade from RC to RTM ok ? i have been hearing of several problems so far... did it go off without a hitch as promised ?  

Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2010 10:57pm

It went fine it seems. No errors. Process took about 10 minutes. I was really hoping to see my Active Alerts log clear up, but it's all yellow now again with Script or Executable Failed to run and Service Check Data from multiple servers and workstations...
April 22nd, 2010 11:04pm

yeah i am not sure about the script erros... i have been getting those the whole time, the only fix i really knew about that they said would be fixed was the oledb errors... are you seeing any of those ?
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2010 11:11pm

if they're errors you don't care about you can override them to not generate alerts if you want.  I know they're annoying, but for me if it's out of sight, out of mind.
April 23rd, 2010 12:10am

no, let's not fix the problem LOL, let's just sweep that dirt under the rug and not worry about it... hehe  but no he's right though,  you can override them, but be carefull about which rules you override some of the rules are under a bigger rule, and if you override the bigger rule you could not get any of the other alerts  that the bigger rule encompases...
Free Windows Admin Tool Kit Click here and download it now
April 23rd, 2010 12:22am

Just got OleDB error.. is that the one that supposed to be fixed?

 

Alert: OleDB: Results Error

Source: LASCE.domain.com

Path: LASCE.domain.com

Last modified by: System

Last modified time: 4/22/2010 2:36:42 PM Alert 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: LASCE.domain.com

 

Instance ID: {5808AB12-6A2B-EC3B-A2C3-524F7452D896}

 

Management group: LASCE_MG

 

April 23rd, 2010 1:22am

Thanks for all of your patience with these and taking time to report them.

The script errors being reported for monitoring are coming from Management Packs.

A quick side note for anyone not familiar with Management Packs (MPs). They are pretty cool - they contain all of the monitoring, knowledge, reports etc that let Essentials know how to monitor the health of Windows and applications. Essentials shares many MPs with Operations Manager, and lots of different groups within Microsoft write MPs.

The great thing about MPs is that they get updated on a regular basis, although each team sets their own schedule, so you'll see updates for different MPs at different times.

For the errors listed in the thread above, we made changes to fix errors coming from the following workflows:

  • Microsoft.SystemCenter.Essentials.WUAgent.ProxyConfigurationDetection
  • Microsoft.SystemCenter.Essentials.Internal.ManagedVMClient.Discovery
  • Microsoft.SystemCenter.Essentials.ComputerManufacturerDetails.BiosSerialNumber.Discovery

There is also a fix for the following, but the Management Pack isn't in the Essentials catalog just yet. It is in the Operations Manager catalog if you want to download and import it:

  • Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor
  • Microsoft.SystemCenter.DiscoverWindowsComputerProperties

The next two I'm hoping will be fixed in the next version of the SQL Server MP (I don't know the timeframe for release, and I haven't seen a new MP, so I can't be sure):

  • Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor
  • Microsoft.SQLServer.2005.DBEngine.FullTextSearchServiceMonitor

Until there is an update in the SQL MP, you can override the rules as described in this blog posting.

Danny01, your "baby" sounds like it is in the 90th percentile for weight :-). I think you're already using Automatic Selection of Product Categories, which helps to cut down on what is downloaded. If you elected to download more than the default critical and security updates or multiple languages then you will see more stuff downloaded. The "Download express installation files" will use more server storage space - during synchronization the updates themselves are downloaded. The other option only downloads updates once they are approved. If you don't approve an update it is never downloaded. 

If you had a few machines that were behind on updates, then what I expect to see is an initial spike in the amount of updates downloaded and distributed. The volume can be particularly big if you select Service Packs and you had some machines missing services packs. As all of the updates are pushed out and computers updated, the update space should stablize, and then as the Maintenance job kicks in it could even start to go down. 

By default the updates maintenance isn't enabled. To check its status, and to enable it:

  1. Go to the Administration Workspace
  2. Select the Settings node in the navigation pane
  3. Double click the Update Management Settings at the bottom of the list in the center pane
  4. Select checkbox next to Schedule maintenance

At this point, you can click the Decline now and then the Update now buttons to see if you can free some space. It might take some time though so if you've got things to do in Essentials you might want to let it run on its schedule.

Thanks

Richard

 

Free Windows Admin Tool Kit Click here and download it now
April 23rd, 2010 1:36am

Thanks for the heads up Richard. I downloaded and imported the updated MP from your link, and also disabled SQL Full Text search monitor per blog post. Will let you know if it helps with all the warnings.
April 23rd, 2010 2:13am

I don't see anymore SQL Full Text Search related errors. However, I see tons of these in Active Alerts:

The process started at 9:45:25 PM failed to create System.PropertyBagData. Errors found in output:

C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 26\1621\SCOMpercentageCPUTimeCounter.vbs(189, 2) Microsoft VBScript runtime error: Type mismatch

also the following errors:

(125, 5) SWbemRefresher: The remote procedure call failed and did not execute.
(212, 2) SWbemObjectSet: Out of memory

State\Monitoring Host Temporary Files 15\1598\CPUUtilization.vbs(209, 9) SWbemObjectEx: The object invoked has disconnected from its clients.

Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "SCOMpercentageCPUTimeCounter.vbs" SCLab171.domain.com false 3
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 26\1621\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.HealthService.SCOMpercentageCPUTimeCollection

Instance name: SCLab171.domain.com

Instance ID: {809935C0-FAEC-829B-184A-7A7CEA19B6FD}

Management group: LASCE_MG

 

The process started at 8:40:19 AM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 1


Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "ManagedVMClient.vbs" {047A6852-C282-151B-5A0F-6B33D623C23C} {384A15A3-9A65-5EDB-B25A-24E7D28306D9} LAITD630E.domain.com Client
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 33\239\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.Essentials.Internal.ManagedVMClient.Discovery

Instance name: LAITD630E.domain.com

Instance ID: {384A15A3-9A65-5EDB-B25A-24E7D28306D9}

Management group: LASCE_MG

 

The process started at 8:40:19 AM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 3221225794


Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "RedirectWSUS.vbs" 0 {26D3CA4A-0EBA-57EB-2A74-589DAAFA8334} {384A15A3-9A65-5EDB-B25A-24E7D28306D9} LAITD630E.domain.com
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 33\243\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.Essentials.WSUSRedirectDiscovery

Instance name: LAITD630E.domain.com

Instance ID: {384A15A3-9A65-5EDB-B25A-24E7D28306D9}

Management group: LASCE_MG

Don't think I've seen these before. They started to fill up the log after I upgraded the MP. There are others too.. Sharepoint discovery, WSUSCategoryGuid, Agent.PatchDiscovery etc.

 

 

Free Windows Admin Tool Kit Click here and download it now
April 23rd, 2010 6:56pm

Richard, you are spot on with why the updates are taking so much space, i figured it was this, and am ok with it... i am hoping that the Maintenance will help later...  it's not a big concern. the updates roll much quicker to the users machines now, i encourage anyone that has the space to do the same....

only time will tell with the Maintenance we will see....  

April 23rd, 2010 8:22pm

Question I am having this same issue with 2010 version will this hot fix for for sce 2010.  note: currently i do not show my system having any of the referenced management packs installed.  


Forced to terminate the following process started at 7:31:57 AM because it ran past the configured timeout 300 seconds.


Command executed: "C:\Windows\system32\cscript.exe" /nologo "ProxyConfigurationDetection.vbs"
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 128\2023\


One or more workflows were affected by this.


Workflow name: Microsoft.SystemCenter.Essentials.WUAgent.ProxyConfigurationDetection

Instance name: Microsoft.SystemCenter.Essentials.WUAgent

Instance ID: {D93BBFE7-7F70-3933-7500-A1E48208BE27}

Management group: M1_MG

Free Windows Admin Tool Kit Click here and download it now
March 4th, 2014 11:40am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics