S
Sam
I make a virtual machine of epm 2003 in which sqlserver 2000 installed with
sp4 then install sqlserver 2005 .
Run sharepoint services 3.0 with the In-place upgrade option.run pcscan tool
.. and then run configuration wizard.
Then install project server 2007 and run make make web applications for SSP
and project server 2007 (pwa).
Then install project professional 2007.
After all these working fine.
then i make a folder with name migration at C:\migration\p12migration.ini
and copy this ini file to here.
and set configuration file with their parameters.
virtual machine name : VM
this is text of p12migration.ini text as follows:
------------------------------------------------------------------------------------------------
[General]
;The Project Server 2007 Migration Tool writes verbose information to the log
;file. If the migration tool cannot write to the log file, it stops running,
;so you can be sure that you can always refer to the log file for more
;information about the migration run. The log file is your main source of
;troubleshooting information for the migration tool.
;The following setting identifies the path to the log file.
LogFilePath=c:\ProjectServer2007Migration
;The following setting identifies the prefix of the migration log file. The
log
;file name is a combination of LogFileNamePrefix and the timestamp of when
the
;migration started. For example: batch1-20060314-1542.log. This log was
;generated from a migration run that started on 3/14/2006 at 3:42 pm.
;You can run the migration tool multiple times. Some reasons for doing this
;could be, for example, to upgrade projects in batches, or if the tool
;crashes. You can use a different Log file name prefix to identify each
;migration run.
LogFileNamePrefix=Batch1
;MigrateAll is a shortcut configuration setting for migrating all projects at
;once. If you specify MigrateAll=Save, all projects in Project Server 2003
;will be migrated to Project Server 2007 and none of them will be published.
;If you specify MigrateAll=Publish, all projects will be migrated, and the
;published projects in Project Server 2003 will be published automatically in
;Project Server 2007.
;NOTE: The MigrateAll setting is ignored if you have specified any project
;names in the [Project Names to Save and Publish] or
;[Project Names to Publish] sections.
MigrateAll=Publish
;If 'FixUpSecurityCategories' property is set to 'yes', projects are
automatically
;added to security categories after they are migrated. If it is set to 'no'
;projects will not be added to any security category after migration.
;Typically, you would set this policy to 'no' if the categories in Project
;Server 2007 will be significantly different from the categories you used in
;Project Server 2003, and you want to add your projects to security categories
;manually.
FixUpSecurityCategories=yes
;By default, the value of 'StopProjectMigrationIfStatusUpdatesPending'
property
;is 'yes'. So, if any project has pending updates, it will not be migrated
;over. But in some cases, customers may want to migrate projects even though
;they have pending updates. Eg. If there are lots of old projects, which
need to
;be migrated, but there are no active project managers for these projects to
;process pending updates. In those cases set the value of this property to
'no'
StopProjectMigrationIfStatusUpdatesPending=yes
;By default, the value of 'NeverPublishMasterProjects' property is set to
'yes'.
;So, master projects are never published, even if they are included in the
;[Project names to Save and Publish] section. This is useful for customers
who
;have set the 'never publish master projects' option in their Project Server
2003
;installation and don't want master projects to be published even by
mistake. But
;if customers want to publish master projects, set the
'NeverPublishMasterProjects'
;option to 'no'. Note that, even if you specify this setting, you need to
;manually include the master projects in the [Project names to Save and
Publish]
;section.
;Note: Publshing a master project in Project Server 2007 will not
;double-count availability (see master project documentation for more details)
NeverPublishMasterProjects=yes
;The policy 'ResetStatusManagerToOwnerOnConflict' controls the migration
tool behaviour
;when a project has a task which has
;different status managers for its assignments. In Project Server 2007, this
situation is
;not supported ie) all assignments in a task can have only one status
manager. By
;default, the value of 'ResetStatusManagerToOwnerOnConflict' property is set
to 'Yes',
;which means that after migration, the status manager for the conflicting
assignments
;would be the project manager. If the value is set to 'No', the project will
not be migrated.
;The customers can fix up the conflict themselves and resubmit the project
for migration.
ResetStatusManagerToOwnerOnConflict=yes
[Project Names to Save]
;The projects you specify in this section will be saved as part of migration,
;but they will not be published.
;Use the full name of the project, which is stored in the PROJ_NAME column in
;the MSP_PROJECTS table.
Project1.published
Project2.Target
[Project Names to Save and Publish]
;To save and publish migrated projects, specify them in this section. Note
that
;only projects that were published in Project Server 2003 can be published
to the
;Project Server 2007 database. If you specify a project that is not a
..published
;version in this section (for example, .target version), it will simply be
saved.
Project3.Published
Project4.Published
[Excluded Project Names]
;Specify any project that you do not want to include during migration. This
;option is typically used with the MigrateAll setting when you want to migrate
;most, but not all, of your projects.
Project5.published
Project6.Target
[Project Server 2007]
;The following setting identifies the Project Web Access URL.
Project2007PWAServer=http://vm/pwa
;The following setting identifies the SQL Server instance that hosts the
;Project Server 2007 databases.
;######## IMPORTANT ############
;By default, the Project Server 2003 databases also should be part of the
;same SQL Server instance as Project Server 2007.
;To do this, back up and restore the Project Server 2003 databases into the
;Project Server 2007 SQL Server instance. If this is a major restriction for
;you, refer to the Project2003SQLServer property in the [Project Server 2003]
;section.
Project2007SQLServer=vm
;The following settings specify the names of the Project Server 2007 Draft and
;Published databases.
DraftDB=ProjectServer_Draft
PublishedDB=ProjectServer_Published
[Project Server 2003]
;If your Project Server 2003 database is in single database configuration
;(as opposed to split database configuration), you need to specify the same
;database name for both Project2003ProjectTablesDB and Project2003WebTablesDB.
;Note that the migration tool does not migrate cube tables. You will need to
;rebuild cubes after migration.
Project2003ProjectTablesDB=ProjectServer
Project2003WebTablesDB=ProjectServer
;You can specify the Linked SQL Server name that points to the SQL Server
;instance where the Project Server 2003 databases reside. By default, this
;configuration is not enabled (the Project2003LinkedSQLServer property in the
;configuration file is commented out) and the migration tool assumes that the
;Project Server 2003 and 2007 databases reside on the same SQL Server
;instance. This is because specifying this property involves some manual
;steps to create the correct Linked SQL Server.
;To create a linked server, do the following:
;1. Connect to the server running Project Server 2007 by using SQL
; enterprise manager.
;2. In SQL Server 2000 Enterprise Manager: In the tree structure, click to
expand the Security folder.
; In SQL Server 2005 Management Studio: In the tree structure, click to
expand Server Objects folder.
;3. Right-click Linked Servers, and then click New Linked Server.
; Refer to the SQL Server documentation for more information on how to
; create a linked server (search for "linked servers" in the
documentation).
; Make sure you click on the 'Security' tab and select the right security
; option (Eg. select 'be made using the login's current security context'
; radio button OR the 'be made using this security context' option and
; give a valid user name/password that works on the Project 2003 SQL
Server).
; The option you choose will depend on how you are running migration.
Choose
; the one that works for you and refer to SQL Linked Server documentation
for
; more details.
;4. Verify that the linked server you created works. ie) You should see the
; linked server you just created under the "Linked Servers" node. Once you
; expand the linked server, you should see the nodes 'Tables' and 'Views'.
; If you click on 'Tables' or 'Views', you should see some entries.
; NOTE: In some IT environments, specific ports related to Microsoft
; Distributed Transaction Coordinator (MSDTC) might need to be opened
; for the linked server configuration to work. For more information,
; see the SQL Server documentation about linked servers or contact
; your system administrator.
;5. Give the name of the SQL Linked Server as the value for the
; Project2003LinkedSQLServer property.
;Project2003LinkedSQLServer=vm
------------------------------------------------------------------------------------------------
running p12migration tool normally. but after few seconds its giving an error.
as follows in log file :
------------------------------------------------------------------------------------------------
**********Phase:Migration initialization start**********
11/26/2008 15:19:58.940 Policy to fix up project server security
categories = true.
11/26/2008 15:19:58.940 Policy to never publish master projects = true.
11/26/2008 15:19:58.940 WARNING: Projects will be migrated even if they
have multiple status managers for the same task.
11/26/2008 15:19:59.211 Adding to run table
11/26/2008 15:19:59.211 preparing Query insert into
dbo.MSP_P12UPGRADE_UPGRADE_RUNS (UPG_RUN_UID, UPG_RUN_MACHINE_NAME,
UPG_RUN_STATUS, UPG_RUN_START_DATE) values (?, ?, 0, GETDATE())
11/26/2008 15:19:59.231 Executing Query insert into
dbo.MSP_P12UPGRADE_UPGRADE_RUNS (UPG_RUN_UID, UPG_RUN_MACHINE_NAME,
UPG_RUN_STATUS, UPG_RUN_START_DATE) values (?, ?, 0, GETDATE())
11/26/2008 15:19:59.261 Connecting to Project Server 2003 sql server
project database
11/26/2008 15:19:59.261 Creating DSN: name = P11-PROJECT-SERVER-DSN,
server = vm, db = ProjectServer, trusted = 1
11/26/2008 15:19:59.261 Created DSN P11-PROJECT-SERVER-DSN
11/26/2008 15:19:59.261 Connection string
DSN=P11-PROJECT-SERVER-DSN;UID=;APP=2007 Microsoft Office
system;WSID=VM;DATABASE=ProjectServer;Trusted_Connection=Yes
11/26/2008 15:19:59.261 Connecting to the Project Server 2003 sql server
web database
11/26/2008 15:19:59.261 Creating DSN: name = P11-PROJECT-SERVER-WEB-DSN,
server = vm, db = ProjectServer, trusted = 1
11/26/2008 15:19:59.271 Created DSN P11-PROJECT-SERVER-WEB-DSN
11/26/2008 15:19:59.271 Connection string
DSN=P11-PROJECT-SERVER-WEB-DSN;UID=;APP=2007 Microsoft Office
system;WSID=VM;DATABASE=ProjectServer;Trusted_Connection=Yes
11/26/2008 15:19:59.271 preparing Query select WADMIN_VERSION_MAJOR,
WADMIN_VERSION_MINOR, WADMIN_VERSION_REVISION, WADMIN_VERSION_BUILD from
dbo.MSP_WEB_ADMIN
11/26/2008 15:19:59.301 Project Server 2003 version is 11,0,15,20030816
11/26/2008 15:19:59.301 ERROR: The Project Server 2003 version (major =
11, minor = 0) is not supported for migration. Please upgrade to the latest
service pack and try again.11/26/2008 15:19:59.301 Time to execute
CUpgrader::CheckP11Version(): 30 ms
11/26/2008 15:19:59.301 Updating run table
11/26/2008 15:19:59.301 preparing Query update
dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE =
GETDATE() where UPG_RUN_UID = ?
11/26/2008 15:19:59.301 Executing Query update
dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE =
GETDATE() where UPG_RUN_UID = ?
11/26/2008 15:19:59.331 Migration finished with return code 80004005
11/26/2008 15:19:59.331 Project migration failed.
------------------------------------------------------------------------------------------------
Question :
-----------
When the single server which i am doing we need to install sqlserver 2005
because in the existence of sqlserver 2000 and sqlserver 2005 .all database
of projectserver 2003 and projectserver 2007 are made in sqlserver 2000
becuase this is the default instance ?
tell me the solution soon . why this problem is happening . why the
migration is not going on.
Please answer me in detail .
sp4 then install sqlserver 2005 .
Run sharepoint services 3.0 with the In-place upgrade option.run pcscan tool
.. and then run configuration wizard.
Then install project server 2007 and run make make web applications for SSP
and project server 2007 (pwa).
Then install project professional 2007.
After all these working fine.
then i make a folder with name migration at C:\migration\p12migration.ini
and copy this ini file to here.
and set configuration file with their parameters.
virtual machine name : VM
this is text of p12migration.ini text as follows:
------------------------------------------------------------------------------------------------
[General]
;The Project Server 2007 Migration Tool writes verbose information to the log
;file. If the migration tool cannot write to the log file, it stops running,
;so you can be sure that you can always refer to the log file for more
;information about the migration run. The log file is your main source of
;troubleshooting information for the migration tool.
;The following setting identifies the path to the log file.
LogFilePath=c:\ProjectServer2007Migration
;The following setting identifies the prefix of the migration log file. The
log
;file name is a combination of LogFileNamePrefix and the timestamp of when
the
;migration started. For example: batch1-20060314-1542.log. This log was
;generated from a migration run that started on 3/14/2006 at 3:42 pm.
;You can run the migration tool multiple times. Some reasons for doing this
;could be, for example, to upgrade projects in batches, or if the tool
;crashes. You can use a different Log file name prefix to identify each
;migration run.
LogFileNamePrefix=Batch1
;MigrateAll is a shortcut configuration setting for migrating all projects at
;once. If you specify MigrateAll=Save, all projects in Project Server 2003
;will be migrated to Project Server 2007 and none of them will be published.
;If you specify MigrateAll=Publish, all projects will be migrated, and the
;published projects in Project Server 2003 will be published automatically in
;Project Server 2007.
;NOTE: The MigrateAll setting is ignored if you have specified any project
;names in the [Project Names to Save and Publish] or
;[Project Names to Publish] sections.
MigrateAll=Publish
;If 'FixUpSecurityCategories' property is set to 'yes', projects are
automatically
;added to security categories after they are migrated. If it is set to 'no'
;projects will not be added to any security category after migration.
;Typically, you would set this policy to 'no' if the categories in Project
;Server 2007 will be significantly different from the categories you used in
;Project Server 2003, and you want to add your projects to security categories
;manually.
FixUpSecurityCategories=yes
;By default, the value of 'StopProjectMigrationIfStatusUpdatesPending'
property
;is 'yes'. So, if any project has pending updates, it will not be migrated
;over. But in some cases, customers may want to migrate projects even though
;they have pending updates. Eg. If there are lots of old projects, which
need to
;be migrated, but there are no active project managers for these projects to
;process pending updates. In those cases set the value of this property to
'no'
StopProjectMigrationIfStatusUpdatesPending=yes
;By default, the value of 'NeverPublishMasterProjects' property is set to
'yes'.
;So, master projects are never published, even if they are included in the
;[Project names to Save and Publish] section. This is useful for customers
who
;have set the 'never publish master projects' option in their Project Server
2003
;installation and don't want master projects to be published even by
mistake. But
;if customers want to publish master projects, set the
'NeverPublishMasterProjects'
;option to 'no'. Note that, even if you specify this setting, you need to
;manually include the master projects in the [Project names to Save and
Publish]
;section.
;Note: Publshing a master project in Project Server 2007 will not
;double-count availability (see master project documentation for more details)
NeverPublishMasterProjects=yes
;The policy 'ResetStatusManagerToOwnerOnConflict' controls the migration
tool behaviour
;when a project has a task which has
;different status managers for its assignments. In Project Server 2007, this
situation is
;not supported ie) all assignments in a task can have only one status
manager. By
;default, the value of 'ResetStatusManagerToOwnerOnConflict' property is set
to 'Yes',
;which means that after migration, the status manager for the conflicting
assignments
;would be the project manager. If the value is set to 'No', the project will
not be migrated.
;The customers can fix up the conflict themselves and resubmit the project
for migration.
ResetStatusManagerToOwnerOnConflict=yes
[Project Names to Save]
;The projects you specify in this section will be saved as part of migration,
;but they will not be published.
;Use the full name of the project, which is stored in the PROJ_NAME column in
;the MSP_PROJECTS table.
Project1.published
Project2.Target
[Project Names to Save and Publish]
;To save and publish migrated projects, specify them in this section. Note
that
;only projects that were published in Project Server 2003 can be published
to the
;Project Server 2007 database. If you specify a project that is not a
..published
;version in this section (for example, .target version), it will simply be
saved.
Project3.Published
Project4.Published
[Excluded Project Names]
;Specify any project that you do not want to include during migration. This
;option is typically used with the MigrateAll setting when you want to migrate
;most, but not all, of your projects.
Project5.published
Project6.Target
[Project Server 2007]
;The following setting identifies the Project Web Access URL.
Project2007PWAServer=http://vm/pwa
;The following setting identifies the SQL Server instance that hosts the
;Project Server 2007 databases.
;######## IMPORTANT ############
;By default, the Project Server 2003 databases also should be part of the
;same SQL Server instance as Project Server 2007.
;To do this, back up and restore the Project Server 2003 databases into the
;Project Server 2007 SQL Server instance. If this is a major restriction for
;you, refer to the Project2003SQLServer property in the [Project Server 2003]
;section.
Project2007SQLServer=vm
;The following settings specify the names of the Project Server 2007 Draft and
;Published databases.
DraftDB=ProjectServer_Draft
PublishedDB=ProjectServer_Published
[Project Server 2003]
;If your Project Server 2003 database is in single database configuration
;(as opposed to split database configuration), you need to specify the same
;database name for both Project2003ProjectTablesDB and Project2003WebTablesDB.
;Note that the migration tool does not migrate cube tables. You will need to
;rebuild cubes after migration.
Project2003ProjectTablesDB=ProjectServer
Project2003WebTablesDB=ProjectServer
;You can specify the Linked SQL Server name that points to the SQL Server
;instance where the Project Server 2003 databases reside. By default, this
;configuration is not enabled (the Project2003LinkedSQLServer property in the
;configuration file is commented out) and the migration tool assumes that the
;Project Server 2003 and 2007 databases reside on the same SQL Server
;instance. This is because specifying this property involves some manual
;steps to create the correct Linked SQL Server.
;To create a linked server, do the following:
;1. Connect to the server running Project Server 2007 by using SQL
; enterprise manager.
;2. In SQL Server 2000 Enterprise Manager: In the tree structure, click to
expand the Security folder.
; In SQL Server 2005 Management Studio: In the tree structure, click to
expand Server Objects folder.
;3. Right-click Linked Servers, and then click New Linked Server.
; Refer to the SQL Server documentation for more information on how to
; create a linked server (search for "linked servers" in the
documentation).
; Make sure you click on the 'Security' tab and select the right security
; option (Eg. select 'be made using the login's current security context'
; radio button OR the 'be made using this security context' option and
; give a valid user name/password that works on the Project 2003 SQL
Server).
; The option you choose will depend on how you are running migration.
Choose
; the one that works for you and refer to SQL Linked Server documentation
for
; more details.
;4. Verify that the linked server you created works. ie) You should see the
; linked server you just created under the "Linked Servers" node. Once you
; expand the linked server, you should see the nodes 'Tables' and 'Views'.
; If you click on 'Tables' or 'Views', you should see some entries.
; NOTE: In some IT environments, specific ports related to Microsoft
; Distributed Transaction Coordinator (MSDTC) might need to be opened
; for the linked server configuration to work. For more information,
; see the SQL Server documentation about linked servers or contact
; your system administrator.
;5. Give the name of the SQL Linked Server as the value for the
; Project2003LinkedSQLServer property.
;Project2003LinkedSQLServer=vm
------------------------------------------------------------------------------------------------
running p12migration tool normally. but after few seconds its giving an error.
as follows in log file :
------------------------------------------------------------------------------------------------
**********Phase:Migration initialization start**********
11/26/2008 15:19:58.940 Policy to fix up project server security
categories = true.
11/26/2008 15:19:58.940 Policy to never publish master projects = true.
11/26/2008 15:19:58.940 WARNING: Projects will be migrated even if they
have multiple status managers for the same task.
11/26/2008 15:19:59.211 Adding to run table
11/26/2008 15:19:59.211 preparing Query insert into
dbo.MSP_P12UPGRADE_UPGRADE_RUNS (UPG_RUN_UID, UPG_RUN_MACHINE_NAME,
UPG_RUN_STATUS, UPG_RUN_START_DATE) values (?, ?, 0, GETDATE())
11/26/2008 15:19:59.231 Executing Query insert into
dbo.MSP_P12UPGRADE_UPGRADE_RUNS (UPG_RUN_UID, UPG_RUN_MACHINE_NAME,
UPG_RUN_STATUS, UPG_RUN_START_DATE) values (?, ?, 0, GETDATE())
11/26/2008 15:19:59.261 Connecting to Project Server 2003 sql server
project database
11/26/2008 15:19:59.261 Creating DSN: name = P11-PROJECT-SERVER-DSN,
server = vm, db = ProjectServer, trusted = 1
11/26/2008 15:19:59.261 Created DSN P11-PROJECT-SERVER-DSN
11/26/2008 15:19:59.261 Connection string
DSN=P11-PROJECT-SERVER-DSN;UID=;APP=2007 Microsoft Office
system;WSID=VM;DATABASE=ProjectServer;Trusted_Connection=Yes
11/26/2008 15:19:59.261 Connecting to the Project Server 2003 sql server
web database
11/26/2008 15:19:59.261 Creating DSN: name = P11-PROJECT-SERVER-WEB-DSN,
server = vm, db = ProjectServer, trusted = 1
11/26/2008 15:19:59.271 Created DSN P11-PROJECT-SERVER-WEB-DSN
11/26/2008 15:19:59.271 Connection string
DSN=P11-PROJECT-SERVER-WEB-DSN;UID=;APP=2007 Microsoft Office
system;WSID=VM;DATABASE=ProjectServer;Trusted_Connection=Yes
11/26/2008 15:19:59.271 preparing Query select WADMIN_VERSION_MAJOR,
WADMIN_VERSION_MINOR, WADMIN_VERSION_REVISION, WADMIN_VERSION_BUILD from
dbo.MSP_WEB_ADMIN
11/26/2008 15:19:59.301 Project Server 2003 version is 11,0,15,20030816
11/26/2008 15:19:59.301 ERROR: The Project Server 2003 version (major =
11, minor = 0) is not supported for migration. Please upgrade to the latest
service pack and try again.11/26/2008 15:19:59.301 Time to execute
CUpgrader::CheckP11Version(): 30 ms
11/26/2008 15:19:59.301 Updating run table
11/26/2008 15:19:59.301 preparing Query update
dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE =
GETDATE() where UPG_RUN_UID = ?
11/26/2008 15:19:59.301 Executing Query update
dbo.MSP_P12UPGRADE_UPGRADE_RUNS SET UPG_RUN_STATUS = ?, UPG_RUN_FINISH_DATE =
GETDATE() where UPG_RUN_UID = ?
11/26/2008 15:19:59.331 Migration finished with return code 80004005
11/26/2008 15:19:59.331 Project migration failed.
------------------------------------------------------------------------------------------------
Question :
-----------
When the single server which i am doing we need to install sqlserver 2005
because in the existence of sqlserver 2000 and sqlserver 2005 .all database
of projectserver 2003 and projectserver 2007 are made in sqlserver 2000
becuase this is the default instance ?
tell me the solution soon . why this problem is happening . why the
migration is not going on.
Please answer me in detail .