DotNet Framework Mismatch.

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
2/19/2015 8:11:34 PM
Gravatar
Total Posts 58
"Digg-in yourself to achieve excellence!" Follow #GPsays

DotNet Framework Mismatch.

Hi Joe,

I happen to catch up with a confusion that my Web host(arvixe) is also finding difficult to find the cause.

As you know, the mojoPortal's recent version isnt available on the Web Gallery, I tried installing manually by downloading the Non-Source version from our mojo's Codeplex download area.

I'm wondering why is that not able to run any of the versions from 2.4.0.4 to 2.4.0.8 which completely runs on Target Framework 4.5 and 4.5.1, which seems to be available in the hosting environment.

I asked my host to follow few steps to check the DotNet framework and its IIS registration and associations as per one of my posts http://www.guruprasad.me/blog/how-to-find-dot-net-framework-and-aspnet-registered-quick-tips.aspx
and the Server admin guy did the same and found the entry for .Net framework 4.5.51650 available.

Now I'm able to test a sample web page that confirms both framework 4.5 and 4.5.1 as TargetFramework versions as per the Web.config configuration,

<configuration>
    <system.web>
      <compilation debug="true" targetFramework="4.5.1" />
      <httpRuntime targetFramework="4.5.1" />
    </system.web>
</configuration>

 And the sample page works fine, but not the mojoPortal installation.

Please help in fixing this issue.

Thank you in advance.

Regards,

Guruprasad.

2/20/2015 9:29:59 AM
Gravatar
Total Posts 2253

Re: DotNet Framework Mismatch.

Hi Guruprasad,

If you were to place this on your test page, what does it output?

<%=Environment.Version%>

Thanks,
Joe D.

3/2/2015 10:08:11 PM
Gravatar
Total Posts 58
"Digg-in yourself to achieve excellence!" Follow #GPsays

Re: DotNet Framework Mismatch.

Hi Joe,

Thanks for your kind response.
Im sorry for the delay in responding you,

The Framework Version says "4.0.30319.34209" on the Sample Page that I'm testing Arvixe's Space.

The Web Host is not ready to accept as he says....

Hello,

Don't go after the name, 4.5.2 will display as 4.0 as it is not a major update. Your tests too indicated it is 4.5.2 and there is no need to re-install or re-register .NET 4.5.2.

See http://stackoverflow.com/questions/9559372/how-to-set-net-framework-4-5-version-in-iis-7-application-pool
 

Please help, so that I can run the mojoPortal from any of its versions from 2.4.0.4 to the most recent 2.4.0.8.

Thank you.

3/2/2015 10:43:33 PM
Gravatar
Total Posts 2253

Re: DotNet Framework Mismatch.

We are running mojoPortal 2.4.0.8 on a variety of windows server OS versions (2008, 2008 r2, 2012, 2012 r2) and we are not having any problems. All of our systems are fully patched with .net 4.5.2.

Without more information, I cannot help further. If you are indeed having .net version conflict issues, the problem is more than likely not mojoPortal.

Thanks,
Joe D.

3/3/2015 7:54:43 AM
Gravatar
Total Posts 18439

Re: DotNet Framework Mismatch.

this thread says only that you are unable to run something that should be able to run, you provide no actual description or details of the problem at all, no error message, no stack trace, no clue even what kind of problem other than you say framework mismatch, but no evidence provided of framework mismatch or any other problem. 

 

3/4/2015 6:11:04 AM
Gravatar
Total Posts 58
"Digg-in yourself to achieve excellence!" Follow #GPsays

Re: DotNet Framework Mismatch.

Hi Joe Audette and Joe Davis,

I understand that without sharing any Stack trace or error as output, will be hard for you to analyse. Im sorry about that.

This is what I recieve as error, when I run with the target Framework as 4.5.1.

Server Error in '/' Application.

Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: The compiler failed with error code 1.


Show Detailed Compiler Output:

