Project Server 2003 Setup, Now what

A

AsheNet

I am pretty sure I made it through the entire project server 2003 setup. This
is on a hosted 2003 Server also hosting Exchange 2003. I have a internet
address setup to reach the server and I can login to the Web Project Server
with http or https.

I think there are more things to setup.
I see there is no "cube" setup, I have no idea what that is - probably a
project database.

I have 2 existing project 2003 professional clients on laptops that have
projects started on their laptops. We were trying to figure out how they
interact with Project Server from their Laptops. It appears you can't create
a project on web project server, you have to do that in the client and then
publish it to the web server? I assume I have to configure something on the
client side to talk to the remote project server.

But I cannot find any info on just basically getting started. I have
searched quite a bit for several hours today. I mostly just find articles on
what project can do for you or some instructions on actually managing the
projects once they are setup, but I don't see any info on how to just get
started.

We have made the remote project server web site a trusted site on the
laptops and I also imported the root and web certificates that I had created
for Exchange (RPC over HTTP)

I basically have no idea where to begin in setting up the clients to work
with the server. Right now I have 1 laptop in the data center connected on
the same private network as the server just to make things easier at first.
though - all clients will work from the internet.

It appears there are several things to check and setup for sharepoint
services when I go to the admin section of the Project Server web site. but I
don't really understand. I'm sure there are more things to check and setup as
well. I did everything in the install. I printed out the 30 page install doc
and followed it exactly. It was actually a pretty good document.
 
A

AsheNet

I am the hosting provider. My data center, my server, my action pack copies
of project server 2003 and project 2003 pro.

I understand what the whole thing is supposed to do, just can't find any
information about what to do next after installing project server 2003. Where
do I go from there?
 
D

Dale Howard [MVP]

AsheNet --

Refer to the following FAQ's to create Project Server login accounts in
Project Professional 2003:

http://www.projectserverexperts.com...edgeBase/CreateAdministratorLoginAccount.aspx

http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/CreatePMLoginAccount.aspx

Both you and your project managers need to create login accounts in Project
Professional 2003 before any of you can creating, saving, and publishing
projects. Regarding documentation for Project Server 2003, refer to the
following links for our company's books on how to set up and administer
Project Server 2003, and how to use it from the project manager's
perspective:

http://www.amazon.com/Administering...=sr_1_2?ie=UTF8&s=books&qid=1205192403&sr=8-2

http://www.amazon.com/Managing-Ente...r_1_17?ie=UTF8&s=books&qid=1205192677&sr=8-17

Hope this helps.
 
A

AsheNet

We will definitely get the books if we end up using the software. My job is
to get it working first. Then since we are going to be running many many
projects, we will definitely need the books.

I am getting closer and learning more.

Sharepoint is really confusing for me. (My background is lacking in the web
department)
In Project Web Access - there is a section "Manage Windows Sharepoint
Services" and it has a few things to check. My sharepoint admin site comes up
just fine, but then it says I should have a top level site at
http://servername/site or /sites
I remember this section of the setup "Extend and Create a content database".
I thought I did it all correct, but I am looking in IIS and there is no
folder named "site" or "sites" and therefore the top level site does not come
up as well as the Public Documents Site.
So I went into Sharepoint admin a looked at the section to create a top
level site, but the only option I have is to add another directory under
http://servername/sites/ - basically saying that the /sites directory
already exists? Or to add a top level site under root.

Then besides all this, after doing the steps you mentioned to create Project
Server Login accounts (which successfully connects to my ProjectServer
through the internet) - then I get the dreaded error:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

I noticed this was pretty common after doing some google searches. I saw the
info about the Cliconfg.exe utility (I set tcp/ip for sql on server and
client PC) and another piece about setting the sql server name to be the IP
address (which in my case doesn't make much sense since I am already
connecting through the internet and can't resolve the private server name or
route to the private IP, I am connecting through a firewall in front of my
server which has ports 80, 443, and 1433 open and forwarded to the Project
Server)

Any ideas on what I can do next. It's almost 3 am, I am going to take a break.

--
Matt at AsheNet
Asheville, NC


Dale Howard said:
AsheNet --

Refer to the following FAQ's to create Project Server login accounts in
Project Professional 2003:

http://www.projectserverexperts.com...edgeBase/CreateAdministratorLoginAccount.aspx

http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/CreatePMLoginAccount.aspx

Both you and your project managers need to create login accounts in Project
Professional 2003 before any of you can creating, saving, and publishing
projects. Regarding documentation for Project Server 2003, refer to the
following links for our company's books on how to set up and administer
Project Server 2003, and how to use it from the project manager's
perspective:

http://www.amazon.com/Administering...=sr_1_2?ie=UTF8&s=books&qid=1205192403&sr=8-2

http://www.amazon.com/Managing-Ente...r_1_17?ie=UTF8&s=books&qid=1205192677&sr=8-17

