White Paper - Everest Advanced Edition in Windows … · Web viewClick on Add/Remove Windows...

Introduction.............................................................................................2Prerequisites...........................................................................................2

of 13 Installing GreeneStep Enterprise on Windows Server 2003

GreeneStep Enterprise v6.0.0

White Paper – GreeneStep Enterprise on Windows Server 2003

GreeneStep Technologies

AbstractThis document discusses a few configuration changes needed to be done in the default setup of Windows Server 2003 operating system components to get GreeneStep Enterprise v6.0.0 working smoothly.

Configurations.........................................................................................2Configuration#1 - Enabling Active Server Pages (ASP) in IIS....................................2Configuration#2 - Enabling parent path in IIS..........................................................2Configuration#3 - Enabling Network DTC access.....................................................2Configuration#4 - Enabling Network COM+ access..................................................2

Common Technical Issues.........................................................................2Issue#1 - Unable to save from most of the GreeneStep Enterprise profiles.............2Issue#2 - HTTP 500 - Internal server error shown from some of the pages in E-Commerce................................................................................................................2Issue#3 - Shop Administrator fails to register a shop...............................................2

References...............................................................................................2


IntroductionThis document discusses a few configuration changes that are needed in the default setup of Windows Server 2003 operating system components to get GreeneStep Enterprise working smoothly. Apart from this, this document addresses the issues that may be encountered when GreeneStep Enterprise is deployed on Windows Server 2003.

PrerequisitesGreeneStep Enterprise 6.0.0Windows Server 2003(Enterprise, Standard or Web edition)

ConfigurationsThe following changes in default configurations are required to be carried out in the server to enable GreeneStep Enterprise v6.0.0 to work smoothly on Windows Server 2003.

Configuration#1 - Enabling Active Server Pages (ASP) in IIS If the server is being used as web server for GreeneStep Enterprise E-Commerce, ASP needs to be enabled in IIS. By default, apart from the Web edition of Windows Server 2003, ASP will be disabled in IIS. To enable ASP,

Open Add or Remove Programs from Control Panel Click on Add/Remove Windows Components Select Application Server and click on the Details button Select Internet Information Server and click on the Details button Select World Wide Web Service and click on the Details button To Enable ASP, make sure that Active Server pages option is checked Click OK in all the open dialogs to get the change into effect

Once the installation is over, IIS is ready to process ASP scripts. (Refer Figure 1 for details)


Figure 1: Enabling Active Server Pages on the Windows 2003 server

Configuration#2 - Enabling parent path in IIS In IIS 6.0, the setting for referencing the parent path is disabled. In order to allow using ../ to reference the parent, the settings must be changed as follows:

Bring up Internet Information Services management application Right click on the web site (where e-commerce shop is installed) and

choose properties In the “Home Directory” tab, click on the “Configuration” button In the resultant dialog make sure “Enable Parent paths” check box is

checked. Click OK in both the dialogs to get the change into effect.

Refer to Figure 2 and Figure 3 below.


Figure2: Click on the Configuration Button, which will bring up the following screen.


Figure 3: Make sure the Enable Parent Paths box is checked.


Configuration#3 - Enabling Network DTC access

By default, the Microsoft Distributed Transaction Coordinator (MSDTC) is not configured for network access on Windows Server 2003. MSDTC needs to be enabled for network access in GreeneStep Application and Data servers.

To configure MS DTC for network access:

Go to Control Panel and open Component Services from the Administrative Tools folder.

In the Component Services Wizard, expand Component Services and double-click Computers.

Right-click My Computer and click Properties.

Select the MS DTC tab.

Click Security Configuration.

In the Security Configuration dialog, select the Network DTC Access box.

Under Network DTC Access, click Network Transactions.

Ensure that the DTC Logon Account is set to NT Authority\NetworkService.

Click OK.

Click Yes to continue.

Click OK in the DTC Console Message dialog.

Click OK in the System Properties dialog.

Refer to Figure 4 below.


Figure 4: Enabling Network DTC


Configuration#4 - Enabling Network COM+ access

By default, except for the Web edition of Windows Server 2003, network COM+ access is disabled. Network COM+ access has to be enabled in the server to allow GreeneStep Enterprise server to be accessed from remote systems.

