And when logged in and browsing the content-tree, the same error is thrown inside the workarea when you click the nodes. I have tried restoring from an old backup, but that does not seem to work. Unfortunately I can't give a more detailed description since the error just "started to appear" without changes to the content or site.
Is the website in its own app pool in IIS. If not can you add it. If it is in own app pool can you try restarting it see if that fixes the problem. If it does then keep an eye on it just to ensure it does not go down again. Also can you ensure network service has appropriate permissions on umbraco root dir it may be that they have been lost?
I found the error, it had to do with the languages and managed hostnames. Somehow there was only two languages but the managed hostnames needed three, thus referenced wrongly. Fixed this in the database and the error disappeared.
"Object reference not set..." suddely began without explanation
Info:
Error:
Haven't been working with this site for quite some time and it has run like clockwork until now. When visiting the site, it throws:
-------------------------------------------
---------------------------------------
And when logged in and browsing the content-tree, the same error is thrown inside the workarea when you click the nodes. I have tried restoring from an old backup, but that does not seem to work. Unfortunately I can't give a more detailed description since the error just "started to appear" without changes to the content or site.
Pierre,
Is the website in its own app pool in IIS. If not can you add it. If it is in own app pool can you try restarting it see if that fixes the problem. If it does then keep an eye on it just to ensure it does not go down again. Also can you ensure network service has appropriate permissions on umbraco root dir it may be that they have been lost?
Regards
Ismail
I found the error, it had to do with the languages and managed hostnames. Somehow there was only two languages but the managed hostnames needed three, thus referenced wrongly. Fixed this in the database and the error disappeared.
is working on a reply...