Version

All

Date

24 Jun 2002

Summary

Issues sometimes occur when SQL Server Windows Authentication is used by Argent and an authentication or network bottleneck is encountered.

Argent continues to function, but collected data is not stored in the SQL Server database.

The issue can be resolved by changing the authentication type of the connection to SQL Server from Windows Authentication to SQL Server Authentication.

The following instructions can be used to convert an existing database connection from Windows Authentication to SQL Server Authentication without having to reinstall Argent.

Technical Background

There are two authentication methods used by SQL Server, namely Windows Authentication, and SQL Server Authentication.

When Windows Authentication is used, a user connects through a W200x user account, and SQL Server revalidates the account name and password by a call back to the operating system.

When SQL Server Authentication is used, a user connects with a specified login name and password and SQL Server performs the authentication itself.

Resolution

To convert an existing database connection used by Argent from using Windows Authentication to SQL Server Authentication, do the following.

1. Stop the Argent services.
2. Compare following two samples:

   Windows Authentication:

   driver=SQL Server;server=SERVERNAME;database=DATABASENAME;Trusted_Connection=Yes

   SQL Server Authentication:

   driver=SQL Server;server=SERVERNAME;database=DATABASE;uid=UID;pwd=PSWD

   Notice that the last string Trusted_Connection=Yes is changed with SQL Server Authentication to uid=UID;pwd=PSWD.

3. Replace strings UID and PSWD with the SQL Server account and password to be used.
4. Adjust the following Registry values under HKEY_LOCAL_MACHINE SOFTWARE\Argent\TheArgentGuardian:

   /SNAPSHOT_ODBCSRC

   /SYSTEM_ODBCSRC

   /SERVER/SNAPSHOT_ODBCSRC

5. After changing the database connection strings specified in registry, restart the Argent services.