locked
Unable to Create new SSP in SharePoint 2007 RRS feed

  • Question

  • Unable to Create new SSP in SharePoint 2007, when we click New SSP it throws the following error.

    "An unhandled exception occurred in the user interface.Exception Information: Invalid URI: A port was expected because of there is a colon (':') present but the port could not be parsed."


    Thanks Vivek http://www.redpipit.com
    Thursday, June 30, 2011 1:46 AM

Answers

  • Hi,

    1. Please go to central administration > operations > alternate access mapping make sure the URLs for your central administration site inludes ":" and port number.

    2. check your server IP is IPV4 OR IPV6

    http://social.msdn.microsoft.com/Forums/en/windowsmobiledev/thread/e043c2a7-bdef-4527-8780-03b54b661417

    3. You can use the way in below link to debug this error.

    http://secretsofsharepoint.com/cs/blogs/todd-klindt/archive/2010/08/24/event-id-6801-invalid-uri-with-user-profile-service-on-sharepoint-2010.aspx

     4. Did you do any customizations to sspdetails.aspx page

     5. Please check event logs and ULS logs to see if there are more relevant message for this issue.

    Seven Ma

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tnmff@microsoft.com     

    • Proposed as answer by dillu Friday, July 1, 2011 9:13 AM
    • Marked as answer by Wayne Fan Monday, July 11, 2011 3:35 AM
    Friday, July 1, 2011 8:28 AM
  • This probably could be due to traces of a old corrupt SSP

    Event viewer and ULS are the places that I will look into. use ULS log viewer.

    If you have more than one SSP's then use the below command to remove all the associated SSP's. Just keep one for the purpose of association.

    Syntax

    stsadm -o deletessp
       -title <SSP name>
       [-deletedatabases]
       [-force]

    Check for the IIS Site and App Pool (SSP) on all the servers holding the web application service in the farm,. If found manual delete should work.

    Also the SSP database. Total clean up followed by an IISReset/Restarting the Timer Job Service.

    Create a new SSP using the below command. Doing this from command line always works great for me;

    stsadm -o createssp
       -title <SSP name>
       -url <Web application URL>
       -mysiteurl <MySite URL>
       -ssplogin <user name>
       -indexserver <index server>
       -indexlocation <index file path>
       [-ssppassword <password>]
       [-sspdatabaseserver <SSP database server>]
       [-sspdatabasename <SSP database name>]
       [-sspsqlauthlogin <SQL user name>]
       [-sspsqlauthpassword <SQL password>]
       [-searchdatabaseserver <search database server>]
       [-searchdatabasename <search database name>]
       [-searchsqlauthlogin <SQL user name>]
       [-searchsqlauthpassword <SQL password>]
       [-ssl <yes|no>]
    • Marked as answer by Wayne Fan Monday, July 11, 2011 3:35 AM
    Friday, July 1, 2011 12:11 PM

All replies

  • When I re try the delete command in STSADM i got this error "A failure occured during the processing of this command. check diagnostic logs for more information."
    Thanks Vivek http://www.redpipit.com
    Thursday, June 30, 2011 6:56 AM
  • Hi,

    1. Please go to central administration > operations > alternate access mapping make sure the URLs for your central administration site inludes ":" and port number.

    2. check your server IP is IPV4 OR IPV6

    http://social.msdn.microsoft.com/Forums/en/windowsmobiledev/thread/e043c2a7-bdef-4527-8780-03b54b661417

    3. You can use the way in below link to debug this error.

    http://secretsofsharepoint.com/cs/blogs/todd-klindt/archive/2010/08/24/event-id-6801-invalid-uri-with-user-profile-service-on-sharepoint-2010.aspx

     4. Did you do any customizations to sspdetails.aspx page

     5. Please check event logs and ULS logs to see if there are more relevant message for this issue.

    Seven Ma

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tnmff@microsoft.com     

    • Proposed as answer by dillu Friday, July 1, 2011 9:13 AM
    • Marked as answer by Wayne Fan Monday, July 11, 2011 3:35 AM
    Friday, July 1, 2011 8:28 AM
  • This probably could be due to traces of a old corrupt SSP

    Event viewer and ULS are the places that I will look into. use ULS log viewer.

    If you have more than one SSP's then use the below command to remove all the associated SSP's. Just keep one for the purpose of association.

    Syntax

    stsadm -o deletessp
       -title <SSP name>
       [-deletedatabases]
       [-force]

    Check for the IIS Site and App Pool (SSP) on all the servers holding the web application service in the farm,. If found manual delete should work.

    Also the SSP database. Total clean up followed by an IISReset/Restarting the Timer Job Service.

    Create a new SSP using the below command. Doing this from command line always works great for me;

    stsadm -o createssp
       -title <SSP name>
       -url <Web application URL>
       -mysiteurl <MySite URL>
       -ssplogin <user name>
       -indexserver <index server>
       -indexlocation <index file path>
       [-ssppassword <password>]
       [-sspdatabaseserver <SSP database server>]
       [-sspdatabasename <SSP database name>]
       [-sspsqlauthlogin <SQL user name>]
       [-sspsqlauthpassword <SQL password>]
       [-searchdatabaseserver <search database server>]
       [-searchdatabasename <search database name>]
       [-searchsqlauthlogin <SQL user name>]
       [-searchsqlauthpassword <SQL password>]
       [-ssl <yes|no>]
    • Marked as answer by Wayne Fan Monday, July 11, 2011 3:35 AM
    Friday, July 1, 2011 12:11 PM