Trouble Shooting - Slow Response caused by Windows Server COM+ Components - Trouble Shooting

Slow Response caused by COM+ objects
Component services.
Go to Start Administrative Task Component services

open Components and look for a long running dll.
Mark down the name.

Event Viewer
Look for any error in the application folder related with application.

Configure IIS to be a Smart Host for Exchange Server

Step 1: Verify the Installation of the SMTP Service
In Control Panel, open Add/Remove Programs, click Add/Remove Windows Components. Click the Internet Information Services (IIS) component, click Details, and then verify that the SMTP Service check box is selected.
If it is not selected, click to select it, click OK, and then follow the installation directions that are displayed.

Step 2: Configure the SMTP Service to Relay for Internal Domains
Depending on the scenario, it may be necessary to configure the SMTP service to relay inbound messages for your internal domains.
1. Click Start, point to Programs, click Administrative Tools, and then click Internet Services Manager.
2. Expand the tree under the server name, and then expand the Default SMTP Virtual Server. By default, you should have a Local (Default) domain with the fully qualified domain name of the server.
3. Configure the domain for inbound:
a. Right-click the Domains icon, click New, and then click Domain.
b. Click Remote, click Next, and then type the forwarder.yourcompany.com in the Name box. Click Finish.

Configure the domain for relay
1. In the properties for the domain that you just created, click to select the Allow the Incoming Mail to be Relayed to this Domain check box.
2. If this is being set up for a internal domain, you should specify the server that receives e-mail for the domain name by the IP address in the Route domain dialog box.
3. Click the forward all e-mail to smart host option, and then type the IP address of the server that is responsible for e-mail for that domain in square brackets.
Note: Typing the IP address of the server in brackets is necessary so that the server recognizes this is an IP address and not to attempt a DNS lookup.

Step 3: Specify the Hosts That You Want to Openly Relay to All Domains
Note:
Anyone can send to the domains that you specified in Step 2.

This step is for hosts, which are most likely your internal servers that would need to send to all domains on the Internet. It is not recommended to not have any restrictions because anyone can use your server as an open relay. It is recommended to only allow the minimum, necessary hosts to openly relay to all domains. To do so:
1. Open the properties of the Default SMTP Virtual Server.
2. On the Access tab, click Relay.
3. Click Only the list below, make sure the list is empty. Check the checkbox before “Allow all computers which successfully authenticate to relay, regardless of the list above”.

Install and Configure the Oracle 10g ODBC driver on Windows 2003 Server

Verify MDAC version 2.8 (use comcheck.exe).
If less than 2.8, install MDAC 2.8 by using Windows 2003 Server CDs.

Run CC_Pkg.exe
Install it in E:\Program Files\CompChecker
Run Component Checker
Make sure MDAC has version 2.8 and up
Setup Oracle ODBC and Provider for OLE DB drivers. Install or update TNSNAMES.ORA in E:\Program Files\\Network\Admin folder.

Install Oracle Client including ODBC and Provider for OLEDB
Open 10g_win32_client.zip

A. Run Setup.exe.

B. Oracle Universal installer screen.
Name: OraClient10g_hisrep
Path: E:\Oracle\Product\10.1.0\Client_hisrep
Chose “Administrator” option
Click ‘Next”

1. At Welcome Screen
-Leave ‘Typical’ button unchecked.

2. Select Naming Methods screen.
- Select ‘Local Naming’ option and > to ‘Selected Naming’ side.
- Click ‘Next’

3. Service Name screen.
- Enter sidname: hisrep
- Click ‘Next’

4. Select Protocols screen.
- Select TCP
-Click ‘Next”

5. TCP/IP Protocol screen.
- Host Name: hisreppldb.iweb.gm.com
- Keep ‘Use standard prot number of 1521.
- Click ‘Next”

6. Test screen.
- Keep ‘Yes, perform a test checked.
- Click ‘Next’

7. Net Service Name screen.
- Net Service Name: hisrep
- Click ‘Next’

8. Connect Test/Logon screen.
- Username: Medgate_v60_app
- Password: medgate60
- Click ‘OK’

9. Another Net Service Name? screen.
- Leave ‘No’ checked.
- Click ‘Next”

10. Net Service configuration Done screen.
- Click ‘Next’

11. Naming Methods configuration Done screen.
- Click ‘Next’

12. Done ‘OracleNet Configuration Complete’ screen.
- Click ‘Finish’

13. End of Installation screen.
- Click ‘Exit’
- Do you Really want to exit? prompt
- Click ‘Yes’

Verify ODBC driver.
Create new DSN source.
Go to Start->Administrative Tools->Data Source (ODBC)
Click “System DSN” Tab
Click “Add” button
Select the driver: “Oracle in OraDB10g_xxx”
Click “Finish”
Configure the Oracle ODBC Driver:
Data source name = <your_data_source>
Description = Oracle database
TNS Service name = <your_service_name>
UserID = <user_id>

TEST the database connection by click “Test Connection” button

Make sure it can establish connection. The connection will be used for other install components.

