Check out error: Internal Error. Details are available in Magento log file. Report ID: webapi-591ed1dd4a440

[kaseyfurlong]

Preconditions

1 Magent0 2.0.

Steps to reproduce

1. Add item to cart
2. Navigate to check out
3. Error appears immediately upon arriving at the checkout page.

Expected result

1. No error should display. You should be able to enter your information and proceed to review and payment.

Actual result

1. Unable to proceed. No shipping methods display.

[korostii]

Details are available in Magento log file

Well? Did you read it? What does it say?

The actual error report contains additional information about the issue, which is vital for troubleshooting purposes. Please attach its contents to the issue.

You should be able to find the corresponding error report inside the following folder: <Your Magento2 Installation directory>/var/report/api/

[steverobbins]

I got the same error in 2.1.3.

Internal Error. Details are available in Magento log file. Report ID: webapi-599484a94e42c

There is only one entry in var/report/api

[***@*** public_html]$ cat var/report/api/754952492864 
s:222:"Fatal Error: 'Allowed memory size of 805306368 bytes exhausted (tried to allocate 114195699 bytes)' in '/***/deploy/releases/20170822011920/vendor/magento/zendframework1/library/Zend/Debug.php' on line 104";

Seems pretty clear that I ran out of memory, but at almost 1GB isn't that a lot be using?

I'm also wondering what's the correlation between the two report numbers. How do I know webapi-599484a94e42c relates to 754952492864?

[Zeiiin]

Hi kaseyfurlong, may you please share how you got past the internal error issue which shows up as one fills in shipping address as shown above by you?

Thanks, Z

[magento-engcom-team]

@kaseyfurlong We can't reproduce this issue. Please install clean and fresh Magento, and try to reproduce this issue again.

[magento-engcom-team]

@kaseyfurlong we are closing this issue due to inactivity. If you'd like to update it, please reopen the issue.

[magento-engcom-team]

@kaseyfurlong, thank you for your report. We were not able to reproduce this issue by following the steps you provided. If you'd like to update it, please reopen the issue.

[COYktercero]

We are experiencing this issue as well. We can see in checkout errors via Google Analytics. I see these errors being generated but I do not know how to trigger/replicate. I do not have any files in /var/report/api folder past 9/22/2017 even though error is being generated daily.

Version: Magento Commerce 2.1.9

[kaseyfurlong]

Adding eServices to copy.

Thank you,

Kasey Furlong | Account Executive

M: 813.362.5918 T: 800.430.1312

From: COYktercero [mailto:notifications@github.com] Sent: Wednesday, November 08, 2017 10:02 PM To: magento/magento2 magento2@noreply.github.com Cc: Kasey Furlong kfurlong@jaggedpeak.com; Mention mention@noreply.github.com Subject: Re: [magento/magento2] Check out error: Internal Error. Details are available in Magento log file. Report ID: webapi-591ed1dd4a440 (#9700)

We are experiencing this issue as well. We can see in checkout errors via Google Analytics. I see these errors being generated but I do not know how to trigger/replicate. I do not have any files in /var/report/api folder past 9/22/2017 even though error is being generated daily.

Version: Magento Commerce 2.1.9 [error]https://user-images.githubusercontent.com/25631637/32586422-46cea6de-c4b7-11e7-905d-e872f8e21dd8.JPG

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/magento/magento2/issues/9700#issuecomment-343033178, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbeP7BjOzTbm0LvzAnJrQiLGB7huur8Iks5s0mszgaJpZM4NgeZn.

www.jaggedpeak.comhttp://www.jaggedpeak.com [Jagged Peak Logo - Download Images to view.]

This mail (including all attachments) may contain confidential information which is privileged. It is intended solely for the identified recipient(s) to whom it is addressed. If you are not an intended recipient, please reply to us immediately and delete this message from your system. You may not copy or use it for any purpose, or otherwise disclose its contents to any person.

[fbkaasa]

We are experiencing problems as well Magento 2.2.6

Internal Error. Details are available in Magento log file. Report ID: webapi-5beb501e8c3b7 But there are no var/report/api folder or files

[csmith-fm]

This is by far not the clearest way of reporting faults, as such issues you're expecting a separate file to be generated within the "var/report" folder, with any API calls being in the api directory. For any errors with "webapi" at the beginning however, this is not the case.

If you head over to vendor/magento/framework/Webapi/ErrorProcessor.php, go down to approximately line 200, and you will see the "_critical" method:

protected function _critical(\Exception $exception)
{
    $reportId = uniqid("webapi-");
    $message = "Report ID: {$reportId}; Message: {$exception->getMessage()}";
    $code = $exception->getCode();
    $exception = new \Exception($message, $code, $exception);
    $this->_logger->critical($exception);
    return $reportId;
}

Notice that instead of creating a fresh file and inserting it into the reports directory, it's appending it into the global log file. So head over to "var/log" and open up "exception.log" - it will contain the string "Report ID: webapi-591ed1dd4a440", and the error message will follow. You can easily find this using the Find functionality in any text editor, or if you're viewing it directly from a Linux terminal, then just use:

cat var/log/exception.log | grep "Report ID: webapi-591ed1dd4a440"

It will print the exact line of the error, and you can go from there :+1:

[amolbhandari]

As per Magneto 2.2.3 This issue is logged int var/log/exception.log file.