Steps to identify issues on the server.
Run Check Project
Before disconnecting a user from the server, run Check Project. This action updates queries on the network. To do so, in Estimating Link, go to Help > Check Project.
Try Estimating Link locally
On a user's pc, try running Estimating Link locally and not connected to the server. To do so, in Estimating Link, go to Setup > Options > Database. Under Connect to a Different Database, click the down arrow and select (local)\TCLI and click connect. In the section above, Current Connection, it should read like the below:
Test the program running locally and see if the same issues are present. If they are not, then we can conclude that it's a networking issue.
Ram
Ensure that the server has enough RAM. Running programs on the server other than Estimating Link has presented issues in the past. We recommend that the server be dedicated to Estimating Link.
Estimating Link Server Requirements
For more information on our server requirements, please see: Estimating Link - Server Requirements
Known Windows 2012 Operating System Issues
Shadow Copy Issue
Check into the Windows Server Operating 2012 known issue regarding shadow copies. This was something that was in a Microsoft update for the operating system that caused problems. This was a problem another IT company discovered and was able to rectify. The update disabled limiting the shadow copies which ultimately caused unforeseen problems.
Error Log Growth
This is a known Windows error that can happen when:
- When a database is moved from one server to another or if the database is no longer owned by the same user or otherwise has a permission issue because of being “reattached” (DETACH/ATTACH) to SQL Server.
-
May also happen if the database is restored via a backup. It is likely caused by an Orphaned User attached to the database.
For the solution to this issue, please see: ERRORLOG Growth Issue