This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: InstallShield 2012 License Corruption error
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 24, 2017
09:32 AM
InstallShield 2012 License Corruption error
When attempting to start Installshield, I get a license corruption error. The activation also fails with error 50041 "Failed to connect to the license server". A Wireshark trace hints that the TLS handshake sequence failed.
I'm going through the Email activation, but I'm curious about what leads to this condition? This comes to mind -
I'm going through the Email activation, but I'm curious about what leads to this condition? This comes to mind -
A long time period elapses between invocations of InstallShield. In the meantime, even though it's on the same computer, same Windows, and same hard drive, the BIOS has been updated and there are many Windows patches. This sort of licensing is this exact reason that I try to avoid using Installshield in the first place. I have successfully worked Installshield out of many other software packages, but when I need it for this package, I need it now, not after fiddling around with the license.
TLS security standards change, causing the InstallShield 2012 activation handshake to be out of date.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 12, 2017
01:47 PM
bikeoid wrote:
When attempting to start Installshield, I get a license corruption error. The activation also fails with error 50041 "Failed to connect to the license server". A Wireshark trace hints that the TLS handshake sequence failed.
I'm going through the Email activation, but I'm curious about what leads to this condition? This comes to mind -
A long time period elapses between invocations of InstallShield. In the meantime, even though it's on the same computer, same Windows, and same hard drive, the BIOS has been updated and there are many Windows patches. This sort of licensing is this exact reason that I try to avoid using Installshield in the first place. I have successfully worked Installshield out of many other software packages, but when I need it for this package, I need it now, not after fiddling around with the license.
TLS security standards change, causing the InstallShield 2012 activation handshake to be out of date.
I have the same problem and support is very lacking. I guess they dont care to loose their customer base.