Hello All,
The issue has been resolved after removed the custom trigger (sys.triggers) in CM database.
Thank you!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello Everyone,
We have a single standalone Primary Site currently running Configuration Manager version 2403. I'm attempting to upgrade to version 2409, but the upgrade consistently fails at the "Upgrade ConfigMgr database" step. Upon reviewing the cmupdate.log file, the only error I can identify appears to be related to the ODBC driver.
ERROR: SQL Server error: IF NOT EXISTS(SELECT * FROM sys.triggers WHERE name = 'DBSchema_ins_upd') ~ BEGIN ~ EXEC('CREATE TRIGGER DBSchema_ins_upd ON DBSchema FOR INSERT, UPDATE AS ~ BEGIN ~ INSERT INTO DBSchemaChangeHistory (ChangeID, ObjectName, ObjectVersion, UpdatedBy, UpdateTime, LastEventType, ObjectHash, ObjectHashAlg) ~ SELECT NEWID(), ObjectName, ObjectVersion, UpdatedBy, UpdateTime, LastEventType, ObjectHash, ObjectHashAlg FROM inserted ~ END') ~ END ~ ELSE ~ BEGIN ~ EXEC('ALTER TRIGGER DBSchema_ins_upd ON DBSchema FOR INSERT, UPDATE AS ~ BEGIN ~ INSERT INTO DBSchemaChangeHistory (ChangeID, ObjectName, ObjectVersion, UpdatedBy, UpdateTime, LastEventType, ObjectHash, ObjectHashAlg) ~ SELECT NEWID(), ObjectName, ObjectVersion, UpdatedBy, UpdateTime, LastEventType, ObjectHash, ObjectHashAlg FROM inserted ~ END') ~ END and then Failed to update database.. Failed to apply update changes 0x87d20b15
I couldn't find any errors in the hman.log file. All the necessary permissions appear to be correctly configured. I've also reviewed several related articles posted in the documentation and community forums but haven't found a solution yet. https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjBhLzum-yNAxXMIEQIHW2FAgYQFnoECAsQAQ&url=https%3A%2F%2Fwww.prajwaldesai.com%2Fconfigmgr-database-upgrade-error-0x87d20b15%2F&usg=AOvVaw3qR4tizZOYxtHlLVYtdi2y&opi=89978449
I’ve restarted the primary server multiple times and attempted the upgrade 4–5 times, but the failure occurs at the same stage each time.
Could you please assist with this issue?
Thanks.
Hello All,
The issue has been resolved after removed the custom trigger (sys.triggers) in CM database.
Thank you!