I have been working with tech support for nearly 2 months to solve an issue that seems unsolvable. Calendar items posted to TM sync readily to Exchange, but items posted to Outlook fail to sync into timematters.
The error message from the sync log is:
2012-10-05 06:35:56,684  DEBUG - Getting Time Matters event changes from 10/05/2012 06:35:34 to 10/05/2012 06:35:562012-10-05 06:35:59,232  DEBUG - Getting Appt cf1b1d33-038c-4b1b-8712-45171dd2ed582012-10-05 06:35:59,723  DEBUG - Inserting Appointment cf1b1d33-038c-4b1b-8712-45171dd2ed582012-10-05 06:35:59,792  INFO - Adding Event "test" to Time Matters2012-10-05 06:36:01,728  INFO - Error Exception adding Event to tm: Object reference not set to an instance of an object.2012-10-05 06:36:09,506  INFO - End of Appointment Synchronization for altlaw.local\jaltman
Does anyone have the 11.1 exchange sync working correctly? Anyone seen this and know of a solution? Server is SBS08. I had not updated the sync program in a long time and dont really remember the version i was running prior to upgrading, but it was running fine. I spend well over half my time in the courthouse and really need for my outlook calendar items to sync back so the office does set me appoinments in conflict with what I do remotely.
ANy help deeply appreciated.
Jim Altman 170 Mitchell St. SW Atlanta, Georgia 30303 (404) 526-8868
You might want to explore having someone convert you to a fairly inexpensive hosted exchange account and set this up for you. This might be more time and cost effective than trying to resolve what I assume is a a local SBS Exchange Server set-up. For example, we have many firms using Mail Street, and now Office 365 from Microsoft, and have had great success with each provider.
Tom Caffrey, CIC (Moderator)President, Premier SoftwareTele: 856-429-3010 Web: www.premiersoftware.comDEVELOPER - WealthData for Estates and Elder Law; CivilData for Litigation Feature Home of SOS: Small Office Server, a subscription based server for small law firms
thanks for the reply. the problem is the connector writing into the timemattters database, not an exchange problem. i have run my own exchange server for years and it is flawless. the connector was running fine till i upgraded to 11.1. note the log above, it reads and writes exchange fine, it reads timematters fine, it errors when writing to timematters.