You can go to the Manage Queue and find the error and click on the
description of the error to get a better idea.
Two things it might be:
1) Are you trying to enter invalid data into a cost, date or number field?
2) See below about an issue with graphical indicators.
BEHAVIOR/SYMPTOMS:
====================
When trying to add or update a project level custom field that has a
graphical
indicator associated with it but no formulae you cannot save the change.
This applies only if the project has been created or edited through the PSI
or (in
some cases) is an Activity Plan or Proposal. It applies to changes through
the
Activity Plan/Proposal UI or via Edit Project Properties in the Project
Center.
It is only an issue with Activity Plans and Proposals if other custom fields
are
set during a save - or a field has a default value.
There may be other root causes that will give the same generic error.
ERROR MESSAGE OR RESULT:
===========================
When updating a custom field for an Activity Plan or Proposal you will get
an error
dialog box:-
Windows Internet Explorer
An error has occurred when saving your project to the server. Please contact
your
system administrator for assistance.
[GeneralUnhandledException]
When updating a custom field through Project Center's Edit Project
Properties
option the error will display at the top of the page in red:-
The project could not be saved due to the following reason(s):
“An unknown error has occurredâ€
CAUSE:
====================
Projects created through the PSI, or ones which have any of their custom
fields
updated through the PSI or PWA have duplicate custom fields created for any
project
level fields with graphical indicators but no formulae. The rows created are
identical apart from a different the CUSTOM_FIELD_UID which will be unique
and the
INDICATOR_VALUE which may contain a value for one of the rows but not the
other.
RESOLUTION/WORKAROUND:
===========================
Setting custom fields before the first save avoids this problem.
Any custom fields affected by this bug can still be edited through Project
Professional if they are "full" projects (except multi value fields in some
circumstances).
The graphical indicator can be removed and just the data used which resolves
the
issue for new projects.
The following query will identify any projects and the custom fields that
are
duplicated within the project. In most cases there will be 2 - but there can
be
more. WARNING - There can be false positive results from this query if
MultiValue
project level fields are set - although if these fields also use graphical
indicators they will generate the error for PSI created projects and these
fields
cannot then be set through Project Professional.
SELECT MSP_PROJECTS.PROJ_NAME,
MSP_CUSTOM_FIELDS_PUBLISHED_VIEW.MD_PROP_NAME,
COUNT(MSP_PROJ_CUSTOM_FIELD_VALUES.MD_PROP_UID) AS
NumOccurrences, MSP_PROJ_CUSTOM_FIELD_VALUES.MD_PROP_UID,
MSP_PROJECTS.PROJ_UID
FROM MSP_PROJ_CUSTOM_FIELD_VALUES INNER JOIN
MSP_PROJECTS ON MSP_PROJ_CUSTOM_FIELD_VALUES.PROJ_UID =
MSP_PROJECTS.PROJ_UID INNER JOIN
MSP_CUSTOM_FIELDS_PUBLISHED_VIEW ON
MSP_PROJ_CUSTOM_FIELD_VALUES.MD_PROP_UID =
MSP_CUSTOM_FIELDS_PUBLISHED_VIEW.MD_PROP_UID
GROUP BY MSP_PROJ_CUSTOM_FIELD_VALUES.MD_PROP_UID, MSP_PROJECTS.PROJ_NAME,
MSP_CUSTOM_FIELDS_PUBLISHED_VIEW.MD_PROP_NAME,
MSP_PROJECTS.PROJ_UID
HAVING (COUNT(MSP_PROJ_CUSTOM_FIELD_VALUES.MD_PROP_UID) > 1)
ORDER BY MSP_PROJECTS.PROJ_NAME
It is also possible to resolve the issue by removing all but one of any
duplicate
rows from the MSP_PROJ_CUSTOM_FIELD_VALUES table.
