T
Tim
First an overview of what we have. I have a Windows 2003 Server running
SharePoint Services 3.0 and Project Server 2003 running in our DMZ. This is
a test project server and it has the admin SharePoint site running on it. I
have 10 users that will be using Project Server. We have a SQL 2005 Express
server also on Windows 2003 Server running on our internal LAN. Of course
Project 2003 Server has no idea that SPS 3.0 exists, so I followed KB article
917401 with great success to setup the Project database using the command
line.
Symptoms: PWA has it's users logon using windows authentication except for
the PWA admin account, but the users can only get into PWA when logging into
the test SharePoint & Project server. When I'm logged into my PC and
navigate to the PWA site, I get the following error...
"Project was unable to log you on at this time because the Project Server
database cannot be accessed. Please try again later or check with your
Project Server administrator. (5001)"
When I login to the Project server I get a Welcome plus my name.
At that time I see on the main screen a task and risk that states, "There is
a problem establishing a connection with the Web server running Windows
SharePoint Services. Contact your system administrator."
Can someone direct me on how to troubleshoot extending the Project site in
SharePoint 3.0? I've tried doing this by creating a new application within
SharePoint, but it won't let me reference the Project site in IIS because the
port is already in use. Within PWA logged in as the admin, testing the
SharePoint admin URL pops up the admin site with no problem.
When I specify the following SharePoint setting within the Project admin
site, it obviously fails.
Under the "Create a site under this SharePoint URL:" field I have
http://betasp:8080/sites which is just a sites folder under the main PWA
site. When I click to verify the public documents site
"http://betasp:8080/sites/MS_ProjectServer_PublicDocuments" obviously it
fails because the sites and MS_ProjectServer_PublicDocuments folders do not
exist.
I know it's not a firewall issue as far as the SPS3.0 server in the DMZ
going to the SQL server in the LAN has nothing but excepted packets. My PC
in the LAN going to the PWA site has nothing, but accepted packets. the IDs
are setup right, but they ONLY WORK when authenticated locally to the SPS &
Project server. So the accounts for the MSProjectServerRole and
MSProjectUserRole are OK. It must be something to do with Project and
SharePoint not getting allong together.
I think I'm close to getting a test site up and running and appreciate any
help.
SharePoint Services 3.0 and Project Server 2003 running in our DMZ. This is
a test project server and it has the admin SharePoint site running on it. I
have 10 users that will be using Project Server. We have a SQL 2005 Express
server also on Windows 2003 Server running on our internal LAN. Of course
Project 2003 Server has no idea that SPS 3.0 exists, so I followed KB article
917401 with great success to setup the Project database using the command
line.
Symptoms: PWA has it's users logon using windows authentication except for
the PWA admin account, but the users can only get into PWA when logging into
the test SharePoint & Project server. When I'm logged into my PC and
navigate to the PWA site, I get the following error...
"Project was unable to log you on at this time because the Project Server
database cannot be accessed. Please try again later or check with your
Project Server administrator. (5001)"
When I login to the Project server I get a Welcome plus my name.
At that time I see on the main screen a task and risk that states, "There is
a problem establishing a connection with the Web server running Windows
SharePoint Services. Contact your system administrator."
Can someone direct me on how to troubleshoot extending the Project site in
SharePoint 3.0? I've tried doing this by creating a new application within
SharePoint, but it won't let me reference the Project site in IIS because the
port is already in use. Within PWA logged in as the admin, testing the
SharePoint admin URL pops up the admin site with no problem.
When I specify the following SharePoint setting within the Project admin
site, it obviously fails.
Under the "Create a site under this SharePoint URL:" field I have
http://betasp:8080/sites which is just a sites folder under the main PWA
site. When I click to verify the public documents site
"http://betasp:8080/sites/MS_ProjectServer_PublicDocuments" obviously it
fails because the sites and MS_ProjectServer_PublicDocuments folders do not
exist.
I know it's not a firewall issue as far as the SPS3.0 server in the DMZ
going to the SQL server in the LAN has nothing but excepted packets. My PC
in the LAN going to the PWA site has nothing, but accepted packets. the IDs
are setup right, but they ONLY WORK when authenticated locally to the SPS &
Project server. So the accounts for the MSProjectServerRole and
MSProjectUserRole are OK. It must be something to do with Project and
SharePoint not getting allong together.
I think I'm close to getting a test site up and running and appreciate any
help.