C:\Windows\SysWOW64\inetsrv> "C:\Windows\Microsoft.NET\Framework\v4.0.30319\csc.exe" /t:library /utf8output /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\386b5143\00ffd598_3549d001\Lucene.Net.Contrib.Memory.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_32\System.Web\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\bd2693a7\00ffd598_3549d001\MetaDataExtractor.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\11491900\00ffd598_3549d001\DotNetOpenAuth.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\17efab0f\00ffd598_3549d001\dotless.Core.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\74311a32\00ffd598_3549d001\Argotic.Extensions.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activities.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\d9b15e60\00ffd598_3549d001\Brettle.Web.NeatHtmlTools.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\8b1dcd97\002c079a_3549d001\Newtonsoft.Json.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\4730372c\00ffd598_3549d001\Argotic.Core.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\c01fcf0d\002c079a_3549d001\Novell.Directory.Ldap.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\f6a19422\00ffd598_3549d001\log4net.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\9395dc5a\002c079a_3549d001\System.Web.WebPages.Deployment.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Extensions\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Extensions.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.ApplicationServices\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.ApplicationServices.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\fea4fbb8\00ffd598_3549d001\Google.GData.Extensions.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.WebPages.Deployment\v4.0_2.0.0.0__31bf3856ad364e35\System.Web.WebPages.Deployment.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\8c332d9e\002c079a_3549d001\System.Web.Helpers.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.DataSetExtensions\v4.0_4.0.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\04aced53\00ffd598_3549d001\Antlr3.Runtime.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\62fed480\002c079a_3549d001\Subkismet.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.Activities.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\d223b32e\002c079a_3549d001\mojoPortal.Net.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\6e2b3642\002c079a_3549d001\WebStore.Business.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activation\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activation.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\c93f7302\00ffd598_3549d001\ContentSecurityPolicy.Net.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\802b811e\002c079a_3549d001\System.Web.Mvc.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\8246beec\00ffd598_3549d001\HtmlDiff.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\84a54490\002c079a_3549d001\ZedGraph.Web.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\85abab72\002c079a_3549d001\Microsoft.Web.DistributedCache.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\b5b86feb\002c079a_3549d001\WebStore.UI.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\10edf22f\00ffd598_3549d001\HtmlAgilityPack.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\App_GlobalResources.dzmgv9os.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\022b167f\002c079a_3549d001\Microsoft.WindowsFabric.Data.Common.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\5841529b\002c079a_3549d001\System.Web.Optimization.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\7fbd7479\002c079a_3549d001\System.Net.Http.Formatting.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ComponentModel.DataAnnotations\v4.0_4.0.0.0__31bf3856ad364e35\System.ComponentModel.DataAnnotations.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\abb98ae5\002c079a_3549d001\mojoPortal.Web.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\5744a3f6\002c079a_3549d001\mojoPortal.Business.WebHelpers.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\1fd4d96d\002c079a_3549d001\Microsoft.WindowsFabric.Common.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.DynamicData\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.DynamicData.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\17cde21b\00ffd598_3549d001\Ionic.Zip.Reduced.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\f4fba1ca\002c079a_3549d001\System.Web.Razor.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\a1b2cd8d\00ffd598_3549d001\Lucene.Net.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\e768a02f\002c079a_3549d001\Microsoft.ApplicationServer.Caching.Core.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\5d978afa\002c079a_3549d001\mojoPortal.Features.Business.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.WorkflowServices\v4.0_4.0.0.0__31bf3856ad364e35\System.WorkflowServices.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\be008d7b\00ffd598_3549d001\Google.GData.Client.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\9bf4bf22\002c079a_3549d001\Microsoft.Web.Preview.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\8ef93fa9\002c079a_3549d001\WebGrease.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\a023ee20\002c079a_3549d001\mojoPortal.Business.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\c98910bf\00ffd598_3549d001\Brettle.Web.NeatHtml.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\bc992243\00ffd598_3549d001\Microsoft.ApplicationServer.Caching.Client.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\6acb26a2\002c079a_3549d001\Recaptcha.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\08d4a9f2\002c079a_3549d001\SanitizerProviders.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\58675bf9\002c079a_3549d001\TimelineNet.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\9a9e9c2d\00ffd598_3549d001\Google.GData.Analytics.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\7d273d2f\002c079a_3549d001\mojoPortal.Web.Framework.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\41483798\00ffd598_3549d001\Argotic.Common.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\4a1f5b91\00ffd598_3549d001\Lucene.Net.Contrib.Analyzers.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\3acaaa74\002c079a_3549d001\Mono.Security.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\10a20224\002c079a_3549d001\mojoPortal.Features.Data.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\10998d27\00ffd598_3549d001\Lucene.Net.Contrib.Highlighter.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\bf3f3354\002c079a_3549d001\mojoPortal.Web.Editor.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\572d793b\002c079a_3549d001\mojoPortal.Data.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\4bd0513f\002c079a_3549d001\WebStore.Data.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\f8ac8962\002c079a_3549d001\System.Web.WebPages.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\b64be6da\00ffd598_3549d001\AjaxControlToolkit.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\eda2e942\00ffd598_3549d001\CSSFriendly.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\8ac81304\002c079a_3549d001\mojoPortal.Features.UI.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Web.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Web.Infrastructure.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Web\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Web.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.WebPages.Deployment\v4.0_1.0.0.0__31bf3856ad364e35\System.Web.WebPages.Deployment.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Data.Linq.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\c0e22b77\002c079a_3549d001\mojoPortal.Web.Controls.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\cccc1726\002c079a_3549d001\System.Web.WebPages.Razor.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\5094510c\002c079a_3549d001\System.Web.Http.WebHost.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\b394118b\002c079a_3549d001\ZedGraph.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\77acb50c\00ffd598_3549d001\GCheckout.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\assembly\dl3\1e4163fd\002c079a_3549d001\System.Web.Http.dll" /out:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\App_global.asax.djrmkgf4.dll" /debug- /optimize+ /w:4 /nowarn:1659;1699;1701;612;618 /warnaserror- "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\App_global.asax.djrmkgf4.0.cs" "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\8505fa45\41b5102c\App_global.asax.djrmkgf4.1.cs"



Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34209

Regards,

Guruprasad

3/4/2015 8:58:44 AM
Gravatar
Total Posts 18439

Re: DotNet Framework Mismatch.

I'm guessing this is caused by bad deployment. files are not in the correct location or extra copies of files or folders are in incorrect locations or extra web.config files exist in unexpected locations and this is causing problems for the asp.net compiler which is trying to process all these files.

please provide details about how you installed mojoportal

what file package you used

was it a new install in empty hosting or something else already installed there

name of folder where the files were deployed and what files or folders were deployed

give as much detail as possible of the steps you made to install

3/4/2015 12:35:06 PM
Gravatar
Total Posts 58
"Digg-in yourself to achieve excellence!" Follow #GPsays

Re: DotNet Framework Mismatch.

Hi Joe Audette,

I tried from the Most recent version mojoportal-2-4-0-8-mssql-net45-deploymentfiles.zip directly deployed to the Site's root making sure, there're no files including any prior Web.config (As you know Ive been using mojoPortal and developing sites since 2009).

Also tried earlier with the mojoportal-2-4-0-4-mssql-net45-deploymentfiles.zip package too. It fails with the same error.

How do i Deploy?
--------------------------

1. I used a simple Zip and Extract method from Desktop to FTP and extract from File Manager(which I ever use to do my installations, which use to work great).

2. I download the package and zip ONLY the wwwroot content as a direct ZIP file and deploy them to the root site.


Whereas, it works great until the version 2.4.0.3. Actually I noticed when I developed a site on 2.4.0.4 and had very tough time to downgrade the work along with theming and site, way back to its prior version (when I was discussing about the SSL issue with you)

Now, I happen to test on Arvixe's Juniper Server, which is a Windows 2012 R2 Standard build machine which is not favoring mojoPortal  versions from 2.4.0.4 to 2.4.0.8 (until now).

But any Sample page works fine. So cant understand where exactly things go wrong! Please let me know what I can do further.

Thanks in Advance,

Guruprasad
 

3/4/2015 1:03:20 PM
Gravatar
Total Posts 18439

Re: DotNet Framework Mismatch.

maybe this thread will help you, ask Arvixe to disable 32 bit on the application pool, it seems to cause problems on Arvixe servers

though I also still have doubt about your install process and whether extra files are deployed such as temporary files leftover from extracting on the server. I don't trust any web control panel file manager. I extract locally and upload files directly by ftp

downgrading any version of mojoportal is always problematic, in some specific cases it can work if there is not much difference between versions but generally if a site has a newer version installed, going back does not change the newer schema changes and the old code may  not work with the newer schema, the only time its ok is if there were no schema changes between the 2 versions.

