LinkAge Message Exchange 3.2
| 31 ). | XFOR: Some Recipients Ignored on Mail Sent to Two or More CMS Nodes |
| When sending mail using the Linkage Exchange-OfficeVision/VM Connector from Exchange to recipients on two or more different CMS nodes, the message may not be delivered to all of the intended recipients. | |
| 32 ). | XFOR: lsccmmex.exe causes AV when processing inbound mail from CCMail to Exchange |
| The Lsccmmex.exe process causes an access violation when inbound mail from Lotus cc:Mail to Exchange Server is being processed. This can occur when the Lsccmmex process is processing a zero-length text item in the body of the message. | |
| 33 ). | XFOR: Notes Client Receives "Error Loading Metafile" |
| This problem occurs when you are using the LinkAge Connector for Lotus Notes 3.2 with Microsoft Exchange Server 4.0 or 5.0, or when you are using Microsoft Exchange Server 5.5. The Lotus Notes e-mail client (versions 4.5 and 4.6) may receive an error... | |
| 34 ). | XFOR: Attachment with PC Binary or PC ASCII Flag Set Unreadable |
| An attachment of type PC Binary or PC ASCII that is sent from IBM Office Vision (PROFS and/or OV/VM) to Exchange via the Linkage Message Exchange OV/VM Connector version 3.2 is unreadable in Exchange. | |
| 35 ). | XFOR: Access Violation in Lsdxants.exe with Long Fullname Field |
| The Linkage Directory Exchange Agent for Lotus Notes version 3.2 may access violate when encountering a Lotus Notes document Fullname attribute that is greater than 252 characters. The resulting crash will include LSDXANTS!LNDXAProcessOutbound in the... | |
| 36 ). | DXM Access Violation Processing NAMEM Macro |
| The Linkage Directory Exchange Manager version 3.2 may access violate when the NAMEM macro is used in a mapping rule. If Windows NT and Linkage 3.2 symbols are installed and functioning correctly, the resulting stack frame will look similar to the... | |
| 37 ). | XFOR Lsccmmex.exe Access Violates When Processing Delivery Report |
| The Lsccmmex.exe process causes an access violation when processing delivery reports from Exchange Server to cc:Mail. If the Linkage and Windows NT symbols are loaded correctly then the call stack will look like the following: > kb FramePtr RetAddr... | |
| 38 ). | XFOR: Queue Viewer Does Not Load; Missing RPCDCE4.DLL |
| A dialog box may appear that contains the following error message: This may occur under any of these conditions: When the Exchange Notes Connector (LinkAge Message Exchange version 3.2) starts, the dialog box may appear. -or- The Queue Viewer may not... | |
| 39 ). | XFOR: Backup Exec Event ID 3004 When Backing Up LinkAge |
| This article applies to LinkAge version 3.2 Notes, and the OV/VM and/or SNADS connectors. The following error message appears in the Windows NT Event Viewer application log: The description for Event ID (3004) in Source (Backup Exec 6.1) could not be... | |
| 40 ). | XFOR: GroupWise/Lotus Notes DXA Slow to Respond to Full Reload |
| Immediately after starting the Lotus Notes/GroupWise connector, administrators may find that performing a Full Reload on the connector will result in a delayed response of up to two minutes. It will appear as if the Directory Exchange Agent (DXA) had... | |
| 41 ). | XFOR: Completely Removing LinkAge V3.2 Connector Software |
| This article will describe the steps required to completely remove the LinkAge Software programs from a server. | |
| 42 ). | Exchange Connector for Lotus Notes stops with error message: Error opening mailbox domain/server!!Exchange.bad |
| If you start the Microsoft Exchange Connector for Lotus Notes, the Convert and Transfer processes may be displayed as stopped in the Exchange Connectivity Administrator program. | |
Previous Page
Page 3 of 3
PC Fixer
Fix a wide variety of PC problems for Free!