T
Trevor Stone
Hi Everyone,
We completed a test migration from PS2003 (SP3) to PS2007 (SP1+Infra
Update) using the Migration tool to bring over the configuration and
projects. After a bit of testing, the projects, custom fields/outline
codes (and their values), and all PWA views came over pretty nicely.
A few filters were dropped, but all views were visible in Project
Center, Resource Center, etc.
The problem is that when we go to Server Settings | Mange Views |
Create New View, we get the following error:
System.Web.Services.Protocols.SoapException: ProjectServerError(s)
LastError=GeneralUnhandledException Instructions: Pass this into
PSClientError constructor to access all error information
at Microsoft.Office.Project.Server.WebService.View.ReadProjectFields
(Guid table_uid)
Trying to edit most of the views produces a similar error. This
includes both migrated views and 2007 default views. Testing on
another newly installed 2007 environment that has no migrated data
shows we can edit/create views there, so signs point to the migration
process or data as the culprit.
I thinking we'll need to do another thorough data scrub on the 2003
outline code lookup table values for dupes or illegal chars as a
starting point.
Has anyone ever received this error when taking these steps, or could
provide some suggestions for troubleshooting?
Anything is appreciated.
Thanks,
Trevor
We completed a test migration from PS2003 (SP3) to PS2007 (SP1+Infra
Update) using the Migration tool to bring over the configuration and
projects. After a bit of testing, the projects, custom fields/outline
codes (and their values), and all PWA views came over pretty nicely.
A few filters were dropped, but all views were visible in Project
Center, Resource Center, etc.
The problem is that when we go to Server Settings | Mange Views |
Create New View, we get the following error:
System.Web.Services.Protocols.SoapException: ProjectServerError(s)
LastError=GeneralUnhandledException Instructions: Pass this into
PSClientError constructor to access all error information
at Microsoft.Office.Project.Server.WebService.View.ReadProjectFields
(Guid table_uid)
Trying to edit most of the views produces a similar error. This
includes both migrated views and 2007 default views. Testing on
another newly installed 2007 environment that has no migrated data
shows we can edit/create views there, so signs point to the migration
process or data as the culprit.
I thinking we'll need to do another thorough data scrub on the 2003
outline code lookup table values for dupes or illegal chars as a
starting point.
Has anyone ever received this error when taking these steps, or could
provide some suggestions for troubleshooting?
Anything is appreciated.
Thanks,
Trevor