Turn on ASP support in IIS (Windows 2003 server)

Turn on ASP support in IIS Administration.
Open IIS Manager
- click Web Sites
- open
- Right click
- Select Properties
- Select Tab ‘Home Directory”
- Click ‘Configuration Button”
- Verify that .ASP and .ASPX are in ‘Application Extensions’ list. Otherwise add them.
- Click OK to close.

Configure SMTP on IIS (Windows 2003)

Step 1: Verify the Installation of the SMTP Service
In Control Panel, open Add/Remove Programs, click Add/Remove Windows Components. Click the Internet Information Services (IIS) component, click Details, and then verify that the SMTP Service check box is selected.
If it is not selected, click to select it, click OK, and then follow the installation directions that are displayed.

Step 2: Configure the SMTP Service to Relay for Internal Domains
Depending on the scenario, it may be necessary to configure the SMTP service to relay inbound messages for your internal domains.
Click Start, point to Programs, click Administrative Tools, and then click Internet Services Manager.
Expand the tree under the server name, and then expand the Default SMTP Virtual Server. By default, you should have a Local (Default) domain with the fully qualified domain name of the server.

Configure the domain for inbound:
Right-click the Domains icon, click New, and then click Domain.
Click Remote, click Next, and then type the forwarder.gm.com in the Name box. Click Finish.

Configure the domain for relay
In the properties for the domain that you just created, click to select the Allow the Incoming Mail to be Relayed to this Domain check box.
If this is being set up for a internal domain, you should specify the server that receives e-mail for the domain name by the IP address in the Route domain dialog box.
Click the forward all e-mail to smart host option, and then type the IP address of the server that is responsible for e-mail for that domain in square brackets. IP of forwarder.yourcompany.com is:
[168.208.12.12]
Note: Typing the IP address of the server in brackets is necessary so that the server recognizes this is an IP address and not to attempt a DNS lookup.
Click OK.

Install SMTP service under Windows Server 2003

The version of Microsoft IIS that ships with Windows 2003 contains a service that you can use to deliver mail using SMTP. To install this SMTP service, perform the following steps:
1. Start the Control Panel Add/Remove Programs applet.
2. Click Add/Remove Windows Components.
3. After the Windows Components Wizard appears, select Applications Server and click Details.
4. Select Internet Information Services (IIS), then click Details.
5. Select SMTP Service, then click OK as this figure shows.
6. Continue to click OK to close all other dialog boxes until you're back at the Windows Components Wizard page, then click Next.
Windows 2003 will copy the files required for the SMTP service (you might be prompted to insert the installation CD-ROM) and configure the service. You can also install the SMTP service through the E-mail Services tool, which is a POP3 component that automatically installs SMTP. Windows 2003 configures the SMTP service to use a default server, and you can use the IIS Manager to modify the server settings.

Determine MDAC version
Determining which version of MDAC is installed on a computer at any given time presents certain difficulties because individual MDAC files may have been replaced by an errant installer, which complicates the situation. Component Checker is probably the most useful tool that is available for verifying MDAC installations. Component Checker is available for download from Data Access and Storage Developer Center MDAC Downloads.


Install and Use the Component Checker Tool
The most reliable way to determine which version of MDAC is installed is to compare the version number of each MDAC DLL file to a list of the DLL files that are shipped with each MDAC version. The Component Checker can help you to do this. It checks the files on the computer, compares them to a list from each version of MDAC, and reports the closest match.To install Component Checker, follow these steps:
1. Browse to the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en)
2. Click the link to download Component Checker. When you are prompted by the browser, save Cc.exe (a self-extracting executable file) to the desktop.
3. On the desktop, double-click Cc.exe; this extracts the Component Checker files and installs to the default location, C:\Comcheck.
To use Component Checker to check the MDAC version, follow these steps:
1. From the Start menu, click Run.
2. In the Open text box, type c:\comcheck\comcheck.exe and then click OK.
3. In the Component Checker - Choose Analysis Type dialog box, select Perform Analysis of your machine and automatically determine the release version, and then click OK.
4. The program attempts to identify the MDAC version on your computer by scanning all of the core MDAC files and registry settings. This process normally takes several minutes. When finished, you should receive the following message:
The MDAC version that is closest to the version on your computer is 'XXXX'.
5. Click OK.
6. A summary of the Component Checker scan appears. Note that the Dir, FileDescription, and FileSize errors can be safely ignored.

Check the Version Information Stored in the Registry
Although not the most reliable way to check the MDAC version, checking the registry for the version information is an easy way to double-check this information (if you are not experiencing any MDAC-related issues).The version information is found in the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer
To check the registry, follow these steps:
1.On the Start menu, click Run.
2.In the Open text box, type regedit and then click OK; this starts Registry Editor.
3.In the Navigation pane, drill-down to the following path:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess
4.In the Details pane, look in the Name column for FullInstallVer and Version. Each of these keys will have corresponding version information in the Data column.
5.When finished, click Exit on the Registry menu to close Registry Editor.