We have about a dozen Umbraco sites (all 4.5.2) running on a server that received an automatic Windows Update last night. When the server restarted, about half of those sites started throwing the "there's still work to do" no nodes error when visiting their home page. Logging into the back office and doing a "republish entire site" took care of the problem in each case.
Question: has anyone seen this before? I'm not 100% sure it was caused by a Windows Update, but why would about half of our sites suddenly start throwing the no nodes error? I wasn't able to log onto the machine to check for umbraco.config, etc.--I had to get the sites back live ASAP--but why would this happen?
I think that it is more likely connected to the restart of the machine, than the updates themselves. When it starts back up, then it migh fire up the app pools before the sql server can get running, which might lead umbraco to believe that there is no content.
Darren Ferguson has a description and a workaround for a similar issue here
Windows Update causes "No Nodes" error?
We have about a dozen Umbraco sites (all 4.5.2) running on a server that received an automatic Windows Update last night. When the server restarted, about half of those sites started throwing the "there's still work to do" no nodes error when visiting their home page. Logging into the back office and doing a "republish entire site" took care of the problem in each case.
Question: has anyone seen this before? I'm not 100% sure it was caused by a Windows Update, but why would about half of our sites suddenly start throwing the no nodes error? I wasn't able to log onto the machine to check for umbraco.config, etc.--I had to get the sites back live ASAP--but why would this happen?
Thanks,
Matt
Hi.
I think that it is more likely connected to the restart of the machine, than the updates themselves. When it starts back up, then it migh fire up the app pools before the sql server can get running, which might lead umbraco to believe that there is no content.
Darren Ferguson has a description and a workaround for a similar issue here
Is the sql server placed on the same machine?
is working on a reply...