Cannot Access Projects Via PWA... and I'm the Admin

[Frank J.]

Project Server 2007, with SP1

This is a strange one. I am set up on the Server with full Admin Rights.
System was always working fine until about last Thursday. I cannot access
(open any Published Projects).

While in PWA I can all looks normal, I can even perform all Server Setting
Functions.

If I open up Project Pro on my laptop, I can logon (connect) to the server
and even save and publish a new Project.

However while in PWA, if I try to edit an existing project I get the
following error message...

To perform this action, you need Microsoft Office Project Professional 2007.
If you are using this version, verify that the account for the computer
running Project Seerver has been set up and selected. To verify the account,
on the tools menu, click Enterprise Options, and then click Project Web
Accounts. If you still cannot perform this action, contact your server
Administrator to ensure that features have been enabled on project server.

Other note, two staff members set up as PROJECT Managers are running fine.
I have tried the following with no luck:


1. Resetting my rights on the server;
2. Resync with active directory;
3. Logging on with my ID from another computer.

So far no luck

frankj

 

[Paul Conroy]

Try clearing the temp files within IE before browsing to PWA.

--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com

 

[Scott Morrissey]

Frank - the only time I have seen this is when you log into PWA and
Professional using different paths. If I log into PWA using an "alias" or
generic path and Professional using the direct server path, I get this error.

Take a look at the exact path that you are logging into each component. In
PWA, try the direct link where the server is and not an alias. This might
work for you.

 

[Mac Hart]

Experienced same project a few weeks ago. Actually several of us did
(different companies and locations) at about the same time.

I reinstalled Project Pro on my laptop, and the PWA worked fine after that.
This fix did not work for a few other users with the same error. Still
looking into the problem. Microsoft released some critical patches to the
laptop for Project 2003, but wondering if they fiddled with IE??

 

[Jim Erwin]

If Scott's recommendation doesn't work (hopefully it should), try
deleting and recreating the connection to PWA from Project Pro. It
could just have gotten corrupted somehow.

 

[Frank J.]

Just to kep those trying to help posted...

I tried Paul's suggestion of clearing Internet casche.... that did not help
I looked at Scotts suggestion.... but we are not using an alias
and I tried Jim's suggestion of breaking the link and than reestablishing...
nope.

I will now try to uninstall project and re-install.

Frankj

 

[Frank J.]

RESOLVED!!!

After many days of "fighting this issue", I went back and review the
suggestions in this chain by all. Determined that our tech support team
indeed did change the hard address to an alais as Scott had suggest as a
posible cause. Going back to the real address resolved issue. So much for
teams here keeping each other informed of system changes :-(

I thank all for your suggestions!!!!

Frankj

 

[Camsaway]

Hi,
I'm also experiencing the same probs. Pardon my niavety, but what do you
mean by hard name 'v' alias? We have a DNS entry for epm.intranet which
points to the IP of the server that is hosting Project Server 2007, then in
the site config we have this configured as the site name. We epm.intranet in
the configuration of the project server account within Project Pro 2007. Are
you saying we need to use the servername (and set EPM as the default sitE)
instead of the URL in DNS?

Cheers,
Cameron.

 

[Frank J.]

Camsaway,

Yes... we reverted back to the Server name to get this to work. My
technical people here tell me this will cause problems for off-site people to
access without haveing to go through VPN.

But for now, by using the server name I have had no problem


Frank

 

[Camsaway]

Oh well. Not an option for me unfortunately. (Server is used for more than
EPM so don't want to set it as default site).

I'll have to keep looking.

 

[Gary L. Chefetz [MVP]]

Camsaway:

You can use a DNS alias without any problem, however you must use it for
both your PWA session and as the URL for your Project Server account in the
Project Client. The two must match. If you use machine name in one, then you
must use machine name in the other. Get it?

Now, do you really have the same problem or the same symptoms? Me-too posts
don't provide enough information to determine the difference. Start your own
thread if this doesn't answer your question.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com