Export (0) Print
Expand All

Troubleshooting System Center 2012 - Service Manager Deployment Issues

Updated: January 17, 2012

Applies To: System Center 2012 - Service Manager Release Candidate

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

An installation log file is captured during the installation of System Center 2012 – Service Manager. After Service Manager is running, various events are captured in the Windows Event Log. In addition, there are some Windows PowerShell commands that you can use to help troubleshoot data warehouse jobs. For more information, see "Troubleshoot Data Warehouse Jobs" in the Administrator's Guide for System Center 2012 – Service Manager Beta.

Installation Log Files

A log file, SCSMInstall.log, captures the progress of the installation. You can use this log file to troubleshoot a failed installation. You can find this log file in the %temp% folder. To troubleshoot installation problems, you can open the log files and search for a line that reads Return Value 3. If you find such a line in the log file, look above this line for any indication that a particular step failed.

Event Logs

For this release, Service Manager event logs are located in Event Viewer, in the Application and Service Logs folder, in the Microsoft folder, and then listed as Operations Manager.

Create Database error

During setup, when you were configuring Service Manager or data warehouse databases, you were given the opportunity to specify how much disk space to allocate for each database. The default setting is 2,000 megabytes (MB) (2 gigabytes (GB)). In addition to the disk space that is required for the database, Service Manager sets aside additional space for file groups and log files. The additional space that is required for the file groups and log files can be equal to the space that is required for the database.

If there is insufficient disk space available, a message appears, indicating that an error occurred during execution of a custom action: _CreateDatabase. The installation stops before permanent changes are made. If you examine the Service Manager setup log, you find the following string:

Additional Error Description : MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file

You have to either increase the amount of free disk space that is available or reduce the amount of space that Service Manager allocates for the database, and then attempt the installation again. If you are installing Service Manager in a nonproduction environment, you can specify as little as 500 MB for the database.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft