![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy Connect 2.1 ; Prinergy Direct 2.1 ; Prinergy Access 2.1 ; Prinergy Powerpack 2.1 | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
||
|
|
||
Symptoms |
Either the Araxi service or the system state backup on the secondary server or render station fails to start. The system state backup service fails to start either from the system backup triggered after the database backup or if you manually attempt to start the AraxiSysStateBackup service on the server. |
|
|
|
||
Cause |
There may be multiple instances of NameServ.exe running on the system. Check Task Manager for multiple instances of "NameServ.exe" . |
|
|
|
||
Solution |
Run TLIST -T. Kill all the NameServ.exe processes running that are at the root. DO NOT kill the nameserv.exe that is a child process of IMR.EXE. :D:\WINNT\Profiles\ARAXI>tlist -t :System Process (0) :System (8) :... : Araxi.exe (2940) : imr.exe (2068) : nameserv.exe (2816) :nameserv.exe (2156) :nameserv.exe (2180) :nameserv.exe (2644) :nameserv.exe (1996) :nameserv.exe (928) In the example above, kill processes 2156, 2180, 2644, 1996 and 928. But do NOT kill process 2816. To kill the processes: Kill <process id> Example: kill 2156 Alternatively, you can stop Prinergy and kill all the instances of Nameserv.exe running on the server, or reboot the server. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
28 May 2003 |
|