Downloading of service pack files for OMIMSSC 7.3 fails
Hi,
I realised that v7.3 of the OMIMSSC was released and tried to use the in-place upgrade feature. We are on v7.2 and according to the readme we can use the service packs rather than installing from scratch.
When clicking the "Check for Updates" button in the appliance admin page we get the following error:
Failed to perform the requested action. For more information, see the activity log.
In the "Appliance Logs" under "Generic Logs" I can see the following errror:
The provided repository URL " http://://" does not contain valid service pack update files. For more information on how to create a service pack update RPM repository, refer to the “Providing repository URL information for service pack updates” section in the “Installation Guide”.
I've tried multiple browsers from different systems and are getting always the same error. I doubt it is a problem with the local browser as the function is executed by the appliance. Rebooting the appliance didn't make a difference either.
Looking at the error message "The provided repository URL " http://://" does not contain valid service pack update files" sounds to me as if the configured URL is not passed through to the function performing the download.
Interestingly enough I just removed the URL and put the same URL back in to make it work. Looks like the path was showing on the screen but not used in background. Issue solved
Thorsten_S
1 Rookie
•
45 Posts
1975
0
Posted July 20th, 2021 00:00
Hi @Dell -Charles R
I've tried multiple browsers from different systems and are getting always the same error. I doubt it is a problem with the local browser as the function is executed by the appliance. Rebooting the appliance didn't make a difference either.
Looking at the error message "The provided repository URL " http://://" does not contain valid service pack update files" sounds to me as if the configured URL is not passed through to the function performing the download.
Interestingly enough I just removed the URL and put the same URL back in to make it work. Looks like the path was showing on the screen but not used in background. Issue solved
Thanks
Thorsten