Database error (0x8004E14)

[SBelling]

Greetings:

We are experiencing a spooler error when attempting to
publish an update to a project within our system. I have
been unable to find any detailed information related to
the error message (Database error (0x8004E14)) and I am
hoping some of you may know what this is and/or where to
find additional information.

Is there a "master reference" anywhere to the Project
Server spooler errors?

Thanks,
SBelling

 

[SBelling]

Chris:

Thanks for this info. Do you know of a workaround that one
can do within the project assignments to get past this,
such as removing resources from tasks or the project?

Is this most likely to occur when the project manager is
also a resource on this project?

Thanks,
SBelling

 

[Gary L. Chefetz \(MVP\)]

The quickest, easiest way to work around this is to save the project as an
mpp file, delete it from Project Server, import the mpp file and republish
the assignments. The steps necessary to do this depend on your configuration
and use of the system.

Considerations:

All pending and saved timesheet data against the project must be updated by
the resources and accepted by the PM
SharePoint subweb, do you need to save it or not?
Task-level Enterprise attributes need to be copied to local fields for
preservation
Managed time periods must be disabled in order to republish actual work
Actual work restored through this process may not exactly match its original
state (save backups for auditability if required)

Your other option is to hunt these down using SQL.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-

 

[SBelling]

Understood. Many thanks for the advice.

SBelling

-----Original Message-----
The quickest, easiest way to work around this is to save the project as an
mpp file, delete it from Project Server, import the mpp file and republish
the assignments. The steps necessary to do this depend on your configuration
and use of the system.

Considerations:

All pending and saved timesheet data against the project must be updated by
the resources and accepted by the PM
SharePoint subweb, do you need to save it or not?
Task-level Enterprise attributes need to be copied to local fields for
preservation
Managed time periods must be disabled in order to republish actual work
Actual work restored through this process may not exactly match its original
state (save backups for auditability if required)

Your other option is to hunt these down using SQL.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-



.

 

[TomL]

Which tables and fields should the query check? I have read the schemas, but
I still cannot find the offending record/field.

Thanks.

 

[Gary L. Chefetz \(MVP\)]

Tom:

Sounds like the first option is the best for you.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-

 

[TomL]

Will this process lose all timesheet data and/or actual work protected?

Thanks for your help.

 

[Gary L. Chefetz \(MVP\)]

Tom:

If you're using managed time periods, you'll need to disable this feature
during this process. There is a strong likelihood that this process will
distort your actual work record due to differences between the way Project
and PWA handle the data. In general, schedules that use effort-based
planning with as-soon-as-possible scheduling will remain nearly intact.
Projects using fixed-duration tasks as well as other variables will assume a
time-phased distribution that Project typically applies in processing actual
work against these tasks.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-