Runtime Exception in Order Process : Determining the active language requires a contextual employee instance.

[Theodor-Maja]

I get this Exception when i want to buy a Product in my Shop ! and want to proceed the Order in the last Step !

There comes many Error-Messages ! , but the Article is normally on Stock and so on !!!

I am using Prestashop 1.7.7.2

Do someone have the same Problem and can help ?

Best Regards

Theodor Maja

[Ashley B.]

Hi Theodor Maja,

We can't help resolve the problem, but we also found this exact same symptom last night, so I thought I would comment as it may help you or someone else get closer to a solution.

More concretely: the customer passes the order through to the final stage and during the payment processing the order is committed, an error 500 occurs, the order is left with no status in the back office and the customer no longer has access to the order as if the order has been processed (nothing is emailed or communicated to the customer).

In our logs, the error 500 has a very similar stack trace as you show here.

In our situation, we are running Prestashop 1.7.7.3 and we tracked the issue down to the Amazon Marketplace Module (version 4.9.326) - just disabling this ensured our sites were working again. We determined this was a potential issue because it was the most recent thing that had changed.

We aren't yet sure if the issue is related to something wrong in the database (it was working in our test environment), but we are now working with the module author.

I would suggest you look at recent modules you have installed and try to disable them to see if one of those is causing the issue.

Regards,

 - Ashley

[Theodor-Maja]

Hello Ashley B.

Thank you for your reply !

I solved my problem by modfiy the Presta-Code !

I disable the StockMovement Function and it works 🙂

Regards
Theodor

[Ashley B.]

Hello again Theodor!

Are you sure that's a good idea? What happens with your inventory when you process orders now? We probably won't be making such a change, accurate stock keeping is important for us, but we haven't analysed the issue. We'd rather run standard Prestashop code and fix the issue with the 3rd party module.

Regards,

 - Ashley

[Ashley B.]

By the way, in our situation, the module developer very quickly came back to us with a new version which resolved the issue.

[Ernestas Luza]

Hello, I got the same issue. Not sure if it will be the same for you guys but it appeared in my case on payments. So this problem appears if the context doesn't have an employee in its parameters, and it comes from SymfonyContainer since it tries to call ps core api stock movement repository, and the context is made out of scope so it doesn't have an employee. In my case, I found a module witch initiates a new AppKernel which is requered for Symfony(dont know all the details but if it's called in front it creates symfony container) to work and it caused a problem. A recommendation is to try to find a module witch is trying to call a new Kernel and boot it. If you don't have access to code, it's not much you can do just try disabling custom modules.

Edited November 16, 2022 by Ernestas Luza (see edit history)

[Damian]

Check this post and my answear