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 ...
Accessing Sitecore XP logs and diagnostics information on Azure Web Apps differs from the on-premise approach. This article explains how to collect basic Sitecore diagnostics information, such as logs and configuration data, for a Sitecore XP solution deployed to Azure Web Apps.
To access enhanced logging data of a Sitecore XP instance deployed to Azure Web ...
Azure Redis cache is the default session provider Sitecore 9.0 will use in Azure Paas. Out of the box, Azure Redis Cache will be configured and used by Sitecore.
Sitecore uses this session provider as a means of managing out of process (ie. distributed) session state to share contact data across browser sessions and devices. This is required to support ...
How it works
Have a look at the App_Config/Sitecore/Azure/Sitecore.Cloud.ApplicationInsights.config which gets deployed to all CM/CD/PRC/REP roles.
You will see that all the built-in log4net appenders get patched to append via the Application Insights LevelTraceAppender.
You may also notice that sitecore still logs to the file system on Azure PaaS, which ...
The very unfortunate answer to this question is that you can't (at least not as of the writing of this answer).
Per this blog post, dated June 2018:
You cannot, at this moment, create a custom culture on an Azure App
Service. Cultures are part of the standard operating system and
require changes to the registry to modify or add them. An Azure App
I was able to solve this.
Navigate to your Sitecore Azure Toolkit path in Powershell and run the following after unblocking all the files.
And now we can use the commands to create the WDP for the Sitecore Module like Data Exchange Framework by running this ...
As you mentioned Replication is required for some Sitecore databases, but SQL Azure (PaaS) does not support SQL read-write geo-replication currently just read-only(https://docs.microsoft.com/en-us/azure/sql-database/sql-database-designing-cloud-solutions-for-disaster-recovery), so the only option is to have all CD locations connect to the central Core ...
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 ...
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.
Yes, they are both compatible.
WFFM since 8.2 Update-3 (rev. 170413), and EXM since 3.5 (rev. 170810)
More information about all modules compatible with Azure Paas can be found here: https://kb.sitecore.net/articles/201557
In Azure Portal, on your CD's (or other instances) you can add custom domains.
Before doing so, you will need to add DNS records for those domains. You can CNAME them to the xxx-cd.azurewebsites.net site.
After that, it is just standard sitecore, where you need to add those domains in your sitecore configuration (sites node).
Using Maintenance Slots to Eliminate Deployment Downtime
Rather than use a maintenance page, you can actually avoid downtime in Azure by using multiple deployment slots. Think of this kind of like Content Search indexes with Solr or Lucene, using SwitchOnRebuild. Basically, you have (at least) two slots: one for your live site and another for a maintenance ...
I've used this for a while and can confirm that it works (up to SC 8.2). Furthermore, I just tested it and it still works with Sitecore 9 in PaaS.
Once installed, look for Dianoga informational messages in Application Insights after requesting your images. It should look somewhat like this:
If you refresh your image (bypassing the browser cache) once it's ...
With regards to the initial very large time, what you're most likely hitting is that Sitecore can max out the Azure SQL on startup to fill the prefetch cache - see Sitecore Knowledge Base Article 290593 The solution is to disable the prefetch cache by using the configuration file on the attached knowledge base article.
According to Sitecore:
The Sitecore ...
With the help of Sitecore support, we finally found root cause.
They provided a patch for "SC_TICKET entries are never cleared from Properties table." (#223702), this issue is fixed in Sitecore 9.1
More information on this from the blog post https://hishaamn.wordpress.com/2016/04/26/sitecore-authentication-ticket-cleanup/
Sitecore create a ticket for each ...
I found out that this behavior is related to the introduction of SwitchOnRebuild for Azure Search in Sitecore 9.0.2
As from that version, Sitecore has this feature, and it is turned on by default. Which is nice of course. To verify, check the indexes on your Azure Search app and you will see index names with _secondary after rebuilds.
To know which actual ...
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 ...
The difference between Sitecore Email Cloud Delivery and Custom SMTP are pretty simple. But to really understand why they exist, some background is needed.
What is a Mail Transit Provider and why do I need one?
At it's most basic component, the act of Sitecore (or any application really) to send email successfully, requires connection to some kind of ...
We managed to solve this issue with the help of Sitecore and Microsoft:
Increase the min worker thread pool to xxx (where xxx should be greater than busy value on log)
Increase PollingTime to 30.
If above doesn't help upgrade the redis.stackexcahange to latest
And increase sync timeout 5k, connection time 10k and retry timeout 6k (should be ...
I found the problem. The 9.0.1 parameters.xml file in the Sitecore 9.0.1 rev. 171219 (Cloud)_xp1collection.scwdp.zip has a parameter for Messaging Database Application User:
<parameter name="Messaging Database Application User Name" description="Messaging Database Application User Name" defaultValue="messaginguser" tags="">
If the targetframework of the project is lesser than 4.5.2 then try to upgrade the target framework and reinstall the Dianoga from nuget https://www.nuget.org/packages/Dianoga/3.1.1
Also do check if Dianoga.dll is there in bin folder of the application.
Similar issue reported at
Update: Since September 2019, Sitecore will provide support with any Sitecore product issues that are not unique to a containerized environment.
This means that the Support team might ask you to replicate the issue outside containers, although they will try to avoid this.
Also some important information on this on the Sitecore docker repo:
Important Note ...
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 ...
It's not entirely clear if this is happening under load, but there
are a number of troubleshooting steps and configuration changes you
can make to optimise your Sitecore implementation with Redis. The
out of the box settings often need some tweaking depending on your
Confirm the Redis cache is not under too much load. You ...
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.
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.
You will want to refer to the 'Deploy a custom model' documentation for your version. This link is for 10.0: https://doc.sitecore.com/developers/100/sitecore-experience-platform/en/deploy-a-custom-model.html
From the docs, the roles that should be updated are:
All instances of xConnect Collection
All instances of xConnect Collection Search
xConnect Search ...
It's not Sitecore. MSDN Subscriptions (for whatever reason) places restrictions based on the type of account you are using.
If you are using a Visual Studio Enterprise Subscription you are limited to the following locations:
South Central US
West US 2
West Central US
If you are using a Microsoft Azure Enterprise ...