Question: I am getting "SQL Server ODBC connection failed" messages.
Answer: Check your ODBC setup to make sure your database library is set to DBMSSOCN. Make sure you can ping the SQL Server node that is named in the SQL Server ODBC setup.
Question: I installed TIMS3 Client Access but my users do not see the TIMS3 Common Group of icons.
Answer: Your users are probably set up on the domain controller with a common user profile (e.g. usr.man) that they have no privilege to modify. Using a privileged account name, activate the User Profile Editor to check that the profile is configured to display common groups.
Question: I cannot get Project Navigator or the Database icon to display any database records.
Answer: Check your ODBC setup to make sure the database library is set to DBMSSOCN for SQL Server communications. For Access, make sure the database file name is correct, that the drive is available, and the user has change permission to the drive.
Question: When Project Navigator is in the File List View, a privileged user (administrator) can see all files in a directory listing. However, a regular non-privileged user can not see the list of files, even though I have granted Full Domain security access for the user’s primary group to the directory as well as each file in the directory.
Answer: On the Windows file server check to ensure that the root directory of all project drives (eg, C:\, D:\, etc) have been configured to grant at least Read access to the Domain built-in Everyone group.
Question: A regular user is not able to Check Out files, even though he has been granted Full Domain security access to the file on the server.
Answer: The Windows built-in System account must be given Full access to all project files to allow the TIMS3 file server to lock the file during file transfer. By default, the System account is used to run the File Server process. You can verify this using the Control Panel->Services icon.
Question: While using the TIMS3 Data Manager a SQL Server Login dialog appeared for the TIMS3 database. I accepted the default Login ID of ‘sa’ and clicked OK. Then a SQL Server Login error dialog appeared with text that mention something like "Unable to connect. The maximum number of ‘50’ configured user connections are already connected. System Administrator can configure to a higher value with sp_configure. What do I do?
Answer: The number of user connections to the SQL Server has been exceeded probably because it is now being used by too many TIMS3 users or other SQL Server applications. The TIMS3 Data Manager and Project Navigator can use roughly 2 to 15 connections per application depending on the type of action being performed. Increase the number of user connections using the SQL Server Enterprise Manager. Select the SQL Server name and press the mouse right-click button and select the Configure option. Click on the Configuration tab and scroll down the list to find the ‘user connections’ setting and increase the number in the Current column Click on OK to save the setting and then stop and start the SQL Server using the mouse right-click.