UNSOLVED
problem with savepnpc
Hello, I have a problem with backing up 2 clients when "savepnpc" is used.
When backup starts the "preclntsave.exe" successfully shuts down an SQL-Server instance. After that the save sets also run successfully. But the "pstclntsave.exe" doesn't start the script in the group.res. In logfile savepnpc.log there are entries:
17.12.2006 23:31:32 pstclntsave: Client is still active in the worklist.
17.12.2006 23:31:32 pstclntsave: Worklist not complete. Some saves are still running.
For me it seems that the "pstclntsave.exe"-process doesn't get the info that "preclntsave.exe" and save-commands (all savesets) ran successfully. So the post-commands aren't executed until the savepnpc-timeout occurs or when the group is manually stopped.
This is the environment:
Networker Server 7.2.1 on Solaris9
2 clients with savepnpc-problems on W2K SP4
I have tried different networker client versions up to 7.3.2 without success. I suppose the problem maybe came with a MS Windows patch...?
Thanks in advance for your help.
When backup starts the "preclntsave.exe" successfully shuts down an SQL-Server instance. After that the save sets also run successfully. But the "pstclntsave.exe" doesn't start the script in the group.res. In logfile savepnpc.log there are entries:
17.12.2006 23:31:32 pstclntsave: Client is still active in the worklist.
17.12.2006 23:31:32 pstclntsave: Worklist not complete. Some saves are still running.
For me it seems that the "pstclntsave.exe"-process doesn't get the info that "preclntsave.exe" and save-commands (all savesets) ran successfully. So the post-commands aren't executed until the savepnpc-timeout occurs or when the group is manually stopped.
This is the environment:
Networker Server 7.2.1 on Solaris9
2 clients with savepnpc-problems on W2K SP4
I have tried different networker client versions up to 7.3.2 without success. I suppose the problem maybe came with a MS Windows patch...?
Thanks in advance for your help.
- In this case problem could be server side even that is not what one would think. As you are on 7.2.1 install 7.2.2 jumbo patch version on both server and client and see what happens then. If it doesn't work ask your support to provide debuging steps for savepnpc to see what is really going on.
- There is a small part where server is involved too, but this is really minor and I would not expect to influence it.
If you get an issue with win2k SP4 only it could be something with build or patch level then. To get it work you will still need to support to identify what exactly is failing and why and if that would be MS fault you would need to provide that data then to them (to obtain fix).
otmanix
2 Intern
•
52 Posts
329
0
Posted December 19th, 2006 01:00
Do you really think it might be a server problem? I forgot to mention that there are other clients (W2K3, Solaris, Linux) in the environment which also use "savepnpc" and there are no problems. The strange behavior only occurs on the 2 W2K SP4 clients.
Otmar