In WebSphere, check your MS JDBC DRIVER variables (you may find them set to a path where the sqljdbc.jar file is not updated)
"WebSphere UI Console | Environment | Websphere Variables"
The following variables should be "NULL", or it will override the updated jar file located in the "MAXIMO.ear\lib" deployment directory.
MICROSOFT_JDBC_DRIVER_NATIVEPATH
MICROSOFT_JDBC_DRIVER_PATH
(for Example, it may have the following: C:\IBM\WebSphere\AppServer\ctgMX\lib)
Alternately, if the path value is defined, you could copy the "..maximo\applications\maximo\lib\sqljdbc.jar" to the path defined.
------------------------------
Jay Chauncey
VP of Quality and Support
edi
St. Petersburg FL
------------------------------
Original Message:
Sent: Fri June 09, 2023 08:32 AM
From: Steven Shull
Subject: Maximo 7.6.1.3 apply fixpack issue
Something like this needs a support case. I haven't heard about this issue and I was unable to find anything about it (though I am not able to view the case listed above).
------------------------------
Steven Shull
------------------------------
Original Message:
Sent: Thu June 08, 2023 03:01 PM
From: Pablo Condoleo
Subject: Maximo 7.6.1.3 apply fixpack issue
Hi bcalex AA34, I have a similar issue with a customer with Maximo 7.6.1.3 and MS SqlServer 18 applying ifix 06. Do you know what fixes this was fixed?
Best regards
------------------------------
Pablo Condoleo
Original Message:
Sent: Mon June 05, 2023 10:03 AM
From: bcalex AA34
Subject: Maximo 7.6.1.3 apply fixpack issue
We reported This issue (TS010521035.) and has been fixed in later IFIXes. Also IFIXes updates configuration xml s and if any custom changes done to be reapplied.
------------------------------
Bobby Alex