We help IT Professionals succeed at work.

SharePoint MOSS 2007 SSP issue - Unable to access as invalid URI error is returned

stoplak
stoplak asked
on
Hopefully a answer can be given as to why this has occcured and what can be done to resolve it.

In a nutshell the SSP within the MOSS 2007 farm can no longer be accessed as the system will return a invalid URI error from either a client browser or from the local host server (WFE).

Initial investigations gave the following as the error return:

[UriFormatException: Invalid URI: A port was expected because of there is a colon (':') present but the port could not be parsed.]
   System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) +7201167
   System.Uri.CreateUri(Uri baseUri, String relativeUri, Boolean dontEscape) +209
   Microsoft.SharePoint.Administration.SPWebApplication.GetResponseUri(SPUrlZone zone, String path) +99
   Microsoft.SharePoint.Administration.SPSiteCollection.get_Item(String strSiteName) +122
   Microsoft.Office.Server.Web.SharedServicesQuickLaunchProvider.GetChildNodes(SiteMapNode parent) +297
   System.Web.UI.WebControls.SiteMapDataSource.GetTreeView(String viewPath) +35
   System.Web.UI.WebControls.HierarchicalDataBoundControl.GetData(String viewPath) +43
   System.Web.UI.WebControls.Menu.DataBindItem(MenuItem item) +53
   System.Web.UI.WebControls.Menu.PerformDataBinding() +49
   System.Web.UI.WebControls.HierarchicalDataBoundControl.PerformSelect() +114
   System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +82
   System.Web.UI.WebControls.Menu.EnsureDataBound() +38
   System.Web.UI.WebControls.Menu.OnPreRender(EventArgs e, Boolean registerScript) +64
   Microsoft.SharePoint.WebControls.AspMenu.OnPreRender(EventArgs e) +166
   System.Web.UI.Control.PreRenderRecursiveInternal() +108
   System.Web.UI.Control.PreRenderRecursiveInternal() +224
   System.Web.UI.Control.PreRenderRecursiveInternal() +224
   System.Web.UI.Control.PreRenderRecursiveInternal() +224
   System.Web.UI.Control.PreRenderRecursiveInternal() +224
   System.Web.UI.Control.PreRenderRecursiveInternal() +224
   System.Web.UI.Control.PreRenderRecursiveInternal() +224
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3394

 
The AAM was checked to see if this was caused by the central admin site URL's being changed (as some suggestions from other sites said to check), but the AAM has not changed as far as I can see.  I can access everything from Central admin, just not the SSP.

Attempts to build a new SSP failed as the system was unable to provision a new SSP and returned teh same error.

I have searched the web in regards to the URI error, but was unable to find any solution.
Comment
Watch Question

Seelan NaidooMicrosoft Systems Admin
Commented:
Hi,

Can you see the SSP via IIS Manager?
What port is it using?
Commented:
Just the basics - IISRESET been ran?  Server been restarted?
BTW, what service pack are you at? (OS, SQL & MOSS)

Author

Commented:
Sorry for the late reply, been away from work due to illness.

Now to your questions.....

Yes - a IISRESET command was run on all WFE servers and a server restart on all WFE servers was conducted as well.

Yes -  I can see the SSP's web application pool and site within IIS manager

All the WFE servers are patched to the latest O/S and MOSS patches.  The SQL cluster that is connected to the farm is also patched to the lasted versions.  These were updated to the latest by myself when I recently took over the role as SharePoint Admin for my company approx 3 months ago.

The SSP is using port 50002, while the central admin is using port 50000

Now the weird thing is I can still access the search administration page within the SSP.  So I still have full search administrative control.  I would have thought that if the SSP admin page was giving the error, then I wouldnt have been able to access the sub pages.
Seelan NaidooMicrosoft Systems Admin
Commented:
Has any changed regarding Application Pools or service accounts that they use?

Author

Commented:
Thankyou all for trying to getting this weird issue resolved.

In the end I bit the bullet and rebuilt the production envrionment and this immediately resolved the problem.  Drastic as this step was, my company's DR / Major Incident policies dictated this course of action.

Hopefully the URI issue never crops up again.  Once again thankyou to those that replied to this thread to help me.

Author

Commented:
Thankyou all for trying to getting this weird issue resolved.

In the end I bit the bullet and rebuilt the production envrionment and this immediately resolved the problem.  Drastic as this step was, my company's DR / Major Incident policies dictated this course of action.

Hopefully the URI issue never crops up again.  Once again thankyou to those that replied to this thread to help me.

Author

Commented:
Whilst the suggested answers were correct to locate the root cause, they were not used in the solution taken.