Magento2: Magento ver. 2.2.0-dev - A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later.

[vpiyappan]

Installed new version of Magento 2.2.0, Created a new category and product, Search for an item in frontend.
Navigate in Admin panel to view Search Synonyms.
Popup appeared stating "Something went wrong".

Preconditions

1. (Windows 10) i586
2. PHP Version 7.0.15
3. mysql Ver 15.1 Distrib 10.1.21-MariaDB, for Win32 (AMD64)

Steps to reproduce

1. Frontend search for an item in Top Search.
2. Login to Admin panel
3. Navigate to Marketing->Seo & Search->Search Synonyms.
4. Alert will display stating "Something went wrong".
5. Click ok, you will see the error message as "A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later."

Expected result

1. 
   

2.

Actual result

1. [Screenshot, logs]

[korostii]

Please try checking the logs at <your Magento installation dir>/var/log. Those might contain some detailed information about the errors encountered.

[vpiyappan]

I don't found any information in system.log or exception.log.

On Tue, Jun 27, 2017 at 5:36 PM, korostii [e-mail] wrote:

Please try checking the logs at /var/log.
Those might contain some detailed information about the errors encountered.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/magento/magento2/issues/10071#issuecomment-311338283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALPoSODgX7eVj4kIxEiVbVtRQ3sURzwoks5sIPBBgaJpZM4OGhkC
.

--
Regards,

Iyappan Perumal
Technical Architect | Dckap Technologies
[email protected] | : www.dckap.com

[misha-kotov]

I have not been able to reproduce. Can you clarify what your environment stack is? MySQL ver 15.1 doesn't make sense.

[vpiyappan]

My Mysql version is 10.1.21-MariaDB

On Thu, Jun 29, 2017 at 2:53 AM, Misha [e-mail] wrote:

I have not been able to reproduce. Can you clarify what your environment
stack is? MySQL ver 15.1 doesn't make sense.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/magento/magento2/issues/10071#issuecomment-311796199,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALPoSPcuc2KaoUbXxWdgpKFfRR1SfPAcks5sIsRagaJpZM4OGhkC
.

--
Regards,

Iyappan Perumal
Technical Architect | Dckap Technologies
[email protected] | : www.dckap.com

[tjwiebell]

@vpiyappan - I'm getting an identical environment up now to reproduce this bug, but wanted you to verify something first. You have an alert along the top in that screenshot that indicates your index jobs aren't running; could you perform a re-index and verify if the error persists?

-edit- I'm unfortunately unable to re-create this error in an identical environment. This appears to be a UIComponent error, so you should be able to find more details in the network tab of your browsers developer console. I would expect to see a non-200 response from the search_synonyms_grid request (<magento_host>/admin/mui/index/render/?namespace=search_synonyms_grid&<url_params>). This error should also be logged in your web server error logs.

If you could please provide these additional details, that should help us isolate the problem.

[vpiyappan]

You are correct, after re-indexing the issue disappeared.

Thank you!

On Thu, Jun 29, 2017 at 9:30 PM, Tommy Wiebell [e-mail]
wrote:

@vpiyappan https://github.com/vpiyappan - I'm getting an identical
environment up now to reproduce this bug, but wanted you to verify
something first. You have an alert along the top in that screenshot that
indicates your index jobs aren't running; could you perform a re-index and
verify if the error persists?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/magento/magento2/issues/10071#issuecomment-312012434,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALPoSE4y8889YkS4bjGKcv4EXTqiS7K1ks5sI8oqgaJpZM4OGhkC
.

--
Regards,

Iyappan Perumal
Technical Architect | Dckap Technologies
[email protected] | : www.dckap.com

[Stas94]

@vpiyappan Please add more details to your description of the steps you followed when identifying this issue. Screenshots or logs would be helpful, too.

[magento-engcom-team]

@vpiyappan 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.

[ripplejb]

I got same exact error. I have Magento dev environment in my Home folder (~/Magento/magento2/) of my Ubuntu workstation. I did reindex and flush the cache. I am still getting the error. All the call on network are with response code 200 or 302.
This is new install.

as @tjwiebell mentioned, I debugged the ui.

In network I can see this URL is called right before the error.
http://localhost/~/..../mui/index/render/key//?namespace=notification_area&sorting%5Bfield%5D=created_at&sorting%5Bdirection%5D=asc&isAjax=true

