Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
Copper Super Contributor
Posts: 104
Registered: ‎06-29-2009

Synchronization - Error creating history record. I/O error 103

[ Edited ]



We have some problems with synchronization on our SalesLogix 7.5.1 (LAN).

We launch synchronisation server. The sync disappears when treating 2 files.

In Infiles Folder, we have 230 files.

In the event viewer, we have errors :


1. SLXSyncServer error : 

The description for Event ID ( 4 ) in Source ( SlxSyncServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: You cannot load more than one copy of SyncServer at a time..



2. SLXSyncService error : 

Error creating history record.  I/O error 103


Who can help me ?



Message Edited by ben240374 on 10-28-2009 10:20 AM
Bronze Elite Contributor
Posts: 514
Registered: ‎03-24-2009

Re: Sunchronization - Error creating history record. I/O error 103

[ Edited ]



Resolution 2 'The Reboot' has worked for me in the past.


Possible Resolution 1:

  1. Stop the sync service
  2. Reset the sync configuration
  3. Start the sync service

Possible Resolution 2:


This error may be resolved by rebooting the machine. In numerous cases, a complete uninstall and reinstall of all SalesLogix applications on the machine may need to be performed.


Possible Resolution 3:


Ensure that SyncServer.exe is present on the synchronization server, and is the appropriate version.

Message Edited by AdamTravers on 10-28-2009 09:23 AM
Regards, Adam Travers
empath-e Services Limited
Posts: 79
Registered: ‎06-25-2009

Re: Synchronization - Error creating history record. I/O error 103


The first error indicates that there is still an instance of SyncServer running or it abended.  

I would try the following:

1) Stop the Sync Service

2) Run SyncServer manually with the command line parameter: SyncServer.exe /reset


This will allow SyncServer to start up and clear the mutex that was being held by the previous instance.

You then then run a sync cycle and possibly see the actual error that Sync was encountering.


Paul Zeimet

Development Manager

Sage SalesLogix

Paul Zeimet
Development Manager
Infor CRM