When using a PosgreSQL 8.3 or 9.1 database this error happens at the very end of the installation process. The step 7 "Finished" is already shown (see attachment).
SQLSTATE[25P02]: In failed sql transaction: 7 ERROR: current transaction is aborted, commands ignored until end of transaction block: SELECT 1 AS expression FROM{migrate_map_commercekickstartbagscases} migrate_map_commercekickstartbagscases WHERE ( (sourceid1 = :db_condition_placeholder_0) ) FOR UPDATE; Array ([:db_condition_placeholder_0] => TOT1-GRN-OS ) (/srv/www/clients/client0/web1/web/ks7x20beta2plus2/profiles/commerce_kickstart/modules/contrib/migrate/plugins/sources/sqlmap.inc:317)
... and many more SQLSTATE[25P02] errors...
Obviously these errors occur during the creation of the demo store products for the special product types (e.g. commercekickstartbagscases)
Finally you see that no products were created:
Processed 6 (6 created, 0 updated, 6 failed, 0 ignored) in 8.6 sec (42/min) - done with 'CommerceKickstartBagsCases'
... and some more lines for different product types...
Nevertheless this error seems to have no negative effect on the functionality of commerce kickstart. Only the sample products are missing.
But you can add new products manually to a product type without any errors.
For full error log see screenshot as attachment
By the way this bug has nothing to do with the bug described here: http://drupal.org/node/1702692 ("Commerce Kickstart: installation of "demo store" fails when using PostgreSQL database")
The workaround of that issue did not help for this bug here.
When I was googleing around I have found this advice: "I have found two ways around this. Either disconnect and re-connect to clear this error, or run the command rollback;"
http://robertmarkbramprogrammer.blogspot.de/2011/02/postgresql-current-t...
mmmhhh... I do not know if this advice might be useful.
| Comment | File | Size | Author |
|---|---|---|---|
| PostgreSQL_error_at_the_very_end_of_kickstart_installation_process_failed_creation_of_sample_products.pdf | 700.61 KB | Metulski |
Comments
Comment #1
jims1 commentedI got the same issue too. on postgre 9.2.4
Comment #2
lsolesen commentedPlease try with latest dev
Comment #3
lsolesen commentedClosed for inactivity.