Question

6
Replies
219
Views
Anandh Palanisamy Member since 2013 62 posts
Ford Motor Company
Posted: March 7, 2017
Last activity: August 1, 2017
Closed

Wrong date getting insert into pr_sys_locks table on the pxExpireDateTime value

Hi,

We have agent processing, during the agent processing we see the pxExpireDateTime value getting inserted wrongly, due to that those agents are getting failed.

"seeing couple of instances where DMS Agents are getting errored out while they are trying to update System lock. In following example system is changing the pxExpireDateTime from ‘<2017-03-06 15:20:45.84>’ to <0001-03-06 15:20:45.923> .

2017-03-06 14:50:45,953 [.PRPCWorkManager : 3] [ STANDARD] [rdOWSOneApp:01.01.05] (nternal.access.LockManagerImpl) ERROR - Problem updating the lock for "XXXX CF-14762138"

com.pega.pegarules.pub.database.DatabaseException: Problem updating the lock for "XXXX CF-14762138": code: 242 SQLState: S0003 Message: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.

From: (B3D78F747D7D218B452DFDC81D31A5FE4)

SQL: update pr_sys_locks set pxExpireDateTime = ?, pxLockHandle = ?, pxOwnerId = ?, pxSystemName = ?, pxSystemNode = ?, pxUpdateDateTime = ?, pxUpdateOpName = ?, pxUpdateOperator = ?, pxUpdateSystemID = ?, pxUserHost = ? where pzInsKey = ? and pxOwnerId = ? and pxExpireDateTime = ?

SQL Inserts: <0001-03-06 15:20:45.923> <XXXX CF-14762138> <B3D78F747D7D218B452DFDC81D31A5FE4> <systemName> <f9d23fcdc1330deeb5d6be5589242aa7> <2017-03-06 14:50:45.923> <Agent(XXXX-ClaimFile.ProcessBatchClaimCovers)> <System> <systemName> <> <XXXX CF-14762138> <B3D78F747D7D218B452DFDC81D31A5FE4> <2017-03-06 15:20:45.84>

Caused by SQL Problems.

Problem #1, SQLState S0003, Error code 242: com.microsoft.sqlserver.jdbc.SQLServerException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.

Did anyone faced this kind of issue?

Regards,

Anandh

***Updated by moderator: Lochan to add Categories***

Case Management User Interface
Moderation Team has archived post
Share this page LinkedIn