Error “LOAPP is not an object.” When Starting AccountMate

==> Reinstall the Client Run-Time Files

The majority of the time, simply reinstalling the client runtime files on the workstation that’s experiencing the problem will fix the issue. Details are here: Client Installation Procedures | NexLAN and, as it says there, be SURE to run the installation program with <right click> Run as Administrator.

==> Confirm .Net Framework 3.5 Is On/Enabled

If that didn’t resolve the issue, then a Microsoft Windows Update could have disabled the .Net Framework 3.5. Use the built-in Windows “search” feature to search for and run “Turn Windows Features on or off”, you’ll get the screenshot below and you’ll check the boxes for the highlighted  “.NET Framework 3.5” and the options below it (as you expand the folder by clicking on the plus-sign).

==> Detecting the Processor and RAM in System Properties

Sounds crazy, but… the root of the problem could be that Windows can’t detect/read the Processor and RAM configuration of the machine – it will show as “blank” or “Not Available” in System Properties.

Information on how to confirm and fix this is at the following links:

• Processor name not showing in System properties window – Microsoft Community
• Processor & Installed memory/Ram are *Not Available* and can’t view my system info summary – Microsoft Community

==> System Repository is Corrupted

On rare occasion, the Windows System Repository may be corrupted. To check, please run the following at a command prompt with administrator privileges:

winmgmt /verifyrepository

If it says the WMI repository is inconsistent, then run:

winmgmg /salvagerepository

And re-confirm by running the following command again:

winmgmt /verifyrepository

If it STILL says the WMI repository is inconsistent, then run:

winmgmt /resetrepository