Getting CM-CFG-5024 error on content store upgrade when upgrading to Cognos BI 10.2.2 - upgrade

Tried to upgrade one Cognos instance from 10.2.1 -> 10.2.2
Existing 10.2.1 works just fine.
Uninstalled 10.2.1 and installed 10.2.2 as per documentation. When trying to start the Cognos service i get a message i haven't seen before during upgrade.
CM-CFG-5024
Screenshot:

The safest way to do the upgrade is to export the whole Content Store. Upgrade with a new/empty database and reimport the content.
This procedure will help guide you for the export and import the Content Store:
http://www-01.ibm.com/support/docview.wss?uid=swg21340892

There seems to be an open defect for the symptoms you see.
PI47878 - UNABLE TO UPGRADE AN IBM COGNOS 10.2.1 FP8 CONTENT STORE TO10.2.2
Here is the link from IBM SUPPORT PORTAL

Related

Restore Moodle Backup issues: error reading from database

I am trying to restore a backup of Moodle version 2.7 with PHP 5.5 and MySQL 5.5 from one server to another server with Moodle 3.9 and PHP 7.4 and MySQL 8.0. But I am getting the following error:
I even tried the to change ##default_storage_engine to ##storage_engine in /lib/dml/mysqli_native_moodle_database.php but still not working. I also verified the disk space. There is enough space on the disk.
You need to follow an upgrade path from Moodle 2.7
https://docs.moodle.org/311/en/Upgrading_FAQ#How_do_I_upgrade_from_1.9.x_to_3.11.3F
First install Moodle 2.7.20 on the new server and restore the database.
Then upgrade to Moodle 3.2.9
Then you can upgrade to Moodle 3.9.x
Note that you will need to upgrade any additional plugins that were installed too. I'd recommend doing this at each upgrade stage for each version.
If you haven't already, you will also need to back up the site data folder at the same time as the database backup. The site data folder contains uploaded files, these are not stored in the database. As well as custom languages.
https://docs.moodle.org/39/en/Upgrading

Getting error in AWS toolkit for Visual Studio: Error loading AWS profile

I have installed AWS SDK toolkit for VS 2017. It was working fine. All of a sudden since few days back i am getting error "Error loading AWS profiles: Method not found:'Amazon.Runtime.TcpKeepAlive Amazon.Runtime.ClientConfig.get_TcpKeepAlive()"
I have tried uninstalling and reinstalling the toolkit, also i tried installing it on other machine with VS 2013, but both giving same error.
Is it problem with toolkit or anything changed on AWS side?
I have Windows 10 with latest updates.
VS2017 community edition
VS2013 community edition
Thanks in advance.
It is mostly caused an older version of AWSSDK.core that has already been added to GAC and is forcing your VS to use an older version of AWSSDK.core.dll.
After uninstalling all the other/previous versions of AWSSDK libraries (AWSSDK.S3.dll etc) from GAC solved the problem for me.
Also installing the latest AWSSDK.core.dll to GAC can work.
Hope this info helps someone.
Solution here that worked for me :
https://github.com/aws/aws-sdk-net/issues/1138
I have resolved this issue by uninstalling the latest one and installing this previous stable version of aws toolbar from visual studio update website(exact link https://aws.amazon.com/visualstudio where previous vsix downloaded).. if you cannot find the previous version here I added to my drive you can download.. https://drive.google.com/open?id=1Fkrxmv-dM8fwGDjNqse1Ssdm0k3YYbcH
Once you install old extention, be sure to disable auto update extension in VS.

Xcart upgrade from 4.6.2 to 4.7.5

I am trying to upgrade my Xcart 4.6.2 to 4.7.5. I followed the documentioan exactly as mentioned here http://help.x-cart.com/index.php?title=X-Cart:Upgrading#Upgrading_from_version_4.7.0_or_later
However the software is updated and the db remains the same. I said because when I check http://wwww.example/VERSION it says 4.7.5 and when I check http://www.example.com/include/version.php it says X-Cart DB Version: 4.6.2 GOLD.
I did the following steps :
made a development copy of live site in server.
made a fresh installation of the xcart 4.6.2 and pointed the db to the development copy
Downloaded the 4.6.2-4.7.2 upgrade package, extracted it to the root and ran the upgrade from backend. No errors.
I checked http://wwww.example.com/VERSION it says 4.7.2 and http://www.example.com/include/version.php it says X-Cart DB Version: 4.6.2 GOLD
Do you guys faced such issue? Your advises are very much appreciated. Thanks in advance.
Most likely something goes wrong while applying the sql patch (upgrade/4.6.2-4.7.2/patch.sql) because
UPDATE xcart_config SET value = "4.7.2" WHERE name = "version";
is at the very end of it.
So, please, check the following logs for anything out of the ordinary:
var/upgrade/4.6.2-4.7.2/patch.log
var/log/x-errors_sql-.php

Upgrade from mysql 4.1 to mysql 5.5

I was going through upgrade process of mysql server. It is mentioned that to upgrade from 4.1 to 5.5 we need to upgrade step by step like first to 5.0,5.1 ...5.4 and then 5.5.
I have some questions :
What if we directly upgrade from 4.1 to 5.5. What might get effected? functionality or problem related to upgrading
Chances to loose data ? Even though I'll take backup using 'mysqldump --all-data-base' option.
Lets say, I have two database. I'll take only two database backup. I'll install latest version of mysql 5.7 and load two database back. What are chances to loose data or get corrupted ?
I'm curious to know this. If anybody tried? Because I need to do upgrade in live server.
Is there any step by step document which tells exact steps to upgrade from 4.1 to 5.5 in linux server
Major new features added to MySQL 5.0 and 5.1 that may not work/won't work in 4.x can be located here:
MySQL 5.0 - http://dev.mysql.com/doc/refman/5.0/en/mysql-nutshell.html
MySQL 5.1 - http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

Upgrading SugarCRM

I have a problem when upgrading Sugarcrm from 6.2 to 6.3 version. When I upgrade a local Sugarcrm installation it works but when I start upgrading my Sugarcrm 6.2 site and uploading the upgrade package it doesnt upload.
The same thing works on local server rather than the remote server of same version.
If you are using the in-app upgrade wizard, perhaps this blog post may help...
http://developers.sugarcrm.com/wordpress/2011/04/27/howto-get-around-file-upload-size-limit-issues/
Upgrade wizard has lot of limitation. Try silent upgrader. That will help