Microsoft Project Professional client cannot connect to the Microsoft Project Server (328958)
The information in this article applies to:
- Microsoft Project Server 2002
This article was previously published under Q328958 Important This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry SYMPTOMSA Microsoft Project Professional client computer may not
successfully connect to a Microsoft Project Server 2002-based computer that has
a different language setting. For example, an English Project Professional
client that is using Thai regional system settings may not connect to a Project
Server 2002-based computer that is also using Thai regional system
settings.CAUSE This problem may occur if either of the following
conditions exists:
- The Project Professional client computer is using a locale
setting that is different from the locale setting of the Project Server-based
computer.
For example, if a Japanese Project Professional client with
Japanese locale settings tries to connect to a Japanese Project Server computer
that is using English locale settings. - The Project Professional client that was used to generate
the Global Enterprise template is in a different language locale than the
Project Server.
For example, an English Project Professional client
that is using Thai local settings cannot connect to an English Project
Server-based computer that is using Thai locale settings because the Global
Template was created by using English settings.
RESOLUTIONTo resolve this problem, use one of the following
methods. Method 1: Change the
locale setting of the Project Professional clientWhen you suspect that the Project Professional client computer is
using a locale setting that is different from the locale setting of the Project
Server-based computer, change the locale setting of the Project Professional
client to match the locale setting of the server. For information
about how to identify the Codepage IDs for your locale, see the "International
issues" section of the Microsoft Project Server Readme. For additional
information, click the following article number to view the article in the
Microsoft Knowledge Base: 323018
PRJ2002: Where to Find the Readme Files That Are Included with Microsoft Project and Microsoft Project Server
Method 2: Create a registry
key to force the codepages to matchWhen you suspect that the Project Professional client that was
used to generate the Global Enterprise template is in a different language
locale than the Project Server, create a registry key to force the codepages to
match. Warning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk. To
create a registry key to force the codepages to match, follow these steps:
- Click Start, point to
Programs, point to Accessories, and then
click Notepad.
- Type the following text in the Notepad document:
REGEDIT4
[HKEY_CURRENT_USER\Software\Microsoft\Office\MS Project\Codepages] - On the next blank line, repeat the registry key from step
2, at the end of the key add a backslash character (\) followed by the ID of
the codepage that is used on your computer.
The following example
uses the Turkish codepage IDs:[HKEY_CURRENT_USER\Software\Microsoft\Office\MS
Project\Codepages\1254] - On the next blank line, repeat the registry key from step
2, at the end of the key add a backslash character (\) followed by the ID of
the codepage that is used on the Project Server-based computer.
In the
following example, the Project Server-based computer uses the English codepage:[HKEY_CURRENT_USER\Software\Microsoft\Office\MS
Project\Codepages\1254\1252] - Save the file as Projectproid.reg.
The contents
of the example Projectproid.reg file must appear as follows:REGEDIT4
[HKEY_CURRENT_USER\Software\Microsoft\Office\MS Project\Codepages]
[HKEY_CURRENT_USER\Software\Microsoft\Office\MS Project\Codepages\1254]
[HKEY_CURRENT_USER\Software\Microsoft\Office\MS Project\Codepages\1254\1252]
- Double-click the Projectproid.reg file, and
then wait for the process to write to the registry.
With this registry solution, the Project Professional client can
connect to the server, however full functionality in Project Server is not
supported in this configuration. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section of this article.For additional information about the Codepage property,
visit the following Microsoft Web site.
Modification Type: | Minor | Last Reviewed: | 6/6/2005 |
---|
Keywords: | kbprb kbbug KB328958 |
---|
|