Update fail in IIs environment [#2805313]

The following updates returned messages

ultimate_cron module

Update #7205
Failed: PDOException: SQLSTATE[42000]: [Microsoft][ODBC Driver 11 for SQL Server][SQL Server]Object 'ultimate_cron_job.name' cannot be renamed because the object participates in enforced dependencies.: EXEC sp_rename :old, :new, :type; Array ( [:old] => ultimate_cron_job.name [:new] => name_old [:type] => COLUMN ) in db_change_field() (line 3020 of D:\xxxx\xxxx\docroot\includes\database\database.inc).

Comments

Comment #1

23 September 2016 at 15:06

Will Kirchheimer created an issue. See original summary.

Comment #2

wct097 CreditAttribution: wct097 as a volunteer commented 18 November 2016 at 18:49

We had the same issue. I think it's an issue with the database abstraction using the sqlsrv module. I don't have a LAMP setup to confirm, but in MSSQL the ultimate_cron_job table has a calculated field called __unique_machine_name that prevents you from renaming and replacing the name field. I ended up writing a script to backup (copy), drop & replace the ultimate_cron_log and ultimate_cron_lock tables with the field changes in place, then I hacked the ultimate_cron module to remove that portion of the update. It's messy, but it works.

We've had a number of issues with ultimate_cron that we attribute to the differences in how the database abstraction works.