PWA Users cannot access SharePoint Project Site

[Mark Steele]

Greetings!

I currently have all my users / resources set to 'Team Member' role with
category and global permissions also set to 'Team Member'. I have ensured
the 'View Risks, Issues and Documents' check box is selected (on).

All users / resources are set to use AD Authentication.

When my users click on the 'Documents' menu item, and then select 'Public
Documents', 'Shared Documents' - they are prompted to enter a user ID and
password. The only UID / PW combination that works is the WSSAdmin UID /
PW.

The URL they are attempting to access is: -
http://ct1-prj-c01/sites/MS_ProjectServer_PublicDocuments

I thought the users would automatically propagate to the SharePoint Project
workspace.

Any ideas what may be causing this?

Thanks

 

[Rolly Perreaux]

Hi Mark,

Check the permissions to the SharePoint Web Site from IIS Manager
It sounds like built-in Users group doesn't have the necessary
permissions to the SharePoint Site.

By default, they should have the following permissions:
Read & Execute
List Folder Contents
Read
Special Permissions (Create Files/Write Data & Create
Folders/Write Data)

Let us know what you find.

Cheers,

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Rolly Perreaux]

Hi Mark,

Based on your screenshot it appears that you only have one IIS web site,
when you need two.

Do you have SharePoint Project Workspace sites already created for
projects in Project Server?

If not, then this is what I would do:

STEP 1
======
1. Create a new web site for SharePoint. Call it WSS with port 81 or 90
(you can't use port 80 as it's already used for Default Web Site) or use
a Host Header name that is configured in the DNS.
2. Close IIS Manager

STEP 2
======
1. Open SharePoint Central Admin
2. Click Extend or upgrade virtual server
3. Click on WSS link.
4. Under Provisioning Options, click Extend and create a content
database.
5. Under Application Pool, select WSSAppPool
6. Fill in the Site Owner section. (please note that the account used
here is the SharePoint Administrator, not the WSS service account)
7. Under Database, clear the "Use default content database server" check
box, and fill in the appropriate fields for a new SharePoint database.
8. Then click OK.

STEP 3
======
1. Then install the WSSWIZ on the newly created and extended WSS web
site from the Project Server CD. Make sure to write down the URL
information on the last page before closing.

STEP 4
======
1. Open PWA and logon as Administrator and click Admin --> Manage
Windows SharePoint Services.
2. At the Connect to SharePoint server page, change the URLs listed to
the ones that you wrote down in Step 2 and click Save Changes.
3. Once the settings are successfully changed, click on the following
link: http://CT1-PRJ-C01/sites/MS_ProjectServer_PublicDocuments to test
if you can access the Project Server Public Documents workspace. If you
can then all is good to go! ;-)

STEP 5 (old site clean up)
=========================
1. Open SharePoint Central Admin
2. Click Configure virtual server settings
3. Click on Default Web Site link.
4. Under Virtual Server Management, click Remove Windows SharePoint
Services from virtual server.
5. Then you need to decide if you want to keep or delete the content
database associated with the site.

Let us know how it turns out

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

Perry,

Looking in the IIS console - I am not clear on which web site is the one I
should be changing the permissions on (see attachment)



On 8/29/06 12:27 PM, in article
(e-mail address removed), "Rolly Perreaux"

Hi Mark,

Check the permissions to the SharePoint Web Site from IIS Manager
It sounds like built-in Users group doesn't have the necessary
permissions to the SharePoint Site.

By default, they should have the following permissions:
Read & Execute
List Folder Contents
Read
Special Permissions (Create Files/Write Data & Create
Folders/Write Data)

Let us know what you find.

Cheers,

[application/octet-stream]

 

[Mark Steele]

That's odd - I followed the installation guidelines in the 'Small
Installation' guide from Microsoft - on each previous installation, the
document space was available.

I went through the same installation, including extending the virtual server
- that must have failed at some point.

I will follow your instructions listed below - when I clean up the site
(step 5) - will I lose the current content (the projects) loaded through
PWA?

On 8/29/06 5:05 PM, in article
(e-mail address removed), "Rolly Perreaux"

 

[Mark Steele]

Rolly,

Thanks Again.

I created the WSS site and then took a look at the content and noticed it
was identical to what was already in the root.

So - I ran the WSS Wizard off the cd and reinitialized the default web site
and Viola - it is back!

Thanks

On 8/29/06 6:53 PM, in article C11A3DA9.1866A%[email protected], "Mark

 

[Rolly Perreaux]

Hi Mark,

The only thing that _was not_ included in the Installation Guide is that
you need to create two IIS web sites to install SharePoint and Project
Server on the same server.

When you say "the projects" are you referring to the Project Server
database (project plans) or the SharePoint content database (docs, risks
and issues) for the old site?

Note: If you follow the Steps 1-4 then your new WSS site will have a new
content database. Depending on your selection in Step 5 will determine
if you delete the content database or not for the old site. When in
doubt, save the database.

BTW, you should make a backup of all SQL databases before starting this.
But you knew that already <g>

Let us know what happens

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Rolly Perreaux]

Excellent news Mark!

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Mark Steele]

LOL - it still does not let me go to it directly from PWA - I can go to the
website directly though (http://ct1-prj-c01 brings up the Sharepoint
Project)

I am going to create the second website per your instructions

On 8/29/06 7:51 PM, in article
(e-mail address removed), "Rolly Perreaux"

 

[Mark Steele]

That still did not work :-(

I am noticing that when the authentication window opens up, it is asking me
to authenticate to CT1-PRJ-C01.nw.net instead of CT1-PRJ-C01 - could that be
an issue?


On 8/29/06 8:46 PM, in article C11A582D.18687%[email protected], "Mark

 

[Mark Steele]

Oy Vey - you had it right the first time Rolly - the Users builtin did not
have appropriate permissions.

I should have also said it was a single server install running MSDE

On 8/29/06 8:56 PM, in article C11A5A8B.1868A%[email protected], "Mark

 

[Rolly Perreaux]

OK Mark
First things first <g>

1. Did you removed the old SharePoint site from SharePoint Central
Administration?
2. In IIS Manager, under Default Web Sites, do you have only the
following objects listed:
MSADC
ProjectServer
aspnet_client
iisstart.htm
pagerror.gif

3. Is the WSS Service account added to the local Administrators Group?
4. Can you access:
http://CT1-PRJ-C01:<portnumber>/
http://CT1-PRJ-C01:<portnumber>/sites/MS_ProjectServer_PublicDocuments

Let us know what you find

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Rolly Perreaux]

So all is good now Mark?

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Mark Steele]

All is good now!

On 8/29/06 10:01 PM, in article
(e-mail address removed), "Rolly Perreaux"

 

[Gary L. Chefetz [MVP]]

Strictly speaking, you don't need two web sites, although I think it's a
good idea. It does help if you install WSS first, then Project Server.
Otherwise you simply need to manually setup the managed path exclusions.