I have an (old) Umbraco 4.0.3 site which has just sat and ran happily for a few years on an eHosting shared server. The site has just gone down showing "An error occurred while processing your request." message.
I am able to log into the back-office and the node structure and all the content are there. I can save and publish and it seems to be writing to the database, however, when I look at the "Link to document" in the Properties tab this is empty for all pages in the site.
I've tried republishing the site and this hasn't resolved it.
I've read that similar issues to this could be caused by a connection drop to the database at some point. eHosting have confirmed they've performed updates to their servers recently.
Does anyone have any recommendations on how to resolve this one?
This issue is now resolved. In case anyone else has this problem, the issue stemmed from SQL and IIS restarting at different times - specifically IIS starting before SQL and so no connection was available. Restarting SQL again resolved the issue.
Empty "Link to document" in admin
Hi everyone,
I have an (old) Umbraco 4.0.3 site which has just sat and ran happily for a few years on an eHosting shared server. The site has just gone down showing "An error occurred while processing your request." message.
I am able to log into the back-office and the node structure and all the content are there. I can save and publish and it seems to be writing to the database, however, when I look at the "Link to document" in the Properties tab this is empty for all pages in the site.
I've tried republishing the site and this hasn't resolved it.
I've read that similar issues to this could be caused by a connection drop to the database at some point. eHosting have confirmed they've performed updates to their servers recently.
Does anyone have any recommendations on how to resolve this one?
Many thanks,
Mike
This issue is now resolved. In case anyone else has this problem, the issue stemmed from SQL and IIS restarting at different times - specifically IIS starting before SQL and so no connection was available. Restarting SQL again resolved the issue.
is working on a reply...