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.
3/6/2015 10:04:31 PM
Gravatar
Total Posts 57
Web Platform Evangelist.

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 57
Web Platform Evangelist.

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 57
Web Platform Evangelist.

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.