Frequently Asked Questions

Chances are, others have the same questions that you do. Therefore, we have taken the common questions for Diskeeper, Sitekeeper and Undelete and provided the answers (and the questions) below in our Frequently Asked Questions section. Simply select the product below that you have questions about. If you can’t find the answer you’re looking for, you can submit a tech support question here.

Diskeeper | Sitekeeper | Undelete

Question
Snap-In failed to Initialise.
Answer
We suggest that you find and delete 2 files, mmc.exe and mmcndmgr.dll, which should be in WINNT\system32 (under Windows NT), or in WINDOWS\system (under Windows 95/98/ME). Then re-install Diskeeper. This should cause the reinstallation of the Microsoft management console; which should correct the problem. If the problem continues, the problem is likely with the MMC and your local security settings in the registry. The file system path to the .msc file (f:\Program Files\Executive Software\DiskeeperSvr\Diskeeper.msc” may be too long a path for the software to launch successfully. This will occur when the 8dot3 filename generation turned off via the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem, with the value NtfsDisable8dot3NameCreation set to 1. This may also have been set by using the Policy Editor. Set the value to 0 or use the Policy Editor to re-enable the 8dot3 filename generation to solve the problem. Another way of handling the issue is to install DISKEEPER to an 8dot3 compliant directory name like the Execsoft\Diskeep that was the default in previous DISKEEPER versions. It is also possible that the problem may be damaged files on the disk. If the above has no affect, running CHKDSK may correct the problem.

Question

Snap-In failed to Initialise.

Answer

We suggest that you find and delete 2 files, mmc.exe and mmcndmgr.dll, which should be in WINNT\system32 (under Windows NT), or in WINDOWS\system (under Windows 95/98/ME). Then re-install Diskeeper. This should cause the reinstallation of the Microsoft management console; which should correct the problem.

If the problem continues, the problem is likely with the MMC and your local security settings in the registry. The file system path to the .msc file (f:\Program Files\Executive Software\DiskeeperSvr\Diskeeper.msc” may be too long a path for the software to launch successfully. This will occur when the 8dot3 filename generation turned off via the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem, with the value NtfsDisable8dot3NameCreation set to 1. This may also have been set by using the Policy Editor. Set the value to 0 or use the Policy Editor to re-enable the 8dot3 filename generation to solve the problem.

Another way of handling the issue is to install DISKEEPER to an 8dot3 compliant directory name like the Execsoft\Diskeep that was the default in previous DISKEEPER versions.

It is also possible that the problem may be damaged files on the disk. If the above has no affect, running CHKDSK may correct the problem.

<<Back