Jump to content
Welcome to our new Citrix community!
  • 0

"The uploaded update package is invalid" error (after clean install)


Robert Ivens

Question

I did a clean install of Hypervisor 8 Express (april 2019 installer) on a SuperMicro SYS-5018D-FN4T that I use as a homelab. It notified me that there were 4 updates (XS80E001, 2, 3 and 4). But when I try to install any of them I get a "The uploaded update package is invalid" error.

I looked online for answers but haven't found any other then a system date issue. But the system date is correct.

I am using Citrix XenCenter 8.0 and have no VMs created yet.

 

Am I missing something? What could cause the updates to be 'invalid' ?

Link to comment

11 answers to this question

Recommended Posts

  • 0

I don't think that is the case. In older versions it would simply not allow you and tell you to buy a license. Also it worked in XenCenter a couple of months ago on another machine.

Anyway, I just tried it manually and when I uploaded the (.iso) package I get the same error but this time with the info "invalid signature error".

 

Link to comment
  • 0
8 hours ago, Tobias Kreidl said:

Hmmm, sounds like a file corruption then, despite the CRC. It is the right package for the right OS version(sorry, had to ask the obvious!)? There is enough space on the server to hold the update and then some?

There is plenty of space left (/dev/sda1 shows 11% in use), it's a 1TB drive.

 

This is the update I tried via CLI:

https://support.citrix.com/article/CTX250041


 

3 hours ago, Alan Lantz said:

And you are uploading via cli, correct ?

Correct.

Link to comment
  • 0

Hi Alan,

 

49 minutes ago, Alan Lantz said:

I bet your time is off then.

 

https://support.citrix.com/article/CTX231197

 

As I stated in my original post:

On 10/6/2019 at 3:17 PM, Robert Ivens said:

I looked online for answers but haven't found any other then a system date issue. But the system date is correct.

 

I checked the date/time and I always set it up with NTP. I even applied the ntpdate command as stated in that article which gave me the same correct date/time it already had.

So it must have been something else.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...