Operating System Files Are Unstable Following EPM System 11.1.2 Installation on Windows 2008 Server

Operating System Files Are Unstable Following EPM System 11.1.2 Installation on Windows 2008 Server [ID 1243494.1]

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

Modified 26-OCT-2010 Type PROBLEM Status PUBLISHED

In this Document
Symptoms
Cause
Solution



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



Applies to:
Hyperion Financial Data Quality Management - Version: 11.1.2.0.00 and later [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms
After running the EPM system installer and rebooting the Windows 2008 server the machine is unreachable.

The 'Server' service (Lanman) is not running successfully.

The Server is a brand new server with the Operating System installed from scratch. The EPM System is installed using the installer. Following the installation the server is rebooted. When the reboot is complete, the connection to the server with RDP does not function.


Many windows services are not running (i.e Server service).

OS is Windows 2008 Standard x64 with SP2


Cause

The Windows System File Checker was ran on the server following the installation. According to the logs generated from the file checker the 'atl.dll' file was corrupted. The atl.dll file is part of Microsoft Visual C++ 2005 SP1 (vc2005sp1) (a component of the EPM installer) and Microsoft Visual C++ 2008 SP1 (vc2008sp1) which was installed before the EPM installation process.


Solution

In safe mode run the windows system file checker tool:

System File Checker gives an administrator the ability to scan all protected files to verify their versions. If System File Checker discovers that a protected file has been overwritten, it retrieves the correct version of the file from the cache folder (%Systemroot%\System32\Dllcache) or the Windows installation source files, and then replaces the incorrect file. System File Checker also checks and repopulates the cache folder.

You must be logged on as an administrator or as a member of the Administrators group to run System File Checker. If the cache folder becomes damaged or unusable, you can use the sfc /scannow, the sfc /scanonce, or the sfc /scanboot commands to repair its contents.


System File Checker Tool Syntax
Sfc [/Scannow] [/Scanonce] [/Scanboot] [/Revert] [/Purgecache] [/Cachesize=x]

/Scannow: Scans all protected system files immediately and replaces incorrect versions with correct Microsoft versions. This command may require access to the Windows installation source files.