SQL 2000 Standard or Enterprise?

[Tommy Nguyen]

What version of SQL 2000, Standard or Enterprise, am I required to have in
order to use enterprise features in Project Server? The reason why I am
asking is because I am having trouble connecting Project Pro to Project
Server. I understand that in order to connect Project Pro to Project Server
I must enable enterprise features in Project Server. I do have that
enabled. From what I could find on MS' websites, they do not clarify what
version of SQL is needed to do this. Any help is much appreciated.

http://support.microsoft.com/default.aspx?scid=kb;en-us;823433&Product=OffPr2003


Tommy Nguyen

 

[Earl Lewis]

Tommy,

To the best of my knowledge project server requires SQL Enterprise for the
Analysis services. If you don't want to do cube analysis I believe you can
use SQL Standard edition with no problem. Also, don't confuse the enterprise
features of project server with the enterprise version of SQL server.
They're not really related.

Either way (standar or enterprise version) project pro should be able to
connect to the SQL server if your installation is done properly and
completely. Properly and completely are the key words here.

This can be a sticky problem with project server/pro. Post more about the
specific errors or problems you're having and someone will almost certainly
be able to help.

Earl

 

[Tommy Nguyen]

Earl,

Thanks for the quick response. Actaully I have posted more information on
my particular issue and did not receive any help from this newsgroup.
Actually my post is still listed. After extensive troubleshooting, I have
come to this question on the version of SQL. I will take your word for it
that Project Pro will connect to Project Server despite the version of SQL.
If so than I will have to continue troubleshooting my connection issues.
Thanks again!

Tommy Nguyen

 

[Ryan Miller]

Tommy

You can use either version of SQL with Project Server/Pro. As was said, in order to use analysis services you need the enterprise edition

One thing to keep in mind is that if you plan to use WSS, you MUST use the enterprise edition. WSS is not designed to be used with MSDE and eventually you may experience issues including the inability to access any information or sites on your WSS server as was the case in our environment

Ryan

 

[Earl Lewis]

Tommy,

For some reason my newsreader didn't download your previous posts but I
found them on Google Groups.

In my expereince the "Test Connection" button in project pro simply tests to
see if port 80 responds at the stated URL. If it does that's good but it's
far from the end of the story.

It sounds like you're having either database connectivity problems or name
resolution problems.

One thing you can try is setting up an ODBC connection from your workstation
to the target project server db. You can do the test using either the
MSProjectUser credentials or setup a separate account on the server and the
database for the testing. If you have questions about how to do that let me
know. If you can connect to the database with the ODBC connection you should
be able to get to it via project pro.

For the name resolution you can try specifying the IP address of the machine
rather than the machine name. Microsoft in their infinite wizdumb seems to
expect that you're going to be able to resolve a windoze machine name
without any other qualifiers. Well, you may be able to if your on a pure
Windows network. Then again you may not. There are quite a few things I've
done to get around this so let me know if the straight IP address works or
not.

Earl

 

[Tommy Nguyen]

Earl,

Your help so far is much appreciated. I attempted to make an ODBC
connection from my workstation without success using both the MSProjectUser
and sa accounts. I know I have database connectivity problems that is why I
asked about the SQL version. I am searcing the M$ KB right now. Any ideas?

Tommy

 

[Tommy Nguyen]

I am getting the exact same error as stated in KB 818047. Performed their
solution without success.

 

[Earl Lewis]

Tommy,

Did you try using the project server machine IP address on the project
server settings from project pro? You can also use the machine IP address
for the SQL server to try to get around name resolution problems.

Another thing to look at is to see if port 1433 (the standard SQL server
port) is being blocked on your network. When the SQL slammer came along last
year lots of network admins blocked this port traffic on their networks.

If you want to try another test open up the network configuration utility as
described in the KB818047 and change the port number that the server listens
on. Then open the client network utility on your workstation and set it to
the same port number. Make sure the server and the client are both using
TCP/IP and then try connecting again. If you connect successfully your
network guys are blocking 1433 traffic.

Earl

 

[Tommy Nguyen]

Okay. As you suggested, I did try using the IP address in Project Pro and
to my surprise it gave me a different error as compared to using the server
name. The error is:

