Maintenance and Troubleshooting | << | >> |
---|
When a message is sent from an e-mail client, the route through which the message is transferred is selected by comparing the recipient address of the message with entries in the Microsoft Mail Connector Address Space property page.
Most problems in the Microsoft Mail Connector can be quickly traced using Windows NT Control Panel or the Microsoft Exchange Server Administrator program.
Reasons | Actions |
---|---|
The custom MS Mail (PC) message transfer agent (PCMTA) in the Services icon of Windows NT Control Panel has been started. A custom PCMTA called PCMTA Performance Monitor is created at installation for performance monitoring. All functional PCMTAs are configured dynamically and assigned a user-defined name. |
Disable PCMTA Performance Monitor in Windows NT Control Panel. Configure a named instance of the PCMTA in the Microsoft Mail Connector Connector MTAs property page and start it. |
The MTA instance service is not started. | Start the named instance of the MTA service in Windows NT Control Panel. |
The MS Mail interchange service is not running. | Check the Windows NT event log for reported problems. Start the interchange service in Windows NT Control Panel. |
There is no network access to postoffices. | Install the correct network protocol on the Microsoft Exchange Server, and check for connectivity. |
You do not have permissions for the postoffice shares or volumes. | Have the administrator for those file servers grant Read, Write, and Delete permissions. |
All licenses for the NetWare server are in use. No additional connections to the file server are permitted. | Try connecting to the file server with File Manager. If the server is overused, see your NetWare documentation for a solution. |
The MS Mail (AppleTalk) message transfer agent (ATMTA) is spawning a 16-bit application. The NetWare redirector establishes unnecessary connections that use up NetWare postoffices. | Comment out the nw16 line in the Autoexec.nt file to disable the 16-bit NetWare redirector. |
The connector mail database is corrupted. | Verify that all connector postoffice directories exist and their contents are intact. |
The target postoffice mail database has become corrupted. |
Verify that all target postoffice directories exist and their contents are intact. Check the Inqueue3.mbg mailbag. Make sure the file divides evenly by 116 (116 bytes per message header). |
Messages are stalled in MS Mail queues. | Return or delete some of the oldest messages in the queue and test again. If you are unable to return or delete, the outbound mailbag may be failing. |
An indirect routing connection is inoperative. | Verify that all routing is configured correctly. Check the integrity of the each inbound mailbag (Inqueue3.mbg). Verify the integrity of the mail database on each server along the route. |
Reasons | Actions |
---|---|
The address space is incorrect. | Check the addresses of the intended recipients against the address space for the connector. |
The routing table was not rebuilt after the last changes. | In the MTA General property page, choose Recalculate Routing. |
Reason | Action |
---|---|
The interchange was not correctly configured. | Select the Maximize MS Mail (PC) Compatibility option in the MS Mail Connector Interchange property page. |
Reasons | Actions |
---|---|
Both instances are using a modem script that specifies use of the same communications port. | Edit the modem script source file to change or remove the communications port setting. Recompile the source file into a new script file, and replace the old one with the new one. |
Instances of the MS Mail (PC) MTA are configured to use the same communications port. | Combine instances or configure them to use different communications ports. |
Reason | Action |
---|---|
The hard drive where the connector postoffice is located is not formatted as a Windows NT file system (NTFS) volume. | Back up the drive; use the Windows NT Convert.exe program from the command prompt to update the drive format to NTFS. |
Reasons | Actions |
---|---|
An instance with the same name previously existed and was incorrectly removed. | If this occurs when you try to add the instance again, either use a different instance name or choose Apply three times and ignore the error messages. |
You don't have permissions to create instances. | Check with the site administrator. |
Reasons | Actions |
---|---|
There is a script problem. | For more information on script file modification and troubleshooting, see the MS Mail for PC Networks Administrator's Guide. |
The modem cable doesn't support request to send (RTS) or clear to send (CTS) flow control. | Replace the modem cable with one that supports these pinouts. |
Reason | Action |
---|---|
The Mappings.txt file needs a new entry for this file type. | Use a Macintosh utility to find the file's creator and type. Edit the Mappings.txt file to map the creator and type to an extension. |