We had a box that was getting the error except its 0x00000000 .

Legato has a 7.1.3 client that has some debugging hooks.  Running this
version it returned a 1450 code or something like that.  Turned out the
client needed a nonpagedpool memory parameter adjusted.  This solved
the problem; although on a similar box with less physical ram, the
techinique did not work.   It has to do with physical ram, adding additional
page file/swap space did not help.

I apologize I do not recall the exact parameter changed. I can find out
the exact value that was changed.  There was a microsoft document about it.


Robert Maiello
Pioneer Data Systems



On Thu, 21 Jul 2005 17:30:22 +0200, Kuin, CNM <CKuin AT WLZ DOT NL> wrote:

>> -----Original Message-----
>> From: Olaf Zaplinski [mailto:o.zaplinski AT BROADNET DOT DE]
>> Sent: dinsdag 12 juli 2005 18:06
>>
>> has somebody seen this before?
>>
>> -- Unsuccessful Save Sets ---
>>
>> * data-ber:SYSTEM STATE:\ 1 retry attempted
>> * data-ber:SYSTEM STATE:\ Registry - Cannot save Registry key
>> SOFTWARE:
>> 0x00000006
>> * data-ber:SYSTEM STATE:\ Registry - Error saving
>> * data-ber:SYSTEM STATE:\ save: RPC error: RPC cannot encode arguments
>> * data-ber:SYSTEM STATE:\ save: save of SYSTEM STATE:\ failed
>>
>> According to the Netw

orker KB this indicates that the Windows
>> machine's
>> pagefile is too small, but here it is of 1,5 GB size.
>>
>> Any ideas?
>I have a similar error on a NT4 SP6a machine. (Legato 7.1.2 + LGTpa66980)
>* s1.wlz.nl:SYSTEM STATE:\ 1 retry attempted
>* s1.wlz.nl:SYSTEM STATE:\ Registry - Cannot save Registry key SECURITY:
>0x00000570
>* s1.wlz.nl:SYSTEM STATE:\ Registry - Error saving
>* s1.wlz.nl:SYSTEM STATE:\ save: RPC error: RPC cannot encode arguments
>* s1.wlz.nl:SYSTEM STATE:\ save: save of SYSTEM STATE:\ to
>backupserver.wlz.nl failed
>
>Backups ran fine until the machine restarted earlier this week.
>According to support this should probably be fixed by a post SP6a hotfix.
>However, MS doesn't support NT4 anymore :(
>Even if I knew which hotfix, I can't request one from MS...
>
>The error could be caused by a software installation which finished it's
>task after reboot and probably broke up something...
>The last installation that didn't work out, prior to the reboot, was on
>April 18th this year. (by a colleague of mine)
>
>If anyone has any idea...
>
>With regards,
>Cor Kuin
>Sysadmin
>Waterlandziekenhuis
>The Netherlands.
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listserv.temple DOT edu or visit the list's Web site at
>http://listserv.temple.edu/archives/networker.html where you can
>also view and post messages to the list. Questions regarding this list
>should be sent to stan AT temple DOT edu
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=