No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


VSM can't start the topology process

Publication Date:  2012-09-26 Views:  125 Downloads:  0

Issue Description

After restart the VSM server, found that topology process failed to start. Check the log \ server log \ \ iMAPTopo_p51_ *, printing "CIPScopeIDManager init failed!". And start network topology successfully at the command line manually.

Alarm Information


Handling Process

Due to environmental factors, the topology can start after renovate the environment. Restoration approach is as follows:
Step 1: at the windows2003 32-bit operating system, changed the SYSTEM user permission as permit in the c:\windows\system32\cmd.exe. At Windows2003 64 - bit operating SYSTEM, changed the SYSTEM user permission as permit in the c:\windows\SysWOW64\cmd.exe.
Step 2: If the office site frequent appearance operating system file permission is modified lead to the problem that failed to start topology, change the start-user of the network management. The changing steps as chart the shows: (according to the serial number operation)

Root Cause

After confirmation, the problem that failed to start the office site topology was because the operating system cmd. exe file permission is modified. It used the windows2003 32-bit operating system at the beginning, and the modified file path is: c:\windows\system32\cmd.exe. It used the windows2003 64-bit operating system at the second time, the modified file path for: c:\windows\SysWOW64\cmd.exe.