Resource file name error after SP2 of Win S2008

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

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.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
5/28/2009 2:27:35 AM
Gravatar
Total Posts 4

Resource file name error after SP2 of Win S2008

After applying Service Pack 2 of Windows Server 2008, my mojoPortal application "crashes", reporting several errors of the same type:

The namespace 'Resources' already contains a definition for 'nnn'

where 'nnn' are some of the file names of resources files in the global resources folder.

Googling on the error led me to believe that the the reason can be that a resource file is named wrongly. I deleted all resource files in that folder except for the default resource (English) and my language, and that solved the problem for me. Perhaps any user applying the Service pack will get the same error.

5/28/2009 5:17:12 AM
Gravatar
Total Posts 18439

Re: Resource file name error after SP2 of Win S2008

Hi Fred,

This issue is discussed in our FAQ http://www.mojoportal.com/faq.aspx

You need to delete files from the /App_GlobalResources folder where the file name ends with .zh-Hant.resx

In the latest version of mojoPortal these files have already been renamed to .zh-CHT.resx but the .zh_Hant.resx files may be hanging around from previous versions if you have upgraded. 

If you are running an older version of mojoPortal and you don't already see files with .zh-CHT.resx, then you could just rename the .zh_Hant.resx files to .zh-CHT.resx, otherwise just delete the .zh-Hant.resx files.

Hope it helps,

Joe

5/28/2009 5:49:07 AM
Gravatar
Total Posts 4

Re: Resource file name error after SP2 of Win S2008

Thank you Joe,

Sorry for my not reading the FAQ before posting. I mistakenly connected the S.P. install with this problem since I happened to see the symptom at the exact same time I installed this brand new service pack.

Also, thank you very much for your great work with this excellent system. I am impressed!

Regards,
Fred

(PS. Refering to the answer to the FAQ: my computer (including .NET Framework) is as updated as it could be.)

5/28/2009 5:59:35 AM
Gravatar
Total Posts 18439

Re: Resource file name error after SP2 of Win S2008

Hi Fred,

The FAQ changed, originally it recommended using the "new" names like zh-Hant.resx over the old names, but unpatched systems did not recognize the new names.

From what I understand though it was discovered some serious performance issue could occur in ASP.NET using the new names so my contacts at MS told me to rename back to the old names which I did a version or 2 ago and I updated the FAQ. It seems now with SP2 they have changed it so up to date systems no longer recognize zh-Hant. I think they did this to prevent performance problems and force app developers to go back to the old names.

So we have come full circle, where once it was systems that were not up to date didnot recognize the new culture names but now it is the up to date systems that no longer recognize those names and we are supposed to go back to using the old names.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.