No Reporting (Data) within FCS Console - MOM 2005 Service Not Running
-
Wednesday, May 12, 2010 2:23 PM
We are experiencing multiple issues with FCS, which was deployed within our domain for the last three weeks. Until this week, not problems were noted but now the MOM services fails to start and SQL is also showing errors in the event logs. Since the MOM service fails to start, the FCS console shows no data.
We have followed the advise from simular issues (Event ID's 9014/9015 ) noted within the Forefront forums, but none have solved the problems.
Here is one of the event logs:
Event Type: Error
Event Source: MOM.Datawarehousing.DTSPackageGenerator.exe
Event Category: None
Event ID: 1001
Date: 5/11/2010
Time: 1:02:51 AM
User: N/A
Computer: FCS03
Description:
Step StepInvokeInnerPackage failed.
Step Error Source: Microsoft OLE DB Provider for SQL Server
Step Error Description: (1:SC_Inner_DTS_Package) SubStep 'DTSStep_ExecuteSQLTask_SC_EventFact_View_1_Insert' failed with the following error:
Could not allocate space for object 'dbo.SC_EventFact_Table'.'inxSAS_EventFact_EventDetailAndTime' in database 'SystemCenterReporting' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
Execution was canceled by user.
Step Error Code: -2147220441
Step Error Help File:
Step Error Help Context ID:0For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 1105
Date: 5/11/2010
Time: 1:02:51 AM
User: SCCSC\FCSadm
Computer: FCS03
Description:
Could not allocate space for object 'sys.sysobjvalues'.'clst' in database 'SystemCenterReporting' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 51 04 00 00 11 00 00 00 Q.......
0008: 06 00 00 00 46 00 43 00 ....F.C.
0010: 53 00 30 00 33 00 00 00 S.0.3...
0018: 16 00 00 00 53 00 79 00 ....S.y.
0020: 73 00 74 00 65 00 6d 00 s.t.e.m.
0028: 43 00 65 00 6e 00 74 00 C.e.n.t.
0030: 65 00 72 00 52 00 65 00 e.r.R.e.
0038: 70 00 6f 00 72 00 74 00 p.o.r.t.
0040: 69 00 6e 00 67 00 00 00 i.n.g...
Event Type: Error
Event Source: Microsoft Operations Manager
Event Category: None
Event ID: 9014
Date: 5/11/2010
Time: 8:40:59 AM
User: N/A
Computer: FCS03
Description:
The Microsoft Operations Manager service (MOMService.exe) terminated due to an unhandled exception. It will attempt to restart itself.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Microsoft Operations Manager
Event Category: None
Event ID: 9015
Date: 5/11/2010
Time: 8:40:59 AM
User: N/A
Computer: FCS03
Description:
The Microsoft Operations Manager service (MOMService.exe) received an unexpected exception.
Thread Id: 0x13d0
Thread Name: ForefrontClientSecurity5072
Exception code: 0x00000000c0000005
Exception description: Access Violation
Exception address: 010EC0DC
Exception flags: 0x0For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
All Replies
-
Wednesday, May 12, 2010 5:18 PM
have you seen this link http://support.microsoft.com/kb/899158/en-us
Also what is the FCS OS-version, 2003 or 2008 ?
Bechir Gharbi. MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront (Time Zone : GMT+1)- Marked As Answer by PCradit Wednesday, May 12, 2010 11:00 PM
-
Wednesday, May 12, 2010 11:00 PM
Thanks for the reply, and yes saw the KB899158 and resolved that issue and the SQL databases sizing issue's that started the MOM problems. The two links below are great references for preventling the related issues from occurring, unfortunately we didn't see this prior to our deployment and went with the default setting. At the time, everything was fine, but as soon as we stated mananging 1400+ clients the databases had no room to grow. Nevertheless, I would highly recommend that these be carefully considered when planning for or troubleshooting a related FCS/MOM problem.
FCS reporting database sizing (and other common FCS issues):
http://blogs.technet.com/fcsnerds/archive/2008/09/25/fcs-with-mom-2005-database-guidance.aspx
How to reduce the number of days to retain FCS reporting data:- Marked As Answer by PCradit Wednesday, May 12, 2010 11:00 PM

