Vm2Mage FAQ: Troubleshooting

The following FAQ contains questions and answers on Vm2Mage troubleshooting.

Something does not work

In all cases, first upgrade Vm2Mage to the latest available version. The procedure of how to upgrade Vm2Mage in both Joomla! as Magento is available in our tutorial section.

When you need help, make sure you understand our support policy as described in these FAQ. Also, before posting to the Yireo Forum, make sure you have checked your Apache logs for any PHP Errors or PHP Warnings.

Failed to initialize XML-RPC

This error is given if the XML-RPC client within Joomla! is unable to contact the XML-RPC server of Magento. In most cases, you did not configure anything yet regarding the API. Make sure you configure the "Parameters" within Vm2Mage by filling in an API-host, API-user and API-key.

If the settings are right, you should be able to see dropdown-options under the "API Widgets" within the modal popup of "Parameters". If the settings are incorrect, these options will be regular input-fields, not selection-boxes.

Invalid API path

If the API-settings in the Vm2Mage "Parameters" are properly configured, you may still receive the error "Invalid API path". In this case, the connection to Magento is up and running, but within Magento the Vm2Mage API-path is unknown.

Make sure you have properly installed the Vm2Mage extension within Magento. Also, go to "System > Cache Management" and refresh the "Configuration" cache and the "Webservices Configuration" cache.

Invalid UTF-8 sequence in argument

If you receive a PHP Warning in your Apache ErrorLog mentioning something like "Invalid UTF-8 sequence" your VirtueMart installation is probably not encoded with the right characterset. Make sure all characters of product-titles, category-descriptions and so on, are displayed in the right way within VirtueMart, before migrating things with Vm2Mage. In most cases this can be solved by exporting and re-importing the MySQL database with the right encoding-settings.

This issue is not related to Vm2Mage, but to a corrupt VirtueMart installation.

Unknown API-response: 'No data received from server.'

When migrating products, users or categories, this message may appear. In this case, the migration might be succesfull, but some kind of PHP Notice or PHP Warning occurred. Check your Apache logs for more information on this matter.

Unknown API-response: 'Invalid return payload'

Most likely, some PHP Warning or PHP Error was thrown during migraton, which causes the API-output to be corrupt. Carefully check your Apache logs. If your Apache logs are totally empty, make sure you are actually using these logs. Also, checkout the other FAQ in this section, because they contain helpfull information for requesting support.

Unknown API-response: 'XML-RPC non-object value: 0'

Most likely, some PHP Warning or PHP Error was thrown during migraton, which causes the API-output to be corrupt. Carefully check your Apache logs. If your Apache logs are totally empty, make sure you are actually using these logs. Also, checkout the other FAQ in this section, because they contain helpfull information for requesting support.

Unknown API-response: 'Internal Server Error'

This error is generated by Apache, and tells you to inspect the Apache errorlog. Make sure that PHP error-logging is enabled and that Apache errorlogs are capable of receiving PHP Fatal Errors. If in doubt, contact the system administrator of your webserver.

Alternatively open up the Magento index.php file and enable the line mentioning display_errors. This will print PHP-errors on screen, instead of hiding them. Don't forget to comment the line again once you're done troubleshooting.

Other Unknown API-response codes

When Vm2Mage returns an error Unknown API-response, this means that the feedback received from Magento is not correct. Make sure to enable Magento debugging in the Developer-section, and make sure you also watch any errors in the Apache errorlog.

There are some status-codes generated by Vm2Mage as well: With code 731, the attribute-initialization failed in general, with code 732 the attribute-initialized failed for a specific attribute. With code 733, the migration of either a product, customer or category failed in general, with code 734, a specific migration failed.

How to debug a migration?

Within the product/category/user overview of the Vm2Mage component in Joomla!, you will find a small link on the right called View, which allows you to zoom into a specific item. On that item-page, the database-information that Vm2Mage has found is printed. In the bottom there is a link Debug Migration, which can be used to replay the migration of that specific item.

A secret trick is to add the parameter &xmlrpc=1 to the URL of the item-page, which will print XML-RPC debugging information on screen. In most cases, this is not needed.

Reindexing flat catalog fails

If after a migration, the Magento index for Product Flat Data fails to rebuilt properly, first make sure to enable Magento debugging. Next retry again, and open up the Magento logs in var/log to see if any error was logged.

If there is a SQL-error mentioned at the exact same moment that the Product Flat Data index was reindexed, it might indicate that the flat-tables structure is corrupt. Simply wiping out that index might fix things. Run the following SQL-query:

SET FOREIGN_KEY_CHECKS=0; TRUNCATE TABLE catalog_product_flat_1;

Try rebuilding the indices afterwards.

Cannot find an active Azure Market Place Translator Subscription

If you receive the error Cannot find an active Azure Market Place Translator Subscription associated with the request credentials it is most likely that you have registered for the API, but have not registered for the Microsoff Translator API as a service. Navigate to the URL https://datamarket.azure.com/account/datasets to check if the service is listed. If it is not, search the Azure Marketplace for the right service, and register for a specific service-subscription.