Not sure what you did to "adjust" the surrogate keys, but that is an ill-advised action if you're not familiar with SQL or how to set/reset the key values directly in the database. That may now be the source of your problem.

If the keys are in sync, and since we are close to the beginning of a new year, verify you have properly created your 2025 calendars in GL and IM, especially if your transaction posting worked properly before the end of 2024. If the problem persists, you need to post the exact messages you are receiving, the tasks in which you receive them, and include your version.

The suggestion was to find the MAX(intJobLineKey) value in tPA00125 and then add + 1 to this and ensure the tciSurrogateKey - NextKey value for tablename = 'tPA00125' was equal to the MAX + 1 value or greater. The reasoning was because the system was unable to create a project transaction and the SQL Profiler trace was indicating an attempt to create a record which already existed and thus generating an Exception. Support is collecting the database for review as the above solution did not resolve the issue.