Win2008 + MSSQL2008 -> Dispatcher "cannot load driver com.microsoft.jdbc...

[reinhard_weidner2]

Hi all,

this installation drives me nuts..

WinServer 2008 64-bit

MS SQL-Server 2008 Enterprise

JVM 1.4.2_30 32bit (after n-th trial)

MS-JDBC-Driver 1.2

IC installs, adding IC-Configuration also works (without error), but when testing a dispatcher, the jvm moans:

> MxDispatcher:Loading driver: com.microsoft.jdbc.sqlsserver.SQLServerDriver

> Can not load driver:'com.microsoft.jdbc.sqlserver.SQLServerDriver

...but:

in the IC I told him to use "com.microsoft.sqlserver.jdbc.SQLServerDriver" as stated in the documents of the MS-JDBC-Driver

This seems to be hardcoded somewhere since it comes always into the dispacher.prop file regardless what you configure.

Is there a working setup-guide for SQL-Server 2008 out there.

It is supported since Oct.2010 but the installguides do not reflect this.

best regards,

Reinhard Weidner

[markus_doehr2]

> WinServer 2008 64-bit

> MS SQL-Server 2008 Enterprise

> JVM 1.4.2_30 32bit (after n-th trial)

> MS-JDBC-Driver 1.2

Why are you using a 32bit Java? A 32bit JVM can't load a 64bit JDBC driver.

Markus

[reinhard_weidner2]

It's the 32 bit JDBC-driver.

According to docu, IC does require a 32bit JVM on Windows environments.

With 64bit Java it cant even load the JVM.

regards,

Reinhard Weidner

[markus_doehr2]

According to page 12 of

https://service.sap.com/~sapidb/011000358700001223842010E

you can also use the 64bit JVM.

Markus

[former_member2987]

Have you tried 1.4.2_19 rather than 1.4.2_30? I've always used 19. That could be part of the probelm.

Good luck!

Matt

[markus_doehr2]

1.4.2_19 is ancient, that version shouldn't be used any more. It was one of the first ones supported on x64, there were a huge number of corrections between that version and the current one (including timezone fixes that may cause trouble). On top there is a kerberos issue with that which will prevent the system from doing proper SSO.

It's always advised to use the latest JVM, it's unlikely, that a driver can't be loaded in a newer version.

Markus

[former_member2987]

Markus,

Thanks for that information. I do most of my development in a sandbox environement and that's what I'm running. Not really a NetWeaver guru, so it's all helpful.

As a rule, I try not to block out any possibility when troubleshooting, that's why I brought it up.

And let's be honest, all 1.4.2 versions are ancient.

Thanks again, I'll have to go look for that updated version now...

[reinhard_weidner2]

Hi Markus,

your Document refer to IDM 7.20 although it is not stated that clearly (only in the revision flag).

On page 10 of the doc. 7.11 rev.11 it is stated

"Note:

You need to install the 32-bit version of the Java Virtual Machine on Microsoft Windows."

It is tricky from beginning to end with all these versions...

regards,

Reinhard

[reinhard_weidner2]

Great relief, it works.

Trick is:

You may not install the inital database-structure from the shipment disks with SQL-Server 2008!

After removal of the mxmc_db schema and run of the scripts from the SP05 files it worked

So to sum up, with

Windows 2008 Server

MS-SQLServer 2008

install

JDK_1.4.2_30 32-bit (or similar)

MS-JDBC-Driver 1.2

Directly install IDM from SP05-Files, then it works without trouble.