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
- :
- Corrupted LE password in Visual Studio 2015
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
‎Sep 06, 2015
06:14 PM
Corrupted LE password in Visual Studio 2015
Cannot seem to prevent "Corrupted password" during initialization of template after new install of LE and creation of Setup project in VS2015. Re-tried clean uninstalls of LE, re-installs of LE, and trying to create a Setup project in VS 2015.
Even when I reload VS2015 after attempting to repair the password, and fetching registration text via S/N entry, the xml text message also throws an error.
Having no luck. Any suggestions?
Even when I reload VS2015 after attempting to repair the password, and fetching registration text via S/N entry, the xml text message also throws an error.
Having no luck. Any suggestions?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 08, 2015
01:55 PM
Hi,
Can you provide a screenshot of the message you are seeing?
Can you provide a screenshot of the message you are seeing?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 15, 2015
03:58 PM
If your issue is in regards to offline activation:
It looks like there was an issue with offline activations which has been resolved and a new installer has been released.
Please re-download the installer and re-install once again and you should not run into this issue going forward.
It looks like there was an issue with offline activations which has been resolved and a new installer has been released.
Please re-download the installer and re-install once again and you should not run into this issue going forward.