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
On Windows NT 4.0 Terminal Server "Unable to launch or to connect to the Diskeeper service. Possible causes are that another Diskeeper process is currently connected to this computer or Diskeeper is not installed correctly".
Answer
The problem is that NT4 terminal server uses the first person who logged in to launch Diskeeper. If this person is not the administrator who logged in afterwards on the console, COM and Diskeeper get confused. If the administrator logs into the console first before anybody else (even as a client session) and stays logged in, he will always be able to run Diskeeper. This is why it works if the administrator logs in and others log in afterwards. However, this is not very workable. The other option is to configure the Diskeeper GUI to always have COM launch the GUI as a particular local administrator. For this to work, however, this will mean that Diskeeper will only be able to be run from one local account. This is workable if there is only one person or one login who would regularly want to run Diskeeper. Note that this issue does not exist on Windows 2000 where COM selects the user actually logged in to the console, and does not just pick the first user session, client or otherwise. To modify the DCOM setting: 1. Log in to the Terminal Server console locally as a user with admin privileges. 2. Go to start>run and type "dcomcnfg". 3. In the dcomcnfg dialog, double click on the "Diskeeper GUI" application. 4. Select the "identity" tab. 5. Change the setting from "interactive user" to "this user" and select the browse button 6. Select the local system name from the "List Names From:" pull down menu. 7. Select the local username that you wish to run Diskeeper and select the "Add" button. 8. Type in the password (including confirmation) for the user you selected launch Diskeeper in step 7. 9. Select "OK" and then "OK" again. 10. If the user that was input into the DCOM setting is not the same user that logged in, log out and back in as the local user specified in the DCOM settings. 11. Start Diskeeper. It may be that the Diskeeper service is in a problematic state from previous attempts to start under the above.

Question

On Windows NT 4.0 Terminal Server "Unable to launch or to connect to the Diskeeper service. Possible causes are that another Diskeeper process is currently connected to this computer or Diskeeper is not installed correctly".

Answer

The problem is that NT4 terminal server uses the first person who logged in to launch Diskeeper. If this person is not the administrator who logged in afterwards on the console, COM and Diskeeper get confused. If the administrator logs into the console first before anybody else (even as a client session) and stays logged in, he will always be able to run Diskeeper. This is why it works if the administrator logs in and others log in afterwards. However, this is not very workable. The other option is to configure the Diskeeper GUI to always have COM launch the GUI as a particular local administrator. For this to work, however, this will mean that Diskeeper will only be able to be run from one local account. This is workable if there is only one person or one login who would regularly want to run Diskeeper. Note that this issue does not exist on Windows 2000 where COM selects the user actually logged in to the console, and does not just pick the first user session, client or otherwise.

To modify the DCOM setting:

1. Log in to the Terminal Server console locally as a user with admin privileges.
2. Go to start>run and type "dcomcnfg".
3. In the dcomcnfg dialog, double click on the "Diskeeper GUI" application.
4. Select the "identity" tab.
5. Change the setting from "interactive user" to "this user" and select the browse button
6. Select the local system name from the "List Names From:" pull down menu.
7. Select the local username that you wish to run Diskeeper and select the "Add" button.
8. Type in the password (including confirmation) for the user you selected launch Diskeeper in step 7.
9. Select "OK" and then "OK" again.
10. If the user that was input into the DCOM setting is not the same user that logged in, log out and back in as the local user specified in the DCOM settings.
11. Start Diskeeper.

It may be that the Diskeeper service is in a problematic state from previous attempts to start under the above.

<<Back