1. Home
  2. Troubleshooting
  3. Installation Issues
  4. Troubleshooting Installation issues on Windows OS

Troubleshooting Installation issues on Windows OS

Can’t download the AimBetter_Agent.zip program

This is very unusual, but if you have this problem, please inform our support team of it at [email protected].

Check that your Windows OS user has Administrator privileges

Open the Command Prompt by clicking on the Windows Start menu and typing “cmd” in the search box. Type the following command:

net localgroup administrators

If your user is not in the Administrator list, it doesn’t have administrator privileges.

To install the AimBetter Agent, you need Administrator privileges. After installation, you can switch the user that runs the AimBetter Agent service to a  Minimal Permissions User.

Can’t run the AimBetter_Agent.zip program

— Possibility 1- Lack of administrator privileges

Check that your Windows OS user has administrator privileges to install this program, as explained in the above session.

— Possibility 2- Some programs may be blocking it from running.

You should check if there is some EDR or anti-virus program impending the running of the AimBetter_Agent program.

Enable every configuration related to “aimbetter” or “montarget” domains.

After checking that there is no problem with administrator privileges or blocking programs, if you still cannot run the AimBetter_Agent program, please inform our support team of it at [email protected].

The AimBetter Configuration App

After running the AimBetter_Agent program, the AimBetter Configuration App will automatically open and ask for the information needed to complete the installation.

If there is some issue with the installation from this stage on, red lights in the AimBetter Configuration App will indicate the reason.

When there is a “More Info” button, or an “info” icon beside the red light, you should click it to receive an indication the problem probable reason.

— Restart the AimBetter Agent Service

After any change in the AimBetter Configuration, restart the AimBetter Service Agent service.

To restart the AimBetter Agent service, go to “Settings” at the top right of the AimBetter Configuration, click on Stop, and then on Start.

Don’t have a License key

— Possibility 1 – You don’t have an Account

You should create an account using the Signup form.

After filling up this form, you should receive an “AimBetter Account Confirmation” email in which you’ll be requested to verify your email address.

After the verification email, you should receive a “Welcome to AimBetter” email with your License Key and Identifier.

— Possibility 2 – You have an account but cannot find the License key

You can try looking for the “Welcome to AimBetter” email in your inbox. If you still can’t find it, please contact the AimBetter team at [email protected], attaching your email or phone number.

Make sure to insert the License key and Identifier exactly as they appear in your “Welcome to AimBetter” email, without spaces or missing characters.

Proxy Configuration

If there is a Proxy server that needs to be configured, a popup message will appear requesting to insert the Proxy address. You should insert the exact details of the Proxy server in this window and click OK.

Click here for more details about Proxy Configuration.

Server Status light is red

Click on the “More Info” button or the “info” icon beside the Server Status red light to get an indication of the issue probable reason

— Possibility 1 – The server is down

Check that the Server is on.

— Possibility 2 – The server IP/Name is wrong

If the IP/Name inserted when adding a server in the AImBetter Configuration program is not correct, a “Failed to Connect to server” error will appear.

If the installation is “Local”, insert a dot ( . ) to the IP/Name field.

To check the correct name of the server, you can open the cmd and type hostname.

You can edit the IP/ Name by clicking on the Edit button at the end of the Server Status row beneath the Password field.

— Possibility 3 – The server clock is not sync

If the message when clicking “More Info” is “Client time and API time out of sync” (as in the following image), it is because the server’s clock is not synchronized with AimBetter’s API clock, which follows the NIST-F1 official standard. The solution is configuring the server clock to the right time – this can only be done by the customer himself, adjusting the server’s clock to the correct time.

The client’s time is behind the correct time

— Possibility 4 – TLS 1.2 is not enabled

If the message when clicking “More Info” relates to a “Secure Channel Failure” (as in the following image), you should check if TLS 1.2 is enabled.

Service Status light is red

Click on “info” beside the Service Status red light to get an indication of the issue probable reason

— Possibility 1 – Lack of administrator privileges

When installing the AimBetter Agent, you should be logged in with a user that has administrator privileges. To check that the user you are logged in has administrator privileges, make the following check.

After installation, you can change the user who runs the AimBetter Agent Service to one with the minimum required permissions.

Ensure the AimBetter Agent service user has reading and writing permission over the AimBetter folder (C:\Program Files (x86)\AimBetter).

— Possibility 2- Some programs may be blocking it from running.

You should check if an EDR or anti-virus program is impeding the running of the AimBetter_Agent service or deleting files in the AimBetter folder created during the installation.

Enable every configuration related to “aimbetter” or “montarget” domains or the AimBetter folder C:\Program Files (x86)\AimBetter.

— Possibility 3 – There is some broken performance counter

After checking that the user running the AimBetter Agent has all the minimum required user permissions if the Service Status is still red, this may be caused by some broken performance counter. The solution is to rebuild these counters through the following procedure.

Open CMD (command prompt program) as administrator, and run the following scripts:

Script 1

cd c:\windows\system32
     lodctr /R

Script 2

cd c:\windows\sysWOW64
     lodctr /R

API Status light is red

Click on “info” beside the API Status red light to get an indication of the issue probable reason

— Possibility 1 – There is a Proxy server that needs to be configured

Check Proxy Settings.

— Possibility 2 – There is some Firewall blocking

Check Firewall Settings requirements.

–Possibility 3 – There is some Antivirus or other Cybersecurity application blocking

Check that access to https://api.aimbetter.com/ is allowed in the cybersecurity application configuration.

— Possibility 4 – No Internet outbound traffic through Port 443 to https://api.aimbetter.com/

Check Agent’s System requirements, especially regarding Internet access (Port 443).

As part of these requirements, check that the .NET framework is updated and that TLS 1.2 is supported

— Possibility 5 – The AimBetter Agent Service has stopped

Check AimBetter Agent Service Settings.

WMI Status light is red

Click on the “More Info” button besides the WMI Status red light to get an indication of the issue probable reason

— Possibility 1 – Lack of administrator privileges

When installing the AimBetter Agent, you should be logged in as a user who has administrator privileges. To check that the user you are logged in as has administrator privileges, make the following check.

After installation, you can change the user who runs the AimBetter Agent Service to one who has the minimum required permissions.

Ensure the AimBetter Agent service user has reading and writing permission over the AimBetter folder (C:\Program Files (x86)\AimBetter).

— Possibility 2 – There is some Firewall blocking

Check Firewall Settings requirements.

— Possibility 3 – The DCOM Settings are nor correct

Check DCOM Settings and Ping requirements.

— Possibility 4 – The AimBetter Agent Service is not running

Check AimBetter Agent Service Settings.

— Possibility 5 – The WMI Services are not running

Check WMI Services Settings.

— Possibility 6 – The is some issue with WMI that needs to be investigated

Check WMI Debug.

SQL Server Status light is red

Click on the “More Info” button besides the SQL Server Status red light to get an indication of the issue probable reason

— Possibility 1 – There is some Firewall blocking

Check Firewall Settings requirements.

— Possibility 2 – The AimBetter Agent Service is not running

Check AimBetter Agent Service Settings.

— Possibility 3 – MSSQL Credentials issue

Check MSSQL Credentials.

— Possibility 4 – MSSQL Port Settings issue

Check MSSQL Port Settings.

— Possibility 5 – SQL Server Services are not running

Check SQL Services Settings.

Oracle Status light is red

Click on the “More Info” button besides the SQL Server Status red light to get an indication of the issue probable reason

— Possibility 1 – There is some Firewall blocking

Check Firewall Settings requirements.

— Possibility 2 – The AimBetter Agent Service is not running

Check AimBetter Agent Service Settings.

— Possibility 3 – Oracle Services are not running

Check Oracle Services Settings.

Web Server installation issues

— Possibility 1 – Program blocked by group policy

Check IIS – Error: Program blocked by group policy

— Possibility 2 – No data in AppPools and Websites Tabs

Check IIS – No data in AppPools and Websites Tabs

Still couldn’t fix the issue? Send us AimBetter folder logs

If the previous checks and procedures didn’t solve all the issues with the AimBetter Installation, please follow the next steps:

— Step 1 – Stop the AimBetter Agent service

— Step 2 – Go to the AimBetter Agent log folder and delete all its files.

The path to this folder is C:\Program Files (x86)\AimBetter\Monitor\Agent_log

— Step 3 – Restart the AimBetter Agent Service

To restart the AimBetter Agent service, go to “Settings” at the top right of the AimBetter Configuration, click on “Stop,” and then on “Start.”

— Step 4 – Go to the AimBetter Agent log folder, copy all its files, and send them to us.

Go once more to the AimBetter Agent log folder in this path C:\Program Files (x86)\AimBetter\Monitor\Agent_log

Copy all its files and send them to [email protected]. We’ll be in contact with you shortly to give further assistance.

Was this article helpful?

On This Page