Skip to Content
avatar image
Former Member

Console connect problem with repository

Hi

I have a problem with the connection from MD Console 5.5.41.58 to the repository in a local installed MS-SQL.

I can create a NEW repository ( I can see the tables via MS Enterprise Manager), but the Repository is not available via CONSOLE.

I get the following message In the MDM server Log :

ErrorRecord->HResult/NativeErr: 0x80040e4d/0

Description: Login failed for user 'sa'.

Source/File/Line: Microsoft OLE DB Provider for SQL Server/.\OLEDB_DBConnection.cpp/284

I have added "SQLSVR Allow Windows Authentication Mode=TRUE" to mds.ini

Thanks and regards

Dick

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Aug 27, 2007 at 02:33 PM

    Hi Dick,

    From the error you provided, the authentication of user "sa" is failing. Please make sure you are providing the correct password for this user.

    If you want to use Windows authentication, don't provide a username or password in the Mount/Create Repository dialog in the Console.

    Regards,

    cleo

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Cleo

      I use the same SQL Client 8.00.760 on all 3 installations

      MDS and SQL are running on the same server. (2 are OK and 1 (my laptop) gives this problem)

      However when I connect with the Console on my laptop to the MDM-server (with same SQL version) at one of the other installations , then there are no problems.

      Kind regards

      Dick

  • avatar image
    Former Member
    Aug 31, 2007 at 05:26 PM

    There may be a problem with the SQL Server authentication mode.

    Please examine the Server Properties page for the SQL Server Instance

    to which connections are failing.

    It allows two possibilities:

    1) Windows Authentication mode

    2) SQL Server and Windows Authentication mode

    It should be set to 2).

    Regards,

    Dave Poy

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Dick,

      If you have more than one MDS installed on your system, there is more than one MDS.ini file on your sytem (I believe they live in the same directory as the executable itself). If the MDS.ini that you're expecting to be updated is not being updated, it's because the other MDS on the system is the one that is registered to execute. In other words, if you have two versions of MDS on your system, you may be running version A when you mean to be running version B.

      I don't know if this situation is typically supported in the field, but I can share with you some steps to help you switch between versions (and it will solve the problem with the MDS.ini file not being updated). It won't explain why you had authentication errors with the database login in the log, though...

      Open up the Services Control Panel Applet, scroll down and find MDM Server in the list. If you right-click and view the properties, you can see the path of the executable, which should tell you which version is currently running.

      To change to the other version:

      1. Stop MDS (either through Services or through the Console/CLIX)

      2. Open a Command Prompt Window, and change directory to the location of the MDS executable that you want to be using.

      3. In the directory with the version of MDS that you want to use, type "MDS.exe /regserver" and hit enter.

      That's it! Now when you use the Console and start MDS, you'll be using the one in the other directory. Note that if you have two different versions that go across Patch releases, you'll need to use different versions of Console and Data Manager too, potentially, as the protocol may change between Patch releases.

      Cheers,

      Cleopatra