no-one else is reporting this problem so it does not seem the problem is intrinsic to the mojoportal package, it is some strange deployment problem in my opinion

3/4/2015 2:53:24 PM
Gravatar
Total Posts 2253

Re: DotNet Framework Mismatch.

Hi Guruprasad,

You can also switch to i7MEDIA for your hosting. There isn't a host in the world that knows mojoPortal better than us and we guarantee full compatibility with mojoPortal. We also do not overload our servers like most shared hosting companies.

Thanks,
Joe D.

3/6/2015 10:04:31 PM
Gravatar
Total Posts 58
"Digg-in yourself to achieve excellence!" Follow #GPsays

Re: DotNet Framework Mismatch.

Hi Joe Audette and Joe Davis,

Glad News! The issue is fixed.

My Hosting provider admitted there's an issue with the Application Pool for the websites.

Hi,

>>>Was that an 32-bit issue on the App Pool?

Yes, you are right. I have enabled '32 bit application' (set to TRUE )on application pool configuration setting for the domain.

Please don't hesitate to let me know if you need any more assistance.

Thank you!
 

So, the thread that you shared across, really helped Joe. Thanks a ton.

Wishing you have a great day with Loads of Smiles ahead :-)

Regards

Guruprasad

3/7/2015 8:15:05 AM
Gravatar
Total Posts 18439

Re: DotNet Framework Mismatch.

That is strange since on the other thread he always had problems until that was set to false, true caused errors for him

3/8/2015 11:09:09 AM
Gravatar
Total Posts 58
"Digg-in yourself to achieve excellence!" Follow #GPsays

Re: DotNet Framework Mismatch.

Whoa! that was short Luck!

The site doesnt work except the Home page, which is default.aspx.

This time I have asked the Host to do a deep analysis on why their configuration is failing to run.

@Joe Audette: Do you have any idea, why is it failing and helping few folks to have the application run having 32-bit disabled and in my case with 32-bit enabled on app pool?

Is there a Work Around for this? Can you release some quick patch to the release to help us come outta these kinda issues?

Or any guideline, other than changing the web host?

Thanks,

Guruprasad

3/8/2015 11:22:32 AM
Gravatar
Total Posts 18439

Re: DotNet Framework Mismatch.

I cannot release a patch since there is nothing wrong in mojoPortal that I am aware of. No fault in mojoPortal has been identified. 

mojoportal does not require 32 bit enabled and does not require it disabled. I only pointed out that someone else had a recurring problem in the same hosting when 32 bit was enabled.

I have no idea why the problem is happening. Many many others including myself use the exact same packages without any error.

changing settings like 32 bit on the application pool does force the application to restart and re-compile, and that may resolve an error for a while.

my advice is disable 32 bit since it is not needed by mojoportal and some people get errors in the same hosting with it enabled, and making that change may resolve the problem at least for a while.

errors that happen down in the windows/temporary aspnet files are outside the control of mojoportal code and more related to the asp.net compiler and server configuration, though it can also be caused by missing or mismatched set of deployment files. generally if I encounter an error down there I stop the web site. delete those temporary files and restart the web site so that aspnet can re-compile clean. stopping the iis web site is required because the files cannot be deleted while they are in use.

3/10/2015 3:20:32 AM
Gravatar
Total Posts 58
"Digg-in yourself to achieve excellence!" Follow #GPsays

Re: DotNet Framework Mismatch.

Hi Joe,

You're right!

Looks like the Temporary Internet Files have cached files of the previously compiled application. The Web Host arvixe says...

Hey There,

Compiler issues with be due to temporary files being held in the wrong architecture (32 or 64bit).

These temporary files are removed when rebooting the server or if our server management team does a manual purge, which I believe is what happened here.

You are free to use which ever MojoPortal version you'd like.

Thank you,

I guess, I have to ask them to enable/disable the 32-bit on Application Pool, whenever I get that issue and also ask them to clean the Temp folder.

Rest, as assured by them, seems like, will work good hereafter.

Even I wonder how these strange things happen, when it doesn't create any issue on local Development Win Server 2012 R2 and on Win 8.1.

Anyways, thanks a lot for assisting and helping across to get this issue fixed.

Smiles Ahead Joe,

Regards,

Guruprasad

You must sign in to post in the forums. This thread is closed to new posts.