Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.
If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.
When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:
You may also want to review the installation or upgrading documentation.
Hi,
I have just upgraded mojoportal and had the server updated to .NET 4.0 everything is now okay...
Then I noticed I was getting the error for the Machine Key change.
I copied the web.config file from the server to my local machine I generated a new Machine Key in the app I changed the Machine Key I copied the newly edited web.config back to the server I reload the site and BANG...
Now I am getting the following error...
Server Error in '/' Application. -------------------------------------------------------------------------------- Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>
Server Error in '/' Application. --------------------------------------------------------------------------------
Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>
I change the Machine Key back to the original one and the site works?
Am I missing another change here somewhere?
Phill
Sounds like you typoed something in Web.config that causes an error and now it cannot load Web.config
I would review it carefully and look for any malformed tags extra angle brackets or missing angle brackets.
Hope it helps,
Joe
Hi Joe,
Thanks I will look over the line I added for the Machine Key as it was the only thing I changed. Maybe I errorred when I copied it from the generator box in the admin page.
I'll try again and let you know the results.
Thanks Phill
Well I was unable to re-create the error again... so once again your eminence is correct... and once again I bow to your expertise... as you noted I must have missed a chr or space.