cancel
Showing results for 
Search instead for 
Did you mean: 

Can't save credit memo in Magento 2.1.3

Can't save credit memo in Magento 2.1.3

Magento 2.1.3
Payment method: Credit Card (Braintree)
Environment: Sandbox
Payment Action: Authorize

  1. Create order
  2. Create invoice
  3. Create credit memo for invoice
  4. Press "Refund" button

Expected result
Save credit memo, perform refund action at Braintree

Current result
Magento Admin panel. Error message "We can't save the credit memo right now."
var/log/exception.log

 

[2017-01-29 19:03:35] main.CRITICAL: exception 'Exception' with message 'Recoverable Error: Argument 1 passed to Magento\Framework\Exception\LocalizedException::__construct() must be an instance of Magento\Framework\Phrase, string given, called in /home/vippstony/public_html/vendor/magento/module-sales/Model/Service/CreditmemoService.php on line 185 and defined in /home/vippstony/public_html /vendor/magento/framework/Exception/LocalizedException.php on line 34' in /home/vippstony/public_html/vendor/magento/framework/App/ErrorHandler.php:61 Stack trace:
#0 /home/vippstony/public_html/vendor/magento/framework/Exception/LocalizedException.php(34): Magento\Framework\App\ErrorHandler->handler(4096, 'Argument 1 pass...', '/home/vippstony...', 34, Array )
#1 /home/vippstony/public_html/vendor/magento/module-sales/Model/Service/CreditmemoService.php(185): Magento\Framework\Exception\LocalizedException->__construct('Transaction has...') #2 /home/vippstony/public_html/vendor/magento/module-sales/Controller/Adminhtml/Order/Creditmemo/Save.php(105): Magento\Sales\Model\Service\CreditmemoService->refund(Object(Magento\Sales\Model\Orde r\Creditmemo), false)

 

 

2 REPLIES

Re: Can't save credit memo in Magento 2.1.3

Hi @olukyanenko,



Have you customized your Magento 2.1.3 instance?

Best regards.

Gabriel

If my answer was useful, please give "Kudos" to this post.
If my answer helps you to resolve the problem, click on "Accept as Solution".

Re: Can't save credit memo in Magento 2.1.3

No.

I got the answer here - https://github.com/magento/magento2/issues/8309

 

Spoiler
Hi, guys, thanks for reporting, this is known issue (internal ticket MAGETWO-62428) and fix will be available in Magento 2.1.4 version.