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 |
|---|
| Diskeeper "Can not/failed to initalise as listener" message keeps coming up (does not apply to Windows 9X). |
Answer |
|
Please make sure you have build 9.0.511 and higher to correct this issue. Run 'Check for Updates' within the Diskeeper interface to make sure that you receive the latest setup. If you are running build 511 and are still experiencing issues, please perform the following: We have found that some systems may have a restriction in the registry that does not allow administrator access to the Diskeeper registry keys, which is why the error messages 'Diskeeper could not initialise as listener' or 'Connect to service' will come up. Please find the steps below to allow you to utilise Diskeeper. Here's how to allow administrator access to the Diskeeper registry keys. (Please note: This fix does not apply to Windows 9X) Before you begin any editing of the registry, always update your emergency repair disk (ERD). If you do not have a repair disk, please use the 'Registry backup procedures and perform the backup then proceed to the 'Could not Initialise Registry fix section. Registry Backup: Go to Start and then Select 'Run Could not Initialise (or connect to service) Registry Fix: 1. From the Desktop, click START, then RUN You should then be able to operate Diskeeper from an administrator account. If you are still running into problems with Diskeeper, please click the 'Did not solve link below and complete the form on the issue.
|
