I am using DNN3 3.2.1.  I jus created a module a tried to run add it on my site but it generates this error:

" MinMax persistance type of cookie requires a ModuleId"

Does anyone know why this occurs?

When you say delete the resx files, do you mean the localization ones in App_LocalResources or do you mean the ones matching the module controls in the module root?

I have a 3.2.0 that I started to see this one so I upgraded to 3.2.2, in dev enviroment.  The only thing which made it go away was compiling the dotnetnuke.controls.sln.

I was able to reproduce the problem with the modules I already mentioned. When I delete all the resx files in C:\Inetpub\wwwroot\Dotnetnuke\DesktopModules\Bonosoft - Multi Page content\App_LocalResources the error goes away. The same is valid for Inventua Side-Menu and Inventua Googlesearch. All running on .Net 2.0. These errors do not appear under .Net 1.1.

A clean install of DNN 3.2.2. does not create .resources files in C:\Inetpub\wwwroot\Dotnetnuke\App_GlobalResources that cause an upgrade from 3.1.1. to fail so I was not able to reproduce that problem. If you want me to do install 3.1.1 and then upgrade to 3.2.2. I can do that too.

Hi Mariette,

I got this exact error when I tested DNN 3.2.0 with ASP.NET 2.0, which I tested as a result of your post in the Inventua forums.  This error is actually just a follow-on side effect of the "real" error, which is a "ResX input is not valid. Cannot find valid "resheader" tags for the ResX reader and writer type names" (have a look in your log viewer to see these).

The error happens because DNN 3.2 ships with a web.config that is appropriate for ASP.NET 1.1.  Adding this to web.config fixed the problem.

  <compilation debug="false" strict="false">
      <buildProviders>
        <remove extension=".resx" />
        <remove extension=".resources" />
      </buildProviders>
      <assemblies>
        <add assembly="Microsoft.VisualBasic, Version=8.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
      </assemblies>
      <!-- register your app_code subfolders to generate granular assemblies during compilation
      <codeSubDirectories>
         <add directoryName="sub-directory name"/>
      </codeSubDirectories>
      -->
    </compilation>

Hi Anthony,

Thanks, that worked but the Filemanager in DNN 3.2.2 on .Net 2.0 does not work. It does not show any folders and gives an error 'Object required' in the left bottom corner of IE. When you click the refresh icon in the file manager this happens:

A critical error has occurred.
Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.

I got around that one in web.config, too.  Find the <pages> node, and add enableEventValidation="false", like this:

  <pages validateRequest="false" enableViewStateMac="true" enableEventValidation="false" />

I also am having problems here.  When adding a module to a new page. It seems all the solutions provided have not corrected the problem.  I am working in 4.0.2 form the starter kit using VS 2005 pro.

I unchecked the friendly URL feature and I no longer had the problem... 

hope this helps

Paul.