To enable Network COM+:

Open Add or Remove Programs from Control Panel Click on Add/Remove Windows Components Select Application Server and click on the Details button Make sure that “Enable network COM+ access” check box is checked Click OK in both the dialogs to get the change into effect

Refer to the Figure 5 below.

Figure 5: Enabling Network COM+


The users using GreeneStep Enterprise needs to be added to the Distributed COM User Group for proper authentication.

Go to My Computer Right click and select Manage Click on Groups under Local Users and Group Double click on Distributed COM Users Add the required users

Figure 6: Adding users to the Distributed COM Group


Common Technical IssuesThis section contains information about common technical issues related to working with GreeneStep Enterprise v6.0.0 on Windows 2003 server.

Issue#1 - Unable to save from most of the GreeneStep Enterprise Profiles

SYMPTOMSSaving of most of the profiles fail with following error message:

Unable to save given Data

And, following error message will appear in svrerr.log file (which is the GreeneStep Enterprise server error log file and can be found in C:\Documents and Settings\All Users\Application Data\Everest\Temp folder)

New transaction cannot enlist in the specified transaction coordinator

The same error may appear in E-Commerce also while creating new customers or creating documents.

CAUSEThis typically happens when Distributed Transaction Coordinator or DTC (which is used by GreeneStep Enterprise to maintain data integrity during save process) on GreeneStep Enterprise application server and GreeneStep Enterprise database server fail to communicate with each other. The common reasons for this to happen are:

1. Network DTC is not enabled2. Application server is not able to reach database server using NETBIOS

name3. Bug with DTC in windows 2003 servers when application and database

servers are in different domains (See [1] under References section below).

4. Firewall exists between application and database server

RESOLUTIONThe following steps can be followed to avoid this error:

1. Network DTC access needs to be enabled in both application and data servers. Please refer to the configurations section (Configuration#3) for details.

2. Install DTC in both application and data servers by executing the following command from the command prompt.

msdtc –install


After installing, restart both the servers and set the Distributed Transaction Coordinator Service Startup type to automatic and start the service (Service would have stopped and changed to “manual” startup mode after executing above command).

3. If the application and data servers exist in different subnets or domain, then both systems should be able to reach each other with the NETBIOS name in the network. If both systems are not able to ping each other with the NETBIOS name (assuming that ping is enabled between two systems), then enter the IP address and NETBIOS name of the data server in the LMHOSTS file in the application server machine and vice versa. The LMHOSTS file will be present in WINDOWS\system32\drivers\etc folder. After this restart, both servers or purge and preload the remote cache name table with the following command from the command prompt:

nbtstat -R

4. If application and data server machines are present in different subnet or domain, then DTC in application server and data server cannot authenticate each other due to a bug in DTC in Windows Server 2003. Then the RPC security needs to be turned off in data server to get the distributed transactions working.

To resolve this problem, turn off the Remote Procedure Call (RPC) security by setting the DWORD value for the TurnOffRpcSecurity registry value to 1. Start Registry Editor (Regedt32.exe), and then set the value of the HKLM\software\microsoft\msdtc\TurnOffRpcSecurity registry key to 1.

After the registry changes, restart the Distributed Transaction Coordinator service.

5. If the firewall exists between application server and database server, apart from the above mentioned steps the required ports need to be opened for SQL server, RPC and DCOM in the servers, which are behind the firewall. E.g. port 1433 for SQL server, 135 for RPC and 4000-4020 for DCOM need to be opened and DCOM should be configured to work on 4000-4020 series.


Issue#2 - HTTP 500 - Internal server error shown in some of the pages in E-Commerce

SYMPTOM“HTTP 500 - Internal server error ” displayed on accessing some of the pages in E-Commerce shops

CAUSEThis issue may arise when in IIS referencing parent path is disabled.

RESOLUTIONPlease refer to the configurations section (Configuration#2) for details.

References[1] http://support.microsoft.com/?id=827805


http://support.microsoft.com/?id=827805

White Paper - Everest Advanced Edition in Windows … · Web viewClick on Add/Remove Windows...

Documents

Transcript of White Paper - Everest Advanced Edition in Windows … · Web viewClick on Add/Remove Windows...