Job Failed. Could not Load Project. Project Server error code:42

A

Angie

I just loaded both the Windows Sharepoint Services 3.0 SP1 and 2007 MS Office
Servers SP1 (Project Server) in my test environment. I can open the PWA site
and all web sites, but I cannot open project from a Project Pro 2007 client
workstation using my previous project server account setups.
I get the following error message...
"Job Failed; Job Type: Load, Error ID 42(0X2A); Error Description: Project
Server encountered a problem with this error code:42.
Could not load Project. Please try after some time. If the problem persists,
contact your system administrator.
The only option is to click ok through this error.
Then this message appears " Could not retrieve enterprise global template.
There seems to be a problem with the database, contact your server
administrator"

Any ideas? Is this a permissions issue? Any ideas on what to research on the
database side?
Please help!
 
M

MHS70

I'm having the same problem.  Did you find a solution yet?






- Show quoted text -

Don't panic - it's not a database issue - it's definitely a
permissions issue. I've gone through this before, but don't have the
time to replicate, so my instructions may not be perfect...

First off, you can't use 2003 account informaiton since 2003 used a
proprietary authentication scheme and 2007 uses Windows login scheme-
however you are logged into your PC, that is the informaiton passed
along from 2007 Client to 2007 Server.

With that said, first, I would use PWA and go to "Server Settings" and
"Manage Users" and make sure that the authentication you have selected
is Windows. While you're there, make sure the bare minimum are
"allow"ed, such as "Log on to Project Server from Project
Professional", and "Open Project", etc.

Then, on the client end of things, go to Start->Programs->Microsoft
Office->Microsoft Tools->Microsoft Office Project 2007 Server
Accounts. Make sure the URL is correct.

I'll be glad to give you further instructions, but it may not be
necessary at this stage.
 
W

wildo

I wish it was that simple. We have another installation that works fine, and
this is a new install. These are both clean 2007 installs, using Windows
Authentication. I'm an administrator (actually have given myself all
groups), and have not changed anything in security anywhere. Two other
users, one with only admin and another with PM, have the same problem.
Everything is correct in the MS Project Pro side with the account and URL.

We're able to connect and operate everything fine with PWA - it's just the
connection with Project Pro that gives problems.

The only differences between the one that works and the one that doesn't, is
the new one is in a different server area, and that it has SP1 installed
while the old one does not.

Is there an SP1 that is required for the desktop for it to work? Any other
ideas?
 
M

MHS70

I wish it was that simple.  We have another installation that works fine, and
this is a new install.  These are both clean 2007 installs, using Windows
Authentication.  I'm an administrator (actually have given myself all
groups), and have not changed anything in security anywhere.  Two other
users, one with only admin and another with PM, have the same problem.
Everything is correct in the MSProjectPro side with the account and URL.

We're able to connect and operate everything fine with PWA - it's just the
connection withProjectPro that gives problems.

The only differences between the one that works and the one that doesn't, is
the new one is in a different server area, and that it has SP1 installed
while the old one does not.  

Is there an SP1 that is required for the desktop for it to work?  Any other
ideas?










- Show quoted text -

How soon do you get the error message - as soon as project starts or
when you attempt to open a project on the server?
 
W

wildo

It happens when immediately when trying to connect.

I also installed SP1 for MS Project Pro, and still have the same problem.
 
W

wildo

No resolution yet, and we have several people looking into it - getting ready
to uninstall and reinstall and see what happens.

In the meantime, I also found that I cannot create and save a new proposal
either, all within PWA. So if these two are related, it's not just a problem
in connecting with Project Pro.
 
C

Char

Hi Wildo,

I'm working on this issue right now with Microsoft. In my situtation they
noticed that my Project Server databases weren't ugpraded to SP1. You'll need
to run the select * from versions query to check very version #. This is a
good site that will tell you what RTM and SP1 versions should be.

http://blogs.msdn.com/shaden/

Looks as though I need to push out SP1 again. I'm waiting on a resolution
from Microsoft as I type....
 
W

wildo

Thanks for the info. Unfortunately I don't have access to the database, so
am asking someone to look in to it.

If you get an answer from Microsoft, or find a resolution yourself, please
share. Thanks.
 
C

Char

Do you know if the DBA pre-created the Project databases? If so, the
databases weren't applied with SP1...not sure why.
As a test, what you could provision a new PWA site with new databases (don't
manually create the databases before hand) and see if you can connect using
Pro. I tested it and it worked, I can connect to the new site using Pro.
 
W

wildo

That appears to be our problem - THANKS !!

Char said:
Do you know if the DBA pre-created the Project databases? If so, the
databases weren't applied with SP1...not sure why.
As a test, what you could provision a new PWA site with new databases (don't
manually create the databases before hand) and see if you can connect using
Pro. I tested it and it worked, I can connect to the new site using Pro.
 
A

Andy S

So is there a solution here that doesn't require creating new Project
Server databases? I am getting the error code 42, and I see that my
databases have not had SP1 applied. Won't I lose my data if I create
new databases?
 
W

Wajdi

I have the same problem, after I migrated the farm to new servers updated to
SP1, the PWA was successful but when I tried to open Project professional the
following error occured:

error 42(0x2a)
error description: Project Server encountered a problem with this error code
42.

<detail><errinfo><general><class name="An unhandled exception occurred in

WinProj.ReadProjectCoreData."><error id="42" name="GeneralUnhandledException"

uid="d48cc6b0-d5de-4bdb-8685-bf2110d61ae9"/></class></general></errinfo></detail>

could not retrieve enterprise global template

this is same error that occured to Angie, I wish someone would help on this
because it's critical
 
D

Dule

Please help. I receive the same error message when trying to enter Project
Proffesional.
Can someone experienced just give us a suggest in way we should go to find a
solution. I really dont want to create new databases. Can the post SP1 hotfix
resolve the problem? The problem was born just after the SP1 installation.
 
M

masjfal

....and so am I. I've installed Project Professional 2007 on one Citrix
Presentation Server 4.5 and as soon the application is started we get one of
the following two errors:

"Could not access Enterprise Global"
or
"Could not retrieve Enterprise Global template. There seems to be a problem
with the database, please contact your server administrator"

Any ideas... anyone?

//Masjfal
 
S

Sohaib Al-Husseini

Hi,

I have recently faced the same error, we got it in many implementations. In order to solve it we tried to remove all resources from summary tasks, but it didn't work. As our last resort we went to the resource sheet view and deleted the resources, it worked fine with us like magic.

Hope it would be applicable for other cases, too.

Thanks
 

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