Inappropiate web.config for new server?

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.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

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.

5/16/2017 7:36:01 AM
Gravatar
Total Posts 218

Inappropiate web.config for new server?

Hello,

I am moving with some mojo-sites to another server.

Everything is fine for the newer versions.
But for an old version (2.3.3.4 MySQL) I get the error message after upload:

The "system.web.extensions / scripting / scriptResourceHandler" section has been defined twice.

This is the line from the web.config:

        <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />

 

If I comment out this line, then the next error message with nearly the same text regarding the next line comes, and so on, and so on.


        <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
          <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere" />
          <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
          <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
          <section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />

 

After I did this some times another error message accurs, something was missed. I think it was not the right way to solve the problem ... smiley

 

Best regards
Matthias

5/17/2017 9:42:54 AM
Gravatar
Total Posts 1188
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: Inappropiate web.config for new server?

When I upgrade our site, I start with the delivered web.config, and merge our custom changes into that. This is important because web.config contains things like the current CKEditor version path, etc.

Typically, any customizations will be in the user.config file, so about the only thing we need to customize web.config for is the timeout value and the custom machine key.

I'd recommend starting from the delivered web.config, and look for anything that needs to be changed for your environment.

I hope that helps.
Jamie

5/18/2017 12:48:07 AM
Gravatar
Total Posts 218

Re: Inappropiate web.config for new server?

Hi Jamie, thanks for your reply. If I next time make an update, I will try it.

Best
Matthias