The following table contains a list of common FPolicy error messages, probable causes, and recommended actions, if any.
| Error message | Cause | Recommended action |
|---|---|---|
| fpolicy.fscreen.server.connectError severity="ERR" | This error is generated when the storage system encounters an error while attempting to communicate with an FPolicy (file policy) server. The communication failure will cause the storage system to break its connection with this server. The error can be due to network problems, security settings on the FPolicy server that deny access to the storage system, or hardware/software problems on the FPolicy server. The problem can also occur if a low memory situation on the storage system prevents the storage system from obtaining resources needed to perform the operation. |
Examine the error code to see if it helps point to the use of the problem. Examine the event logs of the FPolicy (file policy) server to learn if it has disconnected from the storage system and why. Examine the storage system's syslog for error messages which could provide clues. Correct any problems that are found such as network errors or hardware problems on the FPolicy server. Check to see if a software patch has been recently installed on the FPolicy server which may have changed security settings. |
| fpolicy.fscreen.server.closeError severity="ERR" | This error is generated when the storage system encounters an error while attempting to stop communication with an FPolicy (file screening) server. The error can be due to network problems or hardware/software problems on the FPolicy server. | Examine the error code to see if it helps point to the cause of the problem. Examine the event logs of the FPolicy (file policy) server to learn if it has disconnected from the storage system and why. Correct any problems that are found such as network errors or hardware problems on the FPolicy server. This error may not be an error. The storage system may be ending communication with the server because an error has occurred in an earlier attempt to communicate with the server. The error that occurs during the close of the connection may be a continuation of that error condition. |
| fpolicy.fscreen.server.requestError severity="ERR" | This error is generated when the storage system encounters an error while attempting to send a notification request to an FPolicy (file policy) server. The error can be due to network problems or hardware/software problems on the FPolicy server. The storage system will retry this notification with another server of this policy if the policy has multiple servers. Otherwise, the storage system will proceed based on the policy's setting for the required option. If the required setting is on, the storage system will deny the request. If required is off, the storage system will allow the client request to proceed. |
Examine the error code to see if it helps point to the cause of the problem. Examine the event logs of the FPolicy (file policy) server to learn if it has disconnected from the storage system and why. Correct any problems that are found such as network errors or hardware problems on the FPolicy server. |
| fpolicy.fscreen.server.requestRejected severity="ERR" | This error is generated when a storage system's notification request to an FPolicy (file policy) server is rejected by the FPolicy server. The error can be due to software problems on the FPolicy server. | Examine the error code to see if it helps point to the use of the problem. Examine the event logs of the FPolicy (file policy server to learn if it has created an error to explain the problem. The FPolicy server may have detected an internal error, or may be unable to accept more requests. |
| fpolicy.fscreen.server.pingRejected severity="ERR" | From time to time if the FPolicy server connection is idle the storage system will send a status request to learn the status of the FPolicy server. This error is generated when a storage system's status request to an FPolicy server gets an error. This error can occur if the storage system is unable to contact the FPolicy server, or the error can occur if the server returns an error to the storage system's request. The error can be due to network problems or hardware/software problems on the FPolicy server. The storage system will break its connection with the server when this request fails. | Examine the error code to see if it helps point to the cause of the problem. Examine the event logs of the FPolicy (file policy) server to learn if it has disconnected from the storage system and why. Correct any problems that are found such as network errors or hardware problems on the FPolicy server. |
| fpolicy.fscreen.server.completionUnexpectedState severity="ERR" | This error occurs when the FPolicy server has completed a screen request and returned a completion. However, the internal storage system state for this request is not valid. This completion message is ignored by the storage system. | |
| fpolicy.fscreen.server.requestStatusError severity="ERR" | This error occurs when the FPolicy server has accepted a screen request but has not reported the completion of the request. The storage system will check on the status of incomplete requests. If the storage system is unable to send the request, or if the server does not support the request, this error occurs. The error can be due to network problems or hardware/software problems on the FPolicy server which have broken the connection of the server to the storage system. | Examine the error code to see if it helps point to the cause of the problem. Examine the event logs of the FPolicy (file policy) server to learn if it has disconnected from the storage system and why. Correct any problems that are found such as network errors or hardware problems on the server. |
| fpolicy.fscreen.server.connecting.internalError severity="ERR" | This error occurs when the file policy server registers with the storage system and offers to work as an FPolicy server or the storage system. The storage system has not been able to get memory it needs to hold information related to the FPolicy server. | Contact NGS. |
| fpolicy.fscreen.server.connecting.privError severity="ERR" | This error occurs when the FPolicy server registers with the storage system and offers to work as an FPolicy server for the storage system. The server has connected as a user that has insufficient privileges to act as an FPolicy server. The storage system requires that the user under whose name the server connects to the storage system must be at least a member of the storage system's backup-operators group. This registration attempt will be rejected. | Turn on the filer option cifs.trace_login to see what user name the server is using to connect to the storage system. Remember to turn the option off after solving this problem because tracing can affect storage system performance. Check to see the user name under which the file policy service is running on the FPolicy server. Use the wcc command to learn which groups this user belongs to. Perhaps add this user to an appropriate group, or change the properties of the FPolicy server so that it runs under a different user name. |
| fpolicy.fscreen.cfg.pCreateErr severity="ERR" | This error occurs when the storage system processes saved file screening configuration information from the registry. The storage system wishes to create and initialize a new policy. However, the storage system was unable to do so. This error suggests a problem with the consistency of the storage system registry and should not happen. The storage system discards information related to the policy. | It may be possible to remove the policy with the command fpolicy destroy. Then recreate the policy using fpolicy create and set the policy configuration as desired. |
| fpolicy.fscreen.request.pathError severity="ERR" | This error occurs when the storage system encounters an error as it builds a path for the fscreen server to use in accessing a file. Possible errors include: path is too long or Unicode conversion problems. The user will access a file with a path like this: shareName\directories\fileName The storage system will build an absolute path for the server from the root of the storage system: ontap_admin$\vol\volName\sharePath\directories\FileName Normally this is an internal storage system error (bug). |
|
| fpolicy.fscreen.server.requestTO severity="ERR" | This error occurs when the server has accepted a file screen notification but has not reported the completion of the request. The storage system will check on the status of incomplete requests after a timeout has elapsed. If the server disavows all knowledge of a request which it has accepted but not completed, the request is considered to be timed out. Typically this indicates a server problem. | Examine the event logs of the server to learn if it has noted any problems. Contact the server software vendor to learn if their product supports the request-status query. The storage system only times out requests which the server has accepted. It will not time out a request as long as the server affirms that it is still working on the request. The storage system sends request-status messages to the server to learn the status of requests which may have timed out. |
| fpolicy.server.fqdn.unavail severity="ERR" | This message occurs when the Reverse DNS lookup for the FPolicy(tm) (file policy) server IP address fails and the storage system cannot determine the FPolicy server's Fully Qualified Domain Name (FQDN). If the FPolicy server is running on the Microsoft Longhorn OS, the storage system requires the FPolicy server FQDN for authenticating itself to the FPolicy server. | Verify the Reverse DNS lookup configuration on the DNS server. |