ODBC destination stops logging new messages to a remote SQL Server

Possible cause and solution:
  • The remote
    SQL Server
     uses
    Windows
     authentication, and the user name configured for the ODBC Log is not fully qualified. If the domain to which the user name belongs cannot be determined, the connection to the database fails.
    To solve this problem:
    1. In
      FactoryTalk Administration Console
      , select
      Tools > Diagnostics Setup
      .
    2. Expand
      Destination Setup
      , and then select
      ODBC Database
      .
    3. If it is not already selected, select
      Login required
      .
    4. In
      User name
      , type the login user ID for the database.
      When using
      Windows
       authentication (rather than
      SQL Server
       authentication), enter the fully-qualified user name in the format
      DOMAIN\UserName
       or
      user@domain.com
       (for UPN-style entries).
    5. In
      Password
      , type the password for the user account.
    6. In
      Confirm password
      , type the password for the user account again.
    7. Select
      OK
      .
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal