In case of problems

Top  Previous  Next

BAD DOWNLOAD: "NOT A VALID WIN32 EXECUTABLE"

A common reason for OAK to fail to install is that the file that has been downloaded is incomplete, or, less often, corrupted. The usual signal that this is the case is that your computer complains that the file is "not a valid WIN/32 executable". If this proves to be a persistent problem, email oak@operis.com for an alternative.

OAK RIBBON NOT SHOWING - Excel displays message stating that some 'non-trusted' content was disabled.

1) Notice that when you open a blank workbook in Excel, there is a yellow alert bar under the ribbon which says that Excel is blocking some not-trusted content

2) Click 'More info' (i.e. not 'Enable')

3) For each of your trusted add-in publishers, select 'always allow code from this publisher to run', then confirm the dialog

4) Restart Excel

GOOD DOWNLOAD: no action or SELF TESTS FAIL

Some workstations, particularly ones that are locked down in secure environments, may present obstacles to the normal installation process. You may be told directly that you don't have the necessary privileges to install software on that machine, and your computer won't run the OAK installer at all. Alternatively, the installation may appear to happen, but be prevented from doing some necessary thing when it tries to.

This has proved to be a significant issue among the many users of the OAK3, who operated in security conscious businesses in financial services. The setup programs of OAK4 and OAK5 have therefore been engineered to perform a variety of preinstallation tests, to inspect the environment in which it finds itself and form an impression (but not a certainty) of the likelihood that OAK will run without problems.

If one or more of those tests fail, the OAK installer will display the results of all of the tests.

Preinstallation tests 1

Operis will likely ask to see the output from the installer in preinstallation test mode where users are having difficulty installing the product; or an organization's IT department may find it gives all that is needed to overcome installation obstacles. A text summary of the tests suitable for emailing can be generated by pressing the Report button.

OAK CAN NOT LOGIN / REACH THE SERVER

As OAK is now relying on an external provider to hold the licensing system, your IT infrastructure might have firewall rules in place that prevents OAK from reaching those licensing servers and validate your subscription. If that's the case you will need to ask your IT support to whitelist the following addresses / ports:

api.licensespring.com - ports 443 and 80

saas.licensespring.com - ports 443 and 80

 

PROXY SETTINGS

Some IT infrastructures have proxy servers installed that will receive all requests to the Internet (and therefore OAK requests for authenticate the user on OAK's licensing servers provided by LicenseSpring), evaluate the request and forward it to the Internet. Likewise, responses come back to the proxy server and then to OAK.

If a proxy server is present OAK will need to know the proxy server's address and the username / password if these are required to access it - please check with your IT administrator for the required details.

The OAK proxy settings can be inserted through the OAK / Settings button:

ProxySettings1

After inserting the required proxy details, press the OK button and try to login again on the Account task pane at the right. OAK will now be able to reach the Licensespring server and validate your OAK subscription.

AUTHORIZING OAK ON THE WINDOWS FIREWALL

Another reason why OAK might not recognize your login credentials is that your windows Firewall settings are not authorizing OAK to make external calls. To authorize OAK on your Windows Firewall please follow the procedures below:

1) Type firewall into the Windows Start box and select “Allow an app through Windows Firewall”.  (If this doesn’t appear, find it manually through the control panel)

 

WindowsFirewall01

 

2) Assuming “Operis Analysis Kit” doesn’t appear in the list of “Allowed apps and features”, click “Change Settings” and then “Allow another app…”

WindowsFirewall02

 

 

3) In “Add an app”, select “Browse…”, then in the directory bar at the top type “%localappdata%\programs\Operis\OAK5 and press return:

 

WindowsFirewall03

When the directory resolves, navigate to “Operis/OAK5” and select “Operis.OAK.Exe”

4) Select “Add” in the “Add an app” screen, then press OK on the original “Allowed applications” screen.

You should now be able to log into OAK5.

 

See also

Forcing preinstallation testing

Disabled Items