We're Sorry, an Internal error.............

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
10 years ago
I am using the version available on windows Azure, and I have been using the 1.9 version on GoDaddy for a while, but they don't allow trusted connections, so NOPCommerce on GoDaddy is dead-dog slow.

Here is the website - http://stevonop.azurewebsites.net/en/


Now, just entering a few categories, every link gets the error :


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.
[i][/i]

does this system actually work or should I give up now?  There seem to be 6000 different answers to this question
10 years ago
To find out what went wrong you need to turn off the custom errors mode.
1. Open web.config file
2. Find out the following line <customErrors defaultRedirect="errorpage.htm" mode="RemoteOnly">
3. Replace it with <customErrors defaultRedirect="errorpage.htm" mode="Off">
7 years ago
hi i got same error and i open the web.config file and i find this code
<customErrors defaultRedirect="ErrorPage.htm">

please let me know how to solve this issue
7 years ago
haseebsidz wrote:
hi i got same error and i open the web.config file and i find this code
<customErrors defaultRedirect="ErrorPage.htm">

please let me know how to solve this issue


I suggest you to check your website log first, you may find error there!

We're sorry, an internal error occurred.... is not an actual error, to view the actual error followed the steps:

a.m. wrote:
To find out what went wrong you need to turn off the custom errors mode.
1. Open web.config file
2. Find out the following line <customErrors defaultRedirect="errorpage.htm" mode="RemoteOnly">
3. Replace it with <customErrors defaultRedirect="errorpage.htm" mode="Off">


Look at change of mode from "RemoteOnly" to "off".

Hope this helps!
7 years ago
i am using a godaddy platform

this code <customErrors defaultRedirect="errorpage.htm" mode="RemoteOnly">
i find in this file Nop.Web.dll.config so what shell i do shell i put mode="off"


this code <customErrors defaultRedirect="ErrorPage.htm">
i find web.config file.

and i have try to remoteonly to off mode but its not working its showing diffrent error
7 years ago
haseebsidz wrote:
i am using a godaddy platform

this code <customErrors defaultRedirect="errorpage.htm" mode="RemoteOnly">
i find in this file Nop.Web.dll.config so what shell i do shell i put mode="off"


this code <customErrors defaultRedirect="ErrorPage.htm">
i find web.config file.

and i have try to remoteonly to off mode but its not working its showing diffrent error


You should find it at Web.config file. Keep in mind, to change mode from "RemoteOnly" to "off" doesn't solved the issue, it just configuration to see the actual error!!

If you see different error, then that would be the actual error. Search it on forum or create new post if required!
7 years ago
now i got this error

Server Error in '/' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type 'Nop.Web.MvcApplication'.

Source Error:


Line 1:  <%@ Application Codebehind="Global.asax.cs" Inherits="Nop.Web.MvcApplication" Language="C#" %>  
Line 2:  
Line 3:  


Source File: /global.asax    Line: 1

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1590.0
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.