It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,877
×10,962
×7,469
×6,036
×5,939
×3,954
×1

question asked: Jun 01 '17, 2:57 p.m.
question was seen: 4,378 times
last updated: Jun 01 '17, 3:08 p.m.

Related questions

CRRGW6002E The JDBC driver "com.microsoft.sqlserver.jdbc.SQLServerDriver" could not be loaded

1
William Chen (312●1●5) | asked Jun 01 '17, 2:57 p.m.
edited Jun 01 '17, 2:58 p.m.

Here is a common problem and workaround when trying to setup JRS 5.0.2 iFix 009 on Windows Server 2012 with SQL Server 2014 and WAS server 8.5.5.10. The data warehouse test connection fails with below error:

CRRGW5548E An java.lang.IllegalStateException error occurred when validating the database connection, caused by CRRGW6002E The JDBC driver "com.microsoft.sqlserver.jdbc.SQLServerDriver" could not be loaded.

Workaround:

1) Open the WAS Console
2) Select Servers -> WebSphere application servers -> server1 
3) Under Server Infrastructure, expand Java and Process Management, and select  "Process Definition" 
4) Under Additional Properties, select Java Virtual Machine
5) Enter absolute path to "sqljdbc41.jar" into the Classpath field, and save 6) Retry the data warehouse connection test, and if it doesn't work,  restart WAS and try it after a restart

One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
William Chen (312●1●5) | answered Jun 01 '17, 3:08 p.m.
<style type="text/css"> P { margin-bottom: 0.08in; </style>

The JRS is supposed to load the SQL JDBC Driver from the WebSphere JVM Custom property called “SQLSERVER_JDBC_DRIVER_FILE”.  Additionally, two other valid options that you can also consider:

1) Put the sqljdbc41.jar file into server/conf/rs/WAS_sharedLibrary directory.
2) If putting into WAS_sharedLibrary solution doesn't work, put the jdbc driver (sqljdbc41.jar file) in JVM lib/ext directory, for example, C:\WebSphere1\AppServer\java\jre\lib\ext.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.