Thursday, November 21, 2024 7:50:59 PM
Internal Error Running Plugin
When I try to run the plugin I get an Internal Error. I have checked the nopCommerce error long and there is nothing there. I turned on debugging for the plugin and downloaded the log file - searched for "error" and couldn't see anything like that in there. Can you advise me on what to look for?
I noticed the Global.asx file did have a CRLF at the end when I examined it. But I added a space to that blank line per your instructions and saved the file. I tried again to use the "Run Now" from "Scheduled Tasks" for your plugin and still receive the "Internal Error" message. Also tried manually restarting the application - same results.
One thing I can think of that might be unusual about my configuration is that I am running multi-store. Originally I configured the plugin for a single store. Just to test it. It appeared to be working. After a few weeks, I decided to activate it for all stores - so I added all the configuration data to the "All Stores" configuration screen.
That is when I decided to run it manually to allow it to detect deliveries from other stores that it had not been detecting before.
Now I have tried enabling my stores one at a time - and the error goes away until I select one specific store. Enabling the plugin for this store causes the error. Disabling it makes the error go away.
Is there something in the store configuration that I can be checking that could cause this?
That is when I decided to run it manually to allow it to detect deliveries from other stores that it had not been detecting before.
Now I have tried enabling my stores one at a time - and the error goes away until I select one specific store. Enabling the plugin for this store causes the error. Disabling it makes the error go away.
Is there something in the store configuration that I can be checking that could cause this?
Of course, reality has just altered itself to work against me. As is often the case.
For the past 2 days I have been able to generate this error at will. As soon as I set up a debug environment to capture data for you - the error goes away. Now, even if I enable "All Stores", I no longer receive the error.
However - I do have a log file that I captured yesterday that I can send to you. When I was still getting the error. I will send this to you and hope that it can shed some light on this problem.
For the past 2 days I have been able to generate this error at will. As soon as I set up a debug environment to capture data for you - the error goes away. Now, even if I enable "All Stores", I no longer receive the error.
However - I do have a log file that I captured yesterday that I can send to you. When I was still getting the error. I will send this to you and hope that it can shed some light on this problem.
Yes - I still receive the error when I try to manually run the plugin in from the schedule task page.
We're sorry, an internal error occurred.
Our supporting staff has been notified of this error and will address the issue shortly.
We apologize for the inconvenience.
Please try clicking your browsers 'back' button or try reloading the home page.
If you continue to receive this message, please try again in a little while.
Thank you for your patience.
There are no errors in the nopCommerce log.
I left debug mode on for your plugin. I have sent it to you in an email. I have looked at it and do not see any errors.
We're sorry, an internal error occurred.
Our supporting staff has been notified of this error and will address the issue shortly.
We apologize for the inconvenience.
Please try clicking your browsers 'back' button or try reloading the home page.
If you continue to receive this message, please try again in a little while.
Thank you for your patience.
There are no errors in the nopCommerce log.
I left debug mode on for your plugin. I have sent it to you in an email. I have looked at it and do not see any errors.
OK - I installed the update.
Previously, when I received the error, the task would take some time before throwing the error. Maybe 30 seconds or even a minute.
Now - when I click Run Task Now - it is instantaneous. At first I thought that it was failing right away. But I look at the log file and it appears to be working. The entries in the log file are from today's date so I know they are new entries.
So I think it may be working now. I will monitor it for the next few days to see if it is updating delivery status as it should.
Previously, when I received the error, the task would take some time before throwing the error. Maybe 30 seconds or even a minute.
Now - when I click Run Task Now - it is instantaneous. At first I thought that it was failing right away. But I look at the log file and it appears to be working. The entries in the log file are from today's date so I know they are new entries.
So I think it may be working now. I will monitor it for the next few days to see if it is updating delivery status as it should.