Pipeline logging not disabled in production environment (327715)


The information in this article applies to:

  • Microsoft Commerce Server 2000
This article was previously published under Q327715

SYMPTOMS

Pipeline logging is not disabled although the Application object variable (MSCSEnv) is set to PRODUCTION in Global.asa.

CAUSE

The InitSitePipelines() function in the Global_siteconf_lib.asp file contains a programming error. The InitSitePipelines() function redimensions MSCSEnv locally, therefore overriding the application level variable, and the test for pipeline logging for development is unsuccessful if the application level variable is set to TRUE.

RESOLUTION

To resolve this problem, use one of the following methods:
  • In the InitSitePipelines() function in Global_siteconf_lib.asp, comment out the following line: 
    Dim MSCSEnv
  • In the InitSitePipelines() function in Global_siteconf_lib.asp, remove the following line: 
    Dim MSCSEnv
  • In the InitSitePipelines() function in Global_siteconf_lib.asp, modify the MSCSEnv test to examine the application level variable (instead of the local level variable): 
    If Application("MSCSEnv") = DEVELOPMENT Then
 dictPipeline.LoggingEnabled = True
 dictPipeline.LogsCycled = True
 ElseIf Application("MSCSEnv") = PRODUCTION Then
 dictPipeline.LoggingEnabled = False
 dictPipeline.LogsCycled = False
 End If

STATUS

Microsoft has confirmed that this is a problem in Commerce Server 2000.

MORE INFORMATION

To resolve this problem, you must modify any site that is based on the Commerce 2000 sample retail site.
Modification Type:MajorLast Reviewed:9/14/2005
Keywords:kbbug kbfix KB327715
©2004 Microsoft Corporation. All rights reserved.