I am using DNN 2.1.2 for the first time and I get the following error:
"It appears that your menu dll is out of sync with your script file". Has anyone seen this before?

Thanks

This happens when the version of your solpartwebcontrols.dll is not in sync with your script file (spmenu.js). Usually this happens when a user opens up the dotnetnuke project in VS.net and has the reference path for the solpartwebcontrols.dll in the wrong place, therefore an older version of the control gets put into the bin folder.

I initially had 3.0.10 on this machine and then deleted it. I then installed 2.1.2. At this point, I got the error. Once I deleted temporary files and refreshed the page, this error went away.

So what do we have to do??

make sure the solpartwebcontrols.dll in your bin folder is the right version. right-click on it and go to properties, then click the version tab. You will see the version... then open up the spmenu.js file in the controls\solpartmenu folder and check the version in the header. Find the version of the dll that matches and put it in the bin folder. (if you haven't updated the menu, then this dll will be in the original zip for dotnetnuke). If you have upgraded then the files will be in the upgrade zip you downloaded.

"It appears that your menu dll is out of sync with your script file"
 I get this error if I change the DNN 3.1 Blog Module Settings\Page Settings\Cache Time(secs) to anything other than zero.


Can anyone else confirm? Does anyone know a work around?

Thanks,
Mike

Mike,

I had the same problem with the Forum Module and set the Cache to zero and the menu dll sync error issue was resolved.

Thank you!

Lewis

When you turn on module chaching, the structure of the module changes. The PortalModuleBase loads a copy of itself from the cache into itself. The parent's ID property is set in the Skin's InjectModule method, but I've found that the child's ID property is never set (I still use DNN 3.2), so it can raise problems (for example, you can't find local resource files).

The error above comes from spmenu.js, line number 373 in my case, anyway it's the definition of SolpartMenu.prototype.GenerateSubMenus function. The script can't find a certain span, so it thinks that the version is wrong. You can alter the function to find out which span is missing. That would one of the empty spans at the beginning of the page, ending with "_divOuterTables". I suspect that the module contains a solpart menu, and while the module renders in a wrong way (due to the problem above), the menu renders wrong as well, forgetting to put the above span (among other things).

ulu