Martynas,

It looks like pstclntsave.exe when executed is failing on that client. Actually, you said clients - are you getting indentical error on more that one client? If so, are trying to execute the same post command?

Can you try to make a test:
a) try to execute manually pre and post commands and see if it works fine (on the client that was failing)
b) try to replace post command with something fairly simple like echo something with redirection to the file
c) if b) would fail too try to restart nsrexecd (net stop nsrexecd and then net start nsrexecd) and retry b)
d) if c) would fail too try to restart machine and retry b)

I don't expect a) to fail, but check it out all. If b would not fail it would suggest that something withing post command that it being called is casuing this error. Adding debugging to script you call (I assume) should help. c and d are here just to eliminate usual suspects.

Hi,

Do you perform an upgrade of your Legato Networker Server ? The scripts in version 7.1.3 do not work the same as the previous versions

yes I did!
I've migrated from 7.11 to 7.13 to have ability to use domain groups for users.
What is the difference ? maybe you can describe shortly?

BTW: I have backup servers in a few locations. On some of clients I use precmd and pstcmd top stop and start databases and etc. there are different applications which do not startup after migration, but on some servers pstcmd works fine (networker version is the same 7.13). I've removed old *.res file and started group to create new *.res file after that filled it with required lines and scripts do not start precmd start and pstcmd do not. I've manualy ran scripts which it starts and stops, and everything works fine no errors but networker cannot execute it.


Message was edited by: mdabasinskas

Martynas,

The only issue with post cmd between 7.1.1 and 7.1.3 that I'm aware of is described in Support Note 70262 (LGTpa74194) where post command succeeds only if redirection of standard error (STDERR) is removed. You may wish to check that.

Having the same NW version and running the same post script may indicate problem on client side (even not necessary).

Did you try to make a test on clients where you have failute to use simple pre and post commands like echo > C:\Temp\pre.test and post.test just to see if that fails too or only with your specific start/stop script this error comes out?

Also, another thing to consider... try to set debug level. Both post and pre commands support debug level of 1, 2 and 3. According to manual. I didn't test it, but I assume if your backup command would look like savepnpc -D3 that should apply to both pre and post commands (once again, I didn't test it so far).

I've created test group and created grouname.res on client with simple echo Stop > test.txt on precmd and echo Start > test.txt and it works fine.
then I've removed old res files and started group to create new default res file but mine script did not started services from this side we can say that script have problems not savepnpc program. but manualy i can run script.

Can you send how your hroupname.res file looks like? Are you calling the script or you are trying to execute net start | stop command directly? If you are running the script, can you send how your script looks like (the one which is failing)? If you are running the script are you just listing path to your batch file or you use call command (not sure about win2k3, but it used to exist before)? Are you using full paths? Are you using spaces in paths and if yes do you use quotes, / or \\ in paths? Is the environment set when you call your post command exactly the same as it is when you call it manually? There could be number of small things here that could cause your error and I just tried to list few that I did see in the past.

A couple of things you can look at; most common issue with savepnpc is that it fails somewhere along the line and leaves lock files in the res/tmp directory so it is worth stopping both Networker server and client, clearing out this directory and restarting. Another thing you can do is delete and recreate the groupname.res file in case there is any corruption there.

Well, every time I had problem with pre and post scripts failing withou any changes in the system, I could solve it doing exactly that, removing the lock files and recreating the .res files.

If you can run those scripts manualy, that's what you should try....

Hi Gents,

this is an example of group.res file:

type: savepnpc;
precmd: "C:\\Stop_DB.cmd";
pstcmd: "C:\\Start_DB.cmd";
abort precmd with group: No;

this is a script Stop_DB.cmd:
net stop "CCURE800"

and Start_DB.cmd:
net start "CCURE800"

as you see nothing strange here... It works then I start manualy those scripts. But networker only start precmd but not pstcmd...

and after all I get messages on some of server in event log:
Reporting queued error: faulting application pstclntsave.exe, version 7.1.3.0, faulting module pstclntsave.exe, version 7.1.3.0, fault address 0x000016ce.
but this message appears not on all machines.

I've tried to delete all files in /tmp folder but this did not helped. I've created test group with test.res on server and it executed both scripts precmd and pstcmd.

any ideas?

I hate to come back to the same, but I have to ask... you said test.res was on the server... I assume we are talking about the same server as the one from where this actual group.res is failing, right? Second, did you try to reboot the client (whole machine) in question and see if you still have the problem.

Your setup is very simple and what you do should work. Now the question is if you get the error from event log during the call to pstclntsave or during it execution. To find out there edit start script to looks like following:
.................................
echo "here we go" >> C:\pst.log
time /T >> C:\pst.log
echo "see my env"
set > C:\set.pnpc
echo "and now starting the service"
net start "CCURE800"
.................................
Then go to command like and execute "set > set.cmd" and compare set.cmd and set.pnpc (in my case there was 200K difference). Everything missing could influence your problem so set it up in start script.

Also, check pst.log. If you have entries from echo command and timestamp then it means that problem is when calling net start command and in such case setting environment variables that are missing (from set.cmd) could address your issue.

Thanks for all of you. This problem is solved.
I've recreated *.res file and deleted all files in tmp folders. This solved the problem.