Loading...
Loading...
AUTH_ERROR 5 AUTH_ERROR 5server_X : 10 threads started. 1 Checker IP Address(es): xx.xxx.xxx.xx AUTH_ERROR 5 at Wed Feb 29 13:23:03 2012 (GMT-00:00) MS-RPC over SMB, CAVA version: 4.9.3.0, ntStatus: SUCCESS AV Engine: Symantec AV Server Name: cava.example.com Last time signature updated: Web Feb 29 13:20:23 2012 (GMT-00:00) Cause: The account being used for checking does not have the virus checking privilege assigned to it. Actions: Ensure that the CAVA service in services.msc is set to logon as a user and not a local system account. _____________________________________________________________________________________________________________________________________________________________ ERROR_AUTH 64 ERROR_AUTH 64server_X : 10 threads started. 1 Checker IP Address(es): xx.xxx.xxx.xx ERROR_AUTH 64 at Wed Feb 29 13:23:03 2012 (GMT-00:00) MS-RPC over SMB, CAVA version: 4.9.3.0, ntStatus: SUCCESS AV Engine: Symantec AV Server Name: cava.example.com Last time signature updated: Web Feb 29 13:20:23 2012 (GMT-00:00) Cause: Kerberos error caused by out of sync ' Time ' between the Data Mover and Anti-Virus Server. Action: Implement NTP or sync ' Time ' manually. _____________________________________________________________________________________________________________________________________________________________ AUTH_ERROR 86 AUTH_ERROR 86server_X : 10 threads started. 1 Checker IP Address(es): xx.xxx.xxx.xx AUTH_ERROR 86 at Wed Feb 29 13:23:03 2012 (GMT-00:00) MS-RPC over SMB, CAVA version: 4.9.3.0, ntStatus: SUCCESS AV Engine: Symantec AV Server Name: cava.example.com Last time signature updated: Web Feb 29 13:20:23 2012 (GMT-00:00) Cause: Password inconsistency between the CAVA service and user password in Active Directory (AD). (Example: Password expired and was changed, but was not updated on the CAVA service.) Action: Right-click the CAVA service in services.msc > Properties > Log On tab > update the user password to reflect that in AD. _____________________________________________________________________________________________________________________________________________________________ AUTH_ERROR 1265 AUTH_ERROR 1265server_X : 10 threads started. 1 Checker IP Address(es): xx.xxx.xxx.xx AUTH_ERROR 1265 at Wed Feb 29 13:23:03 2012 (GMT-00:00) MS-RPC over SMB, CAVA version: 4.9.3.0, ntStatus: SUCCESS AV Engine: Symantec AV Server Name: cava.example.com Last time signature updated: Web Feb 29 13:20:23 2012 (GMT-00:00) Cause: The user account that CAVA uses has expired in Active Directory (AD). The user will not be able to login to the server at all using the credentials. Action: Unlock the account and set it to never expire and try again. _____________________________________________________________________________________________________________________________________________________________ ERROR_ AUTH 1326 ERROR_AUTH 1326server_X : 10 threads started. 1 Checker IP Address(es): xx.xxx.xxx.xx ERROR_AUTH 1326 at Wed Feb 29 13:23:03 2012 (GMT-00:00) MS-RPC over SMB, CAVA version: 4.9.3.0, ntStatus: SUCCESS AV Engine: Symantec AV Server Name: cava.example.com Last time signature updated: Web Feb 29 13:20:23 2012 (GMT-00:00) Cause : Password for the account running CAVA has expired. Action: Reset the password and set it to never expire. Make any changes to CAVA service as required. _____________________________________________________________________________________________________________________________________________________________ AUTH_ERROR 1331 AUTH_ERROR 1331server_X : 10 threads started. 1 Checker IP Address(es): xx.xxx.xxx.xx AUTH_ERROR 1331 at Wed Feb 29 13:23:03 2012 (GMT-00:00) MS-RPC over SMB, CAVA version: 4.9.3.0, ntStatus: SUCCESS AV Engine: Symantec AV Server Name: cava.example.com Last time signature updated: Web Feb 29 13:20:23 2012 (GMT-00:00) Cause : The user account for CAVA has been disabled in Active Directory (AD) or is only allowed to logon during certain hours. Action : Re-enable account and remove any logon restrictions in AD. _____________________________________________________________________________________________________________________________________________________________ AUTH_ERROR 1909 AUTH_ERROR 1909server_X : 10 threads started. 1 Checker IP Address(es): xx.xxx.xxx.xx AUTH_ERROR 1909 at Wed Feb 29 13:23:03 2012 (GMT-00:00) MS-RPC over SMB, CAVA version: 4.9.3.0, ntStatus: SUCCESS AV Engine: Symantec AV Server Name: cava.example.com Last time signature updated: Web Feb 29 13:20:23 2012 (GMT-00:00) Cause: User account locked due to too many invalid login attempts. Action: Unlock account/reset password. Make any changes to CAVA service as required. _____________________________________________________________________________________________________________________________________________________________ AV_NOT_FOUND AV_NOT_FOUND1533198284: VC: 5: xx.xxx.xxx.xx AV_NOT_FOUND at Thu Aug 2 08:24:39 2018 (GMT-00:00) 1533198284: VC: 5: HTTP, CAVA version: 8.5.1.0 1533198284: VC: 5: AV Engine: Unknown third party antivirus software 1533198284: VC: 5: Server Name: xx.xxx.xxx.xx Cause: AV_NOT_FOUND indicates that the virus-checking service on the Virtual Data Mover (VDM) cannot communicate with the CAVA client on the Anti-Virus (AV) server. Local administrative rights must be assigned to the AV user on each AV server to allow CAVA and the virus-checking service on the Data Mover to start successfully. The " OpenProcess " failing usually indicates that the " emc cava " service is running in a user context that has not been given "local admin" rights on the system or that some rights are missing on that group. The "local admin" account on CAVA systems doesn't have the " SeDebug " right (debug programs) that is needed by CAVA facility to track state of AV engines. Action: Recommended troubleshoot for AV_NOT_FOUND at the Resolution Section, in this article. Document Dell CEE - Using the Common Event Enabler on Windows Platforms : Restricted Group GPO - page 13 Assign rights - page 23
Background Explanation The Active Directory (AD) Domain Controller (DC) doesn't allow anonymous access with the CIFS server machine account as it should be performing with NTLM and machine accounts. Other DC's in the environment may allow for anonymous access to the CAVA user with the CIFS server machine account. The authentication method between the Virtual Data Mover (VDM) and DC is NTLM (Microsoft) however Kerberos could also be used. The DC in the environment should allow anonymous access as part of establishing a secure channel between the VDM and the DC. Other option is to configure the AV servers to use Kerberos authentication instead of NTLM. Background Events The AV servers are not being authenticated by the AD DC. The VDM server logs an error whenever the authentication to the DC fails for the Viruschecker Domain user. With NTLM Authentication the VDM must forward the user's credentials on to a Domain Controller (pass-through authentication) using DCERPC NetrLogonSamLogon asking it to authenticate the user. The DM is using the computer account of the CIFS Server for DCERPC NetrLogonSamLogon function. The DC will treat access using the computer account as equivalent to anonymous access. This can be seen in the network trace when the DM is sending the pass-through authentication to on the DC's.
Recommended Troubleshoot for ERROR_AUTH: Confirm the domain CAVA user has sufficient rights, which means, it is correctly added to the local CAVA group on the Data Mover and assigned the Virus-Checking privilege. For details on the correct configuration, visit the Dell Support Page at and look for Dell CEE - Using the Common Event Enabler on Windows Platforms . For more information, investigate Microsoft Developer Network (external link) at for a complete list of Microsoft error codes. In that list, look for the numerical code that follows the " ERROR_AUTH " message and check its definition. _____________________________________________________________________________________________________________________________________________________________ Recommended Troubleshoot for AV_NOT_FOUND : Confirm viruschecker.conf settings. Confirm the CAVA service is running with the AV user account. Confirm the installed Anti-Virus (TrendMicro, McAfee, others) service is running with the local system account. Confirm the AV user is member of the local admin group on each AV server. Confirm that the Anti-virus and CEE have been un-installed and re-installed (using the correct order, CEE first, then Anti-virus). Rebooted the CAVA server multiple times. Confirm that the CAVA servers have one network interface only. If AV_NOT_FOUND cannot be resolved using the preceding troubleshooting steps, contact Dell Technical Support or an Authorized Service Representative and reference this Knowledge Base article ID.
Click on a version to see all relevant bugs