macopedia / magmi-m2

Magmi GitHub, see branch magento2 for a version compatible with Magento 2
113 stars 53 forks source link

SQLSTATE[42000]: Syntax error or access violation: 1142 TRIGGER command denied to user #79

Closed gfxguru closed 4 years ago

gfxguru commented 4 years ago

// Provide a general summary of the issue in the Title above Getting error msg trying to import products. The error occurs on the SKU column.

csv example attached.

Preconditions

// Provide a more detailed information about you Magento, Apache2/nginx, PHP & MySQL version // Provide example CSV file to help us reproduce your issue 1. Magento 2.3.3 MariaDB 10. Apache 2.4

Marco2016-10-3.txt

Steps to reproduce

// Provide a list of steps to reproduce this bug, include which plugins you use // You can attach your magmi profile files stored in directory "{your Magento dir}/magmi/conf/{your profile name directory}

Actual result

for table 'catalog_product_entity' - ERROR ON RECORD #2 SKU mag2604 - 3 SQLSTATE[42000]: Syntax error or access violation: 1142 TRIGGER command denied to user 'resellerbay'@'%' for table 'catalog_product_entity' - ERROR ON RECORD #3 SKU mag2606 - 4 SQLSTATE[42000]: Syntax error or access violation: 1142 TRIGGER command denied to user 'resellerbay'@'%' for table 'catalog_product_entity' - ERROR ON RECORD #4 SKU mag2607 - 5 SQLSTATE[42000]: Syntax error or access violation: 1142 TRIGGER command denied to user 'resellerbay'@'%' for table 'catalog_product_entity' - ERROR ON RECORD #5 SKU mag2608 - 6 SQLSTATE[42000]: Syntax error or access violation: 1142 TRIGGER command denied to user 'resellerbay'@'%' for table 'catalog_product_entity' - ERROR ON RECORD #6 SKU mag2609 - 7 SQLSTATE[42000]: Syntax error or access violation: 1142 TRIGGER command denied to user 'resellerbay'@'%' for table 'catalog_product_entity' - ERROR ON RECORD #7 SKU mag2610 - 8 SQLSTATE[42000]: Syntax error or access violation: 1142 TRIGGER command denied to user 'resellerbay'@'%' for table 'catalog_product_entity' - ERROR ON RECORD #8 Trace not found

this happens on every product sku

gfxguru commented 4 years ago

Actually it was my stupidity., wrong database...