Test Network Setup Question

[Guest]

I'm trying to setup ProjectServer 2003 on a test network which uses Win
Server 2003 and a domain. I want to install project server on the one and
only server machine I have which is also the domain controler. I want to
install SQL Server on a 2nd machine which is running Win XP.

I'm having trouble installing Project Server.

1) The first way I tried was install the project server db on sql server
first. I created the users and roles as specified in the docs. then I went
to the DC to install project server. in the window where it wants me to
enter the 2 users and passwords (MSProjectServerUser and MSProjectUser) it
says it "The user name and password you entered is not allowed to log on to
the Server 'NameOfXPMachine'. Check that the serer name, login name and
password are valid and try again." I can't seem to get past this part.

2) 2nd way: I created MSProjectServerUser and MSProjectUser as domain
users from the DC machine and then added them both to the ProjectServer
database and then added the appropreate roles to them. I get the same
error.

3) 3rd way: I deleted the database, and then added a user to the windows
domain and also to sql server with admin security and admin createdatabase
roles (as specified by the instruction where the project server install will
create the db). I made it through the entire Project Server wizard OK and
it started to instll everything. It successfuly created the ProjectServer
database on the WinXP machine and it looked like it installed all the
Project Server components. Then at the very end of the install I get a msg
saying that the install ended prematurly and the install failed. then the
install un-did itself so no Project Server components were installed. It
gave me no information about why it ended prematurely and there was no
useful informaiton in any event logs.

Note: in all 3 methods I'm selecting Standard Project Server and not Ent.
Proj Svr. I also select the install later option for Share Point and
Analysis Services and mail.

What can I do to get this installed?

Thanks.

 

[Aaron Tamblyn]

I have completed this using the method in Step 1. Before reinstalling cover
off the following.
a. Make sure the system is cleaned up. Delete the ProjectServer database
and delete the logins you created. Check that IIS is clean and there are not
unnecessary sites, application pools etc.

b. When you install the project server database make sure you complete all
the actions including creating the roles for the connection logins. (Steps 6
to 9 below)

These are the steps I follow from the install guide:
You can create the Project Server database manually by using Microsoft SQL
Serverâ„¢ 2000 scripts provided on the Project Server 2003 CD. Use these
procedures if you do not want the database to be created by the Project
Server Setup program. Note It is recommended that you run the scripts on the
computer on which you are creating the database.
ô€˜ To create the Project Server database
1. In SQL Serverâ„¢ 2000 Enterprise Manager, create a new database for use
with Project Server 2003.
2. In Microsoft Windows® Explorer, navigate to the Support folder on the
Project
Server 2003 CD.
3. In the Support folder, copy the Database folder to a location on your
database server.
4. Open a command prompt window, and then navigate to the Database folder
where
you copied it locally.
5. Run Setupdb.cmd by using the following syntax:
SETUPDB.cmd SQL ServerName DatabaseName UserName Password
NOPAUSE
For example,
Setupdb.cmd PROJSQL2003 ProjectServer sa hello NOPAUSE
Notes
If you omit the UserName and Password parameters, the script will use NT
Authentication.
NOPAUSE is an optional parameter that will cause setupdb.cmd to return to
the command
prompt after completion.
6. Using SQL Server Query Analyzer and connecting as sa, run PSRoles.sql
from within the Project Server database context.
This script creates the two database roles needed by the Project Server
logins:
MSProjectServerRole and MSProjectRole.
7. Create the following two logins by using SQL Server Authentication in the
new
database: MSProjectServerUser and MSProjectUser.
8. Using SQL Server Query Analyzer or Enterprise Manager and connecting as
sa, grant each login access to the Project Server database.
9. Assign the MSProjectServerRole role to the MSProjectServerUser login, and
then
assign the MSProjectRole role to the MSProjectUser login.




c. On the Front End box use Query Analyser to test that you can connect to
the Project Server database

d. On the Front End server do you have any lock down applied. For example
have you locked down the file system. I have had failed installs in the past
due to the customer having file system restrictions.

 

[moondaddy]

Thanks. I have followed these instructions to the T several times. For now
I have installed SQL Server on the window server where I will be installing
Project Server just to I can see the thing succeed. The install succeeded,
but Project Server wont run and you are already responding to that post
above. Once I get past that issue and can see that Project Server will
work, I will come back to this issue and try to get Project Server using SQL
server on the WinXP machine.

 

[John Sitka]

The domain controller is a special case,
It has tighter security policies than other server machines
and is especially difficult to configure multiplex type access accounts
(IUSER, ASPNET, MSProjectServerUser and MSProjectUser) on these machines. Approches...
build a test server as a member server to the domain and have a successful install
then try to accomplish the same thing on the domain controller, or
Reference the Small Business Server comments/threads and documents.
There are other mentions of setup that don't make sense
XP machines as Domain Controllers????

 

[John Sitka]

....XP machines as Domain Controllers????
I reread, you didn't say that...
But what of SQLServer on XP?
Either way you are fighting domain autherntication and policy
and running server services on a workstation.

 

[moondaddy]

I never mentioned anything about an XP machine as a Domain Controler. I
said I was trying to install Project Server on the DC and have it use a sql
server database living on an XP machine. The reason for this is that I'm
short on hardware for setting up the test install.

 

[moondaddy]

Thanks.

--
(e-mail address removed)

...XP machines as Domain Controllers????
I reread, you didn't say that...
But what of SQLServer on XP?
Either way you are fighting domain autherntication and policy
and running server services on a workstation.

 

[John Sitka]

understand the shortness of hardware thing...

the core of the issue is
authentication and policy for the special user accounts(Domain controller)
AND
the fact that SQL server running on XP is for local use only.
This has to do with the network libraries being disabled,
It's a simple switch to throw when installing MSDE DISABLENETWORKPROTOCOLS=0 from the command line.
Other editions probably have workarounds as well.