Resource Kit: Errors with Back/Restore of Enterprise Fields

[Kurt Petteloot]

Hi,

I've been testing the backup/restore tool and it sure promises to tackle a
lot of issues we encounter each time we want to reproduce one environment
onto another. I did encounter however a number of errors while attempting a
restore of custom enterprise fields.

This is an extract of the first few lines of the log (hope it helps):

02:21:13 : Restoring Custom Fields and Lookup Tables...
02:21:14 : Updating Lookup Tables...
02:21:14 : Creating lookup table BusinessUnit...
02:21:14 : SoapException: System.Web.Services.Protocols.SoapException:
ProjectServerError(s) LastError=GeneralLCIDInvalid Instructions: Pass this
into PSClientError constructor to access all error information
at
Microsoft.Office.Project.Server.WebService.LookupTable.UpdateLookupTables(LookupTableDataSet
ltds, Boolean validateOnly, Boolean autoCheckIn, Int32 language)
02:21:15 : ERROR: Project Server Error: GeneralLCIDInvalid Context:
Creating lookup table BusinessUnit
02:21:15 : Updating lookup table ProjectReportGroups...
02:21:16 : Updating lookup table State...
02:21:17 : Creating lookup table ProjectStatus...
02:21:17 : SoapException: System.Web.Services.Protocols.SoapException:
ProjectServerError(s) LastError=GeneralLCIDInvalid Instructions: Pass this
into PSClientError constructor to access all error information
at
Microsoft.Office.Project.Server.WebService.LookupTable.UpdateLookupTables(LookupTableDataSet
ltds, Boolean validateOnly, Boolean autoCheckIn, Int32 language)
02:21:17 : ERROR: Project Server Error: GeneralLCIDInvalid Context:
Creating lookup table ProjectStatus
02:21:17 : Updating lookup table PlanningLevel...
02:21:18 : Creating lookup table Region...

..... <log goes on>....

The 'BusinessUnit' lookup table for instance returns an error and is not
created in the target environment as a result from that. The fields that
require this lookup table are also not created obviously.

I reckon that the xml file containing the description of the fields would
help a lot in resolving this issue, but it makes no sense to paste lines from
that file into this message, does it? So in case anyone feels like he/she
wants to help me out, let me know where I can drop the XML.


Any help is much appreciated. Thanks in advance.

Kind regards
Kurt

 

[Gary L. Chefetz [MVP]]

Kurt:

Have you got any non-alphanumeric characters in list values? Did you use any
of these in field names? Do you use blank spaces in custom field names?

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Kurt Petteloot]

Hi Gary,

The first item where the restore procedure runs into an error is with the
restore of a lookup table called 'BusinessUnit' which has no spaces or any
other strange characters in its name. The list 1 only one level 'deep' and
contains about 7 items, 5 of which have a space in the name. I cannot imagine
that this is causing the problem.

 

[Gary L. Chefetz [MVP]]

Did you try it without the spaces?

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com