Pcc:
Microsoft recommends and expects you to engage professional services to
assist you with installation and configuration. These are fairly well stated
in Microsoft's marketing and documentation. No, configuring and managing an
EPM solution is nowhere near as easy as your installation experience. In
conclusion, it's safe to say that you shouldn't recommend the solution to
management based on "easy."
You're assuming that you have the same problem as another poster, but it's
difficult to take me-too posts seriously, because comparing symptoms is
rarely a good way to make a diagnosis. Post more detail on the actual steps
you're taking, and have taken, and we'll try to get you over the issue.
--
Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com
-
I'm having the exact same problem. I'm not sure how MS expects me to
recommend this very expensive solution to my upper management team when I
can't even get a test environment working. Frankly I think it's
rediculous
that the integration of these products is so picky. That being said....is
management and maintenance of a Project Server setup as complex and time
consuming as the initial setup?
If anyone has a clear step by step for getting SQL 2000, Windows
SharePoint
& Project Server 2003 working properly I would love to see it. For
whatever
reason MS must have missed some important information in their
Installation
Guides because I have looked through all of them and can not resolve this
issue.
:
Sounds like your stuck on the install, here's some peripheral info that
may
or may not help...the MSFT response
You receive a "Cannot connect to the configuration database" error
message
when you connect to your Windows SharePoint Services Web site
http://support.microsoft.com/kb/823287
We used the "configurable" option & selected a domain account that had
permission on both the SQL server hosting the WSS tables & the WSS
server.
The "NT AUTHORITY\NETWORK SERVICE (....)" just didn't have the
horsepower.
-Johnnie
PS the installation guide(s) are also good sources to insure you have
ALL
possibilities/problems eliminated.
Thanx for your reply Johnnie, but I'm afraid it didn't help... I'm
still
stuck in the "Set configuration database server" page. In what form
should
I
enter the name of the Database server? Just the hostname (projecttest
in
my
setup)? No back slashes? BTW both SharePoint and Project Server reside
on
the same server.
The strangest thing is that when I installed Project Server, I was
asked
to
enter the name of the database for Project and that was no problem at
all.
As a matter of fact it's running at this very moment. So I if anyone
has
any
idea to get the sharepoint configuration database running....TIA
"Johnnie Rotten @hotmail.com>" <jay_rhoten<removethis> wrote in
message
The WSS -> SQL configuration is somewhat tricky. During the
administrative
virtual server installation you're asked for an security account.
The
doco
I've perused says that a domain account with rights to both the
front-end
web server & back-end data base server is recommended. The account
must
have create database rights on the SQL server, a member of Security
Admin,
Process Admin, & Database Creators roles.
Sounds like you're doing a remotesql deployment...so, you may want to
review
the accounts you've created. I downloaded the Project Server 2003
install
guide and the medium install guide, both have some short comings
concerning
WSS. They did help me resolve the problems I had during the install.
Also, the "Administrators Guide for Windows Sharepoint Services" ->
Deployment was a good cross reference for me.
http://www.microsoft.com/downloads/...f6-8224-4b19-a6a4-3e33fa13d230&DisplayLang=en
-Johnnie
I am trying to install Project Server 2003 for evaluation purposes
for
the
company I work for. All worked fine untill I came across the next
problem:
In the "Set Configuration Database Server" screen I entered the
name of
the
"Database Server", I entered the "SQL Server database name",
specified
"Use
Windows Authentication" and left the "Users already have domain
accounts"
untouched. After pressing enter, I keep receiving the next error
message:
"[DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist
or
access
denied. (Error code: 17)."
I added "NT AUTHORITY\NETWORK SERVICE (....)" to the local
Administrators
group, with no result. Hope someone can help...
Grtz, Erwin