- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Re: Inplace upgrade from R80.40 to R81 is failing
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Inplace upgrade from R80.40 to R81 is failing
Hi All,
I am trying to upgrade R80.40 to R81 on open server and its failing with below update.
Any clue or do I need to adopt offline upgrade?
Result: Verifier results Package: R81 Gaia Fresh Install and upgrade Clean Install: Installation is allowed. Upgrade: The following results are not compatible with the package:
- Verification failed:
1. Operation is not supported. There are locked objects on published, discarded or non-existing worksession in DB. Please address sk123346 for a fix.
Notes: 1. It is recommended to use the latest upgrade tools package. The latest package is installed automatically on online environments, for upgrade of offline environments refer to sk135172.
2. Only latest revision will be upgraded. It is recommended to publish important changes before upgrade. Unpublished changes will be lost.
3. Run the upgrade verification on all servers in your environment before you upgrade.
This installation package is not supported on Cloud environments.
This installation package may not be supported on your appliance model.
For the latest software images, see sk166536
This installation package may not be supported on your server.
For R81 Open Server support, see sk166715.
In-place upgrade is not supported for CloudGuard IaaS
ClusterXL in Load Sharing mode with IPSec VPN blade enabled cannot be upgraded to R81. For more information see sk162637.
To upgrade management machine from R80.10 and lower, first upgrade to R80.40 and only then upgrade to R81.
To upgrade gateway machine from R77.20 and lower, first upgrade to R80.40 and only then upgrade to R81
Blason R
CCSA,CCSE,CCCS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Have you followed the sk123346 as per the verifier output?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No sk is showing up when searched for sk123346
Blason R
CCSA,CCSE,CCCS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's an internal SK that TAC can work through with you where required.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you've followed the notes, resolved any that apply and the issue persists I would contact TAC for assistance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yep - eventually have involved the TAC.
Blason R
CCSA,CCSE,CCCS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please keep us posted about this case. We're planning to do the same and would appreciate additional information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Regarding the first item on the CPU Verification message you received, did you use the latest Upgrade Tools and checked for open sessions or locked objects?
Operation is not supported. There are locked objects on published, discarded or non-existing worksession in DB. Please address sk123346 for a fix.
Notes: 1. It is recommended to use the latest upgrade tools package. The latest package is installed automatically on online environments, for upgrade of offline environments refer to sk135172.
Thanks
Tal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had the same Problem and got a script from TAC to delete locks directly from the database (deleteLockedObjects.sh).
After running the script verifier was OK.
