MIP Slowness or Crashes, Closing the Program Unexpectedly Common Causes

 1. If everyone is out of MIP on every workstation and nothing else is running that is attached to SQL, you should try stopping and starting the SQL Server service. The instructions can be found in this link http://kb.abila.com/article/how-stop-and-then-start-mip-or-fr50-sql-server-service-instance

2. Try having one of the users that is seeing crashing or slowness log into MIP on the server and try to do the same operations that are an issue on their own machine. If it works correctly on the server, it would not be an MIP user account issue and instead, may have something to do with network, firewall, or anti-virus.

3. Make sure your SQL service pack is up to date by going to SQL management studio on the server, connecting, and looking at the top of the object explorer to see the version number and comparing it to the list in this web page https://buildnumbers.wordpress.com/sqlserver/. If there are newer service packs for your version of SQL, it is recommended to upgrade to the newest service pack.

4. Make sure your server is up to system requirements for MIP by checking this link http://www.abila.com/solutions/fund-accounting/mip-fund-accounting/system-requirements/

5. Check the size of your log file by going to C:\Program Files\Microsoft SQL Server\mssqlyourserverinstancename\MSSQL\DATA and find the organization file size. There should be 2 files with the same name but different extensions, the data file (.def) should be much larger than the log file (.ldf). If the log file is larger, please have everyone log out of MIP (when convenient) and go to the top of your program, click File>Compress and compress both your main database and the NpsSqlSys as well.

6. For reporting slowness issues, you may also want to go to http://kb.abila.com/article/slowness-when-printing-exporting-or-running-reports-screen

7. For attachments crashing, please visit http://kb.abila.com/article/df-fa-24184-opening-encrypted-attachment-crashes-mip-workstation

8. For miscellaneous causes and resolutions, please visit the below two articles:

A. (Ignore the error, the fixes may still apply) http://kb.abila.com/article/error-message-%E2%80%9Cyour-licensed-seat-no-longer-active%E2%80%9D

B. http://kb.abila.com/article/computer-times-out-and-disconnects-mip-fund-accounting

C. Search the knowledge base for the specific action you are doing and error you are receiving to see if there is a separate article.