Response for the URL is,
{"totalRecords":0,"items":[]}

All the pages of admin give error once I receive the response.

Please help me resolving the issue. Let me know if you need any more detail.

[moleculech]

I got the same error (Magento 2.2.0, ngix). But only for backend-users with limited access (catalog and customers). There is no error messages in the admin-account.

All available backend-pages are contaminated. There is no deleted store-view as mentioned in the know-issues section of the dokumentation.

Nothing helpful to be found in log..

Thanks for any help.

edit 1
Found the problem in my case: All backend-users seems to need these privileges:

[Adrian003]

Hi,

I have the same error, migrated from Magento 1.9.3 to Magento 2.2 (via Magento 2 Data Migration Tool). Catalog is working just fine but for customers I receive "A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later." (in the Admin interface)
In the front-end when trying to login with a new user it's not working, for old imported customers the same.

Any clue ? In the logs I don't have any records related to this.

P.S. Can be related to upgrade_customer_password_hash ?

Thanks,
Adrian

[onepack]

@moleculech This solved it for me as well.
The strange thing is that the complete subadmin user-role was copied and got my user name as role-name while editing.
I removed it, edited the original with the new permissions and after a re-login all was fixed after that for the subadmins.

[cristienache]

Thanks @moleculech! It fixed my issue!

After first attempt of creating a second user with limited permissions, I have deleted the user, created another one and followed @moleculech's advice and it worked!

Thanks again!

Regards,
Cristi

[srmedizina]

Hi.

I got the same error but unfortunately the suggestet solution with permissions doesnt work.

I only have 1 User Login with the Administrator Role and "All" rights selectet from the dropdown (not custom).

I have no additional Logins with separate rights.

This is the error:

I dont know the relevant information you may need too, so feel free to ask and i give all infos
that are needed.

Magento Version 2.2.0 on Debian

best regards
Sebastian

[mindsoul]

thanks @moleculech, also my issue dissapear on magento 2.2.0

[Alex7Lem]

I solved this problem with one command line:
php bin/magento maintenance:enable; php bin/magento setup:upgrade; php bin/magento setup:di:compile; php bin/magento setup:static-content:deploy -f; php bin/magento cache:clean; php bin/magento maintenance:disable

[na159]

I have the same error magento 2.2.1

[tommybds]

@moleculech fix worked for me, thanks :) (magento CE 2.2.0)

[Silarn]

The initial issue was a slightly different problem, but the issue/solution found by @moleculech seems to be legitimate and probably needs to be re-reported. Missing a permission should not make you get an error on every admin page.

[rmendoza3]

I am using Magento Commerce 2.2 and just migrated data a couple of days ago. I set the admin user password to expire after two days to test this feature. Today, I am getting the error "A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later." There were no changes to admin from yesterday to today.

First I tried reindexing. I have tried @moleculech fix, really both admin users already had full access. I was able to update my password, since it is expired, with this error up. Then it went away.

I am not sure this helps others but it could be that one admin user's password expired and that creates an error for all users. Just leaving this here in case it helps someone else.

[kluntz]

Got the same error on 2.2.

Reset the admin password and the problem was solved.

[webshotNL]

Got the exact same error on Magento 2.2.2 fresh install with Varnish cache. After resetting the admin password problem seems to be solved. So, thanks kluntz ;)

[snoroozi]

@tjwiebell thanks. I'm hoping this does the trick for me too.

[ghost]

So the Magento 2 error messages have the same level of sophistication is the IT Crowd ? The best answer there is really "try turning it off and on again" ??

[jellesiderius]

We had the same problem... This could be anything. For us the fix was to change our current logged in admin user's password...

[shenmusam]

I change the admin user's password,nice!!

[gizmocn]

I have same issue, after enable cache, the issue disappear

[reillo]

Yes, resetting the password works.

[seanscott49]

I had the issue too, and it turned out to be an issue with Custom Options. Once I deleted them, I was able to save the product. Make the changes and re-add the custom options back in.

[lano-vargas]

Hello, Am i late for the magento weirdness findings out of the blue I start having this issue but on one user only that was admin user but other users with admin access didn't have this issue.

So moleculech finding did not work for me, what worked was reseting password in the end but I first had also run php bin/magento indexer:reindex && php bin/magento setup:di:compile && php bin/magento cache:clean && php bin/magento cache:flush.

