Windows Error Reporting

J

J Burford Fields

We are using Project Server 2003. When I save one project, Project
Professional fails. "Microsoft Project has encountered a problem and
needs to close...."

If I send an error report, I get the thank you dialog box with a link
to "Get more information about prventing this problem in the future."

If I click that link it goes to a link with the information, below.
Problem is that I know SP2 has been installed but I'm running on a
"managed" system in a secure environment. No way I can download. I
am not even allowed to install the Active X component that checks for
a valid installation of Project.

J
----------------------------

Download updates for Microsoft Office System Software

This problem was caused by Microsoft Office System Software. Microsoft
Office System Software was created by Microsoft Corporation.

An update is available for your Microsoft Office System product. This
cumulative update fixes many of the problems customers have reported
to us through the problem reporting system.

Solution

--------------------------------------------------------------------------------


Get the update from the Office Update website

Note: There might be more than one update to install at the Office
Update website. We recommend you install all Required Updates on this
site to keep your Office System software up to date.

If you are asked for the original Office System CD-ROM

If you are asked for the original CD-ROM you used to install Office
and you don't have the CD-ROM available, you can still update your
computer using the Office Update website and by following these steps:

Go online to Office Update.
Click Check for Updates. Office Update will check your computer for
updates you need.
After Office Update checks your computer, click Options (in the upper
right corner of the page, just below the Go button).
On the Options for using Office Update page, select Use larger update
files that should not require access to my product CD or network
installation location.
Click Save. Office Update will check your computer again for updates
you need.
After Office Update checks your computer, click the Agree and Install
button to install the updates.
 
J

J Burford Fields

JB:

Happy new year to you, too! Is this a holiday rant, or are you looking for
information?

--

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













- Show quoted text -

My reputation precedes me? Wasn't meant to look like a rant.
Puzzling to me that just one file causes the error and that the error
messages lead me to advice to update Office (which already is).

I am trying to sort through a fix for this project. We will try
rebuilding the binary file, today, probably. Otherwise, I'll make a
spreadsheet of the "actuals" and try the xml export/import or a DBA
restore from a previous backup.

Any other thoughts would be appreciated.
 
J

J Burford Fields

My reputation precedes me?  Wasn't meant to look like a rant.
Puzzling to me that just one file causes the error and that the error
messages lead me to advice to update Office (which already is).

I am trying to sort through a fix for this project.  We will try
rebuilding the binary file, today, probably.  Otherwise, I'll make a
spreadsheet of the "actuals" and try the xml export/import or a DBA
restore from a previous backup.

Any other thoughts would be appreciated.- Hide quoted text -

- Show quoted text -

One of the things that confuses me is that on the Force Rebuild, the
instructions say to change the PROJ_EXT_EDITED field from 0 to 1, but
what we see is TRUE in that field.
 
J

J Burford Fields

One of the things that confuses me is that on the Force Rebuild, the
instructions say to change the PROJ_EXT_EDITED field from 0 to 1, but
what we see is TRUE in that field.- Hide quoted text -

- Show quoted text -

Probably bad form to reply so often to a thread I started. Turned out
the DBA was using a different tool. Using SQL Enterprise Manager on
the SQL server box yielded ones and zeros. The field was already a
one. Nevertheless, we re-entered the "1" and it seems to have fixed
the problem.
 
Top