It’s not a matter of if, but when this problem will manifest at one of your client’s sites. The characteristics of this problem manifest such that you can log into Time Matters, navigate to main lists, but the main lists are empty (see below).

This has become a very common problem now that the SQL based version of Time Matters has entered the mainstream. From my experience, the following two problems are the most likely culprits:

1.  The Time Matters database owner has inadvertently been given an improper server role (see below).  The only option needed is Public.

2.  The Time Matters database owner’s schema is inappropriately configured for the wrong database user (see below). The schema must be the same as the database user. 

 What causes this to happen? From my experience it happens when firms move their database and attempt to reconnect the database user. It has happened when other problems exist and folks start clicking on options without testing the impact of each new option they try.