PS2003 - PS2007 migration. One project will not migrate, all others fine.

[RichardG]

Hi,

I am in the process of performing a PS2003 to PS2007 migration. We have about 17,000 resources and 1,200 projects. All projects migrate across OK except one.

I've tried to migrate this project several times, but still get the same error in the migration log:

10/07/2009 18:53:43.303 Connecting to Project Server 2007 ...
10/07/2009 18:54:13.521 Login failed because of invalid username or password
10/07/2009 18:54:13.521 psiComm->Login() failed with status 8c040005

I can't figure out why the account I'm using to perform the migration can't log in to Project Server 2007 for this project, but is fine for all the other projects. The account is a member of the PS2007 administrators group. I'm guessing that the message in the log is a red herring, but have no idea at all what else it might be.

Any ideas?

Thanks,
Richard


The full log entry for this project is below


**********Phase:Migration of Project <Troublesome_Project>.Published start**********
10/07/2009 18:51:06.865 Getting Project info from Project Server 2007
10/07/2009 18:51:06.865 preparing Query select PROJ_UID, PROJ_NAME, PROJ_TYPE from dbo.MSP_PROJECTS where PROJ_NAME = ?
10/07/2009 18:51:06.865 Could not get info for <Troublesome_Project>_Published in Project Server 2007
10/07/2009 18:51:06.865 preparing Query select PROJ_CHECKEDOUT from dbo.MSP_PROJECTS where PROJ_ID = ?
10/07/2009 18:51:06.865 preparing Query select cast(isnull(PROJ_LOCKED, '0') as int) from dbo.MSP_PROJECTS where PROJ_ID = ?
10/07/2009 18:51:06.865 preparing Query select case when PROJ_EXT_EDITED = 1 or RESERVED_BINARY_DATA is null then 1 else 0 end from dbo.MSP_PROJECTS where PROJ_ID = ?
10/07/2009 18:51:06.865 Starting migration of project 1 of 1: <Troublesome_Project>.Published
10/07/2009 18:51:06.865
10/07/2009 18:51:06.865 Opening project from Project Server 2003...
10/07/2009 18:51:06.881 Executing Query insert into dbo.MSP_P12UPGRADE_PROJECT_UPGRADES (UPG_RUN_UID, UPG_PROJ_P11_ID, UPG_PROJ_UID, UPG_PROJ_P11_NAME, UPG_PROJ_STATUS, UPG_PROJ_TYPE, UPG_PROJ_START_DATE) values (?, 4655, ?, ?, 3, ?, GETDATE())
10/07/2009 18:51:06.881 preparing Query insert into dbo.MSP_P12UPGRADE_PROJECT_UPGRADES (UPG_RUN_UID, UPG_PROJ_P11_ID, UPG_PROJ_UID, UPG_PROJ_P11_NAME, UPG_PROJ_STATUS, UPG_PROJ_TYPE, UPG_PROJ_START_DATE) values (?, 4655, ?, ?, 3, ?, GETDATE())
10/07/2009 18:51:06.881 preparing Query exec dbo.MSP_P12UPG_DELETE_PROJECT_MAPPINGS ?
10/07/2009 18:51:34.865 Found calendar in both global and local named Standard
10/07/2009 18:51:34.881 Time to execute P12UpgradeDoc::FixupCalendars(): 47 ms
10/07/2009 18:51:52.740 Time to execute P12UpgradeDoc::OpenP11Project(): 45704 ms
10/07/2009 18:51:52.740 Executing Query update dbo.MSP_P12UPGRADE_PROJECT_UPGRADES set UPG_PROJ_STATUS = 4, UPG_PROJ_FINISH_DATE = GETDATE() where UPG_PROJ_P11_ID = 4655
10/07/2009 18:51:52.740 Successfully Opened from Project Server 2003
10/07/2009 18:51:52.756 Time to execute P12UpgradeDoc::FixUpLookupTableValueRowNumber(): 15 ms
10/07/2009 18:51:52.881 Time to execute P12UpgradeDoc::Upgrade() - ENT_ForceCalsToCorpStandards: 125 ms
10/07/2009 18:51:52.881 Loading ent resource data
10/07/2009 18:53:43.303 Connecting to Project Server 2007 ...
10/07/2009 18:54:13.521 Login failed because of invalid username or password
10/07/2009 18:54:13.521 psiComm->Login() failed with status 8c040005
10/07/2009 18:54:13.521 ResourcesStatus call failed with error 8C040005
10/07/2009 18:54:13.537 Time to execute P12UpgradeDoc::LoadP12Doc(): 140656 ms
10/07/2009 18:54:13.537 Time to execute P12UpgradeDoc::Upgrade(): 186671 ms
10/07/2009 18:54:13.537 Migration failed for project <Troublesome_Project>.Published
10/07/2009 18:54:14.568 Time to execute P12ProjectUpgrader::Upgrade(): 187703 ms
10/07/2009 18:54:14.568 migration of project <Troublesome_Project>.Published failed
10/07/2009 18:54:14.568 migration of project <Troublesome_Project>.Published failed with error 8C040005
**********Phase:Migration of Project <Troublesome_Project>.Published end**********

 

[Ben Howard]

Hi Richard,
This is likely going to be very difficult to troubleshoot, so pragmatically
I would open the project in project pro 2003, save it out to an MPP, and then
open it in Project pro 2007, and save as... to the server.

HTH
--
Thanks, Ben.

Please rate this post if it helped.
http://appleparkltd.spaces.live.com/

 

[RichardG]

Hi Ben,

Thanks for the advice. So will doing that match up the Enterprise Resources
between PS2003 and PS2007?

I'll give it a go!

Cheers,
Richard

 

[Ben Howard]

Hi Richard,
If you do an import (tools | enterprise options) it will try and and match
up the resources, if you do a Save As it will match up those with exactly the
same name, and save the others as local resources...
--
Thanks, Ben.

Please rate this post if it helped.
http://appleparkltd.spaces.live.com/

 

[RichardG]

Thanks Ben.

I tried this but got timeout problems when trying to save the plan to
Project Server - it is a very large one (7,000+ resources). The PM is only
using it to control access to the PWS site - i.e., adding a resource to the
plan purely to grant them access to the PWS site. Since the content of the
plan isn't important (as far as scheduling or work is concerned), I think I
might do this in parts - i.e., create a new project in Project Server, copy
a portion of the tasks/assignments from the mpp file to the Project Server
version, save and publish, repeat until all tasks/assignments done...

The best option would be to have the PM manage the site access outside of
Project Server. I'll see what I can do about this, too.

Thanks again,
Richard

 

[Jonathan Sofer [MVP]]

In project 2007 there is the option to allow access to project workspaces by
simply adding resources to the project team. You no longer necessarily have
to have resource assignments to give resources access to the workspace.
This gives the resources "Read" access but not "Team Member" access. For
"Team Member" access, they still need to have an assignment. But you should
investigate if this new feature might work for you and so might eliminate
the need for creating all these bogus resource assignments.

Jonathan

 

[RichardG]

Thanks Jonathan - that is useful to know. I'm not sure whether it will help
in this particular case (I think he needs his resources to be able to log
risks and issues, and therefore they will need read/write access), but I'll
certainly check it out!

Regards,
Richard