tags:

views:

1200

answers:

10

I'm receiving "culture name 'uploads' is not supported" when my asp.net app start. Where I have to view/debug to toggle the error? A full-text for "uploads" returns o entries in my project

A: 

Is the application a simple ASP.NET application or is it built upon DotNetNuke? This kind of error generally occurs in DNN due to this.

If you are not using DNN, check your Application_Start code (in the Global.asax file). It might be setting the CultureInfo. Or check your web.config for any invalid culture values.

Kirtan
+1  A: 

Do you get a stack trace? Sounds like maybe you have some code somewhere that is trying to set the culture based on a URL pattern. For example, sometimes I'll set up multi-lingual sites with urls like this:

http://www.example.com/en-US/
http://www.example.com/es-MX/

I'll then have code in my base page that looks at the URL and attempts to set the culture based on the URL path. But if you tried to hit a url like:

http://www.example.com/uploads

It would fail with an error like what you are seeing if you just blindly take the first path element and try to use it as the culture without checking it first.

Eric Petroelje
no :-) if can step in the debugger but it says "no source code". maybe it's loading the app in the global.asax
Robert
Sounds like Global.asax would be the place to start then. Probably in begin request?
Eric Petroelje
A: 

Assuming that your search through the project wasn't restrictive (widest possible search in all files), then my guess would be that your browser has a User language set to a custom string - "uploads".

In IE, you can check via Tools -> Options -> Languages -> Add -> User defined language.

Cerebrus
A: 

For what it's worth, I have the exact same problem with my setup (Webdev.webserver.exe, Firefox as a client).

The error occurs only on the first request, that triggers the Application context load (or reload)

@Haelix: it's not worth much, since you didn't answer any of the questions people have been asking? Are you using DNN?
John Saunders
+2  A: 

Do not worry, it is not a real error.

when runtime tries to find which resource assemblies exists, it tries to enumerate folders where compiled dll files reside. it assumes name of the folder is culture name, so tries to create a culture for it. unfortunately uploads is a folder which is created automatically by asp.net and it is obviously not a culture :).

runtime ignores some predefined folders like "hash" but not "uploads". so we have to live with it.

+3  A: 

I am getting the exact same error. ["culture name 'uploads' is not supported"]. I do not know what is causing it but I've been able to get around it by clicking [Debug|Exceptions (Ctrl-alt-E) and un-checking "Common Language Runtime Exceptions". I do not have an 'uploads' folder or file in my project and there is nothing in my project that has anything to do with multilingual support and the error fires right off the bat when I run my project ... looking at the call stack just walks me through a whole lot of mscorlib calls. I have no clue why it's even getting called.

+3  A: 

I've deleted this folder and it solved the problem: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\8dfb04ef\44bf70fb\uploads

Alex
search and deletion of 'uploads' folder under Temporary ASP.NET Files solved my problem as well. +1
A: 

Great Alex i solved in similar way. thanks ;-)

MacApp
A: 

JumpingLethalRampage, instead of unchecking all "Commong Language Runtime Exceptions," you could uncheck just "Common Language Runtime Exceptions > System > System.ArgumentException." You don't need to uncheck all CLR items.

A: 

Alex THANK YOU!!!! Had the same issue and that fixed it for me!!!

Jonathan Manley