General Issues
Issue with Exchange/SMTP Server
Configuring XP Pro for 40 Users
Can't See the MobileTech Login Page
API
If you experience any problems with your website, please run through the following tests:
Restart IIS and\or the computer hosting the website.
Run through the tests detailed in the Troubleshooting a Local Network Configuration topic. For example, to confirm that a port is open, use the telnet test (type “[telnet IP Address] [port number]”). For more on the Telnet test, see the Advanced Network Connectivity section of the Troubleshooting a Local Network Configuration topic.
If your Customer Web Access web site is not e-mailing your customers their passwords, there may be a problem with how and Microsoft Exchange is installed. In short, we've found that the only way to enable customer password email messages is to change the IIS IIS (Internet Information Server) is IIS is Microsoft's business-class Web server. Although Apache boasts more total worldwide installations than IIS, many corporations choose IIS as their Web server because it is supported by a commercial organization. Some have criticized IIS in the past, though, for its alleged security weaknesses. IIS has improved over the years, supports many Web standards including SSL, and integrates well with other Microsoft Web technologies such as FrontPage. An administrator can manage IIS through a graphical console, the Internet Services Manager. security level to “low (in-process)”; however, not only is this method insecure, it still doesn't seem to allow the COM object to send email. Thus, the only way to fix the problem is to use the Microsoft workaround as described in their Read Access to the Everyone Group Is Removed After You Install Exchange 2000 SP3 article. We recommend you use Workaround 1. The steps that follow detail how to implement this workaround:
Download the
.vbs files mentioned in the workaround from the following URL:
http://download.microsoft.com/download/9/7/0/9706f302-99f8-49f9-8aa4-df66d771feaf/smtppermissionsscripts.exe
Follow the instructions from the Microsoft article and run the first Visual Basic script. This grants "Exchange Metabase" access to the IUSR_ and IWAM_ accounts.
Give the IUSR_/IWAM_ accounts access to the entire Exchange folder.
Verify that messages are being picked up and placed in C:\Program Files\Exchsrvr\MailRoot\vsi 1\Queue. It may take a few minutes before you start seeing the messages in this location, so please be patient.
Windows XP Professional runs IIS IIS (Internet Information Server) is IIS is Microsoft's business-class Web server. Although Apache boasts more total worldwide installations than IIS, many corporations choose IIS as their Web server because it is supported by a commercial organization. Some have criticized IIS in the past, though, for its alleged security weaknesses. IIS has improved over the years, supports many Web standards including SSL, and integrates well with other Microsoft Web technologies such as FrontPage. An administrator can manage IIS through a graphical console, the Internet Services Manager. 5.1, which, by default, only supports 10 connections. For many companies, this is not enough connections to support all of your users. The steps below enable you to increase IIS' connections limit to 40, which Windows has hardcoded as the maximum number of connections. If you want to support more then 40 concurrent users, you will need to use one of the Server operating systems.
To Increase the Connection Limit of IIS 5.1:
Select Start > Run. The Run dialog box appears.
Type cmd into the Open field.
Click OK. A command prompt window appears.
Type "cd \inetpub\adminscripts" at the prompt. This will connect you to the adminscripts folder.
Type "cscript adsutil.vbs set w3svc/MaxConnections 40" at the prompt. This will run a script that sets the MaxConnections value in the IIS metabase to 40 (the maximum allowed).
Type "iisreset" at the prompt. This command shuts down and starts IIS so that the new settings will take effect.
If you cannot see the MobileTech Login page after installation, ASP.NET 1.1 may be misconfigured. To determine if this is the case:
Open IIS. Select Start > Programs > Administrative Tools > Internet Information Services. The Internet Information Services dialog box appears.
|
|
Note: |
Navigate to your MobileTech folder. You should find it in the Internet Information Services/(name of your computer)/Default Web Site/MobileTech..
Right-click the MobileTech folder and select Properties from the pop-up menu.
Click the HTTP Headers tab.
The Custom HTTP Headers box should display text similar to what appears in the above screenshot. If it does not, perform these steps:
Open a command prompt. To do so:
Select Start > Run. A Run dialog box appears.
Type "Command" or "cmd" in the Open field.
Press Enter. A "dos" or command prompt window appears.
Type "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i". Do not include the quotes.
Press Enter. ASP.NET 1.1. will be configured.
Test the MobileTech Connection. You should now see the login prompt.
If you installed .NET 2.0 before you installed IIS, you may receive a “Failed to access IIS metabase” error.
You will need to repair your ASP.NET installation and set up the appropriate ISAPI extension mappings.
To do so, follow these steps:
Open the Control Panel.
Open Add/Remove Programs.
Scroll down and select .NET Framework 2.0.
Click Change/Remove. The Maintenance Mode dialog box appears.
Select Repair.
Click Next. Follow all of the prompts.
If the above steps did not work, try the following:
Select Start > Run. The Run dialog box appears.
Type C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i.
Press OK. A command window appears, and your ASP.NET installation will be repaired.
When complete, your API connection should work normally.
Back to Website Deployment Checklist
