J
Jeremy
Hi, I have Project Server installed in my test environment in the following
manner: 2 load-balanced Project Server (IIS front-end), 2 DB servers
(clustered for fail-over), and View Processing/Session Manager server. I
have 2 DBs installed on the DB cluster. The second DB was created in the
following manner: DB1 was backed up and restored as DB2. Edit Site was used
to configure DB2. All plans were deleted using the PSCleaner Tool.
Everything works fine except the following.
On DB1 in table MSP_VIEW_SERVICE_PUBLISH_STATUS we have one entry at
2005-07-13 19:31:37.000 for ProjectServer ProjectID=-1, but in DB2 we have
many entries from 2005-07-14 16:05:57.000 to 2005-07-29 00:36:21.000 for both
DB1 and DB2.
The problem we are noticing is that a publish for Site1 has written data to
the Site2 (DB2) database. We end up with 2 rows with the same
ProjectUniqueID (but different WPROJ_ID) in MSP_VIEW_PROJ_PROJECTS_STD.
Any ideas?
manner: 2 load-balanced Project Server (IIS front-end), 2 DB servers
(clustered for fail-over), and View Processing/Session Manager server. I
have 2 DBs installed on the DB cluster. The second DB was created in the
following manner: DB1 was backed up and restored as DB2. Edit Site was used
to configure DB2. All plans were deleted using the PSCleaner Tool.
Everything works fine except the following.
On DB1 in table MSP_VIEW_SERVICE_PUBLISH_STATUS we have one entry at
2005-07-13 19:31:37.000 for ProjectServer ProjectID=-1, but in DB2 we have
many entries from 2005-07-14 16:05:57.000 to 2005-07-29 00:36:21.000 for both
DB1 and DB2.
The problem we are noticing is that a publish for Site1 has written data to
the Site2 (DB2) database. We end up with 2 rows with the same
ProjectUniqueID (but different WPROJ_ID) in MSP_VIEW_PROJ_PROJECTS_STD.
Any ideas?