Start a Conversation

Solved!

Go to Solution

1 Rookie

 • 

9 Posts

109

August 27th, 2023 14:57

parse_ossr_info_file OSSR_Info.xml":[1] function not supported

Hello guys. for a few weeks now I have this issue with a windows server . 

there is a solution from Dell that says to try the solution in this Microsoft kb article KB000462622 , but that is not available. I cant find it. I suppose it says to set the client parallelism to 1 in networker  . but that didnt work. 

A server reboot solved the problem. however, it happened again in 2 days.  I cant just restart the server each time this happens . 

Vss writers were checked every time. they are all stable. and networker service was restarted  with renaming tmp and nsrladb folder  with no success . 

the networker version on both the client server and the backup server is 19.7.0.4 and the client's os version is Windows Server 2012 R2 Standard 6.3

The error is also visible in the OS's event viewer 

the main error is this :

parse_ossr_info_file: Could not load file "C:\Program Files\EMC NetWorker\nsr\tmp\efe0c9d7-ce21-4949-adb6-e09ce2aab2e6\OSSR_Info.xml":[1] function not supported

80880:save: Failed to process OSSR_Info.xml

80885:save: Failed to create OSSR_opaque_props

but here is the entire error message . maybe it helps 

any new ways I can try to solve this ? thanks 

suppressed 2851 bytes of output.

175315:save: Step (3 of 6) for PID-5280: Created the child save process for VSS Emitter on the client 'server' for the save set 'D:\'.

174920:save: Step (4 of 6) for PID-5280: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set 'D:\'.

174908:save:Saving the backup data in the pool 'pool'.

175019:save:Received the media management binding information on the host 'storage_node'.

174910:save:Connected to the nsrmmd process on the host 'storage_node'.

174922:save: Step (5 of 6) for PID-5280: Successfully connected to the target media device through the nsrmmd process on the host 'backup_server' for the save set 'D:\'.

174422:save: Step (6 of 6) for PID-5280: Reading the save sets and writing to the target device.

adejen03sapp12: D:\               level=incr,     64 MB 00:00:47     20 files

Completed savetime=1692978893

90015:save: The backup of VSS emit save set 'D:\' succeeded.

94694:save: The backup of save set 'D:\' succeeded.

174908:save:Saving the backup data in the pool 'pool'.

175019:save:Received the media management binding information on the host 'storage_node'.

174910:save:Connected to the nsrmmd process on the host 'storage_node'.

adejen03sapp12: WINDOWS ROLES AND FEATURES:\ level=incr, 4192 KB 00:00:07     19 files

Completed savetime=1692978970

174908:save:Saving the backup data in the pool 'pool'.

175019:save:Received the media management binding information on the host 'storage_node'.

174910:save:Connected to the nsrmmd process on the host 'storage_node'.

parse_ossr_info_file: Could not load file "C:\Program Files\EMC NetWorker\nsr\tmp\efe0c9d7-ce21-4949-adb6-e09ce2aab2e6\OSSR_Info.xml":[1] function not supported

80880:save: Failed to process OSSR_Info.xml

80885:save: Failed to create OSSR_opaque_props

90019:save: save of 'DISASTER_RECOVERY:\' to server 'backup_server' failed.

1 Rookie

 • 

107 Posts

September 12th, 2023 12:05

How did you try to find the KB000462622? As https://www.dell.com/support/kbdoc/en-us/000462622 forwards to newer KB number https://www.dell.com/support/kbdoc/en-us/000080503.


So if you have an actual login account, you should be able to see and find that? Is however a very old KB, and should even be fixed in nw8.2. The error example is even from 2014 (!).


"Cause

EMC Engineering has investigated this problem. A permanent fix is available. Contact the EMC Customer Support Center for assistance.

Resolution

Workaround:
 
Set the client parallelism to 1.

Solution:
 
Upgrading to NetWorker Client 8.2 fixed the problem and was able to keep the client's parallelism at 4.

Partner Notes

NW162199 - Scheduled backups of the DISASTER_RECOVERY:\ saveset fail with error "parse_ossr_info_file: Could not load file C:\Program Files\EMC NetWorker\nsr\tmp\OSSR_Info.xml"

"

Depending on the possible underlying issue, you might also wanna consider https://www.dell.com/support/kbdoc/en-us/000040315?lang=en and make sure to actually completely delete the NW directories before re-installing in case some permissions were screwed up?

We might have encountered similar issues on a system, but it is very likely related to the client itself, as also a nmm backup was failing, until a reboot was performed combined with NW reinstall. Possibly resource starvation or other issues being the cause, not related to NW itself really, so how is the system itself actually doing and being used and does that work correctly? So not just about stability of VSS writers but the system as a whole and how it is used as I assume someone/something is using the system?

"Cause

Security permission issue with the C:\Program Files\EMC NetWorker\nsr\tmp directory.

Resolution

Propagating the permissions of \tmp from the parent directory *may* resolve issue, however permanent fix is to:
  • Un-install NetWorker client software
  • Re-name (or delete) C:\Program Files\EMC NetWorker\ directory
  • Install NetWorker client software (specifying NW server etc as usual)
  • Run a new backup
This action causes the directory structure to be re-created with the correct security permissions.

"

No Events found!

Top