Yes, the problem was solved. In our case, this was not an Umbraco issue. The client was using WinHost for their hosting services, and the problem was the propogation of the site through their servers. At first, we upgraded the client's plan so it met the requirements of WinHost, but it turned out that wasn't the problem. Working with WinHost support for over a week, they fixed something on their end, then we had to completely wipe the site off their servers and recopy it back again. Then it worked.
So... moral is... check the hosting environment first to ensure it meets with the requirements to properly host your Umbraco site. If that is ruled out, I'm afraid I can't help further...
Well, mine got solved when republishing the site using <useLegacyXmlSchema>true<useLegacyXmlSchema> in umbracoSettings.config. That site is a mishmash of old v4-versions wich might be the reason.
Object reference not set to an instance of an object.
Publishing a website for a client. Home page was working fine, now has an error.
Any page we try to have as the root page (URL showing in Umbraco as "/") throws the error below.
Any sub page we publish shows up fine.
We didn't do anything to the page, I promise. We did upgrade our hosting to a higher site memory allocation, but nothing else there changes either.
Please help!
Umbraco v 4.7.0 (Assembly version: 1.0.4090.38017)
asp.net 4.0
Windows server 2003 / MYSQL / IIS version 6
Stacktrace:
I have the exact same problem (on 4.7.1).
Did you solve it?
Hello Anders.
Yes, the problem was solved. In our case, this was not an Umbraco issue. The client was using WinHost for their hosting services, and the problem was the propogation of the site through their servers. At first, we upgraded the client's plan so it met the requirements of WinHost, but it turned out that wasn't the problem. Working with WinHost support for over a week, they fixed something on their end, then we had to completely wipe the site off their servers and recopy it back again. Then it worked.
So... moral is... check the hosting environment first to ensure it meets with the requirements to properly host your Umbraco site. If that is ruled out, I'm afraid I can't help further...
Good Luck!
Ah.
Well, mine got solved when republishing the site using <useLegacyXmlSchema>true<useLegacyXmlSchema> in umbracoSettings.config.
That site is a mishmash of old v4-versions wich might be the reason.
is working on a reply...