Get Data Moving 1
Results 1 to 4 of 4

Thread: Error connecting to source SQL Server db

  1. #1
    francis_lodwick is offline Junior Member
    Join Date
    Aug 2015
    Posts
    6
    Rep Power
    0

    Error connecting to source SQL Server db

    Hi,

    Something has changed on the VM I use to run Attunity tasks and I now get the following error when I try to full load from a local database to Redshift:

    RetCode: SQL_ERROR SqlState: 28000 NativeError: 18456 Message: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'UserName'. [122502] ODBC general error.

    I can connect to this database fine using SQL Server 2014 Management Studio.

    Does anyone have any ideas on how to debug this?

    The connections to other databases are working fine.

    Thanks.

    J

  2. #2
    stevenguyen is offline Senior Member
    Join Date
    May 2014
    Posts
    299
    Rep Power
    6
    Hello J,

    1. Attunity Replicate only work with X64 Native Client.

    2. On the Attunity Replicate server, could you try to setup a ODBC connection to your Source SQL server does it works?

    3. Have you try to create a new Source DB connection to you SQL server within Replicate, does that work?

  3. #3
    Hein is offline Senior Member
    Join Date
    Dec 2007
    Location
    Nashua, NH - USA.
    Posts
    152
    Rep Power
    12
    Quote Originally Posted by francis_lodwick View Post
    Hi,

    Something has changed on the VM I use to run Attunity tasks and I now get the following error when I try to full load from a local database to Redshift:

    RetCode: SQL_ERROR SqlState: 28000 NativeError: 18456 Message: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'UserName'. [122502] ODBC general error.

    I can connect to this database fine using SQL Server 2014 Management Studio.

    Does anyone have any ideas on how to debug this?

    The connections to other databases are working fine.

    Thanks.

    J
    In the GUI, go to the manage databases sub-screen; search for the source db being used; use the [test] button.
    Same issue? Does the log from that give more clarification?

    Is the endpoint using Windows Authorization or SQLserver authorization?
    re-enter the password?

    Any other tasks using the source?
    Was this task, or any one of those others, perhaps re-imported with a database definition for this source but with stale authentication string?

    Did more break? ... check the date om replicate\data\mk.dat
    That's the 'Master Key' file for the password encryption. If it changes, all passwords are invalidated.

    hth,
    Hein

  4. #4
    francis_lodwick is offline Junior Member
    Join Date
    Aug 2015
    Posts
    6
    Rep Power
    0
    Thanks both, very helpful questions -- I've solved the problem.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •