Highlighted

DC 2019.012.20035 again 523:523-error

New Here ,
Jul 10, 2019

Copy link to clipboard

Copied

I'm really upset right now.

We've got about 500 users that need to work with tools that integrate the reader. But the last half year we're facing the 523:523-problem again and again. Every update we get we hope to get rid of that. But all we get is "hey, have to tried to disable the protection mode?" - Yes, we have. - Like almost every user in here did. And yes, it really helps to eliminate or mostly reduce the problem so the users can work again.

But Adobe, is this all you can give us? You really know about this problem since at least 2017... Give us a valid solution instead of workarounds. We need a solution right now!

Before you ask: it happens on Win7 like on Win10 and Windows Server 2016. It happens if an application is using the reader via plugin in IE. And it's not an option to try repair the installation or create some strange registry keys or start the reader with administration rights or anything other strange stuff.

So fix it right now.

Views

262

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

DC 2019.012.20035 again 523:523-error

New Here ,
Jul 10, 2019

Copy link to clipboard

Copied

I'm really upset right now.

We've got about 500 users that need to work with tools that integrate the reader. But the last half year we're facing the 523:523-problem again and again. Every update we get we hope to get rid of that. But all we get is "hey, have to tried to disable the protection mode?" - Yes, we have. - Like almost every user in here did. And yes, it really helps to eliminate or mostly reduce the problem so the users can work again.

But Adobe, is this all you can give us? You really know about this problem since at least 2017... Give us a valid solution instead of workarounds. We need a solution right now!

Before you ask: it happens on Win7 like on Win10 and Windows Server 2016. It happens if an application is using the reader via plugin in IE. And it's not an option to try repair the installation or create some strange registry keys or start the reader with administration rights or anything other strange stuff.

So fix it right now.

Views

263

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Have something to add?

Join the conversation