Sadegh,

I was able to login to your site in IE 9 on win7

hamiddebel63,

your site has javascript errors happening if you use browser dev tools you will see errors in the console. I suspect that is causing the problem. I would solve those problems first and see if it solves the login problem.

you still have javascript errors happening on the page, you need to solve those because they causing the problem.

If you use Chrome, right click the page and choose Inspect Element, then click on the console tab to see the script errors.

I think you may need to get help from your host because the problems look like something is bad about IIS configuration or the installation of the .NET framework.

Scripts using .axd extension are resulting in a 404 which seems like the extension is not registered correctly in IIS.

sys is undefined means the asp.net ajax framework is not working or not loading, do some googling to find solutions for those problems, they are not caused by mojoPortal but are preventing mojoPortal from working correctly.

You may need to ask your host to re-install the .NET framework or ideally install the newer .NET 4.5 framework

Hi Christian,

The problem with a javascript error "Sys is not defined" has come up a few times recently and when it happens it does cause login failure and the solution you posted is correct and solves the problem.

But to clarify,this should in general not be needed in Web.config under .NET 4 and it never was in the Web.config file that we ship in the .NET 4 packages of mojoPortal as far as I know. I have checked our source code repository where I can see the complete file history and it has never been removed from the file and has never been in the file. I also looked in our old packages for mojoPortal 2.3.9.4 and it does not exist in the web.config file for the .NET 4 packages of that version. I do not have that in any of my site installations including this site.

Something similar was required for .NET 3.5 and has been our web.config for .NET 3.5 packages and still is there in our current package for 3.5, maybe that is where you saw it in versions 2.3.9.4.

In .NET 4 they moved this kind of thing to machine.config so it is not needed in Web.config, and in fact it cannot be in both places or it causes an error. For example if I add it in Web.config on my installation it causes this error:

"Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'ScriptResourceIntegrated-4.0'"

So whenever this problem of sys is undefined comes up for .NET 4 it seems to me like something is not configured correctly in the installation of .NET 4 on the server. When it does come up the site can be fixed by adding this to Web.config but it should not be needed on a correctly installed and configured .NET 4 installation. In fact if you put this in Web.config and later the server configuration gets corrected it will crash the site with the above error. Myself I would try re-installing .NET 4.5 framework instead of putting that in Web.config.

If you create a new .NET 4 web application project in Visual Studio the web.config file it generates also does not have this. So it is not something missing in our Web.config file and not something we should add there by default.

Best,

Joe