Start a Conversation

Solved!

Go to Solution

857

July 22nd, 2022 04:00

Unable to save system state

The VSS writers are fine  .

And I can’t find this file
87306:save: Incorrect directory specification on line 0 of 'C:\Program Files\EMC NetWorker\nsr\tmp\sd000001'.

C:\Program Files\EMC NetWorker\nsr\tmp\sd000001 line 0: illegal token

C:\Program Files\EMC NetWorker\nsr\tmp\sd000001 line 0: syntax error

 

is there something I can do about this ?

 

 

181407:save: Step (1 of 5) for PID-5032: Save has been started on the client

174412:save: Step (2 of 5) for PID-5032: Running the backup on the client for the save set 'pseudo_saveset'.

87306:save: Incorrect directory specification on line 0 of 'C:\Program Files\EMC NetWorker\nsr\tmp\sd000001'.

C:\Program Files\EMC NetWorker\nsr\tmp\sd000001 line 0: illegal token

C:\Program Files\EMC NetWorker\nsr\tmp\sd000001 line 0: syntax error

98263:save: Unable to write the ASR critical volume to saves struct for walker.

174424:save: Step (3 of 5) for PID-5032: Creating the snapshot for the selected save sets.

VSS OTHER: ERROR: VSS failed to process snapshot: Unable to create the VSS snapshot.

 

197048:save: Unable to save the SYSTEM STATE save sets and create the snapshot: Unable to create the VSS snapshot.

 

 

176571:save: Step (4 of 5) for PID-5032: Unable to complete the backup of the disaster recovery save sets. See the savegrp log to track the closure steps of the backup.

176572:save: Error occurred during the backup of the disaster recovery save sets.

 

2.4K Posts

July 22nd, 2022 14:00

VSS errors have become pretty rare since Windows 2008.

Of course one could investigate such errors more thoroughly. However, the easiest way to fix them is just to reboot the client and do a retry.

 

2.4K Posts

July 22nd, 2022 08:00

Once again, the usual questions:

  -  What is the OS version?

  -  What are the NW versions?

  -  Is this a NW server or a NW client?

  -  Has it worked before?

  -  Could it simply be that your OS disk is full?

 

10 Posts

July 22nd, 2022 13:00

Sorry I forget about these . 

Its a windows server 2012 . 

Its networker 19.4.0.3 

And its nw client. 

It worked before of course and the disk is not full.  

No Events found!

Top