LinkAge Message Exchange 3.2
| 1 ). | XFOR: Linkage 3.2 PROFS Connector Repeatedly Restarts Itself |
| The Linkage Message Exchange 3.2 Exchange-OfficeVision/VM Connector may repeatedly halt outbound (to PROFs) message processing and restart itself. Additionally, events similar to the following may be logged in the Exchange Connectivity Manager's Log... | |
| 2 ). | XFOR: Failure Creating Windows NT Accounts Using Linkage 3.2 with LDE |
| When you attempt to create a Windows NT user account after configuring Linkage Message Exchange 3.2 LDE between Lotus Notes and Exchange Server (and enabling Windows NT account creation or deletion), the attempt will produce a failure (viewable in... | |
| 3 ). | XFOR: Linkage SNADS Connector Does Not Handle NDR Properly |
| When an NDR message is received by the Exchange Server computer through the Linkage SNADS Connector, an entry similar to the following is logged in the Exchange Connectivity Manager's log browser: LME-SNADS-IN(014e) 4 22464:- Recipient:... | |
| 4 ). | XFOR: 0-Byte Message or Print Spool File Causes VM2DIA Process to Stop |
| Messages may stop flowing from Exchange to a PROFS system through the OV/VM LinkAge 3.2 connector. A zero-byte message or a print spool file, sent from the PROFS system, may cause the VM2DIA process to stop. This, in turn, causes the connector to stop... | |
| 5 ). | XFOR: How to Dump LDE WorkQueue Using SQL |
| This article explains how to use SQL Server's query tool to dump the current WorkQueue for version 3.2 of LinkAge Directory Exchange (LDE) to a file to send to Microsoft. | |
| 6 ). | XFOR: How to Upload LDE SQL Database to Microsoft |
| This article explains how to send the SQL database used by version 3.2 of LinkAge Directory Exchange (LDE) to a Microsoft support professional. | |
| 7 ). | XFOR: Permissions Not Properly Set by the LinkAge Directory Exchange Agent on New Mailboxes |
| When LinkAge Directory Exchange Agent (DXA) creates an Exchange Server mailbox, permissions for the associated Windows NT account are not set properly to use this mailbox. The user may see an error similar to the following: | |
| 8 ). | XFOR: How to Save Mapping Rules for LDE Using SQL |
| This article explains how to use the SQL Server 6.5 query tool to dump the current Mapping Rules for version 3.2 of Linkage Directory Exchange (LDE) to Microsoft Product Support Services (PSS). | |
| 9 ). | XFOR: Parsing Problem with LinkAge and cc:Mail Connector |
| The LinkAge Message Exchange 3.2 cc:Mail Connector may not correctly parse user names during the directory synchronization (dirsync) process. The problem may occur if there is a cc:Mail postoffice that has been included in the dirsync process using the... | |
| 10 ). | XFOR: Lotus Notes Directory Synchronization Does Not Work After Resetting Pcta.tbl Files |
| If you reset the directory synchronization numbers by using the Microsoft LinkAge Message Exchange 3.2 directory synchronization agent, the following error messages may be logged in the browser logs: 2000/08/02 15:53:59- DXANOTES(0342) 3... | |
| 11 ). | XFOR: Messages Containing Doclinks Are Stuck in Exchange.box |
| When you send a message from Notes to Exchange Server, Notes messages containing doclinks get trapped in the Exchange.box file. | |
| 12 ). | XFOR: LME-PROFS-MEXIN Returns Error Code 80070057 and Exits |
| Inbound mail from OV/VM (PROFS) to Microsoft Exchange via the Linkage 3.2 OV/VM connector may back up and the Transfer to Exchange for OV/VM process (LME-PROFS-MEXIN) may terminate unexpectedly. The Linkage Administrator browse log may have the... | |
| 13 ). | XFOR: LME-PROFS-MEXDIA Crashes Processing a Long File Extension |
| The Microsoft Exchange to OV/VM transform (LME-PROFS-MEXDIA) process may terminate unexpectedly with an access violation. The resulting Drwtsn32.log and/or User.dmp may have a stack back trace similar to the following: function: XFMDOSFEMFind 0037defe... | |
| 14 ). | XFOR: Fixed Length File Sent from OV/VM Using SENDFILE is Corrupted |
| A fixed-format CMS file, which is uploaded to the host (not by the Linkage Connector) and then sent to a Microsoft Exchange user as an attachment using SENDMAIL via the Linkage OV/VM connector, is corrupted and unreadable by the Exchange user. | |
| 15 ). | XFOR: Characters Are Stripped on Fixed File Sent from PROFS |
| This problem occurs when a fixed format file in CMS has been put into the PROFS "store" and is sent to Exchange Server by way of the LinkAge OV/VM (PROFS) connector. This results in an attachment in which the first two characters of the first line are... | |
Page 1 of 3
Next Page
PC Fixer
Fix a wide variety of PC problems for Free!