PWA crash - pjgrid11.ocx on "View Availability"

[Jack Kohn]

We have one PWA user that gets an Internet Explorer crash every time
he selects "View Availability" from the Resources tab.

We have narrowed this problem down to one PWA user, and it affects him
on every workstation he tries. Other PWA users can execute the same
steps successfully.

Interestingly, this same problem was mentioned in this web post from
approx a year ago:
http://www.eggheadcafe.com/forumarchives/projectserver/jun2005/post23369187.asp
The solution suggested there (by Gary Chefetz) was to upgrade MDAC.

However, in our case, we've tried this on multiple workstations, both
Windows 2000 and Win XP. (With Win 2K variously running MDAC
2.70.xxxx, 2.71.xxxx, and 2.80.1022.0, and Win XP running MDAC
2.81.1117.0). It is not workstation-dependent. It has something to do
with this particular user.


His rights on the Project Server are set identically to other working
users. (He's a member of the Project Managers and Team Members groups,
with no additional rights granted to his specific ID). Just for yuks,
I granted this user full rights on the Project Server - he still gets
the same error. I also tried giving him extra Windows rights on his
workstation; even as a local admin he gets the error.


ERROR DETAILS
Under Win 2000, the Internet Explorer error dbox lists the following
Error Signature (which has been consistent in my last couple tries):

AppName: iexplore.exe AppVer: 6.0.2800.1106 ModName: pjgrid11.ocx
ModVer: 11.1.2004.1707 Offset: 0002cd6d

Under Win XP, he gets "IE has encountered a problem and needs to
close..." If we hit Debug, it's followed by an "iexplore,exe -
Application Error / The instruction at "0x2dc3cd6d" referenced memory
at "0x00000098". The memory could not be "read". Click OK..." message.


One possible clue: When this project manager was first added to our MS
Project server, his email address was input incorrectly. The MSP admin
was later alerted to the change in his email and fixed it.

Any ideas? Thanks in advance.

-jmk
Jack Kohn

 

[Gary L. Chefetz [MVP]]

Jack:

Have you tried recreating the user profile in Active Directory?

 

[Gary L. Chefetz [MVP]]

Jack:

You might also simply try a password change before you recreate the profile.

 

[Jack Kohn]

Thanks for the suggestions. I'll look into them. A password change
will be easy. Recreating the user in AD will be a bit more of a
hassle: issues with Exchange, group memberships, etc.

I'll keep you posted. Any other ideas are, of course, welcome, too.

Thanks.

-jmk
Jack Kohn

Jack:

You might also simply try a password change before you recreate the profile.


Jack:

Have you tried recreating the user profile in Active Directory?

--

 

[Jack Kohn]

Well, no luck just doing the password change. Same results. Looks like
we'll try to recreate his AD account.

That *is* what you meant by "recreating the user profile in Active
Directory", isn't it?

More as I learn it. Thanks again.

-jmk
Jack Kohn

 

[Gary L. Chefetz [MVP]]

Yes sir.

 

[Jack Kohn]

I wound up with a workaround. I created a local Windows user account
on the Project server, and then added that account as a user to MS
Project.

When the user needs the Resource Availability report, he'll just log
out of PWA from his Windows ID, and then log into PWA with the local
ID I created.

It's a little kludgey, but the user only needs the report occasionally
and felt this workaround was acceptable.


As an ironic sidenote: I made a typo when I first created the local
account. After I fixed the typo in Windows and in MS Project, PWA
still wouldn't let me log on with it. It's like I broke the account
when I changed the spelling of the ID. I had to create a whole new
local account. It's almost a variation on this user's original
problem.

Thanks for your help. It got us through. Take care.

-jmk

 

[John Sitka]

As an ironic sidenote....
that's funny, happens here all the time, the PWA account is based on Domain\username Windows user account. But we useWindows First
Last name as resource name.
When adding a new resource at Open Enterprise Resource pool it does some look up for
Domain Resource based on the first / last names and the resulting default display names. Spelling is important. Especially when the
functional business language of the Domain Admin's is a second language and spelling mistakes are rampant.
Use the clean up Project Server database for resources if you can before the misnamed resource is "in the game". It might be a
syncronized address book would help on resource creation but I've never seen one of those.

 

[Jack Kohn]

John -
Good tip! Thanks. I just cleaned up that typo-account so no one else
will step in it.

Take care.

-jmk
Jack Kohn