mentok74
asked on
Project 2007 Migration Failures
I am working on a Project 2003 Migration to Project 2007. Upon running the
the Migration Tool i receive the folling in the log:
07/22/2008 16:24:59.162 Log file Initialized
07/22/2008 16:24:59.162 Migration tool version is 12,0,4518,1014
07/22/2008 16:24:59.162 Configuration file is c:\p12migration.ini
07/22/2008 16:24:59.459 Connecting to Project Server 2007 Draft db...
07/22/2008 16:24:59.459 Creating DSN: name = MSP-12-WORKING-DB-DSN, server
= ORBDEVPROJECT, db = ProjectServer_Draft, trusted = 1
07/22/2008 16:24:59.474 Error = Could not load the setup or translator
library
07/22/2008 16:24:59.474 Could not create DSN MSP-12-WORKING-DB-DSN.
07/22/2008 16:24:59.474 COdbcCmd::CreateDSN failed with status 80004005
07/22/2008 16:24:59.474 ConnectToSQLServer failed for Draft db with status
80004005
07/22/2008 16:24:59.474 ERROR: Initializing Project Server 2007
Communicator object failed
07/22/2008 16:24:59.474 Initialize() failed
07/22/2008 16:24:59.474 Error = Could not load the setup or translator
library
07/22/2008 16:24:59.474 Could not remove DSN MSP-12-WORKING-DB-DSN.
07/22/2008 16:24:59.474 Error = Could not load the setup or translator
library
07/22/2008 16:24:59.474 Could not remove DSN MSP-12-PUBLISHED-DB-DSN.
I have done my best to follow the migration guide to a tee. Can anyone
provide some insight on how to fix the above?
I have double checked permissions several times and still keep getting above errors.
Thank you.
Here is a copy of my MigrationSettings:
[General]
LogFilePath=c:\ProjectServ
LogFileNamePrefix=Batch1
MigrateAll=Publish
FixUpSecurityCategories=ye
StopProjectMigrationIfStat
NeverPublishMasterProjects
ResetStatusManagerToOwnerO
[Project Names to Save]
[Project Names to Save and Publish]
[Excluded Project Names]
[Project Server 2007]
;The following setting identifies the Project Web Access URL.
Project2007PWAServer=http://ORBDEVPROJECT/pwa
;The following setting identifies the SQL Server instance that hosts the
;Project Server 2007 databases.
Project2007SQLServer=ORBDE
;The following settings specify the names of the Project Server 2007 Draft and
;Published databases.
DraftDB=ProjectServer_Draf
PublishedDB=ProjectServer_
[Project Server 2003]
Project2003ProjectTablesDB
Project2003WebTablesDB=Pro
;Project2003LinkedSQLServe
the Migration Tool i receive the folling in the log:
07/22/2008 16:24:59.162 Log file Initialized
07/22/2008 16:24:59.162 Migration tool version is 12,0,4518,1014
07/22/2008 16:24:59.162 Configuration file is c:\p12migration.ini
07/22/2008 16:24:59.459 Connecting to Project Server 2007 Draft db...
07/22/2008 16:24:59.459 Creating DSN: name = MSP-12-WORKING-DB-DSN, server
= ORBDEVPROJECT, db = ProjectServer_Draft, trusted = 1
07/22/2008 16:24:59.474 Error = Could not load the setup or translator
library
07/22/2008 16:24:59.474 Could not create DSN MSP-12-WORKING-DB-DSN.
07/22/2008 16:24:59.474 COdbcCmd::CreateDSN failed with status 80004005
07/22/2008 16:24:59.474 ConnectToSQLServer failed for Draft db with status
80004005
07/22/2008 16:24:59.474 ERROR: Initializing Project Server 2007
Communicator object failed
07/22/2008 16:24:59.474 Initialize() failed
07/22/2008 16:24:59.474 Error = Could not load the setup or translator
library
07/22/2008 16:24:59.474 Could not remove DSN MSP-12-WORKING-DB-DSN.
07/22/2008 16:24:59.474 Error = Could not load the setup or translator
library
07/22/2008 16:24:59.474 Could not remove DSN MSP-12-PUBLISHED-DB-DSN.
I have done my best to follow the migration guide to a tee. Can anyone
provide some insight on how to fix the above?
I have double checked permissions several times and still keep getting above errors.
Thank you.
Here is a copy of my MigrationSettings:
[General]
LogFilePath=c:\ProjectServ
LogFileNamePrefix=Batch1
MigrateAll=Publish
FixUpSecurityCategories=ye
StopProjectMigrationIfStat
NeverPublishMasterProjects
ResetStatusManagerToOwnerO
[Project Names to Save]
[Project Names to Save and Publish]
[Excluded Project Names]
[Project Server 2007]
;The following setting identifies the Project Web Access URL.
Project2007PWAServer=http://ORBDEVPROJECT/pwa
;The following setting identifies the SQL Server instance that hosts the
;Project Server 2007 databases.
Project2007SQLServer=ORBDE
;The following settings specify the names of the Project Server 2007 Draft and
;Published databases.
DraftDB=ProjectServer_Draf
PublishedDB=ProjectServer_
[Project Server 2003]
Project2003ProjectTablesDB
Project2003WebTablesDB=Pro
;Project2003LinkedSQLServe
Last Comment
ASKER
Yes, I am running the migration tool using my own account that i used to log into the server with. I am 1) a local admin on the server 2) dbo owner of all the sql dbs 3) a sysadmin in SQL
Thank you for your reply. Can you think of anything else to check?
Thank you for your reply. Can you think of anything else to check?
Sounds like you are on the right track. Does SQL Server restrict the types of connections? Sometimes named pipes is turned off by default.
The SQL Server is running on the same machine as Project Server, it looks like? Are you running the migration tool on the server? Default install of SQL Server? What version?
James Fraser
The SQL Server is running on the same machine as Project Server, it looks like? Are you running the migration tool on the server? Default install of SQL Server? What version?
James Fraser
ASKER
Windows 2003 SP2, SQL 2005 SP2, Project Pro Migration Tool all on the Same Server
SQL = Default Installation (version 2005 SP2)
I have changed the Surface Area Configuration Settings in SQL to use both TCP/IP and Named Pipes
Is that what you are talking about when you mentioned named pipes or should i be looking elsewhere?
SQL = Default Installation (version 2005 SP2)
I have changed the Surface Area Configuration Settings in SQL to use both TCP/IP and Named Pipes
Is that what you are talking about when you mentioned named pipes or should i be looking elsewhere?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
So i updated to MDAC 2.8, installed the "infrastructure Update" and rebooted but it get the exact same error attempting to run the Migration Tool. I'm in the process of confirming ODBC drivers like the article in the above link suggests.
If you think of anything else give me a shout. Thank you.
If you think of anything else give me a shout. Thank you.
ASKER
Hey Man,
Thanks for your suggestions. The link you sent me regarding ODBC was helpful and i finally discovered that the SQLUNIRL.DLL and SQLSRV32.DLL files were missing from c:\windows\system32. Once we copied them over from another server things worked and i was able to successfully migration my server.
Thanks for your suggestions. The link you sent me regarding ODBC was helpful and i finally discovered that the SQLUNIRL.DLL and SQLSRV32.DLL files were missing from c:\windows\system32. Once we copied them over from another server things worked and i was able to successfully migration my server.
Thanks for the update / feedback. Sounds like maybe the SQL install or an update for it went wrong somewhere.
ASKER
Yes, it was very strange. Not sure how it got into such a junked up state. I would suspect you are right, somewhere an install or update went wrong. Thanks again for taking the time to post. Cheers.
Project Management Software
Project management software has the capacity to help plan, organize, and manage resource tools and develop resource estimates. Depending on the sophistication of the software, it can manage estimation and planning, scheduling, cost control and budget management, resource allocation, collaboration software, communication, decision-making, quality management and documentation or administration systems.
3K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
James Fraser