MXMC-Update "failded to connect to mxmc_db on localhost"

[becksen]

Hi all,

IDM 8.0 was installed. Using Eclipse and the development studio an identity store was created. During importing any of the packages (first com.sap.idm.provisioning.engine.idmpck) I got errors. The developer traces showed that a stored procedure in the MXMC_db was missing. Research showed that SP01 for IDENTITY CENTER CORE and a database update should solve the issue.

Unfortunately I could not start the update procedure via MXMC-update. Although mxmc-test and mxmc-verions is successful, the update does not start.

As jdbc url I provide:

jdbc:sqlserver://deidm1:1433;databasename=mxmc_db;user=mxmc_oper;password=<mxmc_oper password>

As path and name of the driver I provide:

C:\usr\sap\IDM\Identity Center\jdbc\sqljdbc4.jar

I've tried mxmc in capital letters also. All dispatchers were stopped. Even runtime components deinstalled. Until now always the same issue.

Has anybody solved this issue already?

Thanks Timmy

[becksen · Accepted solution]

Hi Jai,

your remark is correct but this was also unsuccessfully tested. The script is ignoring capital letters.

It basically doesn't matter what I enter MXMC_db or mxmc_db. The script is handing over the value with mxmc_db.

Correct. With duplicating the user and name it mxmc_oper I was able to skip the initital issue. But now I'm facing the same issue with the database name. But renaming or duplicating the DB is not that reasonable from my perspective.

Best regards,

Timmy

[former_member264923 · Accepted solution]

Hi,

I have the same error over here.

When I take a look into the SQL logfile it says:

Login failed for user 'MXMC_oper'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]

The provided password is correct. I´m able to login to SQL Management Studio.

Did you take a look into your SQL logfile?

Thanks

[jaisuryan · Accepted solution]

Hi Timmy,

Please use mxmc-xupdate.cmd instead of mxmc-update.cmd

And path to the JDBC driver in double quotes

Kind regards,

Jai

[becksen · Accepted solution]

Hi Jai,

thanks that works perfectly.

Best regards and have a good day.

Timmy

[former_member264923]

It could be a problem with the complexity.

I changed my _oper password to a les complex one and now it works.

[becksen]

Hi Pit,

I've experienced this issue earlier with MXMC_admin user. I didn't do the same error twice The answer is no, reason in this case was not the complexity of the password, but could be in other cases. Thanks for the remark.

Finally it works with mxmc-xupdate as proposed by Jai.

Kind regards.

[Former Member]

Hi Timmy,

Did you try without the port? Also you will have to specify the instance name if there is one on the database server:

jdbc:sqlserver://deidm1\<instance name>:1433;databasename=mxmc_db;user=mxmc_oper;password=<mxmc_oper password>

Let me know how you go.

Thanks,

kv

[becksen]

Hi Kv,

thanks for the remark.

Without port the same result.

To specify the issue I've copied the user MXMC_oper and created mxmc_oper. Same security settings and same password. This basically solves the initial login failure. It seems to be quite cleare that the update script is not considering case sensitive. I've deleted MXMC_db and installed the MXMC_db from SP01. This solved my inital issue regarding "missing stored procedures".

Login failed for user 'mxmc_oper'. Reason: Failed to open the explicitly specified database 'mxmc_db'. [CLIENT: <local machine>]

Than I tried mxmc-update from SP02. But this is also not successful because it tries to access database mxmc_db instead of MXMC_db as it was initially created by SAP installation script.

I've SAP IDM running now knowing that a database upgrade won't work which is bothering me.

Finally it is a case sensitive issue which might be solved in the update script or in the ms sql server settings.

But I've not found a solution changing MS SQL settings yet.

Any ideas?

Thanks.

[jaisuryan]

Hi Timmy,

If the database is MXMC_db then jdbc string should be,

jdbc:sqlserver://deidm1:1433;databasename=MXMC_db;user=mxmc_oper;password=<mxmc_oper password>

Question: So your current state is, you have a database MXMC_db and two users in it MXMC_oper and mxmc_oper? Is my understanding correct?

Kind regards,

Jai

[jaisuryan]

Hi Timmy,

Do you have sqljdbc4.jar in the location?

Also, try opening the cmd as administrator.

Kind regards,

Jai

[becksen]

Hi Jai,

thanks for your reply.

Yes sqljdbc4.jar is available there. The original file path is:

C:\Program Files\Microsoft SQL Server JDBC Driver 4.0\sqljdbc_4.0\enu\sqljdbc.jar

I thought it might be to long and moved it to another location. Both ways are not working.

I've run the command line with Administrator, with SIDADM. Same result.

Testing the connection is always successful and also mxmc-versions works as it should:

Best regards

Timmy

[jaisuryan]

Hi Timmy,

Please share the contents of mxmc_update.log file.

and the error screenshot when you execute the script.

Kind regards,
Jai

[becksen]

Hi Jai,

no mxmc_update.log was created. Which is strange. Although mxmc_versions.log and mxmc_test.log were created.

I've recognized that after the error is dislayed a test.txt file was created. It was attached accordingly.

text.txt contains the following message:

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Login failed for user 'mxmc_oper'..

Thanks.

test.txt.zip

[jaisuryan]

Hi Timmy,

You missed sqlserver in JDBC string.. It should be jdbc:sqlserver://

Also, mxmc_test.log shows that login failed for mxmc_oper user. Please verify if you are using the correct password for mxmc_oper user.

Kind regards,

Jai

[becksen]

Hi Jai,

sorry this was a mistake because I've tried several things. Even with jdbc:sqlserver:// the result is the same.

mxmc-test with mxmc_oper was successfull. I was also able to login with MXMC_oper on MS SQL Server Management Studio. But only case sensitive (MXMX_oper, mxmc_oper does not work).

Even renaming the user in Database to mxmc_oper does not help.

Password was replaced so it should be correct. But no improvement.

mxmc-test.txt.zip