Project crash when assigning a resource to a task

[Willis78]

When allocating resources to tasks in Projects 2007 the application crashes
with an exception error. It seems to happen when displaying the dropdown. I
am running XP. The application just quits, the event viewer reports

Faulting application winproj.exe, version 12.0.4518.1014, stamp 45428184,
faulting module winproj.exe, version 12.0.4518.1014, stamp 45428184, debug?
0, fault address 0x0042d513.

Has anybody got any ideas, Diagnostics doesn't report any problems.

 

[Keith]

I am seeing the same problem; although mine seems to be related to the fact
that I am adding a new resource and not that I am using the drop down. (Mine
crashes either way) I was able to work around this problem by creating a new
project creating the task, then copying the old project into the new project.

Keith

 

[Jeapster]

I'm seeing the same issue.

I try to select a resource from the drop down and the application crashes.

I get this as a report

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: 0042d513
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 2057

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

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

 

[Grant]

I am seeing the same issue. The issue appears to be inconsistent over similar
devices with the same install.

 

[Willis78]

I am still experiencing problems with this. I have uninstalled and
re-installed but still have the same problem. Does anyone have any ideas how
to fix this. I have notice that also I get a crash when using the drop downs
in the Predecessor Name (split window view)

Any help is much appreciated

Thanks

Pete

 

[Dave]

I am still experiencing problems with this. I have uninstalled and
re-installed but still have the same problem. Does anyone have any ideas how
to fix this. I have notice that also I get a crash when using the drop downs
in the Predecessor Name (split window view)

Any help is much appreciated

Thanks

Pete

I'd suspect the PC itself or an operating system that has become corrupt.

I think I'd probably look at some of the PC beasting tools and focus
especially on the results for memory thrashing. After that, I'd
probably try and rebuild my hard disk (actually I'd probably replace it
whilst I was at it).

Have you any similar PCs available to you with which you can swap memory
to see if it follows the memory or stays with the PC?

 

[Dr Quack]

I experience the same problem as well and have found an odd solution.
I have a co-worker with Project 2003 open the file, make an edit then
save it. I can then open the new document and edit again, or rather I
was able to edit again until it started happening again.
The same document will crash any other machine running Project 2007
(which suggests the problem is not with my installation or my machine)
but does not crash other machines running Project 2003. I have tried
removing and re-installing project as well as running the MS Office
Diagnostics utility. Neither has helped.

 

[UncleBuckle]

I had this problem until I uninstalled the HP Credential Manager using
add/remove programs. Are you on an HP computer?

 

[JTL]

Hi,

I discovered the same crashing bug in Project 2007, found your mail and
disabled Single Sign On from Credential Manager (just removed checks in every
check box relating to SSO). That fixed the problem.

Thanks a lot.

 

[Frank123]

I am also a HP laptop user and the problem seems to have been caused b
the Credential Manager. Removing the software was not required, I jus
logged off from the Credential Manager

 

[Steve M]

I am having similar problems but on a dell running project 2007. SP 2 i
installed. When I try to view resources, resource graph or resourc
usage project crashes. The only message is that project has encountere
a problem and needs to close.

Any ideas on a correction to this