PWA doesn't launch Pjt Pro 2007 client

[George]

Upon a suggestion from Dale, I'm resubmitting a question with some more
information.

I recently installed Pjt Svr 2007 and find that although I can connect to
Pjt Svr from a Pjt Pro 2007 client, I can't launch Pjt Pro 2007 from PWA. I
get the error message:

"The operation could not be performed as it requires Microsoft Office
Project Professional 2007. Make sure that Project is installed on this
machine and that a profile to this server exists. If Project is currently
running, ensure tht it is logged on to this server and that there is no
dialog open."

I don't know whether it matters or not, but neither the client nor the
server is part of a domain.

I'd appreciate any advice.

 

[Lisa]

George,
I was experiencing a similar issue at a client site.

Cause: We saw the message after the customer requested that Project Server
use the DNS instead of the system name. Our architect made the change, ran
into other issues, and after working with Microsoft had to reinstall Project
Server. It wasn't until a week later that we discovered this issue.

Troubleshooting: There were a number of things we tried and to be honest,
we still aren't sure what fixed it. I did open a case with Microsoft after
performing steps 1-3 below on my own. Case #: SRX070427602441.
1. Make sure the PWA URL and the URL in your Project Pro account match.
2. Delete the account in Project Pro and re-add.
3. Make sure the URL is a trusted site in I.E.
4. The Microsoft Technician checked the settings on the server but didn't
make any changes.
4. We installed Project Pro 2007 on the server and rebooted the server. We
didn't receive the message on the server.
5. I still received the message on the client and then deleted and readded
the account in Project Pro. This time it worked. I made the changeon the
other client PCs and the issue seems to have been resolved.

Lisa

 

[George]

Lisa,
It worked! The URL in the Project Pro account was different than the URL in
the browser for the PWA site. One was a fully qualified domain name and the
other was just the server name. I have no idea why this would make a
difference, but it did.

 

[Lisa]

You're welcome.

Lisa,
It worked! The URL in the Project Pro account was different than the URL in
the browser for the PWA site. One was a fully qualified domain name and the
other was just the server name. I have no idea why this would make a
difference, but it did.

 

[anil]

thank u

George,
I was experiencing a similar issue at a client site.

Cause: We saw the message after the customer requested that Project Server
use the DNS instead of the system name. Our architect made the change, ran
into other issues, and after working with Microsoft had to reinstall Project
Server. It wasn't until a week later that we discovered this issue.

Troubleshooting: There were a number of things we tried and to be honest,
we still aren't sure what fixed it. I did open a case with Microsoft after
performing steps 1-3 below on my own. Case #: SRX070427602441.
1. Make sure the PWA URL and the URL in your Project Pro account match.
2. Delete the account in Project Pro and re-add.
3. Make sure the URL is a trusted site in I.E.
4. The Microsoft Technician checked the settings on the server but didn't
make any changes.
4. We installed Project Pro 2007 on the server and rebooted the server. We
didn't receive the message on the server.
5. I still received the message on the client and then deleted and readded
the account in Project Pro. This time it worked. I made the changeon the
other client PCs and the issue seems to have been resolved.

Lisa

 

[Gary L. Chefetz [MVP]]

George:

It makes sense because the action in PWA looks for the Project Server
account on the client machine to use to open Project Pro. If it doesn't find
the current URL, it assumes that you haven't connected to Project Server
properly.

--

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