CIC Solutions Forums
Certified Independent Consultant Solutions Forums for
LexisNexis® Practice Management Products
Time Matters - PCLaw - Billing Matters - Browser Edition - HotDocs

Search

  • Re: TM Exchange Sync 11.1 works only one way

    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
    Posted to Time Matters (Forum) by Jim Altman on Sat, Oct 6 2012
  • TM Exchange Sync 11.1 works only one way

    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 [14] DEBUG - Getting Time Matters event changes from 10/05/2012 06:35:34 to
    Posted to Time Matters (Forum) by Jim Altman on Fri, Oct 5 2012
  • TM10 Exchange Server Sync autostart

    I am using TM10 on a SBS2003 32 bit, all is well, but when the server gets a reboot the Sync service does not seem to want to start even tho set to automatic. A manual start and it functions fine, all is well. Nothing in the event log to indicate it failed to start, it just doesn't execute the auto-start. Any ideas? Jim Altman Atlanta, Ga. jaltman
    Posted to Time Matters (Forum) by Jim Altman on Tue, Jan 26 2010
  • TM/TSlips dates

    How would I automate the entry of the Time Matter Billing date in the Time entry screen to be also entered into the date for use by timeslips at the bottom of that entry screen so as to eliminate that double entry.... Jim Altman 170 Mitchell St. SW Atlanta, Ga. 30303 (404) 526-8868
    Posted to Time Matters (Forum) by Jim Altman on Tue, Apr 7 2009
  • Re: TM 9 and Timeslips 2008

    I was fighting this same problem, under vista, and as pointer to others, I found that cleaning out all the temp folders (don't forget the one in users\{username}\appdata\local.... and by wipeing out the contents of the \windows\prefetch directory, the problem was resolved.
    Posted to Time Matters (Forum) by Jim Altman on Tue, Apr 7 2009
Page 1 of 1 (5 items) | More Search Options