最佳解答者
All the .msc can't open

問題
解答
-
Dear Customer,
If the issue persists, the issue can be caused by the following factors:
1. Corrupt MMC configuration file
2. File association for .msc file is corrupt
I suggest we try the followings to troubleshoot the issue:
1. Delete Corrupt MMC configuration file
-----------------------
The MMC configuration file is located in the Application Data folder that is associated with the user account:
C:\Documents and Settings\%username%\Application Data\Microsoft\MCC
Please delete existing files in this folder and a new one will be generated automatically next time when .msc files run.
Then test if you can directly run a .msc file. Click Start->Run, type eventvwr.msc and click OK. What's the result
If the issue persists, please try the next step:
2. Check .msc file association
--------------------
a. Right click on a .msc file such as C:\Windows\System32\eventvwr.msc and click Open With->Choose Program
b. Ensure "Microsoft Management Console" is selected.
3. Replace the registry key for .msc file association:
----------------
a. On another working Windows 2003 server, open Registry Editor
b. Export the following registry key to a .reg file such as msc.reg
[HKEY_CLASSES_ROOT\.msc]
[HKEY_CLASSES_ROOT\MSCFile]
c. On the problematic server, delete the above registry keys.
d. Copy the exported file .reg file to the problematic server, and then double click it to import the registry file.
Then please restart the server and test the issue. What's the result?
If you have any questions or concerns, please feel free to let me know. I will be glad to help.
I look forward to your reply.Sincerely,
Tom Zhang2008年11月25日 上午 02:29版主
所有回覆
-
I think this could be caused by system problem of domain controller.(You acn try restart server if possible)
Check if netlogon, sysvol folders , are shared properly on domain controller.(Sometime they could disappear for some reason.Domain controllers need them shared for running domain policy/logon script/authentication stuff.. you need to re-share them if they are missing.
normally [netlogon] local path at
C:\WINDOWS\sysvol\sysvol\domain\SCRIPTS
[sysvol] local path at
C:\WINDOWS\sysvol\sysvol\
another related issue from microsoft
2008年11月12日 上午 04:03 -
Dear Customer,
At this moment, I'd like to suggest you try the following steps to troubleshoot the issue:
1. Click Start, click Run, type cmd , and then click OK.
2. At the command prompt, type cd %windir%\system32 , and then press ENTER.
Note The %windir% folder is the folder where you installed Microsoft Windows.
3. Type the following lines, and press ENTER after each line:
Regsvr32 Msxml.dll
Regsvr32 Msxml2.dll
Regsvr32 Msxml3.dll
4. Type exit , and then press ENTER to close the command prompt window.
5. Restart the computer.
I appreciate your time and cooperation. If anything is unclear, please feel free to let me know. I am looking forward to hearing from you.Have a nice day.
Sincerely
Tom Zhang2008年11月12日 上午 09:32版主 -
If you found this problem after you cleared the virus.
This could be caused by something in system was already damaged by the virus.
Here is a suggestion, but may not very good for the system:
Try create a new user account, put it into administrators , domain admin, enterprise admin group and delegate all rights to that user and try again(Some years before I got simular problem that I can't modify exchange installation, I create a temp account and set these).
The worst case is you may need to restore system state(If you have regularly backup your system state).
2008年11月13日 上午 07:50 -
Dear Customer,
If the issue persists, the issue can be caused by the following factors:
1. Corrupt MMC configuration file
2. File association for .msc file is corrupt
I suggest we try the followings to troubleshoot the issue:
1. Delete Corrupt MMC configuration file
-----------------------
The MMC configuration file is located in the Application Data folder that is associated with the user account:
C:\Documents and Settings\%username%\Application Data\Microsoft\MCC
Please delete existing files in this folder and a new one will be generated automatically next time when .msc files run.
Then test if you can directly run a .msc file. Click Start->Run, type eventvwr.msc and click OK. What's the result
If the issue persists, please try the next step:
2. Check .msc file association
--------------------
a. Right click on a .msc file such as C:\Windows\System32\eventvwr.msc and click Open With->Choose Program
b. Ensure "Microsoft Management Console" is selected.
3. Replace the registry key for .msc file association:
----------------
a. On another working Windows 2003 server, open Registry Editor
b. Export the following registry key to a .reg file such as msc.reg
[HKEY_CLASSES_ROOT\.msc]
[HKEY_CLASSES_ROOT\MSCFile]
c. On the problematic server, delete the above registry keys.
d. Copy the exported file .reg file to the problematic server, and then double click it to import the registry file.
Then please restart the server and test the issue. What's the result?
If you have any questions or concerns, please feel free to let me know. I will be glad to help.
I look forward to your reply.Sincerely,
Tom Zhang2008年11月25日 上午 02:29版主 -
Hi, Tom !
I have absolutely same problem as davidfung does, including W32.SillyFDC virus cleaned, so can I report too ?
My OS is WinXP SP2, can't open any .msc file (Access denied error). Can run mmc.exe and open them from there, but as soon as another .msc is run from console (gpedit.msc when you open GPO for example) it fails again.
I want to thank you for your last post, cause point 3 did the job. Branches [HKEY_CLASSES_ROOT\.msc]
were identical on both problem and good workstations, but replacing the [HKEY_CLASSES_ROOT\MSCFile] from good WS to bad one made .msc files working again. No restart needed.I'm only sorry I didn't save the bad branch to report.
So I assume the reason for this problem was W32.SillyFDC virus that was cleaned but registry changes went unnoticed by Symantec OfficeScan.
Thank you for your efforts,
Sincerely,
Andrey Golubev,
MCSE
2008年12月5日 下午 01:34