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
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Seeing the same thing in IA 2017
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
Oct 26, 2017
02:48 AM
Problems in the begining of the build : UpdateServiceException
Hi,
I was using Installanywhere2015 to package out product. But recently it pops up errors like:
This wasn't happened on last month's build, I 'm wondering why it's there now since I didn't change anything between the period.
Is there something wrong with the license server?
I just did "./build -unregister"and "./build -ls 27000@" and it returned successfully (You have successfully registered this copy of InstallAnywhere.).
So is there any other to verify whether the license server is fine?
I was using Installanywhere2015 to package out product. But recently it pops up errors like:
UpdateService-Err>isus.UpdateServiceException: The server digitally signed its response with an untrusted certificate. Bad chain.
This wasn't happened on last month's build, I 'm wondering why it's there now since I didn't change anything between the period.
Is there something wrong with the license server?
I just did "./build -unregister"and "./build -ls 27000@
So is there any other to verify whether the license server is fine?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 03, 2017
03:14 PM
We're seeing the same error with IA 2017.
It looks like the error is the communication between IA and it's Update Service. Besides the reported errors during automated builds, it's causing the automated builds and the IA GUI to take longer to start up. Which is killing the change/build/debug cycle with installers.
It looks like the error is the communication between IA and it's Update Service. Besides the reported errors during automated builds, it's causing the automated builds and the IA GUI to take longer to start up. Which is killing the change/build/debug cycle with installers.