[ppittman]

I have copied the BES 12.4.0 package onto a server ready for install but when i run the Readiness Tool i receive the follwing error in the Installation Requirements screen.

System Verification Check

The setup application detected that the version of bes12 currently running cannot be upgraded to the latest version.

As far as I know, this version is the latest so not sure why i am receiving this error.

Any ideas?

[knottyrope]

what service pack of BES are you on now?

some version have to be upgraded in increments

[Tracert9000]

I have the same issue.
I have BES 10.2.4 on a separate server. Installing 12.4 on a new server. Readiness tool displays the same message:
The setup application detected that the version of BES12 currently running cannot be upgraded to the latest version. For more information about supported upgrades, please see Supported upgrade environments.

Do I have to install BES 12.2 first?

[ppittman]

Originally Posted by knottyrope

what service pack of BES are you on now?

some version have to be upgraded in increments

Nothing has been installed yet. I was just running the Readiness Tool to check the requirements.

[freakinvibe]

Originally Posted by ppittman

I have copied the BES 12.4.0 package onto a server ready for install but when i run the Readiness Tool i receive the follwing error in the Installation Requirements screen.

System Verification Check

The setup application detected that the version of bes12 currently running cannot be upgraded to the latest version.

As far as I know, this version is the latest so not sure why i am receiving this error.

Any ideas?

If this is a blank, vanilla server that was freshly built, this message should not appear. If you had BES on it before and just uninstalled, it might have left over some stuff, which could trigger that message.

Also, if you are pointing to an existing SQL Server, make sure it does not already have a DB with the name "BES" on it.

[ppittman]

Brand new server that has nothing but the OS installed on it.

The SQL server does already have a BES 5 DB on it so maybe that is the issue?

The new DB has already been created but called BES12mgmt so as not to clash with the original.