I know there is posts with this issue, but nothing has worked so far.
So my issue is that when I get here:
<%$ resources:af.roi.web, InProgressTitle %>
The key is not found in the AppGlobalResources->af.roi.web.resx file, but I can find the file (and the key) in the folder bin/App_GlobalResources.
I have tried changing the Build Action of the resource file, same error.
I have activated windows feature (compatibility with IIS 6, Classic ASP, ...), nothing new.
I know this code work on the server with IIS 6, but I can't figure how to make it run on my local Windows 10 with IIS 10.
I hope one of you has an idea. Thank you anyway.
You can try the solution below:
Right click on your resource (resx) file
Go to Properties
Change "Build Action" to "Content"
If the solution above doesn't work, try "Embedded Resource" option for "Build Action" parameter.
If you are still getting the same error, try changing "Copy to Output Directory" value to "Copy Always". A folder named "App_GlobalResources" will be created when you publish the code. Make sure this folder is in the same location as the page that is giving resource file connection error.
Related
I recently bought a new computer. I moved the drives from my old computer to the new one, installed everything I needed to and opened my project. Now I'm trying to run my project in IIS express but it displaying an error specifying an html output as log file.
When I look at the html problem, it's a 500 error message generated by what looks likes an IIS page. It's saying that the config file cannot be found:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid
Config File
\\?\F:\Development\MyProject\API\web.config
When I switched to the new machine drive letters were changed, so the code I'm running is no longet on drive F like in the message above - it's now on a different drive. I've looked in my code - I have no reference anywhere to a specific path.
I've tried to do clean and rebuild but it doesn't work.
If I look inside files for the path I see that the DLLs are compiled with PDB file path inside them. Why is that? And what happens later on on production?
Also, how do I fix this problem? why does it keeps looking for old location?
I'm fairly sure the IIS Express metabase still has the old path configured for this site. Please see the following answer for how to locate the metabase file (it's usually here: \Documents\IISExpress\config\applicationhost.config):
Where is the IIS Express configuration / metabase file found?
I'm not sure what the most correct way is to correct the problem, but you should be able to manually edit this file and update the "physicalPath" attribute for your site to the correct path to resolve this problem.
I don't know the exact cause of my problem, but the solution was to delete all bin directories from all project folders and re-compile.
To delete the bin directory from all my project I wrote the following PowerShell script:
Get-ChildItem -Path . -Filter *bin* –Recurse | Remove-Item -Recurse -Confirm
I have added an application on IIS 7 and the physical path selected correctly.
However, I got this problem when browsing the application:
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable. the problem is also when I tried it like this: http://abc.com/default.aspx
but if I tried it with: http://abc.com/myimage.png => works
the server has installed .NET Framework 2.0, and also 4.0
Any idea what is wrong here?
THanks in advance.
Do you have the Default Document set to your homepage correctly?
One solution:
Try to add the type to IIS Mime types. Ex: I meet this error when try to click a mkv video file.
Open IIS Manager
Selection "MIME Type" feature
Add...
Enter this content
File name extension: mkv
Mime types: mkv/mkv
OK
Restart the website
Click the file again, its worked
I work with Visual Studio 2008 and work on a web project which contains a web site.
When opening the solution file, I receive the error message:
Unable to open the Web site http://localhost/myWebsite.de. The Web site http://localhost/myWebsite.de does not exist.
I can see the web site greyed out, with the remark "unavailable", in the solution folder.
It is possible to add the web site to the solution, but after relaunching Visual Studio, it´s gone again.
Has anyone had this problem in a similar way?
Open the existing Solution file using notepad, Copy the actual project Directory path and update the solution file content with respect to following options alone
Debug.AspNetCompiler.PhysicalPath = "update the path here"
Release.AspNetCompiler.PhysicalPath = "update the path here"
SlnRelativePath = "update the path here"
leave the remaining config untouched
I think KB 326497 has your answer. Setting up an IIS virtual directory to point to the location the site is running from corrected this error for me.
Question was probably not general enough to answer it...
Must have been some problem with my SourceSafe, after I copied the web site to a
local folder, I had no problems any more.
Please Check with the host file located in "C:\Windows\System32\drivers\etc" directory. There might be chances for redirecting localhost to some other host environment by you or someone else.
If you remove the line for localhost configuration it will work for you.
Scenerio: I have an asp.net website that I am compiling successfully but keep getting an error in the browser saying that it can not find a referenced dll in the solution. I checked the directory in the Temporary ASP.NET File location and all of my referenced dll's are there except for the one it is failing to retrieve. I manually added the location it was looking for and the site worked.
The dll is referenced in code so it should have been moved to the temp folder. Does anyone have any idea why this would happen? I checked the properties on the referenced dll and copy local is set to true so it should be moved to the output directory.
Right click on the DLLs in your References/Bin directory in your project and look at the Copy Local property. Make sure they are set to True.
After hours of searching google and finding nothing, I decided to take a look at the actual properties of the dll file. To my surprise the issue ended up being permissions. For some reason the one dll that was beating me up all day needed correct permissions to be moved to the output folder. ughhh.
When you say "referenced in code" do you mean it's listed in the project file's Reference section? Or do you mean you are manually referring/naming it in your source code?
Have you tried this in your web.config (or higher up the config chain?)
<hostingEnvironment shadowCopyBinAssemblies="false" />
Where exactly are you expecting it to be copied? What is the path the error message is reporting?
I'm receiving "culture name 'uploads' is not supported" when my ASP.NET application start. Where do I have to view/debug to toggle the error?
A full-text search for "uploads" returns 0 entries in my project.
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
Do not worry, it is not a real error.
When the runtime tries to find which resource assemblies exists, it tries to enumerate folders where compiled DLL files reside. It assumes the name of the folder is the culture name, so it 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 :).
The runtime ignores some predefined folders like "hash", but not "uploads". So we have to live with it.
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.
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.
It sounds like maybe you have some code somewhere that is trying to set the culture based on a URL pattern (this may be tracked down if it is possible to get a stack trace). 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.
If the application is it built upon DotNetNuke (and not a simple ASP.NET application), this kind of error generally occurs in DotNetNuke due to the issue described in Culture name '__page' is not supported.
If you are not using DotNetNuke, check your Application_Start code (in the Global.asax file). It might be setting the CultureInfo. Or check your web.config file for any invalid culture values.
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.