"Unexpected server response. Project server has returned an unexpected
response."

Upon viewing the server response in a browser it states that "You are not
authorized to view this page......."

Also I did change the port settings on both server and client. I am still
having the same issues, no connection. Any other suggestions?

 

[Earl Lewis]

Tommy,

So when you use the server name to setup the project server connection in
project pro and test the connection it works. When you use the IP address
and test, it fails? Either way, when you start project pro and try to
connect it fails?

How far back in the installation have you gone to try to resolve this?
Describe as many of the things that you've tried as you can - in some detail
please. I know this is painful - I've been there - done that. The good news
is this problem is resolvable - even though it doesn't seem like it right
now.

Here's a basic checklist:
IIS is started and permissions are configured according to installation
instructions.
SQL server is started and project server accounts are configured according
to installation instructions.
Project server accounts have been created and setup with appropriate
authentication method selected for each.
If you're using windoze authentication - active directory accounts have been
created for the project server accounts and you know the AD login name and
passwords.
You can login to the project web access with one of the credential sets your
trying to use for project pro.
You can "see" the project server machine (and the SQL server if it's
separate) on the network.

I know you've probably been over each of these things 10 times by now but it
never hurts to ask.

Earl

 

[Tommy Nguyen]

First off, I really do appreciate the help thus far.

Yes, to your entire first paragraph.

I've gone through the entire setup steps several times now. I've even
reinstalled Project Server. I've searched the M$ KB and found articles that
may apply to my issue and applied their fixes: KB328958, KB818047. As you
know I've tried your suggestions. All attempts lead back to the same
result.

Yes, I have confirmed the settings for the checklist you provided.

Steps that I am taking right now: I am doing a fresh install of Windows
Server 2003 Standard, SQL 2000 Server Standard, WSS, and Project Server 2003
on a separate machine in attempt to connect using Project Professional 2003.
As a reminder, my current setup of Project Server was on a SBS 2003 server.
All Project Server setup instructions that I have are for Windows Server
2003 and thats what I am trying to attempt now. I will let you know how
that goes.

Tommy Nguyen

 

[Earl Lewis]

Tommy,

I know how frustrating this is - it took me a month or more to get to the
bottom of my connection problems when I had them. So your welcome for the
help but it doesn't seem to be helping.

Also, I know nothing about SBS and how it differs from W2K3 so sorry I can't
offer anything on that front.

OK, here's one last thing that I can think of that you might want to try. Go
to your network connections properties on your workstation and select the IP
protocol item from the list of services used for that connection. Select the
properties button and then click the Advanced button of that window.

At this point your looking at the advanced properties of the TCP/IP protocol
and you should see a DNS tab in that window. At the bottom of the DNS tab
there is an option button that lets you append suffixes to unqualified
machine names. Click the radio button that says "Append these DNS suffixes
(in order)" Add your domain into this list. Don't include the project server
machine name, just the domain name that DNS should tack on to the machine
name to be able to locate the project server. Click the OK buttons until
your out of all the windows and give the project pro connection a try. Let
me know if it helps.

Earl

 

[Gary L. Chefetz [MVP]]

Tommy:

Which version of SBS are you using. I'm not 100% certain, but I think you
need the Premium edition to deploy Project Server. Beyond that, the
installation routine is slightly different the standard instructions for
WIN2K3.

BTW, you do not need SQL Enterprise to use analysis features.

 

[Tommy Nguyen]

Gary,

I have SBS 2003 Premium fully installed. I am having connection issues
using Project Professional 2003 to my Project Server 2003 that is installed
on SBS 2003 Premium. Am I able to use Analysis Services that came with SQL
2000 Standard (SBS 2003 Premium)? So what you are saying is that there is a
difference in Analysis Services that came with SQL Standard and Enterprise.

Tommy Nguyen

 

[Gary L. Chefetz [MVP]]

Tommy:

For your purpose there's no difference between SQL Std and Enterprise.
You'll have all the standard functionality in Project Server using either
edition. As for your connections problems, what are you connecting from?
What is the OS, SP level and MDAC level on the client you're connecting
from?