Hope this helps.
 
D

Dale Howard [MVP]

AsheNet --

I'm not a WSS specialist. I would recommend that you repost this message
about WSS to allow our WSS experts to take a stab at it. Hope this helps.




AsheNet said:
We will definitely get the books if we end up using the software. My job
is
to get it working first. Then since we are going to be running many many
projects, we will definitely need the books.

I am getting closer and learning more.

Sharepoint is really confusing for me. (My background is lacking in the
web
department)
In Project Web Access - there is a section "Manage Windows Sharepoint
Services" and it has a few things to check. My sharepoint admin site comes
up
just fine, but then it says I should have a top level site at
http://servername/site or /sites
I remember this section of the setup "Extend and Create a content
database".
I thought I did it all correct, but I am looking in IIS and there is no
folder named "site" or "sites" and therefore the top level site does not
come
up as well as the Public Documents Site.
So I went into Sharepoint admin a looked at the section to create a top
level site, but the only option I have is to add another directory under
http://servername/sites/ - basically saying that the /sites directory
already exists? Or to add a top level site under root.

Then besides all this, after doing the steps you mentioned to create
Project
Server Login accounts (which successfully connects to my ProjectServer
through the internet) - then I get the dreaded error:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

I noticed this was pretty common after doing some google searches. I saw
the
info about the Cliconfg.exe utility (I set tcp/ip for sql on server and
client PC) and another piece about setting the sql server name to be the
IP
address (which in my case doesn't make much sense since I am already
connecting through the internet and can't resolve the private server name
or
route to the private IP, I am connecting through a firewall in front of my
server which has ports 80, 443, and 1433 open and forwarded to the Project
Server)

Any ideas on what I can do next. It's almost 3 am, I am going to take a
break.
 
N

Nico Oosthuysen

Hi,

Just some terminology - you seem quite clued up so im sure if you just have
some hints you can be on your way...

A Virtual Server can be extended with sharepoint, but that in itself does
not create any sites inside the Virtual Server. When you extend a Virtual
Server, you normally create a Content DB - this database contains all of the
content in that Virtual Server (Sites, and the stuff inside the sites).
A top level site is also called a Site Collection. Site Collection can
contains subsites - somtimes called Subwebs.

When you want to integrate WSS to Project Server ,you need to configure the
WSS installation with some special Project Server related files
(specifically, files that is needed for a special type of Site in WSS,
called a Project Workspace). This is done by running the WSSWIZ.EXE
utility on the WSS installation - this utility also creates a Top Level Site
in the WSS Virtual Server that will be used by your Project Server
installation. This site is called the Public documents site, and is the
second URL that is required from you on the SharePoint Connection page in
PWA.

Hope this helps...

AsheNet said:
We will definitely get the books if we end up using the software. My job
is
to get it working first. Then since we are going to be running many many
projects, we will definitely need the books.

I am getting closer and learning more.

Sharepoint is really confusing for me. (My background is lacking in the
web
department)
In Project Web Access - there is a section "Manage Windows Sharepoint
Services" and it has a few things to check. My sharepoint admin site comes
up
just fine, but then it says I should have a top level site at
http://servername/site or /sites
I remember this section of the setup "Extend and Create a content
database".
I thought I did it all correct, but I am looking in IIS and there is no
folder named "site" or "sites" and therefore the top level site does not
come
up as well as the Public Documents Site.
So I went into Sharepoint admin a looked at the section to create a top
level site, but the only option I have is to add another directory under
http://servername/sites/ - basically saying that the /sites directory
already exists? Or to add a top level site under root.

Then besides all this, after doing the steps you mentioned to create
Project
Server Login accounts (which successfully connects to my ProjectServer
through the internet) - then I get the dreaded error:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

I noticed this was pretty common after doing some google searches. I saw
the
info about the Cliconfg.exe utility (I set tcp/ip for sql on server and
client PC) and another piece about setting the sql server name to be the
IP
address (which in my case doesn't make much sense since I am already
connecting through the internet and can't resolve the private server name
or
route to the private IP, I am connecting through a firewall in front of my
server which has ports 80, 443, and 1433 open and forwarded to the Project
Server)

Any ideas on what I can do next. It's almost 3 am, I am going to take a
break.
 
A

AsheNet

OK - I am getting somewhere. I can now connect to the Project Server from MS
Project Pro 2003 client. Only on the local network. I will just use it
locally for now.
We were doing some testing and I made a project on the client side and then
published it to the server
Then I went to the server and Chose to "Check in" the project
Now I can't work on the project anymore or publish updates until I "check
out" the project
BUT - I cannot find where I can "check out" the project. Help file says
"check out" is done by opening the project for editing - but I can't find
where to do that either

Guidance, anyone?

Looks like we will need a book on how to use Project client with Project
server.
We have existing projects on the client side that we want to import into the
enterprise scenario.
I don't want to "check in" anything ever again though. Can't get it checked
back out....

