Technical Helpweb

Dialogic® DM3 and JCT Media Boards

Dialogic® Services Report System has not Rebooted


Summary
Dialogic® Services report system has not been rebooted after installation and reboot.

Symptom:
The Dialogic® System Release 6.0 PCI for Windows® requires a reboot after installation. Until this reboot occurs, the system will not allow you to start the Dialogic® Configuration Manger (DCM) or to start the Dialogic Services. If the system reports this error even after a reboot, then the instructions in this technical note will remove the check for a reboot.

Reason for the problem:
This problem should not occur in a system that is running normally. If this occurs, it may indicate a problem with the Dialogic install or with the Windows® operating system. This technical note may not resolve every condition in which the symptoms occur, but it can be used to isolate the cause for the general failure. If the symptoms occur, please ensure that the version of Windows is supported by the Dialogic System Release you have installed.

Fix / Solution:
Attached to this technical note is a file called not_rebooted.reg. . Please see Attachments section below. This registry file will remove the registry key that stops the DCM and the Dialogic Services from running until a reboot occurs. Save this file on the file system of the system exhibiting the error, and run it as an executable. Windows will ask you to confirm execution of this file. Accepting this dialog will remove the DlgcNotRebooted key from your registry and will allow the DCM to start, bypassing the OS check for reboot. This should NOT be used to simply bypass the check for reboot.

Product List
Dialogic® System Release 6.0 PCI for Windows® - all Service updates.

Attachments not_rebooted.reg (Zip file)





Feedback

Please rate the usefulness of this page:  
0 - not useful at all
1 - potentially useful
2 - quite useful
3 - very useful
4 - exactly the information I needed     

Please enter a comment about this page: