What was really interesting about this was the user that was referenced, mxmc_admin. Now this is interesting, because during the Identity Store creation process, you are prompted to use mxmc_rt as the user and there is no time during the install that you are asked to create a JAVA based connection string using mxmc_admin.
This started a great deal of troubleshooting and conversations with people who have a great deal of knowledge with IDM's moving parts. Ultimately we wound up looking at the options in IDM's MMC interface.
The problem was in the Classpath Extension. It seems in this installation we had the old Microsoft SQL 2000 JARs loading before the SQL 2005 JAR. Since the MS SQL 2000 drivers were no longer needed, I removed them, regenerated my dispatcher scripts and restarted the dispatcher services. I was now able to export without a problem. I'm saying it's the order that the JARs are ordered in since I looked at my personal sandbox system and saw that I had the following Classpath:
And my Import/Export works just fine, thank you very much.
Some more good troubleshooting to come...
4 comments:
Couple of additional quick thoughts on this...
I'm assuming MSSQL as the database. Also make sure you're using the 1.2 version of the JAR.
Hi Matt, Quick question we get the same error and we can't import the tasks in the IDM Console. We checked the Tools-> Options -> Java and we have this: com.microsoft.sqlserver.jdbc.SQLServerDriver
We used the JDBC 3 and installing the IDM 7.2 with AS Java 7.01.
SQL Server 2008 R2 Enterprise and using dynamic ports.
Java 1.6
At the moment we are stuck and we don't know where else to find the error.
Would appreciate your help
Thanks
Tintin
Hi Matt do you need to use the version of jar 1.2 even if you are installing IDM 7.2?
I'll have to take a look at what I'm using in my Sandbox. I did recently have this issue with 7.2 and SQL Server 2008 and don't recall what I did to fix it. I'll take a look. Maybe we need to update this.
Post a Comment