Forum Discussion

Nico's avatar
Nico
Occasional Contributor
5 years ago

ReadyAPI takes 450 seconds to start under Applocker

Hi

 

My company has implemented AppLocker. This means no files can be executed from the user profile, ie. from %APPDATA%.

 

Event viewer: 

%OSDRIVE%\USERS\<user>\APPDATA\LOCAL\JXBROWSER\7.1\BROWSERCORE64.EXE was prevented from running.

 

Starting from ReadyAPI v3.2.0 it takes the program 450 seconds to start up, during which I can only see a white screen. Then another 450 seconds of freezing after start-up if I hit the "wrong" element, eg. if I click 'Endpoint Explorer'.

 

After start-up the dashboard reads: Browser component disabled.

The issue persists in the latest version 3.3.2.

 

I can live w/o the browser, but waiting 450 seconds every time I start ReadyAPI is not good.

 

Can the browsercore sub-process be noved or started from another location (eg. under program files)?

Or can the browser component be disabled alltogether?

 

System: Windows 10, 64 bit.

Install dir: C:\Program Files\SmartBear\ReadyAPI-3.3.2

 

Cheers

  • I think the Support Team should take a look at this one. This would need a thorough investigation. Please file a support ticket by this link - https://support.smartbear.com/message/?prod=ReadyAPI

     

    The Community would be thankful if you post the final solution when you get it from the Support team, too! Thank you.

  • sonya_m's avatar
    sonya_m
    SmartBear Alumni (Retired)

    I think the Support Team should take a look at this one. This would need a thorough investigation. Please file a support ticket by this link - https://support.smartbear.com/message/?prod=ReadyAPI

     

    The Community would be thankful if you post the final solution when you get it from the Support team, too! Thank you.