2 Unexpected Errors

[VballVol]

I have converted a client form PS2003 to PS2007 and I am receiving 2
errors that I can't figure out:

1) When trying to open the Enterprise Global, I get the unexpected
error and MSP has to restart.

2) Some users are getting the unexpected error when trying to open up a
project from the client. Out of 10 users, 4 are experiencing this.

Any ideas?

Rick

 

[Paul Conroy]

what's the difference between the 6 that are working and the 4 that are not ?

OS Version (Hotfixes/Sevice Packs)
Project Pro (Hotfixes/Service Packs)
Project Plans

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

 

[VballVol]

Paul,

Thanks for the response. The 4 user issue was an indexing issue on the
server. It wasn't an issue with the user, but rather a timeout to SQL.

The Global is still an issue and it is killing me!

Paul Conroy:

what's the difference between the 6 that are working and the 4 that are not ?

OS Version (Hotfixes/Sevice Packs)
Project Pro (Hotfixes/Service Packs)
Project Plans

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

I have converted a client form PS2003 to PS2007 and I am receiving 2
errors that I can't figure out:

1) When trying to open the Enterprise Global, I get the unexpected
error and MSP has to restart.

2) Some users are getting the unexpected error when trying to open up a
project from the client. Out of 10 users, 4 are experiencing this.

Any ideas?

Rick

 

[Mike Mahoney]

Paul,

Thanks for the response.  The 4 user issue was an indexing issue on the
server.  It wasn't an issue with the user, but rather a timeout to SQL.

The Global is still an issue and it is killing me!

Paul Conroy:

what's the difference between the 6 that are working and the 4 that

are not ?

OS Version (Hotfixes/Sevice Packs)
Project Pro (Hotfixes/Service Packs)
Project Plans

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

"VballVol" wrote:

- Show quoted text -

Some thoughts:
1. Install MSP2007 on server see if problem persists - if not issue at
client end, otherwise server or migration problem
2. Create new project server instance - does problem persist - if not
then migration issue
3. Upgrade MSP to SP1

Good luck

Mike

 

[VballVol]

All three suggestions completed and it is still an issue. Anyway to
rebuild the global.mpt?

Mike Mahoney:

Paul,

Thanks for the response. =A0The 4 user issue was an indexing issue on the
server. =A0It wasn't an issue with the user, but rather a timeout to SQL.

The Global is still an issue and it is killing me!

Paul Conroy:

what's the difference between the 6 that are working and the 4

that
are not ?

OS Version (Hotfixes/Sevice Packs)
Project Pro (Hotfixes/Service Packs)
Project Plans

Try enabling client side logging with the following reg key.

=A0Does
this

generate any additional information ?

Windows Registry Editor Version 5.00

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

"VballVol" wrote:

I have converted a client form PS2003 to PS2007 and I am receiving 2
errors that I can't figure out:

1) =A0When trying to open the Enterprise Global, I get the unexpected
error and MSP has to restart.

2) =A0Some users are getting the unexpected error when trying to

open
up a

project from the client. =A0Out of 10 users, 4 are experiencing

this.

Any ideas?

Rick- Hide quoted text -

- Show quoted text -

Some thoughts:
1. Install MSP2007 on server see if problem persists - if not issue at
client end, otherwise server or migration problem
2. Create new project server instance - does problem persist - if not
then migration issue
3. Upgrade MSP to SP1

Good luck

Mike

 

[Mike Mahoney]

All three suggestions completed and it is still an issue.  Anyway to
rebuild the global.mpt?

Mike Mahoney:

Paul,
Thanks for the response. =A0The 4 user issue was an indexing issue on the
server. =A0It wasn't an issue with the user, but rather a timeout to

SQL.

The Global is still an issue and it is killing me!
Paul Conroy:
what's the difference between the 6 that are working and the 4 that
are not ?
OS Version (Hotfixes/Sevice Packs)
Project Pro (Hotfixes/Service Packs)
Project Plans
Try enabling client side logging with the following reg key. =A0Does
this
generate any additional information ?
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\MS Project]
"WinprojLog"=3D"c:\\temp\\"
"DebugCategory"=3Ddword:ffffffff
"DebugLevel"=3Ddword:ffffffff
"DebugLoadSerCategory"=3Ddword:000003ed
:
I have converted a client form PS2003 to PS2007 and I am receiving 2
errors that I can't figure out:
1) =A0When trying to open the Enterprise Global, I get the unexpected
error and MSP has to restart.
2) =A0Some users are getting the unexpected error when trying to open
up a
project from the client. =A0Out of 10 users, 4 are experiencing

this.

Any ideas?
Rick- Hide quoted text -
- Show quoted text -

Some thoughts:
1. Install MSP2007 on server see if problem persists - if not issue at
client end, otherwise server or migration problem
2. Create new project server instance - does problem persist - if not
then migration issue
3. Upgrade MSP to SP1

Good luck

Mike- Hide quoted text -

- Show quoted text -

When you created a new PWA instance the enterprise global should be
blank. If MSP is crashing then it can't be the fault of the enterprise
global but some other issue, maybe your chasing the wrong rabbit.

regards

Mike