Return
-
Title
SCOM (R1 & R2) Error: "The Windows Event Log Provider is still unable to -
Description
When the Foglight SCOM integration is setup on a SCOM server, all of the SCOM agents, except for the one on the SCOM server, is receiveing the following error mesgae: "The Windows Event Log Provider is still unable to open the Foglight event log on computer 'host.quest.corp'. The Provider has been unable to open the Foglight event log for 1514880 seconds. Most recent error details: The system cannot find the file specified. One or more workflows were affected by this. Workflow name: MomUIGeneratedRule096546f5274a4738a2970f4359ee01d7 Instance name: host.quest.corp Instance ID: {5D4CE1FF-6D95-10C1-5311-2A44E1DA5857} Management group: TEST_SCOM"
Once Foglight integration is setup on the SCOM server, it seems that all SCOM agents expect to find the files generated by the XL-Rec-Log service on their machines which should not be the case. Only the agent running on the SCOM server that was configured should find it. -
Resolution
Hot Fix:
Import the XML into the System Center Operations Manager:1. Copy the file Quest.FoglightConnector.xml (attached) to a local directory for installation into the System Center Operations Manager system.
2. Select the 'Administration' button on the bottom left.
3. Select 'Management Packs' from the list on the left.
4. Click the 'Import Management Packs on the right.
5. When the dialog appears, select the file Quest.FoglightConnector.xml from the directory that you've copied to for installation.
6. Click Import to complete the import of the management pack into the System Center Operations Manager system.Add Agent to group1. Select the 'Authoring' button on the bottom left.
2. Click the Groups in the tree
3. Double click on the Quest Foglight Connector Group in the Groups list
4. Click on the Explicit Members tab
5. Click Add/Remove Objects button
6. Click the Search button
7. Choose the agent monitoring the SCOM server and click the add button -
Defect ID
INT-41 -
Attachments