locked
Migrate 2007 to 2010 SSO RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello, we are trying to migrate (not in place upgrade but new servers) SP 2007 to 2010. In management shell I've entered [upgrade-spsinglesignondatabase -ssoconnectionstring "data source=ac-sharepoint\officeservers;database=sso;trusted_connection=yes; -securestoreconnectionstring "data source=drfl-sharepoint\drflsharepoint;database=secure_store_service_db_c99fdcb1816247e18aac4fbeef5284dd;trusted_connection=yes;" ] along with a passphrase of course. the error I'm getting is looks like this: [ + CategoryInfo          : InvalidData: (Microsoft.Offic....UpgradeCommand:
       UpgradeCommand) [Upgrade-SPSingleSignOnDatabase], PipelineStoppedException
        + FullyQualifiedErrorId : Microsoft.Office.SecureStoreService.PowerShellCm
       dlet.UpgradeCommand

    Upgrade-SPSingleSignOnDatabase : An error was encountered while reading from th
    e database that has the connection string 'data source=ac-sharepoint\officeserv
    ers;database=sso;trusted_connection=yes;' : Could not find stored procedure 'db
    o.sso_RetrieveSSOConfig'..
    At line:1 char:31
    + upgrade-spsinglesignondatabase <<<<  -ssoconnectionstring "data source=ac-sha
    repoint\officeservers;database=sso;trusted_connection=yes;" -securestoreconnect
    ionstring "data source=drfl-sharepoint\drflsharepoint;database=secure_store_ser
    vice_db_c99fdcb1816247e18aac4fbeef5284dd;trusted_connection=yes;"
        + CategoryInfo          : NotSpecified: (:) [Upgrade-SPSingleSignOnDatabas
       e], SecureStoreServiceException
        + FullyQualifiedErrorId : Microsoft.Office.SecureStoreService.PowerShellCm
       dlet.UpgradeCommand]

    I'm not sure where I should be finding this stored procedure to chase the error. any help would be greatly appreciated!

    George

    • Moved by Mike Walsh FIN Wednesday, February 16, 2011 7:44 PM SP 2010 q (From:SharePoint - Setup, Upgrade, Administration and Operation (pre-SharePoint 2010))
    Wednesday, February 16, 2011 7:06 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello George,

    We noticed the PowerShell Command has incorrect in Syntax:

    1. upgrade-spsinglesignondatabase -ssoconnectionstring "data source=ac-sharepoint\officeservers;database=sso;trusted_connection=yes; -securestoreconnectionstring "data source=drfl-sharepoint\drflsharepoint;database=secure_store_service_db_c99fdcb1816247e18aac4fbeef5284dd;trusted_connection=yes;"

    "data source=ac-sharepoint\officeservers;database=sso;trusted_connection=yes;  <Missing a quote after yes>;

    Verify the above was indeed not missing a quote. Based on error I believe they weren’t and that this is a typo – but need to verify.

     
    2. Verify that the Single-Sign On Database is named “SSO”. This is the default naming convention in MOSS 2007, but it could be named something else.

    3.Assuming #2 is correct. Check the “SSO” database in SQL Databases (or other name – if named differently) and expand the “Programmability” folder.

    Expand the “Programmability” folder. Expand the “Stored Procedures” folder within . There should be a stored procedure called “dbo.sso_RetrieveSSOConfig”. If this stored procedure does not exist – this is the point of failure.

    We have one option at this point (concluding all Syntax in the PowerShell command is correct):

    Rebuild a new SSO database in SharePoint 2007 which will then contain this stored procedure. Application Definition settings would need to be updated accordingly prior to upgrade.

    This database could then be updated to SharePoint 2010.

    Thanks,

    Manas


    • Marked as answer by GHH3 Tuesday, April 19, 2011 10:29 PM
    Wednesday, March 30, 2011 7:01 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello George,

    We noticed the PowerShell Command has incorrect in Syntax:

    1. upgrade-spsinglesignondatabase -ssoconnectionstring "data source=ac-sharepoint\officeservers;database=sso;trusted_connection=yes; -securestoreconnectionstring "data source=drfl-sharepoint\drflsharepoint;database=secure_store_service_db_c99fdcb1816247e18aac4fbeef5284dd;trusted_connection=yes;"

    "data source=ac-sharepoint\officeservers;database=sso;trusted_connection=yes;  <Missing a quote after yes>;

    Verify the above was indeed not missing a quote. Based on error I believe they weren’t and that this is a typo – but need to verify.

     
    2. Verify that the Single-Sign On Database is named “SSO”. This is the default naming convention in MOSS 2007, but it could be named something else.

    3.Assuming #2 is correct. Check the “SSO” database in SQL Databases (or other name – if named differently) and expand the “Programmability” folder.

    Expand the “Programmability” folder. Expand the “Stored Procedures” folder within . There should be a stored procedure called “dbo.sso_RetrieveSSOConfig”. If this stored procedure does not exist – this is the point of failure.

    We have one option at this point (concluding all Syntax in the PowerShell command is correct):

    Rebuild a new SSO database in SharePoint 2007 which will then contain this stored procedure. Application Definition settings would need to be updated accordingly prior to upgrade.

    This database could then be updated to SharePoint 2010.

    Thanks,

    Manas


    • Marked as answer by GHH3 Tuesday, April 19, 2011 10:29 PM
    Wednesday, March 30, 2011 7:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We're seeing the same issue. I've checked that

    1. the syntax is correct,

    2. SSO database is indeed "SSO" by checking on "managed server settings" from Central Admin on the the server that has SSO service,

    3. the "dbo.sso_RetrieveSSOConfig" does exist in the "SSO" database...

    What else could we try at this point?

    Upgrade-SPSingleSignOnDatabase : The pipeline has been stopped.
