Problem installing Project Server 2003

[Ray Johnson]

I'm getting a failure when attempting to install Project Server 2003. After
doing the configurations steps it appears that nearly every step of the
installation occurs. I even see lines at the end about registering the
product, etc. (The status lines wiz by so I don't know the exact last
step.)

Then all of a sudden it starts rolling back the installation. When finished
rolling back it pops up a dialog box saying:

"The installation ended prematurely because of an error."

The only option is to hit OK and the box goes away and it's done. What the
heck kind of error message is that? I've attempted to adjust every sinle
setting and nothing is making a difference.

A couple of questions:
1) Has anyone seen this before? Were you able to find the problem or a work
around?
2) Is there any install log somwhere that I can look at to determine what
went wrong?
3) Why hasn't MS made installing Project Server any easier to install? What
a pain!

Ray

 

[Ray Johnson]

One additional bit of info. The Application log does have a info message
stating:
"Product: Microsoft Office Project Server 2003 -- Installation operation
failed."

Source: MsiInstaller
EventID: 11708

Clicking the lick to MS support states they don't have any additional info
on the event...

I will say we did get Project Server to install at one point (but they put
it in the wrong place etc.) The problems started after we removed the
installation and attempted to reinstall.

Ray

 

[Vadim Bogdanov]

Ray,

1. check IIS has default web site configured.
2. try to copy installation files from CD to your disk drive and run from
disk drive.

HTH,
Vadim

 

[Ray Johnson]

Already have done both.

I think it does have something to do with IIS though. It's hard to tell but
it says something about IIS right before it starts the roll back.
Unfortunantly, it's only there for an instant and I can't read what it says.

There has got to be a way to get an instal log - isn't there?

Ray

 

[Kevin Flanagan]

With Project Server 2002 this was caused because of
insufficient privileges to creat the Project Server
database on the SQL server. Certain accounts must be
created on the SQL box before you attempt to install or
it will roll back. Did you chack the log on your SQL box?

Kevin

 

[Ray Johnson]

The SQL log looked ok. In fact, the Db was created with all tables, sps,
etc. as well as the two Logins needed by Project server. So I don't think
it was a problem with SQL server. (Thank's for the idea though!)

I'd really like to know if there is any sort of instal log. Is there no one
from MS on this list that can answer if there is an install log tucked away
somewhere?

*rant*
While some MS apps are very easy to install. (Office is a breeze.) Many of
the server type products are a real pain. MS Project in my experience is a
real pain. It's amazing how MS will talk about TCO when you can pound your
head for days because of install issues. Sure the nice GUI installer is
nice - but it's a real pain when you have several GUI installers that all
work different and no installation logs or information about what went wrong
in the GUI installer encounters a failure. Then what - I'm supposed to use
one of my MSDN support calls to find out what went wrong? In the mean time
we have decided to wipe the box and start over - that doesn't help TCO...
*end rant*

Ray

 

[Gary L. Chefetz]

Ray:

Because Microsoft's desktop applications are so easy to install, people have
a false expectation that server software will be just as easy. Microsoft
went out of its way to warn people about this in the Project Server
documentation. It's a shame that people either don't read or pay attention
to the documentation.

--

Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.

 

[brandon thornton]

The problem is likely the same one I am having... Are you
getting to the message "Adding WSS Excluded Paths"?

You can turn on logging for the installation by going to
the prjsrvr directory and running

svrsetup /lv* "c:\yourloggile.txt"

I think the name setup filename and path are correct.
Verify these, however the parameters are correct.

Brandon

 

[Ray Johnson]

What the **** kind of useless comment is that?

We certainly read the MS Project install documentation and it is NOT very
good.

Worse, there is a problem with the installer. Our admin at first did make
some mistakes in the install. (He forgot to set up SharePoint to use SQL
server and put the project server admin pages in the wrong web.) We
uninstalled SharePoint services and Project server and then reinstalled them
following all directions. We then were completely stuck with the error
already discribed in this thread. The installer provides NO way of
determing what went wrong.

We have fixed the problem by completely wiping the server and reinstalling
everything with the EXACT same steps we did before. Everything worked fine
this time. So clearly it's not just reading the docs - you also better not
get anything wrong because doing so will mean you need to start over from
scratch.

Your lame comment not withstanding, MS can and should do better with the
install stuff for Project. I'm not saying it needs to be falling over easy
and good planning and an understanding of the options you'll face is always
important, but it should at least give you a way to debug what is going on.

Ray

 

[Gary L. Chefetz]

Ray:

This is a peer-to-peer forum. Most of us regulars are here because we like
the product. The bottom line is that most people don't get this right first
time out when they try it on their own, so don't let it get you so riled.
Sometimes people don't get it right after10 tries. If I get lazy and don't
pull out my cheat sheet and log, there's a good chance I'll miss a step
despite the number of installations I've done.

Your expections need adjusting if you think that the software should forgive
a missed step. I'm surprised that your Admin didn't warn you of the risks of
major uninstalls and reinstalls, of course, you've already established that
he makes mistakes. Uninstall/reinstalls always have a higher liklihood of
failure and that's neither something introduced with Project Server nor
unique to Microsoft. An extra hour or so to reinstall the OS weighed against
the frustration alone makes it a jolly good what the hey.

--

Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.

 

[Robert]

Same Problem with my install. Thought it was IIS, but
the very next action is either ' configuring project DB '
or ' connecting to project db '. Moves to fast to see
clearly. And, as Ray states, this is a reinstall after
learning that to use STS with Project 2003, requires
specific config.

IF this is a user id access problem, does anyone know
what user id is to be accessing the db at this step?