Parse error in Windows client

Question

Hello, I am having Networker 7.3.2 installed on Windows 2003 server. While taking backup of a Windows client (actually Windows cluster shared drive data), I am getting 'parse error' like C:\Program Files\Legato
sr	mp\sd000025 line 1: parse error C:\Program Files\Legato
sr	mp\sd000025 line 2: parse error C:\Program Files\Legato
sr	mp\sd000025 line 3: parse error C:\Program Files\Legato
sr	mp\sd000025 line 4: parse error C:\Program Files\Legato
sr	mp\sd000025 line 5: parse error C:\Program Files\Legato
sr	mp\sd000025 line 6: parse error. I want to know, what is this error about ? and how to remove this error from appearing in my savegroup information. Regards, R.Thandayuthapani

dk3 · Answer

It would be a good idea to skip Networker's tmp directory with a directive...

rtpani1 · Answer

OK..will try that today. For this I need to create a local directive and place it under C:\Program Files\Legato
sr directory. Am I correct ??

dk3 · Answer

You can have directives on both client or server side. In my Networker tmp directory there is a file named nsr.dir containing the following line:

skip: * .?*

Did you perhaps delete that directive file when cleaning up Networker's tmp directory the last time?

ble1 · Answer

OK..will try that today. For this I need to create alocal directive and place it under C:\ProgramFiles\Legato
sr directory. Am I correct ?? In this specific case it would under C:\Program Files\Legato
sr	mp. As dk said, by default local directive (nsr.dir) is created by default there to skip whole content of directory - did you remove it or manipulate it somehow?

rtpani1 · Answer

Yes, the nsr.dir file exists & no tampering with the file done.

The parse error is seen in this client only. We have other clients where there are no such messages. OFO is running on this client. Can it cause any problem ?

ble1 · Answer

I'm not sure what OFO is... did you mean OFM perhaps? You can easily see if that is related by disabling it temporary. This message is usually seen with corrupted directives. If that would not be the case then issue would be with temporary files created by client input in a way which is not expected by NW when parsing their output to build savegrp completion results. If for example fields are not there where they are supposed to be you will get parse error. The only way to check that is to really inspect tmp files used for these sessions. Debug mode might show that too.

NetWorker

Was this post helpful?