Scott,

Frank

On 8/18/08 11:17 PM, Scott Bingham wrote:

Hello Frank,

This is indicating that the Microsoft has told us that we must save a copy
of file slanaccel.exe (via the System Writer), but we find that the file
does not exist.

After Googling for this file, it appears to be used with the slanaccel
Service in pre-releases of Hyper-V, but was eliminated (or maybe merely
disabled by default) from the RTM version of Hyper-V, but Microsoft has
failed to clean up properly.  I believe that you will need to enable the
role and make it healthy, or else delete the service (probably by the SC
commandline utility).

Thanks,
_Scott

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Francis Swasey
Sent: Friday, August 15, 2008 8:31 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Windows Server 2008 client with NW 7.3.3 Server

We have just connected our second or third Windows Server 2008 64-bit system to our existing NW 7.3.3 Server and are having issues with the VSS backup.

We installed the 64-bit NW 7.4.2 Windows client on the Microsoft Windows 2008 system.

These are the error messages we are getting:

* CLIENT_NAME:VSS SYSTEM FILESET:\ 3 retries attempted
* CLIENT_NAME:VSS SYSTEM FILESET:\ System Writer - Get file
attributes returned error 2 for VSS file
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16\windows\system32\slanac
cel.exe
* CLIENT_NAME:VSS SYSTEM FILESET:\ System Writer - ERROR: Failed
to save filegr files, writer = S
* CLIENT_NAME:VSS SYSTEM FILESET:\ System Writer - Error saving
writer System Writer
* CLIENT_NAME:VSS SYSTEM FILESET:\ System Writer - ERROR:
Aborting backup of saveset VSS SYSTEM FILESET: because of the error with
writer System Writer.
* CLIENT_NAME:VSS SYSTEM FILESET:\ System Writer - Error saving
* CLIENT_NAME:VSS SYSTEM FILESET:\ 39078:save: RPC error: RPC
cannot encode arguments

* CLIENT_NAME:VSS SYSTEM FILESET:\ * CLIENT_NAME:VSS SYSTEM FILESET:\ 7162:save: save of VSS SYSTEM

FILESET:\ to ozzie.uvm.edu failed

I have replaced the real client name with "CLIENT_NAME" in the above messages. A knowledgebase search on Powerlink has turned up one case where a reboot cleared the issue and there was no real knowledge of what the problem was.... before I open an issue with EMC.... Has anyone run into this and know what caused it?

Thanks,

--
Frank Swasey                    | http://www.uvm.edu/~fcs
Sr Systems Administrator        | Always remember: You are UNIQUE,
University of Vermont           |    just like everyone else.
 "I am not young enough to know everything." - Oscar Wilde (1854-1900)


To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER