PM can't save projects.

[ah.longoria]

Hi,

I'm hoping someone can help me out--I'm still new to Project Server. Our
organization has set up Project Server 2003 (a single computer installation)
alongside Project Professional 2003. We've set it up with Project Server
user authentication instead of Active Directory authentication. Everything
seemed to be running fine--our project manager could publish assignments from
Project Pro, and team members were updating their timesheets from PWA.

The only problem we were having, though, was that anytime we tried to access
Project Server (either through PWA or Project Pro), we'd get a Windows logon
prompt, and we'd have to sign in using the local Windows user account that
was set up to access the server. I searched through the message archives of
this group and found a posting that stated that in order to get rid of the
login prompt, we had to enable anonymous access to the server through IIS and
use the 'ProjServ' Windows user account to allow anonymous access. I applied
this setting to the ProjectServer virtual directory as well as the MSADC
virtual directory in IIS, and the prompt stopped appearing.

What's happening now is that when the project manager opens a project from
Project Pro, all of the publishing and saving options are disabled. She can
make modifications to the project, but she can't save or publish anything.
The menu items are simply disabled. I'm at a loss as to what to do. Is it
possible that enabling anonymous access to the server had something to do
with this? I made sure that the project isn't checked out. I also made sure
that all of the user groups/categories she belongs to don't deny Open/Save
access to projects.

I hope this posting isn't too lengthy. I'd appreciate any help or input
from anyone.

Thanks,
Art

 

[Dale Howard [MVP]]

Art --

Did the user create a Project Server login account in Microsoft Project
Professional?

 

[Akram Hussein]

did you make sure that the right security is given to those resources to save
and publish projects.

 

[ah.longoria]

Dale,

Yes, our PM has a Project Server login account in Project Professional. She
signs in to Project Server using her login account everytime she opens
Project Professional. She is able to check out a project from Project
Server, and she is also able to modify/add/delete tasks for the project, but
she can't save or publish the project after making these changes. The menu
items are greyed out and disabled. Is that what happens if a user does not
have the security permission to save/publish projects--the menu items are
disabled?

 

[ah.longoria]

Akram,

From what I can tell, yes, she does have the correct security. I say this
because she has been able to save and publish projects in the past. This
issue has just recently come up. She is a member of three of the default
Project Server user groups--Project Managers, Resource Managers and
Administrators (I just recently added her to the Admin group to see if she'd
still have this problem even with Admin permissions). I also verified the
security permissions for these user groups of which she's a member.
Everything appears to be correct. I will go through and double-check her
permissions, though, because it seems that this is a security permission
issue.

did you make sure that the right security is given to those resources to save
and publish projects.


--
Akram Hussein [Microsoft Office Project MVP]

Hi,

I'm hoping someone can help me out--I'm still new to Project Server. Our
organization has set up Project Server 2003 (a single computer installation)
alongside Project Professional 2003. We've set it up with Project Server
user authentication instead of Active Directory authentication. Everything
seemed to be running fine--our project manager could publish assignments from
Project Pro, and team members were updating their timesheets from PWA.

The only problem we were having, though, was that anytime we tried to access
Project Server (either through PWA or Project Pro), we'd get a Windows logon
prompt, and we'd have to sign in using the local Windows user account that
was set up to access the server. I searched through the message archives of
this group and found a posting that stated that in order to get rid of the
login prompt, we had to enable anonymous access to the server through IIS and
use the 'ProjServ' Windows user account to allow anonymous access. I applied
this setting to the ProjectServer virtual directory as well as the MSADC
virtual directory in IIS, and the prompt stopped appearing.

What's happening now is that when the project manager opens a project from
Project Pro, all of the publishing and saving options are disabled. She can
make modifications to the project, but she can't save or publish anything.
The menu items are simply disabled. I'm at a loss as to what to do. Is it
possible that enabling anonymous access to the server had something to do
with this? I made sure that the project isn't checked out. I also made sure
that all of the user groups/categories she belongs to don't deny Open/Save
access to projects.

I hope this posting isn't too lengthy. I'd appreciate any help or input
from anyone.

Thanks,
Art

 

[ah.longoria]

Dale,

After replying, I realized I may have misunderstood your question. The
Project Server login account that she uses was created in PWA, not from
within Project Professional. All other logins, though, she created from
within Project Professional using the Import Resources wizard. Hers was the
only login not created via the wizard in Project Professional.

 

[Dale Howard [MVP]]

Art --

I would suggest you remove her from both the Resource Managers group and the
Administrators group and then see if the problem goes away. Let us know the
results.

Akram,

From what I can tell, yes, she does have the correct security. I say this
because she has been able to save and publish projects in the past. This
issue has just recently come up. She is a member of three of the default
Project Server user groups--Project Managers, Resource Managers and
Administrators (I just recently added her to the Admin group to see if
she'd
still have this problem even with Admin permissions). I also verified the
security permissions for these user groups of which she's a member.
Everything appears to be correct. I will go through and double-check her
permissions, though, because it seems that this is a security permission
issue.

did you make sure that the right security is given to those resources to
save
and publish projects.


--
Akram Hussein [Microsoft Office Project MVP]

Hi,

I'm hoping someone can help me out--I'm still new to Project Server.
Our
organization has set up Project Server 2003 (a single computer
installation)
alongside Project Professional 2003. We've set it up with Project
Server
user authentication instead of Active Directory authentication.
Everything
seemed to be running fine--our project manager could publish
assignments from
Project Pro, and team members were updating their timesheets from PWA.

The only problem we were having, though, was that anytime we tried to
access
Project Server (either through PWA or Project Pro), we'd get a Windows
logon
prompt, and we'd have to sign in using the local Windows user account
that
was set up to access the server. I searched through the message
archives of
this group and found a posting that stated that in order to get rid of
the
login prompt, we had to enable anonymous access to the server through
IIS and
use the 'ProjServ' Windows user account to allow anonymous access. I
applied
this setting to the ProjectServer virtual directory as well as the
MSADC
virtual directory in IIS, and the prompt stopped appearing.

What's happening now is that when the project manager opens a project
from
Project Pro, all of the publishing and saving options are disabled.
She can
make modifications to the project, but she can't save or publish
anything.
The menu items are simply disabled. I'm at a loss as to what to do.
Is it
possible that enabling anonymous access to the server had something to
do
with this? I made sure that the project isn't checked out. I also
made sure
that all of the user groups/categories she belongs to don't deny
Open/Save
access to projects.

I hope this posting isn't too lengthy. I'd appreciate any help or
input
from anyone.

Thanks,
Art

 

[ah.longoria]

Dale,

I removed her from both groups, but the problem still remained. Her menu
items used to save and publish were disabled.

For reference, I wanted to see if perhaps this was only happening on her
workstation, so using her Project Server login information, I logged on to
Project Professional using a different workstation. I opened the enterprise
project that we've been having issues with, and, surprisingly, the
save/publish options were not disabled! For some reason, they were only
disabled on her specific workstation.

What we ended up doing, then, was providing her with a new Project Server
account and deleting her old one. Her new account has the same permissions
and is a member of the same default user groups as her old one (Project
Managers and Resource Managers), but she can now save/publish from her own
workstation. Not a very elegant solution to a very odd problem, sure, but
everything seems to be working now.

Thanks for all the help and input!

Art --

I would suggest you remove her from both the Resource Managers group and the
Administrators group and then see if the problem goes away. Let us know the
results.

Akram,

From what I can tell, yes, she does have the correct security. I say this
because she has been able to save and publish projects in the past. This
issue has just recently come up. She is a member of three of the default
Project Server user groups--Project Managers, Resource Managers and
Administrators (I just recently added her to the Admin group to see if
she'd
still have this problem even with Admin permissions). I also verified the
security permissions for these user groups of which she's a member.
Everything appears to be correct. I will go through and double-check her
permissions, though, because it seems that this is a security permission
issue.

did you make sure that the right security is given to those resources to
save
and publish projects.


--
Akram Hussein [Microsoft Office Project MVP]


:

Hi,

I'm hoping someone can help me out--I'm still new to Project Server.
Our
organization has set up Project Server 2003 (a single computer
installation)
alongside Project Professional 2003. We've set it up with Project
Server
user authentication instead of Active Directory authentication.
Everything
seemed to be running fine--our project manager could publish
assignments from
Project Pro, and team members were updating their timesheets from PWA.

The only problem we were having, though, was that anytime we tried to
access
Project Server (either through PWA or Project Pro), we'd get a Windows
logon
prompt, and we'd have to sign in using the local Windows user account
that
was set up to access the server. I searched through the message
archives of
this group and found a posting that stated that in order to get rid of
the
login prompt, we had to enable anonymous access to the server through
IIS and
use the 'ProjServ' Windows user account to allow anonymous access. I
applied
this setting to the ProjectServer virtual directory as well as the
MSADC
virtual directory in IIS, and the prompt stopped appearing.

What's happening now is that when the project manager opens a project
from
Project Pro, all of the publishing and saving options are disabled.
She can
make modifications to the project, but she can't save or publish
anything.
The menu items are simply disabled. I'm at a loss as to what to do.
Is it
possible that enabling anonymous access to the server had something to
do
with this? I made sure that the project isn't checked out. I also
made sure
that all of the user groups/categories she belongs to don't deny
Open/Save
access to projects.

I hope this posting isn't too lengthy. I'd appreciate any help or
input
from anyone.

Thanks,
Art

 

[Dale Howard [MVP]]

Art --

Thanks for letting us all know how you solved the problem. Congrats on your
persistence!

Dale,

I removed her from both groups, but the problem still remained. Her menu
items used to save and publish were disabled.

For reference, I wanted to see if perhaps this was only happening on her
workstation, so using her Project Server login information, I logged on to
Project Professional using a different workstation. I opened the
enterprise
project that we've been having issues with, and, surprisingly, the
save/publish options were not disabled! For some reason, they were only
disabled on her specific workstation.

What we ended up doing, then, was providing her with a new Project Server
account and deleting her old one. Her new account has the same
permissions
and is a member of the same default user groups as her old one (Project
Managers and Resource Managers), but she can now save/publish from her own
workstation. Not a very elegant solution to a very odd problem, sure, but
everything seems to be working now.

Thanks for all the help and input!

Art --

I would suggest you remove her from both the Resource Managers group and
the
Administrators group and then see if the problem goes away. Let us know
the
results.

Akram,

From what I can tell, yes, she does have the correct security. I say
this
because she has been able to save and publish projects in the past.
This
issue has just recently come up. She is a member of three of the
default
Project Server user groups--Project Managers, Resource Managers and
Administrators (I just recently added her to the Admin group to see if
she'd
still have this problem even with Admin permissions). I also verified
the
security permissions for these user groups of which she's a member.
Everything appears to be correct. I will go through and double-check
her
permissions, though, because it seems that this is a security
permission
issue.

:

did you make sure that the right security is given to those resources
to
save
and publish projects.


--
Akram Hussein [Microsoft Office Project MVP]


:

Hi,

I'm hoping someone can help me out--I'm still new to Project Server.
Our
organization has set up Project Server 2003 (a single computer
installation)
alongside Project Professional 2003. We've set it up with Project
Server
user authentication instead of Active Directory authentication.
Everything
seemed to be running fine--our project manager could publish
assignments from
Project Pro, and team members were updating their timesheets from
PWA.

The only problem we were having, though, was that anytime we tried
to
access
Project Server (either through PWA or Project Pro), we'd get a
Windows
logon
prompt, and we'd have to sign in using the local Windows user
account
that
was set up to access the server. I searched through the message
archives of
this group and found a posting that stated that in order to get rid
of
the
login prompt, we had to enable anonymous access to the server
through
IIS and
use the 'ProjServ' Windows user account to allow anonymous access.
I
applied
this setting to the ProjectServer virtual directory as well as the
MSADC
virtual directory in IIS, and the prompt stopped appearing.

What's happening now is that when the project manager opens a
project
from
Project Pro, all of the publishing and saving options are disabled.
She can
make modifications to the project, but she can't save or publish
anything.
The menu items are simply disabled. I'm at a loss as to what to do.
Is it
possible that enabling anonymous access to the server had something
to
do
with this? I made sure that the project isn't checked out. I also
made sure
that all of the user groups/categories she belongs to don't deny
Open/Save
access to projects.

I hope this posting isn't too lengthy. I'd appreciate any help or
input
from anyone.

Thanks,
Art