Error after February (2010) CU on SharePoint 2007
I have applied the February Cumulative Updates to a medium size SharePoint 2007 Farm and everything from the Configuration Wizard through to the install log showed the updates as successful. Initial testing also showed it was fine but the following working day we have found a problem in Document Libriaries and Lists. Basically you can not add or update the columns in a Document Library or List and it returns the error: Culture ID 1164 (0x048C) is not a supported culture. Nothing else appears to be affected and this does not affect every Web application as MySites are fine yet TeamSites are affected. Turning on full logging brings the following information: 04/13/2010 08:19:10.84 w3wp.exe (0x2794) 0x17B4 Windows SharePoint Services General 8nca Verbose Application error when access /_layouts/FldEdit.aspx, Error=Culture ID 1164 (0x048C) is not a supported culture. Parameter name: culture at System.Globalization.CultureTableRecord.GetCultureTableRecord(Int32 cultureId, Boolean useUserOverride) at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean useUserOverride) at Microsoft.SharePoint.SPFieldCurrency.GetCombinedNumberFormatInfo(NumberFormatInfo nfiFmt, Int32 currencyLocaleId, SPNumberFormatTypes displayFormat) at Microsoft.SharePoint.ApplicationPages.BasicFieldEditPage.GetCurrencyItemString(Int32 lcidCurrency) at Microsoft.SharePoint.ApplicationPages.BasicFieldEditPage.PopulateCurrencyList(DropDownList ddl) at Microsoft.SharePoint.ApplicationPages.BasicFieldEditPage.OnLoad(EventArgs e) at System.Web.... 04/13/2010 08:19:10.84* w3wp.exe (0x2794) 0x17B4 Windows SharePoint Services General 8nca Verbose ...UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 04/13/2010 08:19:10.83 w3wp.exe (0x2A30) 0x13E4 Windows SharePoint Services Database 7t61 Verbose DatabaseConnectionString acquired. Server=XXXXXXXXX;Database=XXXXXXXXXX;Trusted_Connection=yes;App=Windows SharePoint Services;Timeout=15 Our next thought is to re-run the Configuration Wizard be we have to schedule this in as an outage for the system. Any thoughts or tips would be greatly appreciated as this has got a few of us confused.
April 13th, 2010 11:06am

Than Sharepoint issue, after going through a few posts, I see it as .net framework issue. http://www.ironspeed.com/Designer/5.2.0/WebHelp/Part_VI/Culture_ID_XXX_is_not_a_supported_culture.htm Link above is not sharepoint issue but the same error due to ASP.net frame work. http://www.windows-tech.info/1/eb373f391b0489cf.php also shows this to be ASP.net framework issue. Did you install the Language PACKS Properly on your system? You should check it again. You might have to reinstall AP.net frame work using ASPNET_REGIIS -u (to uninstall) ASPNET_REGIIS -i (to reinstall) and check the issue. Considering this Production environment and issue, I would recommend opening a case with Microsoft CSS and work with them to get it resolved.I LOVE MS..... Thanks and Regards, Kshitiz (Posting is provided "AS IS" with no warranties, and confers no rights.)
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2010 11:50am

Thank you for your response and we had seen similar problems posted on the Internet which are not SharePoint. There are no language packs that I am aware of on this system as it is a purely UK based customer. But the use of ASPNET_REGIIS is something I will consider trying. Will post any result up when I have resolved this rather unusual issue but if anyone else has any thoughts greatly appreciated!
April 13th, 2010 1:41pm

Hi Cleggie... I've seen this issue twice. Once I was able to fix it with help from Microsoft. After updating we copied files from backup into the app_bin folder in the virtual directory. Since the files were not the Feb Cumulative Updates version, it caused this problem. We had an extended virtual directory that had the proper files and simply copied them over into the app_bin folder and it worked. The exact file was Microsoft.SharePoint.ApplicationPages.dll. Make sure it is at version 12.0.6529.5000. It's now happening on a web application that we migrated over from SharePoint 2003. All the correct files are in the app_bin folder. Can't figure out why it is happening. Anything you find would be much appreciated. I'll share any information I come across as well.
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2010 4:32pm

Thanks I am still getting this but will check what you suggested. Anything I find I will post up on this site.
April 15th, 2010 6:46pm

Well I checked and some of the Web Applications had not been updated with the latest version of this dll. So I copied them over and had to recycle the appliction pool for the affected Web Applications so it could load up the new file and it is all working.So thank you for your help. As to why else it might fail then I spent a while looking at all options and wasnt getting far so fear I may be of no more help for you.
Free Windows Admin Tool Kit Click here and download it now
April 15th, 2010 8:09pm

We just applied the Feb 2010 CU and we are experiencing the same problem. I checked the web applications and we are running the version of the DLL listed above. Can you confirm that that is the version you used to correct your issue?
April 16th, 2010 11:13pm

Add me to the list. :) Replacing the DLL's and recycling had not effect.Steve Hahn
Free Windows Admin Tool Kit Click here and download it now
April 20th, 2010 3:17pm

Replaced all versions of the files: Microsoft.SharePoint.ApplicationPages.dll with version 12.0.6529.5000. Recycle did not fix it, but an IISReset seems to have fixed the problem. Hopefully, it will work for others. :) Steve Hahn
April 20th, 2010 8:44pm

This is one part of the puzzle, to get you closer to the solution. After checking all the virtual directories to make sure the Microsoft.SharePoint.ApplicationPages.dll is up to the 6529 version, check the GAC. I did not see any instances of the dll not being updated anywhere but in the GAC, the dll was on 6214. After removing the dll from the GAC and an IISReset, this resolved the issue.bwebmasta, MCP
Free Windows Admin Tool Kit Click here and download it now
June 16th, 2010 8:53pm

If you are using IIS 6.0, IIS reset is not necessary. Just stop the app pool that the web application uses, copy the file, and then start the app pool again. At least that way you minimize the number of sites that become inaccessible to only the ones using that particular pool. In my environment, we have multiple web apps spread across multiple 4 or 5 app pools.
June 28th, 2010 6:24pm

Where are all of you getting this version of the Microsoft.Sharepoint.Applicationpages.dll from? This file is not updated in any of the virtual directory folders on the server. If I need to get this file updated to that version then where do I get it from? Microsoft? What a joke.
Free Windows Admin Tool Kit Click here and download it now
October 15th, 2010 12:03am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics