After upgrading our ECC6 EHP4 system to EHP5 Java will only start on the Node A of our Microsoft cluster.
Java bootstrap fails on Node B and all Dialog servers.
In jvm_bootstrap.out we see the following error for all nodes that Java will not start on.
sap.sql.log.OpenSQLException: Could not load class com.microsoft.sqlserver.jdbc.SQLServerDriver.
After seeing a similar posting at SDN we did the following for one dialog server
Open configtool
- Go to instance --> dispatcher --> Configuration Manager --> Local Properties --> rdbms.driverLocation
- Change it to C:\usr\sap\PRD\DVEBMGS00\exe\mssjdbc\sqljdbc.jar (or similar)
- Go to instance
> server
> Configuration Manager --> Local Properties --> rdbms.driverLocation
- Change it from:
C:\usr\sap\PRD\D15\exe\mssjdbc\base.jar;C:\usr\sap\PRD\D15\exe\mssjdbc\util.jar;C:\usr\sap\PRD\D15\exe\mssjdbc\sqlserver.jar;C:\usr\sap\PRD\D15\exe\mssjdbc\spy.jar
to C:\usr\sap\PRD\D15\exe\mssjdbc\sqljdbc.jar
Because the SDN posting said that C:\usr\sap\PRD\D15\exe\mssjdbc\base.jar;C:\usr\sap\PRD\D15\exe\mssjdbc\util.jar;C:\usr\sap\PRD\D15\exe\mssjdbc\sqlserver.jar;C:\usr\sap\PRD\D15\exe\mssjdbc\spy.jar was an old school driver
The entry for the configtool rdbms.driverLocation for all of the servers that java will not start has a an entry with the exe\mssjdbc\spy.jar
Whereas
The entry for the configtool rdbms.driverLocation for the server that java does start on has an entry of exe\mssjdbc\sqljdbc.jar
The Jar files and the bootstrap.properties file did not get updated by EHPI on the servers having a problem