It happens both in the designer and from the web interface. You might have an issue with the publishing page layout URl being invalid or pointing to a URl which is not an alternate access mapping.
I am really at a loss as to what to do to fix this issue, any suggestions would be greatly appreciated. If you go into the pages library so you can see the home page listed there then hover over the value for the layout field on that page, look to see what the URl is. Do you either fiddler or IE Dev tools (or any other browser based debugger) look for authentication/access denied errors - my guess is that within the actual master pages some artifact (image, css, etc.) you are not allowed to access it - which throws this error.
Server error information comes from the following source files.
For details about the way that error information is defined, see the My SQL Internals Manual.
The problem is a corrupted rpm database, mostly coming into existence because of an aborted update process.
It also happens sometimes when the package containing rpm itself is updated.
Also if the database administrator changes the language setting, that affects the language of error messages.
Rest assured that all the content is still available!
For error checking, use error codes, not error messages.
We are delighted to direct you to the Crack Berry Forums, a well-established and thorough support channel, for continued Black Berry device support.
When we launched Crack 10 years ago, we set out to make it a fun and useful destination where Black Berry Smartphone owners could share their excitement and learn to unleash the full potential of their Black Berry.