Now I am not sure if just reseting the password worked or was a combination of those!

[snoroozi]

Honestly, these are all bs solutions that don't get to the error at hand.

On Wed, Jun 20, 2018, 10:13 AM Juliano Vargas [e-mail]
wrote:

Hello, Am i late for the magento weirdness finding I out of the blue I
start having this issue but on one user only that was admin user but other
users with admin access didn't have this issue.

So moleculech finding did not work for me, what worked was reseting
password in the end but I first had also run php bin/magento
indexer:reindex && php bin/magento setup:di:compile && php bin/magento
cache:clean && php bin/magento cache:flush.

Now I am not sure if just reseting the password worked or was a
combination of those!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/magento/magento2/issues/10071#issuecomment-398763806,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQbJQKNfTyTg7rwpAd15hqeuu7RGC0Qks5t-lhsgaJpZM4OGhkC
.

[Jason-Truman]

Solution For Issue, with reason it happens (most of the time)

Various times you will see messages such as "A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later."

There is a very good reason for this error which i'll describe as follows. This is not an error with Magento. It is not a bug in Magento. There is nothing wrong with your files. There is nothing wrong with your attributes. There is nothing wrong with your database etc... It is not due to logout or password change as some of the posts have mentioned etc...

You will not usually see any indication in the magento log files as there is not actually a 'real' error happening.

This is not an error that is your fault.

Also, this Error can happen in many areas, in any version of Magento 2 (2.0.x, 2.1.x, 2.2.x etc...).

The most common area it occurs is when saving a product, but can happen in other areas also.

Sometimes it will seem to happen with one product and not another. Sometimes it will happen if you are filling out some attributes and not others, or typing descriptions in different ways.

Most of the time if you see this error you will also NOT see an error in any of the official Magento 2 log files, making you very curious about what is going on.

If you get this error: use 'inspect' the page and you will probably notice some files marked as '404' not found. They are not missing files, so dont waste time looking for them. You may see the page perfect when it first loads, but after doing your changes and clicking 'save' then you will see files not being delivered that should be.

It's the lack of "DELIVERY" of these files which is causing the error to occur. As an example, some ajax saving elements or similar may be failing to trigger.

When this happens, check with your hosting environment or hosting company for what they have setup for "modsecurity" (the most common culprate of this issue). Or any other type of application firewall with enhanced protection systems built into it.

Put simply, there are web-application firewalls which monitor traffic. These look for suspicious traffic going to a website, and will block traffic that doesn't feel quite right. In an advanced application like Magento you will sometimes have these application firewalls blocking a bit more aggressively than they should be.

Think of these firewall application protection systems as being the same as an overly agressive antivirus system to help protect you. They are good to have, but sometimes stop stuff they shouldn't be stopping. And when it happens... boy it can be a pain to track down.

If you are using a good hosting provider you can ask them to look into the logs and possibly adjust the level of aggressiveness for your website, or whitelist certain elements. As an example, Nexcess is a popular good provider for hosting, and here is what they say on the issue: https://docs.nexcess.net/article/why-do-i-need-modsecurity.html

Hope this helps anyone who bumps across this thread - there's lots more threads like this out there and this likely is one of the biggest reasons for people seeing this error (not the only reason, but certainly the biggest one)

So not an issue with Magento, rather an issue with antivirus system stopping delivery of various files sometimes, which can cause all sorts of crazy side-effects.

Cheers! happy coding all!

[seanscott49]

Thank you. I use Nexcess. I will try on another server and see if it happens.

[Kist221]

Same error for Magento ver. 2.2.4 trying to send MagePlaza SMTP test email. Can not configure or get to work.

[cgrio]

Hehe the same trouble with this issue:

Action create new product in catalog in magento 2.2.5
Change the Attribute group
The error message is displayed
in debug of Chrome I see that te following address apper error 404:

https://www.mywebsite.com/admin_101010/catalog/product/reload/type/simple/store/0/popup/1/componentJson/1/prev_set_id/9/key/3e2204fe5a8e2f43889649e5f47bc3cba6c13a9281da182a9b537c8c760d89de/?set=&isAjax=true

And this message in debuger:

