If two people try to start Blueworx Voice Response at the same time, one of them will receive the following message:
Blueworx Voice Response is being started by another user.
Automatic retry will be attempted in 3 minutes...
The startup sequence continues to retry until the first user has completed startup, or until it times out (after 15 minutes).
If Blueworx Voice Response is abnormally terminated during the startup sequence, you may receive the same message, even though you are the only person trying to start Blueworx Voice Response. In this case, the problem is caused by files that were created during the initialization sequence being left behind when Blueworx Voice Response was abnormally terminated. You can clean up these files using the following procedure.
Start
ps -def | grep vaeinit
The system displays a list of all processes with vaeinit in their names. (This includes the grep vaeinit process itself, which you can ignore.)
ps -def | grep NODEM
The system displays a list of all processes with NODEM in their names. If there is a vaeinit entry and a NODEM entry, either Blueworx Voice Response is already running, or someone else may be trying to start it. Do not attempt to clean up the files.
/usr/lpp/dirTalk/tools/DTforce.clean
Next step: Now use vaeinit to start up in the usual way, as described in Starting Blueworx Voice Response.