I've inherited a skeleton Sitecore project based on Habitat (Sitecore 8.2 Update 6) but when I access the /sitecore url I'm getting the error:
Parser Error Message: Unknown server tag 'sc:PlatformFontStylesLink'.
In my folder serving the web site, I've used the web.config as supplied by a new Sitecore Instance Manager instance (this will be transformed by Habitat)
sc:PlatformFontStylesLink is a control Sitecore itself uses so for some reason it can't resolve the server tag. I'm guessing this is due to a configuration issue but Im not sure what exactly. The web.config includes this line:
<add tagPrefix="sc" namespace="Sitecore.Web.UI.WebControls" assembly="Sitecore.Kernel" />
Check the version of your sitecore.kernel.dll. Likely it is incorrect.
I've seen that happen if a project in your visual studio solution is referencing the wrong version of sitecore - and "copy local" is set to true.
So to fix this:
Restore the correct version of sitecore.kernel.dll t your site's bin folder (probably a good idea to check all your sitecore*.*.dlls )
Find the offending project - update the reference - and set "copy local" to false.
Also - seeing that you inherited a Sitecore site, and are likely to have more questions down the road - thee is a more specialized Sitecore Stack Exchange site. you might want to check out.
Related
I inherited an Umbraco 7 VS solution where all Umbraco packages are conveniently added through nuget, along with a dump of the database.
I figured I'd have no trouble getting it to build, but I'm a bit stuck on the Umbraco.Web.PublishedContentModels. This file wasn't included in source control, and was added as a reference for the main web project and another supporting project. In the web.config the ModelsBuilder Modelsmode is set to <add key="Umbraco.ModelsBuilder.ModelsMode" value="Dll" /> .
Obviously if I could open the web project, I could generate the Umbraco.Web.PublishedContentModels assembly, but I can't because the project won't build because of the missing Umbraco.Web.PublishedContentModels assembly.
The model builder VS plugin is also just a frontend for the web interface, so that won't work.
This seems like a Catch-22 situation. Any idea how to proceed?
I have solved this using the following steps:
Downloaded a fresh Umbraco site, exact same version, from Umbraco
Edited the web.config to point to my existing database
Changed the ModelsMode for the ModelsBuilder in the Web.config (<add key="Umbraco.ModelsBuilder.ModelsMode" value="Dll" />)
Copied most of the bin folder of the original site to the new site
This allowed me to generate a Umbraco.Web.PublishedContentModels.dll. It wasn't quite the same, but with some minor changes I could get it to build
Once it builds, regenerate the original Umbraco.Web.PublishedContentModels.dll and undo the changes
In conclusion; don't lose that file.
I have problem with IIS. I googled it but couldn't find a solution. I tried to change my config file but it didn't work. If you want any additional information I'm gladly add it. Thank you for all.
Here is my IIS settings
Here is the image of when I try to debug my website from visual studio 2015 (And my awesome paint skills :) )
Here is the image of my visual studio settings for web
It is some internal design of IIS configuration system that in rare cases such an error page comes without the actual line number for the real error (note the line 0 in the error page).
Based on my investigation so far, the most obvious cause can be a missing section definition in IIS schema folder, which probably breaks the XML parser.
The common module that leads to such missing section can be out of band IIS modules shipped as separate MSI downloads from Microsoft.
URL Rewrite module is probably the most likely culprit in this case, as people use it so often, but it is not included in the default IIS installation. Note that it can still be caused by other OOB modules.
A better way to analyze the problem, is to run Jexus Manager (http://jexusmanager.com) which features an XML written by me, which can tell exactly what section definition is missing.
currently I'm trying to create an WebSetup Project for one of our ASP.net4/Silverlight-Web Applications using Visual Studio 2010.
I created the setup Project according to this tutorial, but when I'm trying to build the Setup Project (I did a build of the whole solution before), I get the following error:
Unable to build project output group 'Content Files from MyWebProject (Active)'
According to this and almost any other site I found, this error refers to items that are included in the web-project but missing on disk.
I checked all my projects twice, there is no missing file.
Are there any other solutions to this problem?
Other things I tried:
This post: I do have .xml Files accompanying our .dlls. I also removed the xml File from my project, but it didn't help either
This post: Setting the startup project to my web application changed nothing.
Both of the above Posts are from this thread on forums.asp.net.
I had this problem also. (Visual Studio 2010 Pro, .Net 4.0) I found the missing file using "Publish..." option. Right click on the web app. Up near the top of the menu (5th from the top for me) is "Publish...". Click that. I did "Publish method: File System". Publish fails for the same reason that building the setup fails. The difference is that when Publish fails, it gives an error message.
In most cases it's due to missing files.
Expand all your projects and check that none of them is marked with the Yellow Exclamation mark.
For web applications the usual suspect is config.web and more specifically the Debug/Release versions , click on the '+' next to the Web.Config and see if they are marked as missing.
Good luck
I have faced the same issue at my side. `
[how to resolve ERROR: Unable to build project output group 'Content
Files from XYZ.xyz (Active)]
so solution ==> as per my project resolution I was just removed the reference file same name as the reference shown in the error block as [XYZ.xyz (Active) ] from the WCFSetup project followed by clean with Rebuild the solution.
The problem will be resolved and .MSI, as well as .setup file, will generated
I'm creating a new ASP.net website via Visual Studio. I then try to run the default.aspx page it generates, and it throws this error:
I've tried deleting the affected lines as suggested by MSDN but to no avail! I am on Windows 7, with ASP.net installed
Any ideas?
This is a common error when you assign the Site (that includes a web.config from .net 3.5) to an application pool that is running in 4.0. It causes some of the entries in web.config to be duplicated, so you can: 1) clean up the web.config to remove those duplicated entries, or 2) change the application pool to one that is using .net 2.0.
What exactly have you tried to delete? The MSDN article about the specific error code 0x8020700b7 talks about deleting duplicate entrys in the ApplicationHost.config file. But your error message postet above talks about the web.config which are two completely different files as far as I know.
The marked line 15 should be in the web.config. where the marked duplicate entry should be.
I have a web site that built on Visual studio 2008 and
i need to run it from my computer (Win 7 Ultimate) as a server
I tried to publish it to IIS and this is simply not working
and i have the flowing error :
Error Summary
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Config Error This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
any one can help?
It looks like the Web.config file contains some disallowed section. Some sections can only be set in the machine-wide configuration, some can only be set at the root of a web site, etc.
Simplify your web.config as much as possible (make it as empty as possible) and when the page displays, add one section at a time.
Silly problem but IIS never warn about it
i have missed installing the component (from control panel) that support ASP.NET
when i installed it ,it worked :)