Multiple SFW services stuck in a Starting state, causing system to hang at 'Applying computer settings...' during system startup
Article ID: 100000729
Updated On:
Description
Error Message
The \Program Files\veritas\Veritas Object Bus\Logs\vxisis.log* and the %vmpath%\logs\vm_vxisis.log both report the following error:
DATE TIME:Unexpected error: CPalService::init error code: 1669
DATE TIME:Unexpected error: CPalService::init error code: 1669
DATE TIME:CORBA Exception in CPalService::init: BAD_PARAM, IDL:omg.org/CORBA/BAD_PARAM:1.0
DATE TIME:CPalService init failed 0x:c1000001
DATE TIME:Error in loading the library csfinterfacep.dll
DATE TIME:Error in starting agent 0xc1000001
* On 64-bit sytems, the path to the vxisis.log is: \Program Files (x86)\veritas\Veritas Object Bus\Logs\vxisis.log
Cause
This happens if the configuration information for the Symantec Private Branch Exchange (PBX) is missing from the registry.
Resolution
This issue may be fixed by a repair installation. Otherwise:
0. If the computer is stuck at Applying Computer Settings, either boot into Safe Mode and set the Startup setting of the affected services to Manual; or connect via the Service Control Manager (SCM) from another node and set the Startup value of the affected services to Manual.
1. Create the following keys under:
x86:- HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxPBX.
x64:- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veritas\VxPBX.
| Key name | Key type | value |
|---|---|---|
| AuthUsers | REG_SZ | localsystem (please add this with a leading space) |
| DebugLevel | REG_SZ | 10 |
| Insecure | REG_SZ | 1 |
| InstallPath | REG_SZ | C:\Program Files\Veritas\VxPBX |
| PortNumber | REG_SZ | 1556 |
Table 1: Registry entries required for PBX to work correctly.
Note: Value of InstallPath key may vary the above path denotes the default install location on x86.
2. If any of the following services are running or stuck in 'starting', stop or kill them:
Veritas Action Agent. Appears as vxpal.exe in the Windows Task Manager.
Veritas Gridnode Agent. Appears as vxpal.exe in the Windows Task Manager.
Veritas Storage Agent. Appears as vxpal.exe in the Windows Task Manager.
Veritas Enterprise Agent. Appears as vxsvc.exe in the Windows Task Manager.
Note: If killing the services, it may be necessary to temporarily change the SCM Recovery action to Take No Action to prevent the services from being restarted. In addition, it may be necessary to use the taskkill utility to kill the processes by either process name or Process ID (PID). Run taskkill /? from a command prompt to determine proper syntax.
Examples:
taskkill /IM vxpal.exe /F /T
taskkill /PID 3069 /F /T
3. Restart the Veritas Private Branch Exchange service: > net stop vrtspbx /y > net start vrtspbx
4. Start the agents mentioned in step 2: > net start vxob > net start vxvm > net start actionagent > net start vxgn
Issue/Introduction
