Article ID: 174102
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 4.0 Standard Edition
- Microsoft Exchange Server 5.0 Standard Edition
This article was previously published under Q174102
SYMPTOMS
You find that messages are not flowing from OV/VM to Exchange through the LinkAge Exchange-OV/VM (or LinkAge PROFS) Connector and you get the following error messages in the Application Event log:
The description for Event ID ( 1 ) in Source ( LSIControl ) could not be
found. It contains the following insertion string(s): ENS, 1997/09/05
03:15:37- LME-PROFS-DIAMEX(01e8) 1 40720:Error {CT:160()} finding
correlation table record.
-and-
The description for Event ID ( 1 ) in Source ( LSIControl ) could not be
found. It contains the following insertion string(s): ENS, 1997/09/05
03:15:37- LME-PROFS-DIAMEX(01e8) 1 04065:Critical error: Queue item
handle passed to QMMarkQItemBad is invalid.
You will also find that the OV/VM to Exchange Transform process is not running, and you see the following messages in the Linkage Browse log:
LME-PROFS-DIAMEX 40720: Error {CT:160()} finding correlation table
record
LME-PROFS-DIAMEX 56074: {I/O error has occurred}: Could not find CT
record
for '1997090310234541 server.org '
LME-PROFS-DIAMEX 04065: Critical error: Queue item handle passed to
QMMarkQItemBad is invalid
LME-PROFS-DIAMEX 00514: A RESTART request has been received
LME-PROFS-DIAMEX 00505: LME-PROFS-DIAMEX is ending, last return code was
{A
shutdown request was made}
CAUSE
A possible cause may be a corrupted correlation table.
WORKAROUND
To work around this problem, do the following:
- Stop the Linkage Controller service. This will stop the OV/VM Connector and the SNADS Connector (if present).
- Move the Ct2.idx, Ct2.dat, and Ctlock.dat files from the c:\linkage\tables directory into a backup directory.
- Delete the Ct2.idx, Ct2.dat, and Ctlock.dat files (the Ctlock.dat file may not be present) from the c:\linkage\tables directory.
- Restart the LinkAge Controller and Connector services. The correlation tables will be rebuilt.
NOTE: There are no tools available that will repair a damaged correlation table; currently rebuilding the table is the only known fix for this issue. Damaged correlation tables (the files that make up the correlation tables) should be sent to Microsoft Support for cause analysis through the normal channels.
Keywords: kbfix kbusage KB174102
