Download the AzureToolkit from Sitecore.
Powershell 4.x or newer ($PSVersionTable.PSVersion to check your current version)
Download and install MSDeploy.
SQL Server (The express version is enough)
Microsoft SQL Server Data-Tier Application Framework (DacFX) for SQL server 2012 or later.
1 - Import the methods you will need from ...
This problem is from a breaking change by Microsoft where they changed the default compatibility level to 150. The Sitecore cloud team was on it straight away and have released a fix which is to deploy a small package to set the compatibility level on newly created Azure SQL databases.
So yeah, my DacFX was installed properly, but...
The only thing that I missed is that SQL Server itself is a prerequisite as well.
Since I'm working in a VM which doesn't host any Sitecore instance (it only builds the packages) I didn't realize that quickly.
TLDR; Yes - you have to add the my.trafficmanager.net to the site
definitions of your website (considering that in your case you have
added the actual bindings to the website site removing the catch-all
rule for Sitecore. If that is not the case and you have the website site untouched - there might be a deeper problem with the actual resolution ...
In my case, I'm always doing this to fix that :
Make sure your Sitecore configured properly for SOLR within
Check your connectionstrings for SOLR is configured properly or not
Access SOLR admin (with browser, make sure it's https) to check whether it's on or not
If it's on, check again if your configured index matches with ...
So after investigation, it looks like I need to install Azure RM as a pre-requisite in order to be able to deploy Sitecore to Azure properly.
Just run those two following commands and everything it's gonna be alright.
There are automatic cleanup tasks in place to deal with that.
Basically if you look under <scheduling> in a default Sitecore.config, you will find these.
<agent type="Sitecore.Tasks.UrlAgent" method="Run" interval="00:15:00">
Application Initialization does a call to your website over http. If you have redirect rules that redirect http to https, the initialization receives a 302 and marks the request as done, it does not follow the 302 to load the site on https.
So in order to avoid this, you need to add an additional rules in your rewrite rules to skip the https redirect in ...
The answer to this question depends on a few things, such as if you have customizations to experience editor and/or content editor or any custom jobs etc that need to run on the CA servers. It also depends on what approach and tools you are using for deployment.
However, I'll try and cover some options and typical approaches.
Custom Code Deployment Options
An answer has also been given through the Sitecore Community Slack channel.
Credit to sumithpd (Sr. Product Manager - Experience Platform at Sitecore)
The mentioned class has been removed from the assembly, but it is still referenced in the configuration.
It doesn’t affect any functionality since the class was obsolete for some time, and the log errors can ...
Make sure your fieldName is matching the field name in Sitecore. So if it's Entry Date in Sitecore then make it entry date in the index, however you'll need to set the cloudFieldName to entry_date or entrydate for it to be compatible with azure search conventions.
<field type="System.DateTime" ...
The above response is correct for the straight up conversion of the package to a WDP (scwdp.zip).
In case it helps, there are quite a few goodies that make use of the Azure Toolkit to generate WDPs and to then deploy to Azure in the HabitatHome.Platform repo
The main PS scripts are in /Azure and a lot of it is called / used by build.cake. It's not for the ...
There are likely additional places and methods for retrieving this data, but the following is typically what I resort to:
Note: I have not tested SPECIFICALLY for UpdateInstallationWizard logs
In Azure Portal, select the App Service resource that you used to run the installation.
Scroll down the blade and find App Service logs in the Monitoring section
Not sure but try to change the setting for "tempFolder" in Sitecore.config to "/temp". The setting is configured/overwritten in Sitecore.Azure.Settings.config:
<sc.variable name="tempFolder" value="/temp" />
We have raise this problem to the Sitecore Support which generated a ticket #527731 (Please use this ticket# if you have the same issue)
IMPORTANT: The following approach does not work without the hotfix provided by Sitecore, don't give a shot by simply changing the files specified in the step"after the hotfix has been installed"
Accordingly to the ...
To resolve the CORS CDN error , You would need to create a pipeline which adds the below request headers.This pipeline was written for Cloudfront on Amazon AWS instance , but the underlying logic is to add the Access-Control-Allow-Origin headers to Sitecore requests.
public class CDNResponseHeaders : HttpRequestProcessor
public override void ...
I was suffering from a similar issue for the SQL server for different databases. Below are the details.
Cloud Environment: Sitecore Managed Cloud XP-Small and XP-Medium
Sitecore Version: Sitecore 9.1 Update 1
Cause of the issue: By default from Sitecore Managed Cloud Team indexing strategy was set to "onPublishEndAsyncSingleInstance" in CD role. And ...
This is also a bug in Sitecore 9.1 update 1. I have raised it as a ticket with Sitecore support and they have provided a bug reference 291373. Development of the hotfix is in progress.
I note that in the hotfix mentioned above, 2 of the files are not present in the /bin folder of 9.1.1. The missing files are:
We had the same kind of issues.
We were able to resolve them by tweaking the polling interval of the private session state provider and increasing the timeoutBetweenLockAttempts of the shared session state manager.
Private Session State:
<sessionState mode="Custom" cookieless="false" timeout="20" sessionIDManagerType="Sitecore.SessionManagement....
Default Azure PaaS security
If you have correctly deployed Sitecore on Azure PaaS using the ARM templates and associated Sitecore WebDeploy (.scwdp.zip) packages then by default you will have the following security hardening measures already applied:
Access limited via deny anonymous access web.config rules
Access is limited via deny anonymous access web....
Here is an example of how to patch in an exclude field by ID that I have taken from an SXA config.
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/" xmlns:role="http://www.sitecore.net/xmlconfig/role/" xmlns:search="http://www.sitecore.net/xmlconfig/search/">
Sitecore Azure Toolkit has functionality to generate WDP packages from Sitecore packages.
You can therefore use this instead of using WDP packages for SC 9.0.2.
You can find Azure Toolkit here:
Documentation can be found here:
For the case of Error 403 - This web app is stopped. - this is not easily possible since it is actually the built-in Azure load balancer that is serving the error, not the WebApp or Sitecore.
You can track the status of this feature on Azure Feedback portal and vote for it.
There is a possible workaround: you can route all traffic to your WebApp via your ...
The difficult answer is: it depends... on how you do your deployments.
Normally on PAAS you will deploy the full application (Sitecore + packages + your own code) which means indeed that you need to add the packages to the ARM templates.
If you already have provisioned your environment and don't want to do this again, you need to install the packages once ...
The fact that the filepath is not empty when uploading through your code would mean that those items are uploaded as file based. This means Sitecore will store the actual blob on disk and not in the database. To get those items to a CD server, you would need a solution that copies those files along. But that is not your best solution, as you probably don't ...
This issue was caused by the offending CD server referencing the wrong instance of the index. When we checked the core database's Properties table for which instance each of the CDs were referencing, we found that the two functional CDs were both referencing the currently active instance (sitecore-web-index-secondary, in our case), and the offending CD ...
You can add the following rewrite rule to your web.config to add the required header on font files. The benefit of this is that you don't need any extra code - IIS rewrite module is available by default on Azure WebApps.
<rule name="Enable CORS for Fonts">
This looks like SQL encryption using column encryption keys is enabled, but possibly the way in which this is configured in 9.2 is different from 9.0.2, or the encryption keystore on your xConnect instance has not been configured. If you previously had encryption using column encryption keys and a keystore or Azure KeyVault, you might need to reconfigure ...
The 502 error is a common occurence on Azure PAAS whenever internal Sitecore is booting up after deployment or any other issues. This SSE question details out the different reasons for the same.
502 - Web server received an invalid response while acting as a gateway or proxy server
For the maintenance page , in Sitecore webroot , you can use the default....