ncaught TypeError: Cannot read property 'length' of undefined
at UiClass.getNewData (dynamic-rows-grid.js:185)
at UiClass.initElements (dynamic-rows-grid.js:91)
at setNested (objects.js:43)
at Object.nested (objects.js:117)
at UiClass.set (element.js:305)
at updateValue (links.js:80)
at Function.notifySubscribers (knockout.js:1103)
at Function.observable.valueHasMutated (knockout.js:1300)
at UiClass.observable [as recordData] (knockout.js:1285)
at setNested (objects.js:43)

Can anyone help me?

[Jason-Truman]

Just try asking your hosting provider to whitelist your site for modsecurity or if you have access directly perhaps use your cpanel to do this, or temporarily disable it etc... Likely modsecurity (or another application firewall style system) is blocking the file, which causes issues. The longer written solution describes this in more details.

[ScoFoUK]

Hey @sandsax - I had this problem when changing attribute sets too. I'm using 2.2.5. It turns out it only happens when changing to an attribute set that has attributes in a different group to the attribute set on which it was based.

Steps to reproduce:
Create attribute set 'new attribute set' based on 'default'.
Within 'new attribute set' I can create a new group 'new group'
Within 'new attribute set' I move attribute 'color' to 'new group' and save.
Create new product, change attribute set to 'new attribute set' and get the reported error.

Workaround
Ensure any attributes in your attribute set are in the same group as the attribute set selected as 'based on' at time of creation.

Hope that helps.

[melaxon]

This happens to me only on VDS (Digital Ocean) with no modsecurity. Everything is okay on localhost.
It happens only when I click any link on the backend when the page is not fully loaded only but this does not affect the operation. Error message disappears and the click is being executed normally.
I'm pretty sure something is missing in the environment, maybe I missed some plugin or utility.
I hope the developers may suggest something

[shivanisdev]

I have same issue in v2.2.5

A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later.

and grid is not loading only spinner moving no data loading

[spellmen]

I have same issue in v2.2.5

A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later.

and grid is not loading only spinner moving no data loading

@shivanisehdev86 Have you fixed this issue?

[itg-ddanielson]

I have this same issue on 2.2.5, only when using Varnish locally. When I disable Varnish the popup goes away. I am getting a 404 on an Ajax call to admin/noroute which is the cause of my issue but I have no idea how to solve or even debug this. I have tried re-index, flush cache, reset password etc but nothing

When I disable varnish and inspect the url that should be loading when the no-route endpoint is call I get

...../static/adminhtml/..../backend/en_US/Magento_AsynchronousOperations/template/grid/cells/actions.html

[digvijay2017]

Hi All,
I have also got this issue in Magento 2.2.1.
Well, I have done all the technique which mentioned above. But no luck.

But i have fixed this, that why i want to share the technique for fix this silly issue. Well if you assign the full resource access to a Role, then it's working perfectly. As i know, if you assign the custom resource access to any role, you must assign the Show List resource access to the role. So new role can see the notification after login. For more clarification, please see attach screen:

If you are still getting issue. Please logout and then login again. I hope, this will help you.

[spellmen]

Thanks a lot. I also fixed this issue, but I followed a different approach.

On Thu, Oct 25, 2018 at 12:27 PM Digvijay [e-mail] wrote:

Hi All,
I have also got this issue in Magento 2.2.1.
Well, I have done all the technique which mentioned above. But no luck.

But i have fixed this, that why i want to share the technique for fix this
silly issue. Well if you assign the full resource access to a Role, then
it's working perfectly. As i know, if you assign the custom resource access
to any role, you must assign the Show List resource access to the role.
So new role can see the notification after login. For more clarification,
please see attach screen:
[image: screenshot from 2018-10-25 12-24-03]
https://user-images.githubusercontent.com/30342958/47481425-2df85480-d851-11e8-8f68-252f7e08d3a9.png

I hope, this will help you.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/magento/magento2/issues/10071#issuecomment-432936364,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZwjLZ6_H7DeAS6xqEUnIuAPZH4MpnOdks5uoWDPgaJpZM4OGhkC
.

[digvijay2017]

Hey @spellmen

if you don't mind, Can you share your approach for fixing this issue?

[stephenbori]

The issue for me on this one was mod security blocking the ajax page request if this helps anyone.

[bigsteve]

Please make sure if you run magento2 on nginx you have the below block on your server configuration (or add correspondent apache directive on apache):

location / {
try_files $uri $uri/ /index.php$is_args$args;
}

[m2-assistant[bot]]

Hi @Karlasa. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.