cancel
Showing results for 
Search instead for 
Did you mean: 

Idm 7.2 sp7, error importing SAP provisioning Framework

former_member96398
Participant
0 Kudos

I have a new install of IDM 7.2 sp7, everything looks correct but I'm not sure about the Java levels. I've checked the mxmc_admin password and created a job to ensure the dispatcher and mxmc users have the right passwords (tested in sql studio). I'm kinda at a loss where to look next. Here is the log from the error. Any help would be greatly appreciated.

Curtis

24.07.2013 00:10:11 :I:Parsing arguments to syncutility

24.07.2013 00:10:11 :D:Operation type is IMPORT_TO_GROUP

24.07.2013 00:10:11 :D:Loading driver com.microsoft.sqlserver.jdbc.SQLServerDriver

24.07.2013 00:10:11 :X:Found items in classpath:

24.07.2013 00:10:11 :X:- ".

24.07.2013 00:10:11 :X:- C:\Program Files\sqljdbc_3.0\enu\sqljdbc.jar

24.07.2013 00:10:11 :X:- D:\IdM\Identity Center\Java\logging.jar

24.07.2013 00:10:11 :X:- D:\IdM\Identity Center\Java\imXport.jar

24.07.2013 00:10:11 :X:- D:\IdM\Identity Center\Java\transportation.jar

24.07.2013 00:10:11 :X:- D:\IdM\Identity Center\Java\jh.jar

24.07.2013 00:10:11 :X:- D:\IdM\Identity Center\Java\MIC-impexp.jar

24.07.2013 00:10:11 :X:- D:\IdM\Identity Center\Java\xerces.jar

24.07.2013 00:10:11 :X:- D:\IdM\Identity Center\Java\xalan.jar

24.07.2013 00:10:11 :X:- D:\IdM\Identity Center\Java\xml-apis.jar

24.07.2013 00:10:11 :X:- C:\Users\a82334\Desktop\Microsoft JDBC Driver 4.0 for SQL Server\sqljdbc_4.0\enu\sqljdbc4.jar

24.07.2013 00:10:11 :X:- "

24.07.2013 00:10:12 :D:Loaded JDBC Driver class: com.microsoft.sqlserver.jdbc.SQLServerDriver Version: 3.0

24.07.2013 00:10:12 :I:Creating connection to jdbc:sqlserver://cnaw08v712:1433;databasename=mxmc_db;user=mxmc_admin;password=****@ne

24.07.2013 00:10:12 :I:Could not create connection to the database jdbc:sqlserver://cnaw08v712:1433;databasename=mxmc_db;user=mxmc_admin;password=*****

24.07.2013 00:10:12 :X:Initialized log for com.sap.idm.ic.syncutil.utilities.ShowLogFileDlg. Log level is eXtended

Accepted Solutions (1)

Accepted Solutions (1)

former_member96398
Participant
0 Kudos

Corrected our sap provisioning framework import issue. We had to reran the schema update for sp7 and restarted the dispatcher. Also, imported the sp7 import files from the designtime file for sp07.

Regards,

Curtis

Answers (5)

Answers (5)

former_member96398
Participant
0 Kudos

We did have two JDBC drivers conflicting, deleted all and re-entered everything and bounced the box. That fixed the import error for the sql driver.

We are on 7.2 sp7 and my ident. design designtime for 7.2 brought in a sap framework dated: 4/26/2013.

When I try to import now I'm getting the message:

The import file contains an older db version than the database. The Sql DB is 2008 R2:

Microsoft SQL Server Management Studio   10.50.1702.0
Microsoft Analysis Services Client Tools   10.50.1702.0
Microsoft Data Access Components (MDAC)   6.1.7601.17514
Microsoft MSXML   3.0 6.0
Microsoft Internet Explorer   9.0.8112.16421
Microsoft .NET Framework   2.0.50727.5466
Operating System   6.1.7601

I asked the infrastructure team to download the latest version of the framework from service marketplace and send it to me. Not sure if the one I received is correct.

Any suggestions?

Regards,

Curtis

bxiv
Active Contributor
0 Kudos

Good to hear that the SQL driver issue was resolved, but I don't follow your current 'import' problem?

Also which jdbc driver did you end up going with?

former_member2987
Active Contributor
0 Kudos

Curtis,

I agree with and Former Member.  Check firewalls, ports and try the IP address rather than hostname (you'd be su...

Also try the 2.0 version of the sql jar instead of C:\Program Files\sqljdbc_3.0\enu\sqljdbc.jar.  The properties on mine are:

I've also documented some of my sqljdbc4.jar findings.

And some probably unrelated, but possibly helpful information on Import / Export.

Hope it helps!

Matt

Former Member
0 Kudos

Hi Curtis,

  I agree with Ivan, but if his suggestion doesn't work, you can check the user - mxmc_admin rights or to ask your admins to check if this user has the needed access.

BR,

Simona

ivan_petrov
Active Participant
0 Kudos

Hi Curtis,

As far as I can see you are using only the short name of the host in the connection string.

I think your problem is not IDM related, but it looks like you have a network related issue.

Try first using the full host name and if this doesn't help also, try to use IP address of the host.

You should also switch off any firewalls, or at least check their settings that might prevent the connection.

Hope this will help.

Best regards,

Ivan

bxiv
Active Contributor
0 Kudos

Looks like your using 2 different JDBC drivers, can you verify in the settings of Identity Center which one you have?

former_member96398
Participant
0 Kudos

Here is what we have:

bxiv
Active Contributor
0 Kudos

Here is mine, and I also have Windows x64 for Application and DB (MSSQL).  In your case I would try sqljdbc.jar by itself and sqljdbc4.jar and see if you have a difference.

former_member2987
Active Contributor
0 Kudos

sqljdbc/sqljdbc4 depends on the java version being used.

Also take the classpath extension out.  In 7.2 you only need to specify sqljdbc(4) in the JDBC driver Jar entry.

Matt