At line:1 char:31
+ Upgrade-SPSingleSignOnDatabase <<<< -SSOConnectionString "Data Source=scv-sq
l8\scvsql8;Database=SSO;Trusted_Connection=yes;" -SecureStoreConnectionString "
Data Source=scv-sql8\scvsql8;Database=Secure_Store_Service_DB_39f4ddeebe8543d19
72b0d2b6e087750; Trusted_Connection=yes;"
  + CategoryInfo     : InvalidData: (Microsoft.Offic....UpgradeCommand:
  UpgradeCommand) [Upgrade-SPSingleSignOnDatabase], PipelineStoppedException
  + FullyQualifiedErrorId : Microsoft.Office.SecureStoreService.PowerShellCm
  dlet.UpgradeCommand


Upgrade-SPSingleSignOnDatabase : Operation failed. An error was encountered dur
ing the data migration operation.
At line:1 char:31
+ Upgrade-SPSingleSignOnDatabase <<<< -SSOConnectionString "Data Source=scv-sq
l8\scvsql8;Database=SSO;Trusted_Connection=yes;" -SecureStoreConnectionString "
Data Source=scv-sql8\scvsql8;Database=Secure_Store_Service_DB_39f4ddeebe8543d19
72b0d2b6e087750; Trusted_Connection=yes;"
  + CategoryInfo     : NotSpecified: (:) [Upgrade-SPSingleSignOnDatabas
  e], SecureStoreServiceException
  + FullyQualifiedErrorId : Microsoft.Office.SecureStoreService.PowerShellCm
  dlet.UpgradeCommand

    Emma
    Thursday, May 5, 2011 2:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi George and all other people. Did you got to migrate stored credentials too?

    I used Upgrade-SPSingleSignOnDatabase command and it worked for migrate application definitions, but stored credentials (user/password) had not moved to new SharePoint 2010 farm.

    Is that possible?

    Thanks in advance!

    Toni A.

    Thursday, June 16, 2011 11:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Emma did you find the solution for point 3.
    Thursday, October 27, 2011 11:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi back Toni,

    We went through so many iterations, I'm not sure where exactly things all worked. But since we tightly use AD integration, there was no problem with stored credentials. At some point I found a couple of web blogs that discussed the steps to get an installation like ours to work. Each omitted a step here and there assuming you knew already, but between the two all steps were there, so up we are.

    George

    Thursday, October 27, 2011 12:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I used Upgrade-SPSingleSignOnDatabasecommand and it worked for migrate application definitions, but stored credentials (user/password) had not moved to new SharePoint 2010 farm.

    Is that possible?

    Brini



    Wednesday, March 14, 2012 2:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Solution PLZ for stored credentials
    Wednesday, March 14, 2012 2:34 PM