Ok I created a new user.config file and the only change I made was to comment out the MSSQL sample string and insert the correct MSSQL string.  I touched the web.config and now I am not even getting the custom error messages, I only get the friendly error:

Server Error
500.19 - Server error: Data for this file is configured improperly.
The requested page cannot be accessed because of a configuration error.

Just for the heck of it I re-ran the Setup/default and everything is fine:

Probing system...
File system permissions ok.
MSSQL database connection ok.
database permissions are sufficient to alter schema.
database initial schema already exists.
database core schema is up to date.
1 site(s) found.
Configuring feature Html Content - 00:00:00.2968180
Configuring feature Site Statistics - 00:00:00.5780140
Configuring feature Web Part - 00:00:00.6405020 .......etc.

........Configuring feature Xml/Xsl - 00:00:04.0148540
Ensuring all features are installed in server admin sites... - 00:00:04.0929640
Setup is complete, click the link below to go to the home page.
Site Home Page

Database PlatformMSSQL
Version2.3.6.7
StatusYour installation is up to date.

I have been reapplying it dozens of times I don't think that's it, but I'll try filezilla.  Here is the latest:

To get custom errors back I have to apply it in the user.config.  If I copy the custom error from the web.config and turn the mode to off I get:

We're sorry but a server error has occurred while trying to process your request.

The error has been logged and will be reviewed by our staff as soon as possible. It is possible that the error was just a momentary hiccup and you may wish to use the back button and try again or go back to the home page.

Is that the mojo custom error?

If I use the generic: <!--<customErrors mode="Off"/>

I now get this in the user config!

Server Error in '/' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized element 'customErrors'.

Source Error:

Line 45:
Line 46: 
Line 47:  <customErrors mode="Off"/>
Line 48: 
Line 49:  

Source File: C:\CustomerData\webspaces\webspace_00152178\wwwroot\noelogrady.ie\user.config    Line: 47

If I try to change it in the web.config  I get the friendly 500.19 error.  So I assume it's not reading the web.config properly. 

Is there a very basic web.config file that has the bare minimum necessary to run available?  That way I can see if it something in web.config. 

Is there anything that I should un-comment in the web.config for asp.net4 integrated mode?

The only change I initially made was to add the connection string to the user.config.  That's it.  What is the difference between the web.config & web.fulltrust.config?  I used the fulltrust one, I'll try the regular one.  The filezilla ftp client had no effect.

The only thing I can think of is having then ISP set the webspace to ASP.Net4 Clasisic mode.  What capabilities do I lose in this mode?

Thanks Joe,

At this point I have tried everything including contacting the developer .  I am going to to request the change to ASP.Net classic mode, and if that does not work.  I will try a new provider. 

Will I have to redo the Mojo setup after the ISP switches the webspace to the classic mode? 

Hi,

Existing a web.config file in your skin folder causes configuration errors like this. Are you sure about it?

Hope Helps

Asad

Search skin folder of your site (Data/Sites/[1]/Skins/[YourSkinFolder]) for web.config and delete it if exits. You can send me(a [dot] samarian [at] gmail [dot] com) your site url to look at it.

Ok while looking in the data folder I found the log file and here are the contents reapeated over and over again:

<configuration>
    <system.web>
        <httpHandlers>
            <add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
        </httpHandlers>
    </system.web>
</configuration>
   at System.Web.Handlers.AssemblyResourceLoader.GetWebResourceUrlInternal(Assembly assembly, String resourceName, Boolean htmlEncoded, Boolean forSubstitution, IScriptManager scriptManager)
   at System.Web.Handlers.AssemblyResourceLoader.GetWebResourceUrl(Type type, String resourceName, Boolean htmlEncoded, IScriptManager scriptManager)
   at System.Web.UI.ClientScriptManager.GetWebResourceUrl(Page owner, Type type, String resourceName, Boolean htmlEncoded, IScriptManager scriptManager)
   at System.Web.UI.ClientScriptManager.RenderWebFormsScript(HtmlTextWriter writer)
   at System.Web.UI.Page.RenderWebFormsScript(HtmlTextWriter writer)
   at System.Web.UI.Page.BeginFormRender(HtmlTextWriter writer, String formUniqueID)
   at System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer)
   at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)
   at System.Web.UI.HtmlControls.HtmlForm.Render(HtmlTextWriter output)
   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
   at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)
   at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
   at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)
   at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
   at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)
   at System.Web.UI.Control.Render(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
   at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)
   at mojoPortal.Web.mojoBasePage.Render(HtmlTextWriter writer)
   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)
   at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
