Network and Storage Protocols

File Policy for Enterprise Vault keeps disconnecting

whittlescott
4,862 Views

Help ......

Abit of background information .....

We have been having problems with EV's File policy since the software has been introduced but only on a weekly basis and have always been able to reconnect (either by stopping & starting the admin service or failing over to other EV server) and then the policy stays connected for quite a while. About a month ago we upgraded our filer from ontap 7.2.4 to 7.3.2 and since this upgrade we have been having more problems with the EV file policy...... it has improved several things as now the policy will reconnect by itself but the problem is that it will now not stay connected for more that a couple of hours and thats if we are lucky.

A support call has been logged with Symantec and they have looked at the logs and they seem to be pointing the finger at the Filer... any ideas ?????

Enterprise Vault v8.0.3.1845

Errors messages :

Tue Mar 30 09:30:14 BST cifs.pipe.errorMsg: CIFS: Error on named pipe with \\evserver: Response incorrectly signed
Tue Mar 30 09:30:14 BST cifs.server.infoMsg: CIFS: Warning for server \\evserver: Connection terminated.
Tue Mar 30 09:30:14 BST smbrpc.exceptionCaught: CIFSRPC: An RPC exception with a server of type file policy server occurred.
Tue Mar 30 09:30:14 BST fpolicy.fscreen.server.requestError: FPOLICY: An attempt to make a file screen request to server \\evserver for policy ev-placeholder failed with error [0xc0020052].
Tue Mar 30 09:30:14 BST fpolicy.fscreen.server.droppedConn: FPOLICY: File policy server xxx.xx.xxx.xx for fscreen policy ev-placeholder has disconnected from the filer.
Tue Mar 30 09:30:14 BST fpolicy.fscreen.server.connectedNone: FPOLICY: File policy ev-placeholder (file screening) is enabled but no servers are connected to perform file screening for this policy.
Tue Mar 30 09:31:49 BST fpolicy.enable: FPOLICY: The file policy feature has been enabled.
Tue Mar 30 09:31:49 BST fpolicy.fscreen.server.connecting.successful: FPOLICY: File policy server \\evserver registered with the filer as a server for policy ev-placeholder successfully.
Tue Mar 30 09:34:38 BST cifs.pipe.errorMsg: CIFS: Error on named pipe with \\evserver: Response incorrectly signed
Tue Mar 30 09:34:38 BST cifs.server.infoMsg: CIFS: Warning for server \\evserver: Connection terminated.
Tue Mar 30 09:34:38 BST smbrpc.exceptionCaught: CIFSRPC: An RPC exception with a server of type file policy server occurred.
Tue Mar 30 09:34:38 BST fpolicy.fscreen.server.requestError: FPOLICY: An attempt to make a file screen request to server \\evserver for policy ev-placeholder failed with error [0xc0020052].
Tue Mar 30 09:34:38 BST fpolicy.fscreen.server.droppedConn: FPOLICY: File policy server xxx.xx.xxx.xx for fscreen policy ev-placeholder has disconnected from the filer.
Tue Mar 30 09:34:38 BST fpolicy.fscreen.server.connectedNone: FPOLICY: File policy ev-placeholder (file screening) is enabled but no servers are connected to perform file screening for this policy.
Tue Mar 30 09:34:38 BST fpolicy.fscreen.server.completionRequestLost: FPOLICY: File screen server xxx.xx.xxx.xx for policy **unknown** completed a screen on ONTAP_ADMIN$\vol\vol_cifs_groupdata\filename.doc but the original request was not found.
Tue Mar 30 09:34:38 BST fpolicy.fscreen.server.completionRequestLost: FPOLICY: File screen server xxx.xx.xxx.xx for policy **unknown** completed a screen on ONTAP_ADMIN$\vol\vol_cifs_groupdata\filename.pdf but the original request was not found.
Tue Mar 30 09:36:19 BST fpolicy.enable: FPOLICY: The file policy feature has been enabled.
Tue Mar 30 09:36:19 BST fpolicy.fscreen.server.connecting.successful: FPOLICY: File policy server \\AYVS0017 registered with the filer as a server for policy ev-placeholder successfully.

Anyone seen this before or got any ideas on where we can go from here ?????

Cheers

Scott

4 REPLIES 4

jthaloor
4,863 Views

It appears like CIFS signing is enabled and maybe you have a clock discrepancy between the Filer and the EV server?

whittlescott
4,863 Views

Thanks for your responses ...... some more information ......

cifs.signing.enable          off  -  and I have checked the time settings and they are correct as the filer gets its time from our ntp server.

So looking at the link is there any point of us upgrading to 7.3.3 as we already have cifs.signing off ????

Any ideas ???

Cheers

whittlescott
4,863 Views

Thanks for your help ..... upgraded Ontap to 7.3.3 and that has fixed it

Public