I'm trying to properly configure my RSS feed through Sitecore. I'm getting this error:
"Feed is not configured properly, the feed cannot be rendered. Check Sitecore log for full error report.
Could not load file or assembly 'file:///C:\Inetpub\wwwroot\CabotTwo\WebSite\bin\Support.323326.FeedRenderer.dll' or one of its dependencies. The system cannot find the file specified."
Unfortunately, I have no real experience at all with Sitecore. Does anybody know what I need to do to fix this?
It looks like you have a reference to a DLL from Sitecore product support. Is that assembly mentioned in your Web.config? Is it present in your bin directory?
Related
I was trying to run a .cshtml file but it gave an error:
Server Error in '/' Application.
--------------------------------------------------------------------------------
This type of page is not served.
Description: The type of page you have requested is not served because it has been explicitly forbidden. The extension '.cshtml' may be incorrect. Please review the URL below and make sure that it is spelled correctly.
Requested URL: /index.cshtml
So I searched for the solution and found that I had to edit the web.config file which is in the root directory(here it is My Site), but there is no file like that there there is only an index.cshtml which I had created.
I searched even the IIS and the IIS Express folders in Programs Files\ but there was no file like that?
If you are using WebMatrix, maybe your mistake was the starting point choice.
If you want to create a new Web Pages site you must start from a template in the Template Gallery of WebMatrix. Pay attention that the Empty Site template differs from the Empty Site option outside the Template Gallery because the first holds the files (binaries, packages and the web.config too) that are needed.
As the server error suggests, .cshtml files are not served, the reason for this is because they are server-side files that make up your application, they are just one piece of a much bigger picture.
If you launched your web application in debug mode and the URL in the browser was something like http://localhost:2932/Views/Home/Index.cshtml, just drop the /Views/Home/Index.cshtml part of the URL.
I am getting this error when trying to use the numericupdown control:
Assembly 'AjaxControlToolkit, Version=3.0.30512.20315,
Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' contains a Web
resource with name
'AjaxControlToolkit.NumericUpDown.NumericUpDownBehavior.debug.js', but
does not contain an embedded resource with name
'AjaxControlToolkit.NumericUpDown.NumericUpDownBehavior.debug.js'.
I have researched this and have found that this problem arises because the source code for the AJAXToolkit calls the file 'NumericUpDownBehavior.debug..js'. The only solution I have seen is this one:
Download the ajax control toolkit with the source code. Go to the folder
"AjaxControlToolkit\NumericUpDown\" and there's a file there named
"NumericUpDownBehavior.debug..js". Rename it to "NumericUpDownBehavior.debug.js".
After this open the "AjaxControlToolkt" project in Visual studio and choose "Show All
Files" in Solution Explorer". Exclude from the project the file with
the double dots (.debug..js) and include the correct one. Right click
on the .js file and choose "Properties". From there Choose the Build
Action "Embedded Resource". Compile it and add the resulting dll to to
your projects where you are using ajax (Replace the dll's).
I have tried this but I must have done it wrong because it did not work. Can anyone provide a more detailed solution to this problem?
Thanks!
I have a solution with a website and a class library. I have renamed the class library project from Insight_WebControls to Insight.WebControls. I have also renamed the assembly it produces in its properties.
I have removed from the website's references the old class library and added the new.
However, when I try to build the website, I get the error 'Could not load file or assembly 'Insight_WebControls' or one of its dependencies. The system cannot find the file specified.' There is a dll called 'Insight.WebControls' in the bin folder.
Clearly some part of the website is still looking for the old filename. Can anyone tell me how to point it to Insight.WebControls.dll instead?
Thanks
David
Just as a couple of shots in the dark:
Have you looked inside the web.config to see if there is any reference to the old file name in there?
If that turns up a blank then try opening up the project file for the web site and do a similar search.
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.