A decade later, the Crack Berry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more Black Berry owners with their questions.
All the developer support forum content and knowledge base resources have moved to a new system as of April 1, 2017.
Error codes are stable across GA releases of a given My SQL series.
Before a series reaches GA status, new codes may still be under development and subject to change.
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.
A duplicate database, on the other hand, cannot be used in this way: it is not intended for failover scenarios and does as described in "Preparing the RMAN DUPLICATE Auxiliary Instance: Basic Steps".
For the duplication to work, you must connect RMAN to both the target (primary) database and an auxiliary instance started in mode.
Black Berry remains committed to providing excellent customer support to our customers.Rest assured that all the content is still available!For error checking, use error codes, not error messages.I had the same problem and found this very simple solution which worked for me.The above link offers more detail, but simply put, this is what I did.