Article ID: 302677
Article Last Modified on 9/23/2005
APPLIES TO
- Microsoft Commerce Server 2000 Service Pack 1
This article was previously published under Q302677
SYMPTOMS
Microsoft Commerce Server Manager may not display a site if the locale is changed from one language to another.
CAUSE
This problem is caused by changes to resource properties, such as doubles and Booleans.
When a site has a resource that contains a property of type adDouble, the manager fails when it tries to add a number with the incorrect decimal symbol. For example, your site may have a resource named App Default Config. If you look in the ResourceProps table for this resource, you may find an f_AltCurrencyConversionRate that has an i_VarType of 5 (adDouble) and an s_Value of 1,1007. If your site was installed with the French (Canada) locale with a comma (,) decimal symbol, the number appears as follows:
1,1007
When the computer is switched to the English (Canada) locale, the decimal symbol changes to a period (.). This causes an exception to occur.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Commerce Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
297216 INFO: How to Obtain the Latest Commerce Server 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
-------------------------------------------------------------
13-Jun-2001 15:08 1.0.0.1 28,944 Hotfixsetup.exe
06-Jul-2001 21:27 432 Qfehotfix.ini
05-Jul-2001 22:04 126,976 Qfepatch.msp
05-Jul-2001 22:38 7,168 Qfeunpatch.msp
WORKAROUND
To work around this problem, do one of the following:
- Change the decimal symbol setting in Control Panel.
If the problem is with Boolean properties, run the following commands against the MSCS_ADMIN database:
update resourceprops set s_value = 'False' where s_value Like 'Faux' go update resourceprops set s_value = 'True' where s_value Like 'Vrai' Go
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Commerce Server 2000 Service Pack 2.
Keywords: kbbug kbfix kbcommserv2000presp2fix kbqfe kbcommserv2000sp2fix kbhotfixserver KB302677
