ISSUE: 

After applying Version 2 patch of Portalshield for WSS 3.0, you my see the following error:

• Event ID 3351 - SQL database login failed. Additional error information from SQL Server is included below.    Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
  
  
• Event ID 1000 - (#50070 "Unable to connect to the database "<database name>" on "<remote SQL server name>")

These error may occur every 5 mins in your event logs.

FIX:

Run the SETSQLACT tool at the command prompt to select the appropriate account:

1. Click Start, Run, type cmd click OK.
2. At the prompt, type the appropriate command below and press ENTER: 
   
   CD \Program Files\Network Associates\McAfee PortalShield\bin (For PortalShield 1.x installations)
   
   CD \Program Files\McAfee\McAfee PortalShield\bin (For PortalShield 2.x installations)
   
   
3. Type the following command and press ENTER: 
   
   SETSQLACT.EXE 
   
   
4. Type the name of the account that has access to the remote database and is a member of the Local Administrators group and press ENTER.

Keep this command session open as it will be used later in this procedure.

Modify the registry:

1. Click Start, Run, type regedit and click OK.
2. Navigate to and select the appropriate registry key below:
   
   HKEY_LOCAL_MACHINE\Software\Network Associates\McAfee PortalShield (For PortalShield 1.x installations)
   
   HKEY_LOCAL_MACHINE\Software\McAfee\McAfee PortalShield (For PortalShield 2.x installations)
   
   
3. In the right pane, click Edit, New, DWORD value.
4. Name the new DWORD value ODForceImpersonate and set the Value data to 1.
5. Close Regedit.

At the command prompt:

1. Type the command below and press ENTER to restart Microsoft IIS:
   
    IISRESET 
   
   
2. Wait for the prompt stating Internet services successfully restarted, then close the command session.

Restart the PortalShield service:

1. Click Start, Settings, Control Panel, Administrative Tools, Services.
2. Right-click the McAfee PortalShield service and select Restart.
3. Close the Services window.

This fix was initially used to fix the same issue in PortalShield for WSS 2.0, I came across the same problem for PortalShield for WSS 3.0 after applying Version 2 patch and the same fix resolved my issue for MOSS. The fix is listed on the Macfee site but only references PortalShield for WSS 2.0.

Mcafee