Required license is missing: Runtime Sitecore - sitecore

I am getting this error
Required license is missing: Runtime
I have checked datafolder path
<sc.variable name="dataFolder" value="C:\Path\Data" />
and license file settings
<setting name="LicenseFile" value="$(dataFolder)/license.xml" />
also checked permission all is correct but still it is giving error.

The most likely cause is a patch file in the include folder that is changing your path. Sometimes this is called "DataFolder.config" and may have the default path set in it, which will overwrite the setting value you might have in another patch config or in the Web.config file.
There are some tools that let you track down config settings without having a working Sitecore instance. I would try out the Config Builder (https://marketplace.sitecore.net/Modules/Sitecore_ConfigBuilder.aspx) which should be able to load up all your config settings and help you track down the problem.

I know it is a pretty late to answer, but for folks who end up here - this might be helpful.
There could be couple of reasons why you get this error. Since OP had already mentioned that his license file has not expired - Another viable reason is
The datafolder path is wrong. the first line of the Sitecore.config line defines the datafolder path. For eg: something like this:
<sc.variable name="dataFolder" value="C:\Inetpub\wwwroot\sitecoredev\Data\"/>
if you have any developer create a different instance name or folder and checks it in, it will not find the path and hence you will get this error.

Check if the licence file has expired:
Confirm that the expiration date in the licenses has not been reached or passed. Open the license.xml file with a text editor and search for “expires”; find the line corresponding to the “20060319”. If the date has been reached or passed (for instance, if it is March 19, 2006 or later), the license will not work; obtain an updated license.
https://sdn.sitecore.net/Articles/Troubleshooting/License%20Issues.aspx

I have installed 8.2 update 5 on my local machine. The default installation adds a folder called 'zzz' in App_config/include folder and creates DataFolder.config in that folder and references the data folder name from that config file. My publish overwrote/deleted that folder and i got the error 'Required license is missing: Runtime Sitecore'.
Adding that folder 'zzz' from my backup site resolved that issue.

I have also noticed that even if after fixing the path you may still see this error. Once you fix path with valid license, DON'T forget to reset IIS/ Apppool.

Below are the possibilities for the error.
Verify if the license file is present - You can check this in the default data directory of the Sitecore installation path. If the file is not there add it here and restart the IIS.
The path of the License file is wrong - The default path of the Sitecore license file will be specified in the “web.config,” and if you are using the Sitecore 8+ version, then verify Sitecore.config file(App_config/Sitecore.config) where LicenseFile settings are provided
Overriding the License file path - If you are using any Patch files or thrid-party libraries like brainjocks then make sure the patch file is not overriding the default path.
License expired - Don't forget the check if you provided license is been still active or expired. You can do this by opening the license.xml in editor and verifying the field "expiry" and the date.
Config File settings
<sc.variable name="dataFolder" value="/data" />
<setting name="LicenseFile" value="$(dataFolder)/license.xml" />
Source - Sitecore Required license is missing: Runtime [Solved]

Something to watch out for: I had multiple config files for different environments (e.g. DataFolder.QA.config, DataFolder.Live.config) which were overriding my DataFolder.config with values that were incorrect for my local environment. Deleting the unneeded environment configs got this working.

if you have doubt whether sitecore is looking into correct place, check out /sitecore/admin/showconfig.aspx page. this is what sitecore really uses after combining all configurations. You can chekc both <sc.variable name="dataFolder" value="C:\Path\Data" /> and <setting name="LicenseFile" value="$(dataFolder)/license.xml" /> there. Of course this page only shows <sitecore>...</sitecore> part of configuration.
Also make sure that NETWORK SERVICE account or <your IIS app pool name here> account (depending on which Identity is bound to your App Pool instance) has full access to Data folder and also App_Data subfolder inside webroot, just to rule out any read/write access issue

Related

VuePress build deletes CNAME file in ./docs needed for Github Pages custom domain

I'm trying to get VuePress to work well with GitHub Pages and a custom domain. I have the site working -- https://www.southertonrr.com (repo) -- as long as I manually add a CNAME file to my output folder ('./dest', or in my case, './docs', because that's where GitHub Pages looks for the site) every time after I issue a build command. Otherwise, I assume the build command deletes everything in my output folder and rebuilds the entire site.
Is there a way to get vuepress build to either leave that file alone, or copy a CNAME file from my ./src to my ./docs? Should I be looking at the configureWebpack config to use webpack to do it? (I'm new to webpack.)
Different product completely, but I noticed that Docusaurus for React has a CNAME config setting that does this for you, so I thought I'd check to see if the VuePress community had something similar.
See relative document
Sometimes you may need to provide static assets that are not directly referenced in any of your Markdown or theme components - for example, favicons and PWA icons. In such cases, you can put them inside .vuepress/public and they will be copied to the root of the generated directory.

Graphs in Lucee

I see an error using CFCHART with Lucee. Same code works in CF. But in Lucee it try to refer to a file graph.cfm in a folder lucee.
mytestserver.com/lucee/graph.cfm?img=026f01d7b8c85b891a9c35c102623747&type=png
Do I need to create any mapping? Should this mapping be in Lucee admin or in IIS?
The short answer is: No, you don't need to add any additional mapping in IIS, nor in Lucee or Tomcat.
I've seen this question here for too long, so I'm placing an answer here to shed some light into Lucee's graph.cfm.
Some tags in CFML need to create additional image files to later embbed them as an inline HTML element into the reendered output altogether. Examples for such file creation are <cfimage type="captcha" ...> or like you have already noted in your issue, <cfchart>.
For such functionality Lucee needs to create these files temporarily somewhere and also make them publicly available. To achive this for cfimage/cfchart, Lucee creates the files in the web context folder of your webroot (which typically is located at path-to-your-webroot\WEB-INF\lucee\temp\graph ) and embbed them inline with a link to graph.cfm. The template graph.cfm just reads the temporary file from that folder, and delivers it in realtime to your application.
If you want to take a look into Lucees original graph.cfm, we can take a peek thanks to OpenSource:
source of Lucees graph.cfm at github
In order to make the files and the template graph.cfm temporarily publicly available, which by the way sits behind the WEB-INF folder ( which is also hidden/blocked by default in Tomcat for securtiy reasons), Lucee MUST have a virtual mapping. But you don't need to set it up, because these are already set up by default. You can see this in the image below taken from the "Mapping"-section of Lucee Administrator:
Because graph.cfm is a .cfm file, IIS will redirect the request directly through the implemented CFML connector ( probably Boncode Connector ) per AJP to Tomcat. Thus you don't need to set any mapping in IIS neither.
Because you have not submitted any additonal error information, such as http error codes or stack traces, I don't have any clue of what might be the cause of your error. It may also be some incompability issue which might be addressed if you submit it to the Lucee core team.
Another possibility is that many installation guides advise you to lock down the "/lucee/" path with IIS URL Rewrite Module, because this is also the path where the Lucee Administrator sits behind. If so, you can change the setting in IIS Rewrite Rule and adapt the rule in such a manner, that it would not block the graph.cfm.
It's also important to note that many of these cftags are implemented as Lucee extensions (.lex files). These are not necessarily pre-shipped or pre-installed in Lucee, but you may install it within Lucee Administrator or get them from Lucees Download site and upload it through your Lucee Administrator in the "Extension" section.
I've just encountered this too. Issue being though the the default mapping still don't navigate to "graph.cfm" so we've added an IIS virtual mapping instead.

Setting specifies the context site for experience editor

I am working on multisites and I want to open experience editor for the context site, but sitecore doesn't resolve the context site and it always takes me to the default website, there is a setting in sitecore.config file i set it to "true", but still it takes me to the default website :
http://mywebsite.local/?sc_mode=edit&sc_site=website
here is the setting in sitecore.config, my sitecore version is 8.1 (Update 2)
<!-- PREVIEW - RESOLVE SITE
If false, the Preview.DefaultSite setting specifies the context site to use when a user previews an item.
If true, when a user previews an item, Sitecore tries to resolve the root item and the context site based on the current content language
and the path to the item. If Sitecore cannot resolve the context site, it uses the site that is specified in the Preview.DefaultSite setting.
Default value: false (use the value of the Preview.DefaultSite setting)
-->
<setting name="Preview.ResolveSite" value="true"/>
I have also face this issue before and it is known bug in sitecore. I have tried approach mentioned in below article. (However I am still facing this issue intermittently whenever I copy new dll in sitecore website.)
https://kb.sitecore.net/articles/382913
I have already placed all the files at my one drive link. Please take a backup of your existing file ("WebEditRibbon.aspx ) before replacing
https://1drv.ms/f/s!AotVzR-_yI5ObO5-Pzq02mcx-EU
This Reported as bug in Sitecore 8.1 (Update 2), and this is the fix from support team :
Open the “/sitecore/client/Applications/Launchpad/PageSettings/Buttons/ContentEditing/ExperienceEditor” item in the core database
Change the “Link” field value to:
/?sc_mode=edit&sc_resolvelanguage=0
Updated Answer :
For multi-sites, you need to apply anothor fix I did not find its number on https://kb.sitecore.net/ so i uploaded the required files on dropbox :
Download Sitecore.Support.88883.zip, from this Link
Copy the attached Sitecore.Support.88883.dll file to the /bin folder of your website;
Copy the attached Sitecore.Support.88883.config file to App_Config/Include folder of your website;
Open the "/sitecore/client/Applications/Launchpad/PageSettings/Buttons/ContentEditing/ExperienceEditor" item in the core database
Change the “Link” field value to: /?sc_mode=edit&sc_resolvelanguage=1
Clear the browser cache.

Sitecore license on Deployment

I've deployed my Sitecore project to the server and Im receiving the error
Required license is missing: Runtime Description: An unhandled
exception occurred .....
Exception Details: Sitecore.SecurityModel.License.LicenseException:
Required license is missing: Runtime
Do I need to download and install the Sitecore CMS Setup and enter the license key in that on the server ? I was expecting it all to be contained within the file structure of the web site.
PS/ Exscuse the fact that this is a pretty simple question - extremely pushed for time. Many thanks,
The Sitecore license file is an XML file that is located in your \Data folder by default. It is also named "license.xml" by default. You should have a reference to this file in your web.config file:
<!-- LICENSE
This value define the physical location of the license file.
Can be site path (ex. /folder/...) or absolute (ex. c:\folder\...)
-->
<setting name="LicenseFile" value="$(dataFolder)/license.xml" />
If your site is working in another environment but not your deployment environment, ensure that your path for the \Data folder is the same on this server. Change the path of the dataFolder variable if the path is different:
<sc.variable name="dataFolder" value="D:\<YOUR_PATH_HERE>\Data" />
Hope this helps.

Using fossil embedded documents

I'm using fossil to manage some home projects and keeping notes in the wiki. After running like this for a few months, I'd like to at least try to use embedded documentation; mainly so as to be able easily to go back to previous versions.
I've studied the website page about managing project documentation which confirms that this is a technique I want to follow up, but I can't make out how to do it.
I've cut-and-pasted one of my wiki pages and added it to my fossil repo, but I can't work out where it should go in the directory structure to be accessible as described on the above page.
I've tried in a few places none of which worked. The document is currently %fossil-root%\doc\foo.wiki, (I'm on Windows), where %fossil-root% is the directory holding _ _FOSSIL__ (slighly mangled filename because of markdown), but having started a server with fossil ui, when I point my browser at http://localhost:8080/doc/foo.wiki, fossil presents me with a nicely formatted page saying it can't find index.html. I created /doc/index.html to see what would happen, but it made no difference.
Please can someone help me out, and/or point me to an example repository containing embedded documentation or another "how-to" document.
If your document is located in %fossil-root%\doc\foo.wiki, you can access it at the following URL:
http://localhost:8080/doc/trunk/doc/foo.wiki
This URL breaks down as follows:
http://localhost:8080 is the root URL to access Fossil when you run fossil ui
/doc signals that you want to access embedded documentation
/trunk indicates the checkin containing the documentation you wish to access
/doc/foo.wiki is the path of the document inside the repository
Instead of trunk, you can also specify a tag, or a branch name, or even a hexadecimal checkin identifier.
In the URL you were using, http://localhost:8080/doc/foo.wiki, foo.wiki is interpreted as the checkin name, and no document path is specified, which logically means Fossil won't find anything.
As for an example repository containing embedded documentation, the homepage of the Fossil website itself is a prime example:
https://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki
where
https://www.fossil-scm.org/index.html is Fossil's root URL
/doc indicates a request for embedded documentation
/trunk indicates we want to fetch files from the trunk
/www/ is the path to the requested file inside the repository
index.wiki is the name of the file inside the repository.
So, in the 'trunk' branch of the repository, the file www/index.wiki contains the home page of the Fossil website.
You simply need to put the documentation under the %fossil-root%\www\ directory (or any other directory under version control) in your repository and then you can, for example, add the following line to your header's mainmenu section to link to it:
html "<a href='$home/doc/trunk/www/foo.wiki'>Documentation</a>\n"
As I said, it can be any directory under version control. To test this, pick any file in the repository, let's say a README file at the top level, and go to http://localhost:8080/doc/trunk/README. You should see the README file load up in your browser in a raw text format. By putting wiki or html files under a particular directory such as www you make it easy to organize the files that you specifically want rendered as documentation, which makes it easier to link to them.
http://www.fossil-scm.org/index.html/doc/trunk/www/embeddeddoc.wiki
After fossil 1.33, just prepare your document in the repository.
If the wiki file is put in
/doc/index.wiki
And use web browser to setup -> Admin -> Configuration.
There is a "Index Page" field, fill in your main index.html.
For example:
/doc/trunk/doc/index.wiki
Or if you just want the released version:
/doc/<version>/doc/index.wiki