We have released patch 22.214.171.124 to production:
Virtual System Administrator™
Software Deployment and Update
Tried to patch our demo VSA and running reapply schema got stuck at 46% with this error: Fatal MessageSys Error: Monitoring/Constraints/DF_alertTemplateOverride_agentGuid.sql
Same here. There are problems with DF_alertTemplateOverride_agentGuid.sql and dbo.PKAlertTemplateOverride.sql.
DF_alertTemplateOverride_agentGuid.sql wants to put a constraint on a a field that already has a constraint, and dbo.PKAlertTemplateOverride.sql is trying to put a constraint on a non null field.
Support has been able to reproduce this internally and I got map.xml that fixed the problem. It had those problem rows commented out.
Thank you for your reports on this issue.
Patch 126.96.36.199 has been pulled from production and we will be releasing patch 188.8.131.52 to rectify this issue.
I will update this thread when patch 184.108.40.206 has been released along with a new thread for the documentation.
Apologies for the inconvenience this may have caused.
...and for people who installed it before it was pulled?
karoded Unzip the attached map.zip and place it in C:\Kaseya\DBInstall\Monitoring
karoded Alternatively, If you don't want to apply the out of band fix provided above, you can wait until patch 220.127.116.11 is released to correct the issue.
Or don't run reapply schema if you have done the patching using option 1 as mentioned in installation instructions: help.kaseya.com/.../RN
I always run it manually because its best practice :)
Thanks...I did see your post neuvoja after installing but before running reapply schema so thank you especially for posting that so quickly! -- I just wasn;t sure if perhaps other issues were found that caused the update to be pulled.
A reapply schema should not be needed. If you're seeing functionality break after running a patch which necessitates running a reapply schema, please let us know why so we can look into this.
jeffrey.odolski I think we are having this discussion after almost every patch. Support tells me that its best practice to run reapply schema after a patch and you are telling me its not. So maybe Kaseya should discuss this internally with support & product management teams and tells us customers what is the preferred way?
Absolutely. I'll PM you so we can discuss in detail.
we installed the 18.104.22.168 and had no issues with it. only weird thing is (probably because of the pull back is)
Version Number: 22.214.171.124
Installed Patch Level: 126.96.36.199
Available Patch Level: 188.8.131.52
Updated our demo VSA to .31 and no problems so far. Waiting for the rls notes and gonna patch prod. VSA next week if nothing major is reported over the weekend.