savepnpc errors with fix applied.

[pmidds]

I've applied fix NS561A0 which says it fixes problems with savepnpc I also applied fix NS561A1. Still the below error persists. I've now raised a call with Siemens ( Its a Fujitsu-Siemens installation of networker ). Has anyone had this problem and solved it ? Did you use any of the above fixes or is there a specific patch for this problem ?

Platform Solaris 5.8. Networker 6.1.3 build 428.


* brats02a:C:\ 1 retry attempted
* brats02a:C:\ preclntsave: The tmp file exists. Another savepnpc may be running.
* brats02a:C:\ Preclntsave exiting......!
* brats02a:C:\ savepnpc: Unable to run preclntsave successfully, see savepnpc.log for possible causes.

Thanks.

 

[TDun]

Does the tmp file exist? If so, have you deleted it and re-tried?

 

[pmidds]

Hi TDun, yes I deleted the *.lck files from \nsr\res on the client and cleared out the tmp files on the server but still the same result.

From the savepnpc log on the client I get the following errro - preclntsave: The tmp file for the group exists. Another savepnpc may be running. It certainly seems to point to an offending tmp file but I can't find any more to delete.

Cheers.

 

[TDun]

If you have it, look in /nsr/tmp

 

[pmidds]

Deleting tmp files from \nsr\temp is the way support is sending me. Unfortunately there are no *.tmp files in this folder ( and delete all files in there before testing as well )

 

[TDun]

Do you have any .lck files in the tmp or res directories?
If so, delete these and re-try.

 

[moody]

Once you apply the patch you will see these errors show up in the SAVEPNPC log. You should see one for every file system you have on your server except for the first one. Basically how it was explained to me was the first file system runs the pre stuff and then puts a tmp file in the tmp directory. Then as each additional file system is started the savepnpc looks for the tmp file flags the error and does not re-run the pre stuff. Once all the file systems have been backed up savepnpc deletes the tmp file and runs the post stuff.

Bottom line, you should be able to ignore these informational errors. Make sure that your pre and post commands are running properly, you then should be golden.