Fixed Asset Manager Server Busy

I forgot to mention in my original post, the company file and application are running on the same machine, not though the network. The server computer is my workstation. 

I've also tried setting QBfam25.exe to run as an administrator and running in compatibility mode. No change in the error.

Install the trial version to isolate the problem.

We appreciate the detailed information. As @SIAB mentioned, have you tried installing the trial version of QuickBooks Desktop to isolate the issue with the busy server?

You may also consider rebooting your computer to terminate any stuck, frozen, or conflicting background processes, allowing QuickBooks to start fresh.

If the error occurs only when accessing a specific client in Fixed Asset Manager, the data file may need to be updated or repaired. Go to Accountant/Company > Manage Fixed Assets > Tools > Program Options > General, then uncheck "Automatically compress client", and click OK.

If these steps do not work, you may need to repair your QuickBooks installation. Since you mentioned you have already tried the fixes in the QuickBooks Tool Hub, you can follow the other solutions in this article: Fix Error: Server Busy. This action cannot be completed because the other program is busy.

We'll keep this conversation open if you still need further assistance.

Hello,

When I went to install the trial version, it went to an option to repair the current installation without an option to install the trial version along side the current installation. 

I can also confirm that restarting the computer did not resolve the issue.

I have noticed that FAM is not requesting access to the QuickBooks company file in the first place on startup. No request for access is ever noted in either QuickBooks Enterprise Desktop or FAM. 

The error is also thrown specifically when trying to open FAM. I'm not able to access any tools or settings since the error recurs until I force close the program with task manager.

I will try a full reinstallation this evening next unless you can think of another solution in the meantime.

If a full reinstallation doesn't solve your problem, install the trial version to be sure.