Closing a job in a test site fails after the test database was renamed or rebuilt, because the integration record still points at the old database. Update the connection details, reset the Host System, and save.
Problem
In a test site, closing a job under Ship > Utilities > Close Job returns an error, and the save step fails with "Exception building save batch". The log shows the username and password used to reach the test database are wrong.
Cause
The test-site integration record still holds the old test database's connection details (server, database name, or sign-in), so Shipstore cannot reach the test database and the close/save step fails. Editing the record also resets the Host System box to "custom", which breaks the connection further if you save it that way. (EPMS means Enterprise Print Management System.)
Fix
- Go to Admin > Integrations and open the EPMS integration on the test site.
- Update the load, ship, and void connection details so the database name points at the new test database.
- Confirm the username and password match the current test database.
- Set Host System back to Enterprise Print Management System (it changes to "custom" whenever you edit the record).
- Click Save.
- Close the test job again to confirm the error is gone.
What you should see
Close Job completes with no save error, and the record shows the Host System as Enterprise Print Management System with the new database name.