ContributionsMost RecentMost LikesSolutionsRe: Unable to authenticate license in Ready API Login button unresponsive Just had to do it the once and it held .. no issues since I originally reported this ..recommend you log an official support request if it persists over and over Re: Unable to authenticate license in Ready API Login button unresponsive It is as simple as deleting these 3 files from your users/readyapi directory: license-info.dat, client-info.dat, authorization.dat Shut down ready api Delete those 3 files Start up ready api Done. Hopefully the problem goes away after that. Re: Unable to authenticate license in Ready API Login button unresponsive That is correct .. those are the 3 i deleted then restarted the application. Re: Unable to authenticate license in Ready API Login button unresponsive Solved after a callwith Smartbear .. i had to delete 3 .dat files from my users / ready api directory Unable to authenticate license in Ready API Login button unresponsive Ughhh! 3 hours wasted now. Uninstalled the latest Ready API and reinstalled. 3 days in a row now I have had to login to activate my ready api license. Today the button Login DOES NOT WORK ..so I am completely locked out of the application. The login button is completely unresponsive. No window opens to login. I am expecting a browser to open up and to login .. but nothing happens. Any suggestions / alternate paths to get authenticated? SolvedRe: Specifying a specific Schema when connecting to Postgres Database Connection Found the solution add 'searchpath' to the connection string like this: jdbc:postgresql://0.0.0.1:5432/oompaloompa?searchpath=bluesky&user=player1&password=PASS_VALUE or instead of searchpath= use currentSchema= Specifying a specific Schema when connecting to Postgres Database Connection Hi all .. I have no trouble connecting my ReadyAPI application to a Postgres database. However, I need to specify a specific schema to connect to. Say the schema i need to connect to is called bluesky how do i modify my connection string so that the queries hit that specific schema? jdbc:postgresql://0.0.0.1:5432/oompaloompa?user=player1&password=PASS_VALUE SolvedRe: SOAP Tests aren't running after updating ReadyAPI lena92 if you can't wait till next week for the new build the solution to your problem is here: https://community.smartbear.com/t5/ReadyAPI-Questions/After-upgrade-to-ReadyAPI-3-4-6-all-of-my-requests-are-failing/m-p/255277#M58371 Re: SOAP Tests aren't running after updating ReadyAPI lena92 richie This is fixed in the next version 3.5 which comes out in a week. It was introduced in the build after 3.44.1 (which I have been stuck on for many months now). Re: After upgrade to ReadyAPI 3.4.6 all of my requests are failing as security header is no longer sent Hi barto and bobkaine Fyi .. this 'problem' is fixed in the next release of Ready API 3.5 which will come out in a week's time. I never implemented the solutions proposed by you (i am confident they would work!) as I am not advanced enough to get it going .. good news the software will handle this again natively.