-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Magento 2.1.6 CE "We Can't Place The Order" error #9455
Comments
Hello @The-Krang, Thank you for posting this. I've created an internal ticket to investigate the issue: MAGETWO-68949 |
We get the same identical issue |
Same here this issue has been there forever in magento 2. No fix yet or solution. DOes anyone know why this is being carried over from magento 2 to mangento 2.1.7? |
- Fixed the bug - Added unit test
Issues fixed: - MAGETWO-65422 Write default configs to shared configuration file by app:config:dump - MAGETWO-69567 [Mainline] - Closing the image view window causes mini-cart to drop down - MAGETWO-69607 Edition Specific BN-Codes for 2.2.x - MAGETWO-68936 Billing Agreement page is not loaded if Vault enabled - MAGETWO-57975 Impossible use ExtensionInterfaceFactory - MAGETWO-69580 Unstable automated test Magento\Paypal\Test\TestCase\InContextExpressOnePageCheckoutTest failed on variation InContextExpressOnePageCheckoutTestVariation1 - MAGETWO-69110 Incorrect status for order placed within Authorize.net with Fraud Filters Triggered (Filter Actions = Process as normal and report filter(s) triggered) - MAGETWO-68949 [Github] "We Can't Place The Order" error #9455 - MAGETWO-69112 No request sent to Authorize.net after reordering order in admin - MAGETWO-69584 Command config:sensitive:set does not work on the cloud - MAGETWO-57846 [Github] New Order Status config in payment method is useless #5860 - MAGETWO-67632 [Github] Invalid method usage in PayPal NVP callDoReauthorization method #9336 - MAGETWO-63239 [GITHUB] No possibility to save payment transaction details - MAGETWO-69121 Loader doesn't disappear if Authorize.net transact.dll fails request - MAGETWO-64518 \Magento\CatalogRule\Model\Indexer\IndexBuilder method "doReindexFull()" causes temporary missing sale prices - MAGETWO-60533 Data passed to Magento\Framework\ObjectManager\Config\Compiled is not validated - MAGETWO-70061 Exception on EE installation on environment with default-storage-engine=MyISAM - MAGETWO-69260 Unable to create shipping label due to error of lb to kg conversion - MAGETWO-58961 Multiselect text values are not searchable using QuickSearch with ElasticSearch - MQE-155 [FT] Magento\UrlRewrite\Test\TestCase\CreateProductWithSeveralWebsitesUrlRewriteTest randomly fails on Jenkins
Hi, @The-Krang, the fix merged into the develop branch. |
Hi, I had the error "We can't place the order" on Magento 2.1.7, which was fixed today by turning off GTID_CONSISTENCY. Now I am able to process orders using PayPal. system.log error: Fix: I hope this helps. |
@sladjansimic [2017-07-12 23:11:31] main.CRITICAL: Exception: Wrong order ID: "INV2-HCZX-TDHA-EA8F-3TZQ". in /home/couponc1/public_html/vendor/magento/module-paypal/Model/Ipn.php:140 |
Putting gtid_mode = OFF seems to me an invasive way, someone of Magento Dev Team can confirm that no other fix can be applied? |
We have the same problem with paypal.
Thank you very much for help! |
wow - we just lost about 50 orders on one day before we looked at the logs - this is way more then a problem! it is unbelievably how buggy magento2 is still after over 1.5 years released. |
You would have not even noticed other lost orders because no one informed there was an issue. Its quite surprising- the most important part of website that is payment, has such a bug that has been reported so widely and there is no fix for such a long time |
The bad programming of M2 is a shame for this company. Payment issues which are not solved for such a time period is complete nonsense - but we did not expect anything else from magento side. |
Will there be fix anytime soon? |
Whats the current status on this issue? |
Magento hasn't supported GTID replication since v1. Guess who uses GTID in their HA database setups? Amazon, Google, Azure, Rackspace, and the list goes on. |
When there will be s solution of this problem? Jürgen |
Had the same error after returning from Paypal, while transaction was made, order was not and message appeared on order review page. Problem turned out to be Magento_Signifyd module being disabled. Found an exception in /var/log/system.log, with paypal classes in the stack trace: report.CRITICAL: Exception message: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento.signifyd_case' doesn't exist Re-enabling the module (re-compile, etc) fixed the issue. |
Will this be fixed in 2.1.x latest release? Or just on 2.3? Regards |
We managed to apply a fix on Magento 2.1 and fix below issue. Hope this helps. |
AC-13182::[Upgrade Build] Manual Upgrade Build 2.4.7-p2 -> 2.4.8-beta1
My setup:
2.0.7 CE was installed using Softaculous through CPanel from the web server. Using the Luma theme.
I upgraded from 2.0.7 CE to 2.1.6 CE under System > Web Setup Wizard > System Upgrade.
With PHP Version: 5.6.30, Apache and Linux Web server, phpMyAdmin version 4.0.10.18
Everything was working fine before the upgrade.
I have a success.phtml module that was disabled before the upgrade took place, and is still disabled.
The order success page is not displayed.
The site has only plain downloadable items, non-configurable, and all of them are In Stock and Enabled
.
PayPal Express Checkout is the only configured payment option, with the exact settings as before the upgrade.
PayPal Debug mode is on.
PayPal Skip Order Review Step = yes.
PayPal Payment Action = Sale
In sandbox mode in paypal, testing with a PayPal generated fake credit card number etc., with the site in developement mode.
The orders show up in the Admin at Sales > Orders, but are replaced by the most recent one. They will only increment beyond 000000132 if the order is placed in the Admin.
On the "Review Order" page, it says "We can't place the order.". Clicking the "Place Order" button at the bottom right of the page just shows the same page with the same error.
I have NOT made any changes to the database tables before or after the upgrade.
Your help and suggestions are much appreciated.
Steps to reproduce:
Add item(s) to the shopping cart.
Proceed to shopping cart page.
Proceed to checkout.
The customer logs into his/her account on my store.
Proceed to the payment page, select Pay With Paypal as payment option.
Press Continue to Paypal.
The customer is redirected to the Paypal page.
Enter payment and other information into PayPal's page.
Confirm the order with the "Pay Now" button.
Expected result:
The customer is redirected to order success page which has the order number.
The customer receives an order confirmation e-mail.
Actual result:
The customer is taken to the "Review Order" page, where it says in red letters, "We can't place the order.". Clicking the "Place Order" button at the bottom right of the page just shows the same page with the same error.
The order is recorded in Admin.
In the Admin > Sales > Orders > order number view, it reads, "Order # 000000132 (The order confirmation email is not sent)", "Order Status Suspected Fraud".
The main problem in the debug log appears to be:
main.CRITICAL: PayPal NVP gateway errors: A successful transaction has already
been completed for this token (#10415: Transaction refused because of an
invalid argument. See additional error messages for details). Correlation ID:
219dd382778ee. Version: 72.0. [] []
[2017-04-18 20:39:19] main.CRITICAL:
Exception message: PayPal gateway has rejected request. A successful
transaction has already been completed for this token (#10415: Transaction
refused because of an invalid argument.
The main problem in the system log appears to be:
main.CRITICAL: Exception message: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '000000132-1' for key 'SALES_ORDER_INCREMENT_ID_STORE_ID', query was: INSERT INTO `e_sales_order
Here are the debug and system logs:
Debug.txt
System.txt
The text was updated successfully, but these errors were encountered: