Error Number 0x80040e14 Description ALTER DATABASE failed because a lock could not be placed on database

Question

This is a Go-Live upgrade, so obviously the test upgrade, and a subsequent "refresh migration" were able to go through. 
 However, now that we are trying the final migration, with just the MAS_XXX company data (no system files) we are getting this - over and over again: 
 
 We have severed all connections (the SPID workaround) and restarted the SQL Server several times. 
 Sage 100 Premium, going from 2019 to 2022.1 (LM 7103T has been applied). Tried to manually put the MAS_XXX.bak in the folder (per KB 111959). 
 Anyone have any suggestions? We had hoped to get this done over the weekend. 
 Thanks

rclowe · Accepted Answer

Ended up deleting the target MAS_XXX database and the migration worked.

Kevin M · Answer

I've been burned by that myself, and am now in the habit of taking a backup immediately after the initial software install (including enhancements and service config), so I can always reset to that point. 
 If you've done a test migration, and made changes to system settings (Roles...), take a fresh backup before trying another migration. I've had initial test migrations go fine, only to have 2nd migrations fail with various errors.

Sage 100

Error Number 0x80040e14 Description ALTER DATABASE failed because a lock could not be placed on database

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING