Project 2007 keep Crashing

J

Jon

We have Project server 2007, when working on client computers with Office
project 2007 link to the server, Office Project 2007 on the computer just all
of a sudden crash and closes the application it happens on Windows Xp and
Vista as well.

It would say an error had occurred and ask if I want to restart Project and
to send the problem info to Microsoft. It happens to everyone in the company
and it happens very often. There is no pattern to as what cause it to crash,
as it can crash and restart at any time.

Server problem setup wrongly or is it common for Microsoft project to have
an error and restarts?

In Vista in the Program >Maintain> Problems Report and Solution I got this
info

Problem signature
Problem Event Name: APPCRASH
Application Name: WINPROJ.EXE
Application Version: 12.0.4518.1014
Application Timestamp: 45428184
Fault Module Name: WINPROJ.EXE
Fault Module Version: 12.0.4518.1014
Fault Module Timestamp: 45428184
Exception Code: c0000005
Exception Offset: 001181d7
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 4105

Extra information about the problem
LCID: 1033
Brand: Office12Crash
skulcid: 1033
 
M

Mark Everett | PMP

We have Project server 2007, when working on client computers with Office
project 2007 link to the server, Office Project 2007 on the computer just all
of a sudden crash and closes the application it happens on Windows Xp and
Vista as well.

It would say an error had occurred and ask if I want to restart Project and
to send the problem info to Microsoft. It happens to everyone in the company
and it happens very often. There is no pattern to as what cause it to crash,
as it can crash and restart at any time.

Server problem setup wrongly or is it common for Microsoft project to have
an error and restarts?

In Vista in the Program >Maintain> Problems Report and Solution I got this
info

Problem signature
Problem Event Name:     APPCRASH
Application Name:       WINPROJ.EXE
Application Version:    12.0.4518.1014
Application Timestamp:  45428184
Fault Module Name:      WINPROJ.EXE
Fault Module Version:   12.0.4518.1014
Fault Module Timestamp: 45428184
Exception Code: c0000005
Exception Offset:       001181d7
OS Version:     6.0.6000.2.0.0.256.6
Locale ID:      4105

Extra information about the problem
LCID:   1033
Brand:  Office12Crash
skulcid:        1033

Jon -

By any chance do you have an older version of Project installed also.
I experienced some Project 2007 Professional shutdowns when I was
running it on an XP machine with Project 2003 Professional. Other
than that, I haven't experienced any crashes.

HTH
Mark Everett | PMP
www.catapultsystems.com
 
J

Jon

Hi Mark,

We did a migrate from Microsoft Project Server 2003 to 2007. But no, I just
had my new computer currently and it only had Project 2007 on it.
 
P

Paul Conroy

Enable client side logging to ascertain additional information.

Try enabling client side logging with the following reg key. Does this
generate any additional information ?

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\MS Project]
"WinprojLog"="c:\\temp\\"
"DebugCategory"=dword:ffffffff
"DebugLevel"=dword:ffffffff
"DebugLoadSerCategory"=dword:000003ed

Do you have a clean client build you can install Project Pro on ? It maybe
that another app is causing a conflict.

Are you deploying Project Pro via some packaging software ? if so, try a
manual install as the package maybe corrupt.

Disable Anti-Virus/firewalls as it's not uncommon for these to cause issues.
 
N

Nico Oosthuysen

We had a major issue last year where we picked up bug that would cause
project to crash just about every time you saved a project. In the end, it
was a private release hotfix that MS gave us that sorted it out. Apparently
the hotfix was included in SP1, so its worht installing that. (the MSP SP1).
 
N

Nico Oosthuysen

We had a major issue last year where we picked up bug that would cause
project to crash just about every time you saved a project. In the end, it
was a private release hotfix that MS gave us that sorted it out. Apparently
the hotfix was included in SP1, so its worht installing that. (the MSP SP1).
 
J

Jon

Hey Paul,

I will try what you have recommended, haven’t tested it out yet. And to Nico
, we did installed SP1 and it didn’t fix the bug .

So I would have to keep my fingers cross.



Paul Conroy said:
Enable client side logging to ascertain additional information.

Try enabling client side logging with the following reg key. Does this
generate any additional information ?

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\MS Project]
"WinprojLog"="c:\\temp\\"
"DebugCategory"=dword:ffffffff
"DebugLevel"=dword:ffffffff
"DebugLoadSerCategory"=dword:000003ed

Do you have a clean client build you can install Project Pro on ? It maybe
that another app is causing a conflict.

Are you deploying Project Pro via some packaging software ? if so, try a
manual install as the package maybe corrupt.

Disable Anti-Virus/firewalls as it's not uncommon for these to cause issues.

Jon said:
Hi Mark,

We did a migrate from Microsoft Project Server 2003 to 2007. But no, I just
had my new computer currently and it only had Project 2007 on it.
 
J

John Horton

Jon,
I have similar issues.

Do you find that after you crash and force check the file back in that you
will often crash again if you try to open another file within 10 minutes?

Is your server on site?

Do you generally crash on one of the following: Open, Save, Publish or
Close/Checkin? Or are you crashes more when you are working?
 
D

Dean C

We're having similar problems with crashes. I identified one specific crash
in my post on this thread named 2007 Crashes when saving second linked file
off the server. I also verified that I can crash Project from the Visual
Basic Editor if I accidentally double click the save icon when Global.mpt is
the focus. It does not crash when other files are the focus.
 
J

John Horton

We found a work around. It turns out that having the auto filter turned on in
the enterprise global is part of the problem. Once we turned it off the
crashing stopped. Pretty ridiculous.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top