Hi Tim,

I have not heard of any such problem before.  Is it only happening on a particular machine or all machines?

I recommend you run your app using the Installable Web App (IWA) deployment method instead of Web browser. and see if you still have issues  Since this is browser independent so even if your browser install is corrupted or incorrect settings it will not prevent your app from running.  If you have problems with IWA then there is something strange with your Windows installation rather than a browser issue.

By the way, we are standardizing on the IWA deployment method only for PowerServer 2021, and upgrading to PowerServer 2021 gets you a number of benefits.

Best regards,
Armeen

i have no problems with running on the most current versions of Edge or Chrome.  I am running PS2020, but i had no problems before when testing PS2019.  We have most people using the IWA since that does seem to work better, but i always use Edge.

Install issues are usually related to security. 

Maybe another plug in is causing problems, but that is pretty rare.  I only heard of that problem with Chrome.  

I keep getting the iwarunner answer from our own developer and I'm not a developer but let me explain our setup and hopefully come up with a better solution. Mind you I'm an IT Manager and manage a tech support dept that sets up hundreds of customers with software so that's the angle my opinion is coming from.

We had a powerbuilder application that had to be installed on all our customers systems (about 200 customers and multiple computers at each site) and connect to a database on our server. We needed it to be on the web so we could give them a url and just have them go there and login like any other website but our developer only knows pb so this is the solution that was came up with. Now even though it's a "web product" we still had to login to every pc, change security settings, andget it working in multiple browsers just to get it working with their main browser. This in my mind was essentially the most "un-web" web product I had seen but dealt with it because I was forced to. Now with the IWArunner as a solution it is essentially going back in time to a proprietary client server software that has to be installed on each pc and is only usuable for 1 thing which doesn't sit well with me. We also have another program which (against my wishes) we use iwa and it could be installed on these same pc's so wouldn't that cause an  issue if it's installed for 2 separate pieces of software?

We also still use a powerbuilder application in the office which calls up chrome with a url to get to one piece of software so how would we go about changing it so it calls up iwa runner instead?

So I kept researching with another developer that does not work on Appeon at all and we found this solution: http://support.appeon.com/index.php?/News/NewsItem/View/97/access-to-the-appeon-application-via-https-port-on-google-chrome-58-will-experience-the-known-issue

I replaced the file on our server and cleared out the Chrome cache then this did in fact resolve our issues with a reinstall of the appeonbrowser.exe

Thanks for all the responses though I appreciate it.

Hi all, we just started having a lot of users in a variety of locations report this issue.  Our web application is using Powerserver and PB17r2.  The appeonbrowser.exe in the link referenced in the link above is considerably larger than the old (prior under 1MB and other is ~3MB).

Is that version in the solution compatible?

solution: http://support.appeon.com/index.php?/News/NewsItem/View/97/access-to-the-appeon-application-via-https-port-on-google-chrome-58-will-experience-the-known-issue

I ask because now I can't get it start the install.  Any thoughts?

Thanks!