Unexpected sync error type 2: ''

[joako]

What does this mean??

7:33:55 PM ================================================================
7:33:55 PM Starting Synchronization: Committing cache changes to the Scalix server
7:33:55 PM ================================================================
7:33:55 PM Initializing
7:33:55 PM Connecting to Scalix server
7:33:56 PM Unexpected sync error type 2: ''

[Colsar]

I found when I got the same message it was because one of the services (in my case, the Mime Browser Controller) had stopped.

Run omstat -a to check the status of all Scalix services. Start any of them that aren't running, then look into why they stopped in the first place(!).

[cgaertner]

We have the same problem. If I run omstat -a only the Item Structure Server is listed as stopped. Could this be the problem?

We have changed the port of the Tomcat server, because our Apache uses port 80. Could that be a problem? How does the connector connect to Scalix?

[kanderson]

What version of Scalix Connect are you using? Make sure you're at 11.2, and recreate the Outlook Profile for the user.

Kev.

[cgaertner]

The version of the Connector is 11.2.0.52, the version of the server is 11.2.0.11121. We installed the server 2 weeks ago and we have 2 Outlook test users at the moment who both have the same problem. One of the profiles was created for the third time now and the problem appeared again and again.

[derklugewolf]

Hi,
I have had the same issue. Took me two days of investigation.

My failure was: The login was set to sommthing like: Harry.Schuh. So you can log on at the webinterface with "Harry.Schuh" as username.

I set the Username in the Ourtlook Scalix Connector to: "Harry.Schuh@scalixmailaccount.com" which causes the sysnc error.

After deleting and creating an new Outlook profile with only "Harry.Schuh" all went back to normal and smartcache is working.

This was testet with: Outlook 2003 and Outlook 2007 on Windows XP with the 11.3.0.77 connector and will be reproducible.

Hope this will help people running into same issue

@lex