none
ConvertTo-SPProjectDatabase fails RRS feed

  • Question

  • I am trying to make upgrade of Project Server 2010 to Project Server 2013 on our SP 2013 test environment.

    Running PS script like this:
    Convertto-SPProjectDatabase -WebApplication  Ourwebapp/  -Dbserver Ourserver -ArchiveDbname ProjectServer_Archive -DraftDbname ProjectServer_Draft -PublishedDbname ProjectServer_Published -ReportingDbname ProjectServer_Reporting -ProjectServiceDbname ProjectService2013_PWA

    Returns the following error:

    Convertto-SPProjectDatabase : TCP Provider: No such host is known.
    OLE DB provider "SQLNCLI11" for linked server "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" returned message "Login timeout expired".
    OLE DB provider "SQLNCLI11" for linked server "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" returned message "A network-related or instance-specific error h
    as occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server
     is configured to allow remote connections. For more information see SQL Server Books Online.".

    Linked server xxxxxxxxx… seems to be a GUID.

    I am following the steps described here ee662496(v=office.15). Preceding steps reported ok.

    The upgrade log generated by ConvertTo-SPProjectDatabase says upgrade is 100% ('Finished successfully!') and without warnings or errors. The resulting DB is built however no data have been copied from the original databases.

    Looking into SP log, the error is generated when trying to run a SQL SELECT statement connecting to a server with above mentioned GUID. Judging from the SQL this seems to be an attempt to copy data from the first table in one of the old DB's.

    Can someone tell me what to do?

     

    Monday, June 30, 2014 2:00 PM

Answers

  • The described behaviour turned out to be caused by faulty configuration of SQL Server aliases.
    • Marked as answer by no1ped Friday, September 12, 2014 12:32 PM
    Friday, September 12, 2014 12:32 PM

All replies

  • Check that the firewalls are open for SQL Server.

    Make sure that your SQL is not routing your database thru a Linked Server.

    Can you ping SQL Server?

    Use real syntax in your PowerShell example.  For example Ourwebapp will not work. Are you using http://OurWebApp/PWA?

    And the same for SQL server

    Is it OurServer or is it OurServer.OurDomain.local or ourServer.ourDomain.local/SharePoint

    Is it a name instance?

    Did you check the database security and make sure that the process have access to database, etc?

     


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, July 1, 2014 4:14 AM
    Moderator
  • Hi Michael! - thanks a lot for your quick response!

    Everything is taking place on a single server albeit a cloud server.

    There are no linked servers defined in SQL Server.

    I can ping the servername used in -Dbserver.

    I am using -WebApplication http://OurWebApp/ (not ending with PWA - is that not correct?) as is
    shown in Central Admin - >Manage Web Applications.

    I am using -Dbserver servername.something.company.countrycode.

    It is the default SQL Server instance.

    I am running Windows PowerShell (with SharePoint
    module loaded) as Administrator, and I am logged in with an account, that is
    sysadmin, serveradmin, securityadmin, setupadmin (probably overdoing, but
    anyway..) on SQL Server and db_owner on the four "old" databases.


    Tuesday, July 1, 2014 7:51 AM
  • What version of windows is running in the cloud?

    What form of authentication are you using? AD or Login.onmicrosoft.com

    Did you install the SQL Server Express?  If you are using SQL Azure, that is a who different SQL engine and limited in scope.

    Did you install and get project server running?  I would provision project server and see if it creates a PWA site. Make sure that all can work and then you will know most of you bugs will be out when you do the conversion.  You don't have to use the PWA but I find it a good design.  The top of site collection can be general information about PMO.

    The error message indicates that it cannot find SQL server?  Are you the administrator?

    Are you running SQL authentication? or AD authentication? for SQL Server

    What version of SQL Server is running.  SQL 2014 is not supported at this time.

    Cheers! 


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Wednesday, July 2, 2014 3:15 AM
    Moderator
  • Hi again - and thank you for your effort!

    Server is running Windows Server 2012.
    Using AD authentication.
    Using SQL Server 2012.

    Project Server Service and Project Service Application configured and running.
    I have had a PWA running and accessible, in principle seeming ok, but of course useless since no projects or resources showed, and I then discovered, that no data had been moved to the Project services DB. At that time I happily ignored the error message, since the upgrade log said success (as decribed above).
     I am logged in with an account, that is sysadmin, serveradmin, securityadmin, setupadmin (probably overdoing, but
    anyway..) on SQL Server and db_owner on the four "old" databases.

    I am running AD authentication for SQL Server.

    Using SQL Server 2012.

    Wednesday, July 2, 2014 9:33 AM
  • The described behaviour turned out to be caused by faulty configuration of SQL Server aliases.
    • Marked as answer by no1ped Friday, September 12, 2014 12:32 PM
    Friday, September 12, 2014 12:32 PM