cancel
Showing results for 
Search instead for 
Did you mean: 

Console connect problem with repository

Former Member
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

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

Former Member
0 Kudos

Hi Cleo

thx for your hints.

I have changed the password (was NULLand is now changed ) and tried it again, but without result (I had to change the DBMS settings in the Console)

I also removed the line from MDS.INI, restarted the laptop , but still no result

other ideas ?

Kind regards

Dick

Former Member
0 Kudos

Hi Dick,

Maybe there's something weird about the name of your SQL Server... how is it named? I'm also looking into other possibilities as well.

Thanks,

cleo

Former Member
0 Kudos

I have the same problem using SQLEXPRESS, if I use SQL2000 an MDM 5.5.42.48 it functions.

Regards John-Kjell

Former Member
0 Kudos

Hi

I did the same installation on some other PC's and there it is running without problems.

I can start the console; I can start to create a repository, but then it is not connected .................... :

2772 2007/08/30 21:01:28.130 GMT mds Configured for CPU Count of 1

3536 2007/08/30 21:02:07.520 GMT Creating Repository: testDK, on DBMS Server: NLYEHVSCE1NAX12

3536 2007/08/30 21:03:29.458 GMT Init Database Tag: testDKNLYEHVSCE1NBA78MSQL_6_15_4_3

3536 2007/08/30 21:03:29.536 GMT OLEDB error on / from statement:

3536 2007/08/30 21:03:29.536 GMT 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

3536 2007/08/30 21:03:29.551 GMT Repository testDK creation completed with error

Former Member
0 Kudos

Hi,

What version of SQL Client are you using on the machine with the problem? Is this the same version of SQL Client that is on the other machines without the problem? Are MDS and SQL Server running on the same machine as the Console? If so, what version of SQL Server is running?

Thanks,

Cleopatra

Former Member
0 Kudos

Hi Cleopatra.

I have the same problem.

I run SQL 9.0.3042-sa

MDM server 5.5.42.57

MDM console 5.5.42.48

In SQL Server Managmenet Studio Express I am able to connect to the databseserver and cretae databases, but from MDM I get the errormessage.

Regards John-Kjell

Former Member
0 Kudos

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

Answers (1)

Answers (1)

Former Member
0 Kudos

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

Former Member
0 Kudos

Hi

this is (was) already on "SQL Server and Windows Authentication mode"

Kind regards

Dick

Former Member
0 Kudos

Hi Dick,

Well, this is depressing, as I was really hoping it was an issue with the authentication configuration of SQL Server. Can you try using the Console to look at the DBMS settings of the SQL Server in question (right-click on the server node in the tree, select DBMS Settings, and specify the offending SQL Server)? I would imagine that this would fail, for the same reason (authentication issue) -- please verify that the error is the same by looking at the server logs. (And if you don't get an error, well, I'm baffled...)

If possible, it would be interesting to know if another MDS on the same network can access this SQL Server as well. The errors you're having are between MDS and SQL Server (Console never connects directly to the database). I would try, if possible, using your Console to connect to another MDS, then try to look at the DBMS Settings for the misbehaving SQL Server through that other MDS. Remember that MDS can connect to any database instance (provided the networking permits it), and the Console doesn't care (it just routes requests to MDS), so this might be an interesting test.

I assume if you open SQL Server Management Studio you can connect successfully to the database using sa and the same password you've provided to MDM?

Since someone else reported the same problem in this thread and they're already running SP5 Patch 2, I can't imagine that upgrading to Patch 2 would help... but I'm close to being all out of ideas!

Regards,

Cleopatra

Former Member
0 Kudos

I had the same problem. My solution was to start the MDM server from the place where you in windows start all services. I did that,started the console, mounted the server an created a repository. I the get a question on path and, answered blank on that end then the whole thing was up and running. Good Luck.

Remember to give me points if it helps.

Regards John-Kjell

Former Member
0 Kudos

Hi John,

I lost you part-way through your explanation (path?), but maybe Dick will be able to follow it and let us know if it works.

I'm not sure how starting MDS from the Windows Service Control Manager could make a difference as compared to starting it from the Console; the Console just tells the SCM to start MDS, so it's effectively the same operation.

I'm definitely interested to know if any of this works, though, so hopefully Dick will let us know!

Regards,

Cleopatra

Former Member
0 Kudos

Hi Cleo

some answers to your questions :

1) Console to look at the DBMS settings : no problem; I get the DBMS settings screen

2) SQL Server Management Studio you can connect successfully ? yes, no problem

the tip of starting MDS as first step : still the same problem.

I have now also Patch 02 and I will unistall all sql-server software and then I will try it again.

And when I still have a problem, then I will try the connection from another MDS.

thanks for all your help

Regards

Dick

Former Member
0 Kudos

Hi All

the problem was caused by a mds.ini, that was not updated with the created repositories.

I had installed more then one MDS-server software (in different folders) and the result is that MDS.INI is not updated anymore.

every time, when I create a new repository, then I have to do a manual update of the mds.ini

kind regards

Dick

Message was edited by:

F. t. CECO rep.

Former Member
0 Kudos

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