We have just released Patch 126.96.36.199:
Virtual System Administrator™
After applying update, am unable to reapply schema... receiving this SQL error:
Cannot insert the value NULL into column 'description', table 'ksubscribers.dbo.ticdescription'; column does not allow nulls. INSERT fails.
Found what I suspect is a typo in the "core\script\cleanupData2.sql" file on line 1111:
INSERT INTO ticdescription (noteTime, emailAddr, [description], ticketId, adminOnly, partitionId, machType)
I removed the brackets around description:
INSERT INTO ticdescription (noteTime, emailAddr, description, ticketId, adminOnly, partitionId, machType)
Reapplied schema and it worked okay this time.
We also had a similar issue when trying to reapply schema
Fatal messagesys error: Monitorting/Constrats/DF_alertTemplateOverride_agentGuid.sql
Now we can not start the Kaseya Event Services and Network Discovery service, therefore our system is down and I will need to raise a ticket tomorrow.
I see that your server is up and running at this time. There is no need to run schema after the patch update. However, if you are still encountering any issues with schema please submit a Severity 1 ticket and one of our Support teams will assist you. Thank you.
I just raised a Severity 1 ticket in your behalf, as your server is down. You should have received an email wit hthe ticket number and detials. A support technician will engage shortly. Thank you.
I see that Patch 188.8.131.52 is no longer shown on the patch release page.
I have already installed Patch 184.108.40.206, so where does this leave me?
I have not tried to reapply my schema.
Also this is the second pulled patch in the space of a few releases, i.e. 220.127.116.11, for what was the also an issue when reapplying the scheme.
Kaseya where is the Quality control?
Haigh Systems We have not pulled the patch.
Those have schema issues seem to be related to third party modules such as Webroot. You do not need to run reapply schema but Support will assist with your issues if you run into a wall.
If there's anything we're misunderstanding, please let us know.
Ok, when I was looking at the R94 Patch Releases webpage this morning the 18.104.22.168 patch was no longer listed and then I saw the comments about the patch, hence thinking it had been pulled.
I have just gone back to the same webpage and it's back again, so not sure what's happening,
So it's not a typo that bmanning has pointed out? [description]
Sorry for false accusation.
jeffrey.odolski - Has the issue with Webroot been addressed? "Those have schema issues seem to be related to third party modules such as Webroot." I would like to forego any downtime for a known issue....
Hi Tim Varvais - We did suffered this issue with Webroot, both Webroot and Kaseya have started tickets. To my knowledge the issue is not yet resolved. At this time the Webroot module piece in Reapply Database Schema has been cut out, so it doens't bite us again....
Kaseya support started a ticket with Webroot to solve the root cause of this issue. The Kaseya support guy that has the ticket open is Patrick O'Keeffe. The last update I got on this was exactly one week ago....
Webroot are still working on a resolution for the issues with the installation of the Webroot VSA Module but have not as of yet provided an ETA for when this will be fixed.
When is patch .33 being released?
marcb By EOD today.
Tentatively planned for today for on-premise customers and planned for release on Cloud/SaaS Saturday.
FYI - #222958 WEBROOT - Reapply of Schema error (Kaseya on-prem VSA 22.214.171.124)