Project Server 2003 on Win2k/SQL2K - wrong locale settings?

From: Mike Leone (mleone_at_contributionship.com)
Date: 04/09/04 

Date: Fri, 9 Apr 2004 10:27:05 -0400

(I realize this is probably more of a MS Project Server question, but the folks in that group sent me here, because they never heard of the error I'm getting, and they think it might be SQL related)

Anybody using MS Project Server 2003? I'm trying to install it on a Win2K server that's running SQL2K SP3a(a supported configuration, according to MS). However, when I go to install MS Project Server and tell it the name of the SQL2K instance to use, it says:

"The Windows locale settings on this computer prohibit the creation of the Project Server database. Either change the locale settings on this computer to support code page 850 and use setup to create a database, or manually create the database outside of setup with a collation that supports code page 1252 and then use setup to connect to it."

The Windows locale settings (in Win2K) are set in CONTROL PANEL, REGIONAL SETTINGS. I have chosen ENGLISH (UNITED STATES) as my locale , and chosen WESTERN EUROPE AND UNITED STATES as my language settings. I have verified that I have SET DEFAULT and chosen ENGLISH (UNITED STATES). So I have no idea what causes this error, or what it means. According to what I can see, my locale is set correctly. And from what I can find by googling, code page 850 is supported by a US locale.

I've tried manually creating a database outside of setup, as per the Project Server Installation Guide, but it says nothing about which collation value to choose. So I chose the only collation value that had an "850" in its name (which is the same as my server default, of course - SQL-Latin1_General_CP850_BIN). And when trying to connect to this database during installation (as opposed to letting the installation routine create the DB), it still says that

"The Windows locale settings prohibit a connection to this database. Change the locale settings to support code page 850 before attemping to connect to <my database name>".

MS KB searches are fruitless, google is fruitless, mailing lists have been fruitless, web forums have been fruitless, newsgroups haven't been of help (so far). Anyone have any clue as to what is going wrong? And how to fix it?

Relevant Pages

  • Re: Project Server 2003 on Win2k/SQL2K - wrong locale settings?
    ... (I realize this is probably more of a MS Project Server question, but the folks in that group sent me here, because they never heard of the error I'm getting, and they think it might be SQL related) ... MS KB searches are fruitless, google is fruitless, mailing lists have been fruitless, web forums have been fruitless, newsgroups haven't been of help. ... And how to fix it? ...
    (microsoft.public.sqlserver.setup)
  • Re: Documentation suggestions
    ... Aahz wrote: ... I mention this point only because sometimes debates about process are fruitless, and having _both_ would fix even more problems than just having a good process. ...
    (comp.lang.python)