Upgrade to 1.9.2.2 - Base table or view already exists: 1050 Table 'mage_permission_variable' already existsSQLSTATE[42S01]: Base table or view already exists: 1050Magento admin Base table or view not found#1005 - Can't create table 'smartools.sales_flat_quote_item' (errno: -1)Move Custom Module from one set up to other in local host?Error migrating data using Data migration tool 2.0.7Magento 2 Reindex failed on customer gridSQLSTATE[42S01]: Base table or view already exists: 1050 Table 'productinquiry' already existsMigration error. The installation of the old version is startedSQLSTATE[42S01]: Base table or view already exists: 1050 Table 'eav_entity_type' already existsMagento 2 : Foreign key constraint is incorrectly formed, ALTER TABLE customer_group
"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?
Checks user level and limit the data before saving it to mongoDB
Discriminated by senior researcher because of my ethnicity
Elements that can bond to themselves?
Is there really no use for MD5 anymore?
What happens in the secondary winding if there's no spark plug connected?
Is there any official lore on the Far Realm?
Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?
Converting a sprinkler system's 24V AC outputs to 3.3V DC logic inputs
Betweenness centrality formula
On The Origin of Dissonant Chords
How do I deal with a coworker that keeps asking to make small superficial changes to a report, and it is seriously triggering my anxiety?
Rivers without rain
Why did C use the -> operator instead of reusing the . operator?
Map of water taps to fill bottles
How did Captain America manage to do this?
How to write a column outside the braces in a matrix?
Are there physical dangers to preparing a prepared piano?
How can the Githyanki Supreme Commander move while insubstantial?
"Hidden" theta-term in Hamiltonian formulation of Yang-Mills theory
Can I criticise the more senior developers around me for not writing clean code?
Can I grease a crank spindle/bracket without disassembling the crank set?
Can an Area of Effect spell cast outside a Prismatic Wall extend inside it?
bldc motor, esc and battery draw, nominal vs peak
Upgrade to 1.9.2.2 - Base table or view already exists: 1050 Table 'mage_permission_variable' already exists
SQLSTATE[42S01]: Base table or view already exists: 1050Magento admin Base table or view not found#1005 - Can't create table 'smartools.sales_flat_quote_item' (errno: -1)Move Custom Module from one set up to other in local host?Error migrating data using Data migration tool 2.0.7Magento 2 Reindex failed on customer gridSQLSTATE[42S01]: Base table or view already exists: 1050 Table 'productinquiry' already existsMigration error. The installation of the old version is startedSQLSTATE[42S01]: Base table or view already exists: 1050 Table 'eav_entity_type' already existsMagento 2 : Foreign key constraint is incorrectly formed, ALTER TABLE customer_group
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am trying to upgrade to 1.9.2.2 from 1.9.2.1 through Magento Downloader. On the little screen at the bottom I am getting the error message below:
Exception during cache and session cleaning: Error in file: "app/code/core/Mage/Admin/sql/admin_setup/upgrade-1.6.1.1-1.6.1.2.php" - SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'mage_permission_variable' already exists, query was: CREATE TABLE `mage_permission_variable` ( `variable_id` int UNSIGNED NOT NULL auto_increment COMMENT 'Variable ID' , `variable_name` varchar(255) NOT NULL default '' COMMENT 'Config Path' , `is_allowed` bool NOT NULL default '0' COMMENT 'Mark that config can be processed by filters' , PRIMARY KEY (`variable_id`, `variable_name`), UNIQUE `UNQ_MAGE_PERMISSION_VARIABLE_VARIABLE_NAME` (`variable_name`) ) COMMENT='System variables that can be processed via content filter' ENGINE=INNODB charset=utf8 COLLATE=utf8_general_ci.........................
It repeats this quite a few times and then just stays there and the website is broken.
I'm not at all technical with Magento - could someone help me diagnose what's wrong and how I fix it (in as simple steps as possible!)?
magento-1.9 database error table ce-1.9.2.2
edited Nov 6 '15 at 11:40
7ochem
5,86493770
asked Nov 6 '15 at 11:33
user32880user32880
62
bumped to the homepage by Community♦ 6 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am trying to upgrade to 1.9.2.2 from 1.9.2.1 through Magento Downloader. On the little screen at the bottom I am getting the error message below:
Exception during cache and session cleaning: Error in file: "app/code/core/Mage/Admin/sql/admin_setup/upgrade-1.6.1.1-1.6.1.2.php" - SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'mage_permission_variable' already exists, query was: CREATE TABLE `mage_permission_variable` ( `variable_id` int UNSIGNED NOT NULL auto_increment COMMENT 'Variable ID' , `variable_name` varchar(255) NOT NULL default '' COMMENT 'Config Path' , `is_allowed` bool NOT NULL default '0' COMMENT 'Mark that config can be processed by filters' , PRIMARY KEY (`variable_id`, `variable_name`), UNIQUE `UNQ_MAGE_PERMISSION_VARIABLE_VARIABLE_NAME` (`variable_name`) ) COMMENT='System variables that can be processed via content filter' ENGINE=INNODB charset=utf8 COLLATE=utf8_general_ci.........................
It repeats this quite a few times and then just stays there and the website is broken.
I'm not at all technical with Magento - could someone help me diagnose what's wrong and how I fix it (in as simple steps as possible!)?
magento-1.9 database error table ce-1.9.2.2
edited Nov 6 '15 at 11:40
7ochem
5,86493770
asked Nov 6 '15 at 11:33
user32880user32880
62
bumped to the homepage by Community♦ 6 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
I saw another post and if I delete 'upgrade-1.6.1.1-1.6.1.2.php' then everything appears to work. Is it OK to just delete this file or will it cause me problems in the future?
– user32880
Nov 6 '15 at 19:57
i think you already had applied patch-6788 that creates variable and permissions block. So do not delete the file just comment out that sql code and run setup. After successful run uncomment code.
– Gulshan Maurya
Sep 9 '16 at 5:37
add a comment |
I am trying to upgrade to 1.9.2.2 from 1.9.2.1 through Magento Downloader. On the little screen at the bottom I am getting the error message below:
Exception during cache and session cleaning: Error in file: "app/code/core/Mage/Admin/sql/admin_setup/upgrade-1.6.1.1-1.6.1.2.php" - SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'mage_permission_variable' already exists, query was: CREATE TABLE `mage_permission_variable` ( `variable_id` int UNSIGNED NOT NULL auto_increment COMMENT 'Variable ID' , `variable_name` varchar(255) NOT NULL default '' COMMENT 'Config Path' , `is_allowed` bool NOT NULL default '0' COMMENT 'Mark that config can be processed by filters' , PRIMARY KEY (`variable_id`, `variable_name`), UNIQUE `UNQ_MAGE_PERMISSION_VARIABLE_VARIABLE_NAME` (`variable_name`) ) COMMENT='System variables that can be processed via content filter' ENGINE=INNODB charset=utf8 COLLATE=utf8_general_ci.........................
It repeats this quite a few times and then just stays there and the website is broken.
I'm not at all technical with Magento - could someone help me diagnose what's wrong and how I fix it (in as simple steps as possible!)?
magento-1.9 database error table ce-1.9.2.2
edited Nov 6 '15 at 11:40
7ochem
5,86493770
asked Nov 6 '15 at 11:33
user32880user32880
62
I am trying to upgrade to 1.9.2.2 from 1.9.2.1 through Magento Downloader. On the little screen at the bottom I am getting the error message below:
Exception during cache and session cleaning: Error in file: "app/code/core/Mage/Admin/sql/admin_setup/upgrade-1.6.1.1-1.6.1.2.php" - SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'mage_permission_variable' already exists, query was: CREATE TABLE `mage_permission_variable` ( `variable_id` int UNSIGNED NOT NULL auto_increment COMMENT 'Variable ID' , `variable_name` varchar(255) NOT NULL default '' COMMENT 'Config Path' , `is_allowed` bool NOT NULL default '0' COMMENT 'Mark that config can be processed by filters' , PRIMARY KEY (`variable_id`, `variable_name`), UNIQUE `UNQ_MAGE_PERMISSION_VARIABLE_VARIABLE_NAME` (`variable_name`) ) COMMENT='System variables that can be processed via content filter' ENGINE=INNODB charset=utf8 COLLATE=utf8_general_ci.........................
It repeats this quite a few times and then just stays there and the website is broken.
I'm not at all technical with Magento - could someone help me diagnose what's wrong and how I fix it (in as simple steps as possible!)?
magento-1.9 database error table ce-1.9.2.2
magento-1.9 database error table ce-1.9.2.2
edited Nov 6 '15 at 11:40
7ochem
5,86493770
asked Nov 6 '15 at 11:33
user32880user32880
62
edited Nov 6 '15 at 11:40
7ochem
5,86493770
asked Nov 6 '15 at 11:33
user32880user32880
62
edited Nov 6 '15 at 11:40
7ochem
5,86493770
edited Nov 6 '15 at 11:40
7ochem
5,86493770
edited Nov 6 '15 at 11:40
7ochem
5,86493770
5,86493770
asked Nov 6 '15 at 11:33
user32880user32880
62
asked Nov 6 '15 at 11:33
user32880user32880
62
asked Nov 6 '15 at 11:33
user32880user32880
62
62
bumped to the homepage by Community♦ 6 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 6 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
I saw another post and if I delete 'upgrade-1.6.1.1-1.6.1.2.php' then everything appears to work. Is it OK to just delete this file or will it cause me problems in the future?
– user32880
Nov 6 '15 at 19:57
i think you already had applied patch-6788 that creates variable and permissions block. So do not delete the file just comment out that sql code and run setup. After successful run uncomment code.
– Gulshan Maurya
Sep 9 '16 at 5:37
add a comment |
1
I saw another post and if I delete 'upgrade-1.6.1.1-1.6.1.2.php' then everything appears to work. Is it OK to just delete this file or will it cause me problems in the future?
– user32880
Nov 6 '15 at 19:57
i think you already had applied patch-6788 that creates variable and permissions block. So do not delete the file just comment out that sql code and run setup. After successful run uncomment code.
– Gulshan Maurya
Sep 9 '16 at 5:37
1
1
I saw another post and if I delete 'upgrade-1.6.1.1-1.6.1.2.php' then everything appears to work. Is it OK to just delete this file or will it cause me problems in the future?
– user32880
Nov 6 '15 at 19:57
I saw another post and if I delete 'upgrade-1.6.1.1-1.6.1.2.php' then everything appears to work. Is it OK to just delete this file or will it cause me problems in the future?
– user32880
Nov 6 '15 at 19:57
i think you already had applied patch-6788 that creates variable and permissions block. So do not delete the file just comment out that sql code and run setup. After successful run uncomment code.
– Gulshan Maurya
Sep 9 '16 at 5:37
i think you already had applied patch-6788 that creates variable and permissions block. So do not delete the file just comment out that sql code and run setup. After successful run uncomment code.
– Gulshan Maurya
Sep 9 '16 at 5:37
add a comment |
1 Answer
1
active
oldest
votes
That means you already have the mage_permission_variable table in your database.
Don't delete the file instead of you can drop mage_permission_variable and mage_permission_block table then continue you upgrading process
it will do the trick....
Don't forget to backup the database before dropping those tables
Hope it helps
edited Aug 9 '16 at 14:44
7ochem
5,86493770
answered Nov 21 '15 at 5:52
Ruban KuttyRuban Kutty
1
2
These tables are from a previous patch the OP has maybe installed. The tables might have some custom values - I mean, at least themage_permission_blocktable will have entries. He should not simply drop them, because blocks that are not in the default configuration will miss from the frontend.
– simonthesorcerer
Apr 13 '17 at 22:25
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f89150%2fupgrade-to-1-9-2-2-base-table-or-view-already-exists-1050-table-mage-permiss%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
That means you already have the mage_permission_variable table in your database.
Don't delete the file instead of you can drop mage_permission_variable and mage_permission_block table then continue you upgrading process
it will do the trick....
Don't forget to backup the database before dropping those tables
Hope it helps
edited Aug 9 '16 at 14:44
7ochem
5,86493770
answered Nov 21 '15 at 5:52
Ruban KuttyRuban Kutty
1
2
These tables are from a previous patch the OP has maybe installed. The tables might have some custom values - I mean, at least themage_permission_blocktable will have entries. He should not simply drop them, because blocks that are not in the default configuration will miss from the frontend.
– simonthesorcerer
Apr 13 '17 at 22:25
add a comment |
That means you already have the mage_permission_variable table in your database.
Don't delete the file instead of you can drop mage_permission_variable and mage_permission_block table then continue you upgrading process
it will do the trick....
Don't forget to backup the database before dropping those tables
Hope it helps
edited Aug 9 '16 at 14:44
7ochem
5,86493770
answered Nov 21 '15 at 5:52
Ruban KuttyRuban Kutty
1
2
These tables are from a previous patch the OP has maybe installed. The tables might have some custom values - I mean, at least themage_permission_blocktable will have entries. He should not simply drop them, because blocks that are not in the default configuration will miss from the frontend.
– simonthesorcerer
Apr 13 '17 at 22:25
add a comment |
That means you already have the mage_permission_variable table in your database.
Don't delete the file instead of you can drop mage_permission_variable and mage_permission_block table then continue you upgrading process
it will do the trick....
Don't forget to backup the database before dropping those tables
Hope it helps
edited Aug 9 '16 at 14:44
7ochem
5,86493770
answered Nov 21 '15 at 5:52
Ruban KuttyRuban Kutty
1
That means you already have the mage_permission_variable table in your database.
Don't delete the file instead of you can drop mage_permission_variable and mage_permission_block table then continue you upgrading process
it will do the trick....
Don't forget to backup the database before dropping those tables
Hope it helps
edited Aug 9 '16 at 14:44
7ochem
5,86493770
answered Nov 21 '15 at 5:52
Ruban KuttyRuban Kutty
1
edited Aug 9 '16 at 14:44
7ochem
5,86493770
edited Aug 9 '16 at 14:44
7ochem
5,86493770
edited Aug 9 '16 at 14:44
7ochem
5,86493770
5,86493770
answered Nov 21 '15 at 5:52
Ruban KuttyRuban Kutty
1
answered Nov 21 '15 at 5:52
Ruban KuttyRuban Kutty
1
answered Nov 21 '15 at 5:52
Ruban KuttyRuban Kutty
1
1
2
These tables are from a previous patch the OP has maybe installed. The tables might have some custom values - I mean, at least themage_permission_blocktable will have entries. He should not simply drop them, because blocks that are not in the default configuration will miss from the frontend.
– simonthesorcerer
Apr 13 '17 at 22:25
add a comment |
2
These tables are from a previous patch the OP has maybe installed. The tables might have some custom values - I mean, at least themage_permission_blocktable will have entries. He should not simply drop them, because blocks that are not in the default configuration will miss from the frontend.
– simonthesorcerer
Apr 13 '17 at 22:25
2
2
These tables are from a previous patch the OP has maybe installed. The tables might have some custom values - I mean, at least the
mage_permission_block table will have entries. He should not simply drop them, because blocks that are not in the default configuration will miss from the frontend.– simonthesorcerer
Apr 13 '17 at 22:25
These tables are from a previous patch the OP has maybe installed. The tables might have some custom values - I mean, at least the
mage_permission_block table will have entries. He should not simply drop them, because blocks that are not in the default configuration will miss from the frontend.– simonthesorcerer
Apr 13 '17 at 22:25
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f89150%2fupgrade-to-1-9-2-2-base-table-or-view-already-exists-1050-table-mage-permiss%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I saw another post and if I delete 'upgrade-1.6.1.1-1.6.1.2.php' then everything appears to work. Is it OK to just delete this file or will it cause me problems in the future?
– user32880
Nov 6 '15 at 19:57
i think you already had applied patch-6788 that creates variable and permissions block. So do not delete the file just comment out that sql code and run setup. After successful run uncomment code.
– Gulshan Maurya
Sep 9 '16 at 5:37