2011-09-24 18:23:45,267 ERROR mojoPortal.Web.Global - 84.241.34.194-en-US - /AccessDenied.aspx- Referrer(none)
System.InvalidOperationException: The WebResource.axd handler must be registered in the configuration to process this request.

I believe you are right Joe.  Asad was nice enough to actually take a crack at it (Big Thanks to Asad) and could not get it to work either.  A summary googling the issue basically comes up with the following:

The problem occurs in ASP.net 4 Integrated mode and there are wildcard mappings in applicationhost.config file, one of the the main users of wildcat mappings is this Coldfusion handlers.  The wildcard mappings override the webresource.axd handler, thus wildcard mapings and asp.net4 integrated do not work together.  Microsoft has a hotfix to.net4 that solves this problem with ASp.Net4 Integrated.

1.  Fix:  Apply the .net 4.0 framework hotfix found at: http://support.microsoft.com/kb/2505146.  There are some prerequisite SP's and hotfixes that need to be installed before you do this.

2. Workaround 1: Lets you maintain .NET 4 Integrated mode:  Remove all the wild card mappings references (i.e.ColdFusion) from your applicationHost.config file in system32\inetsrv\config.   Alternatively if you need to keep those mappings you may do so using the example described by MS ASP.NEt developer Thomas Marquardt:" put ASP.NET and ColdFusion in separate applications and setting up the handler mappings so that ColdFusion is not mapped in the ASP.NET application and ASP.NET is not mapped in the ColdFusion application.  You can do this in the UI, or by editing applicationHost.config by hand and encapsulating the system.webServer/handlers section in a <location path="blahblah"> </location> section."

3.  Workaround 2: Switch App Pool to Classic mode.

The provider changed the App Pool to Classic, and the site now works. 

A couple of possible anomalies:

1.  When I click on the little question marks (i. e. help) I am directed to a separate static web page with the help info.  Is this behavior correct or should some type of js/ajax message box pop up?

2.  The Default.aspx does not open when I browse straight to mysite.ie, but when I explicitly type mysite.ie/default.aspx is works fine.  I have adjusted the default page priority on the host server so defaut.aspx is first, but that does not make a difference.  It's not a big thing and I will probably figure it out when I clean up all the junk that was created in attempts to get the site up.  It's actually desirable while I'm updating the site, but I am just wondering if this is an anomaly that might be peculiar to mojoPortal.

Just wanted to close the loop on this.

Hi Joe,

This was a new install of the latest version mojoportal-2-3-6-7-mssql-net40, not the upgrade.  Perhaps its a result of the Classic mode.  I've read some types of AJAX doesn't run in Classic mode.  I am using the viktopersson-hobbit_alt1 theme, but it's style.config looks fine.  I am getting a separate web page with just a white background.  So far, everything else seems to be working fine.   Thanks for the info.

Richard

Next Issue:  I changed the machine key with one generated by Mojo page, commented our the old key, pasted in the new key, and now I am getting the 500 error and cannot access Mojo and more, I tried putting back the old web.config, Passwords were set to clear mode. It's a no go. 

My wild guess is perhaps the IIS user or application user my be locked out, but I have no way to restart the site. Any ideas?.

Never mind I got this sorted.  I copied the full trust web.config from the installation files, opened the web.config in notepad, pasted the new machine key in the exact same space of the default machine key; uploaded it and it worked.  I'll just leave that here for anyone else who might have a similar issue.

I'll tell you; I learned a lot more that I really wanted to know about Mojo over the last few days.  One thing for sure, I won't be implementing and kind of DI composing in this web.config file.