Easy (i thought)
i created an alternate Access mapping to the domain hosting mysite from
within the central Admin website.
this said it had completed ok.
Going to MySite (via either url) showed the standard Sharepoint Error page.
Reading up on this i changed the web.config page to show the actual error:
[HttpException (0x80004005): The DataSourceID of 'TopNavigationMenu' must be
the ID of a control of type IHierarchicalDataSource. A control with ID
'topSiteMap' could not be found.]
System.Web.UI.WebControls.HierarchicalDataBoundControl.GetDataSource()
+1415249
System.Web.UI.WebControls.HierarchicalDataBoundControl.ConnectToHierarchicalDataSource() +158
System.Web.UI.WebControls.HierarchicalDataBoundControl.OnLoad(EventArgs
e) +16
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061
Reading around on this most things say it is todo with badly formed
web.config files.
I web.config had not changed (until i enabled SafeMode's
AllowPageLevelTrace, CallStack along with the CustomError to be able to view
the error)
Anyone got ANY IDEA? currently the MySite part if completely unusable
Check your DNS Settings.
Grtz,
Maurice
"Tepe" <Te...@discussions.microsoft.com> wrote in message
news:A595088B-9AEF-40C4...@microsoft.com...
the DNS is working fine, both the http://x and http://x.y.z both have the
same IP address (the NLB for the front end servers)
any other thoughts?
Did anyone ever figure this out? I am seeing the same issue.
There are safecontrol errors in the sharepoint log, but it does not
say what it cannot load
Ok i got it working about 2 days ago, i removed all custom solutions from
the installation. This did not (by itself) remove the issue.
I then removed the Alternate Access Mapping, and then re-added it 10mins
later.
Somehow this seemed to reset things and it all started to work.
It was then a question of adding in the custom solutions in one at a time
until we found the issue. But this time we just remove the offending custom
solution and reset the Alternate Access Mapping as mentioned above (as
removing the solution did not stop the error message)
Hope this helps