Thanks

Matt


--
Matt at AsheNet
Asheville, NC


Nico Oosthuysen said:
Hi,

Just some terminology - you seem quite clued up so im sure if you just have
some hints you can be on your way...

A Virtual Server can be extended with sharepoint, but that in itself does
not create any sites inside the Virtual Server. When you extend a Virtual
Server, you normally create a Content DB - this database contains all of the
content in that Virtual Server (Sites, and the stuff inside the sites).
A top level site is also called a Site Collection. Site Collection can
contains subsites - somtimes called Subwebs.

When you want to integrate WSS to Project Server ,you need to configure the
WSS installation with some special Project Server related files
(specifically, files that is needed for a special type of Site in WSS,
called a Project Workspace). This is done by running the WSSWIZ.EXE
utility on the WSS installation - this utility also creates a Top Level Site
in the WSS Virtual Server that will be used by your Project Server
installation. This site is called the Public documents site, and is the
second URL that is required from you on the SharePoint Connection page in
PWA.

Hope this helps...

AsheNet said:
We will definitely get the books if we end up using the software. My job
is
to get it working first. Then since we are going to be running many many
projects, we will definitely need the books.

I am getting closer and learning more.

Sharepoint is really confusing for me. (My background is lacking in the
web
department)
In Project Web Access - there is a section "Manage Windows Sharepoint
Services" and it has a few things to check. My sharepoint admin site comes
up
just fine, but then it says I should have a top level site at
http://servername/site or /sites
I remember this section of the setup "Extend and Create a content
database".
I thought I did it all correct, but I am looking in IIS and there is no
folder named "site" or "sites" and therefore the top level site does not
come
up as well as the Public Documents Site.
So I went into Sharepoint admin a looked at the section to create a top
level site, but the only option I have is to add another directory under
http://servername/sites/ - basically saying that the /sites directory
already exists? Or to add a top level site under root.

Then besides all this, after doing the steps you mentioned to create
Project
Server Login accounts (which successfully connects to my ProjectServer
through the internet) - then I get the dreaded error:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

I noticed this was pretty common after doing some google searches. I saw
the
info about the Cliconfg.exe utility (I set tcp/ip for sql on server and
client PC) and another piece about setting the sql server name to be the
IP
address (which in my case doesn't make much sense since I am already
connecting through the internet and can't resolve the private server name
or
route to the private IP, I am connecting through a firewall in front of my
server which has ports 80, 443, and 1433 open and forwarded to the Project
Server)

Any ideas on what I can do next. It's almost 3 am, I am going to take a
break.

--
Matt at AsheNet
Asheville, NC


Dale Howard said:
AsheNet --

Refer to the following FAQ's to create Project Server login accounts in
Project Professional 2003:

http://www.projectserverexperts.com...edgeBase/CreateAdministratorLoginAccount.aspx

http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/CreatePMLoginAccount.aspx

Both you and your project managers need to create login accounts in
Project
Professional 2003 before any of you can creating, saving, and publishing
projects. Regarding documentation for Project Server 2003, refer to the
following links for our company's books on how to set up and administer
Project Server 2003, and how to use it from the project manager's
perspective:

http://www.amazon.com/Administering...=sr_1_2?ie=UTF8&s=books&qid=1205192403&sr=8-2

http://www.amazon.com/Managing-Ente...r_1_17?ie=UTF8&s=books&qid=1205192677&sr=8-17

Hope this helps.




I am pretty sure I made it through the entire project server 2003 setup.
This
is on a hosted 2003 Server also hosting Exchange 2003. I have a
internet
address setup to reach the server and I can login to the Web Project
Server
with http or https.

I think there are more things to setup.
I see there is no "cube" setup, I have no idea what that is - probably
a
project database.

I have 2 existing project 2003 professional clients on laptops that
have
projects started on their laptops. We were trying to figure out how
they
interact with Project Server from their Laptops. It appears you can't
create
a project on web project server, you have to do that in the client and
then
publish it to the web server? I assume I have to configure something on
the
client side to talk to the remote project server.

But I cannot find any info on just basically getting started. I have
searched quite a bit for several hours today. I mostly just find
articles
on
what project can do for you or some instructions on actually managing
the
projects once they are setup, but I don't see any info on how to just
get
started.

We have made the remote project server web site a trusted site on the
laptops and I also imported the root and web certificates that I had
created
for Exchange (RPC over HTTP)

I basically have no idea where to begin in setting up the clients to
work
with the server. Right now I have 1 laptop in the data center connected
on
the same private network as the server just to make things easier at
first.
though - all clients will work from the internet.

It appears there are several things to check and setup for sharepoint
services when I go to the admin section of the Project Server web site.
but I
don't really understand. I'm sure there are more things to check and
setup
as
well. I did everything in the install. I printed out the 30 page
install
doc
and followed it exactly. It was actually a pretty good document.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top