Sitecore.azure Certificate Was Not Installed Properly. Requesting Certificate Upload

Troubleshooting Sitecore Azure

Abstract

Troubleshoot issues and notice answers to frequently asked questions about Sitecore Azure.

A useful reference for some of the near common troubleshooting queries well-nigh using Microsoft Azure, SQL Azure, and Sitecore Azure.

Sitecore Azure assembles the certificate root of a solution for deployment past:

• Copying the document root subfolder of your on-premise Sitecore installation to$(datafolder)\AzurePackages\(xx)Azure\SitecoreWebSite for a Microsoft Azure deployment and to$(datafolder)\AzurePackages\(xx)DevFabric\SitecoreWebSite for a local emulator deployment.

• Removing unnecessary files and subfolders from theSitecoreWebsite folder.

• Copying the contents of the specified subfolder in the Override Sources Folder field of the Azure Deployment detail to the document root of the content editing environment, the$(datafolder)\AzurePackages\(twenty)Azure\SitecoreWebSite subfolder.

• Preparing the web.config file by including files from the Include folder and the Sitecore section configuration source, which isApp_Config\Sitecore.config by default. Information technology also prepares the web.config file by carrying out an Extensible Stylesheet Language Transformation (XSLT) based on the XSLT patch in the Custom Web Config Patch field of the Azure deployment detail.

• Decreasing the size of theweb.config file by the end of preparation, the Sitecore section of theweb.config file is stored in the Sitecore department configuration source file, which isApp_Config\Sitecore.config by default. Editing theconnectionStrings element of theweb.config file. The editing process removes unnecessary connexion strings and adds new ones based on the databases that are stored in theConnection Strings Patch field of the Azure deployment item. Custom connection strings are supported.

• Copying license information from the local installation to the content delivery package. If yous need a different license file in the content commitment installation, add it to the \App Data\AzureOverrideFiles subfolder (the default path specified in theOverride Sources Folder field of the Azure deployment item).

• Modifying the configuration files in the content delivery package to configure or delete databases, athenaeum, agents, sites, watchers, and other features.

If the right credentials take not been established, y'all will be prompted to set up certificate admission.

In theInstall Management Document dialog, there are two installation options:

• Basic installation – This is the fast and simple method offered by Microsoft. Click the link to get a .publishsetting file from Microsoft. Follow the instructions on the Microsoft Portal site, using your Windows Live business relationship. To become the file, relieve thepublishsetting file locally, then upload information technology using theSitecore Azure Install Management Certificate dialog.

• Avant-garde installation – This is the option for advanced users. You lot can use an existing document or generate a self-certificate. Upload the.pfx file for Sitecore. After yous take selected either a.publishsettings or.pfx file, you must provide a countersign for a.pfx file. ClickUpload.

Notation

If you lot do not already have a certificate from a certificate potency installed on your spider web server, you can create a self-generated certificate for evolution and testing purposes.

Equally a function of assembling a solution for deployment, the document root subfolder of your on-premise Sitecore installation (the Deployment server) is copied to a specific folder. During this process some paths to Sitecore documents that are copied to a specific binder can became too long. To avert this, you can melody the path to the target binder by changing the value of the Build folder field of the advisable Environs item. See Assemble a solution for deployment with Sitecore Azure for more details.

Notation

In that location is a configuration item for each environment under /Sitecore/system/Modules/Azure . During assembly, the Build folder for the configuration item is filed and specifies the target folder to copy the Sitecore documents to.

Consider the following for whatsoever ASP.Net awarding, such as Sitecore, on Microsoft Azure.

• The default choice for ASP.Internet session management isRedisSessionStateProvider. This is an out-of-process state provider, therefore factor this in to your code.

• Before moving to the cloud, consider whatsoever internal applications integration within the solution.

• Use configuration files rather than Windows IIS Manager.

• You lot cannot deploy private files to Microsoft Azure. You must deploy the entire document root.

• Microsoft Azure uses local storage for custom files and folders that are large in size, such as deejay caches. Use appropriate API's for I/O tasks. Sitecore Azure is preconfigured to provide a default local storage called SitecoreWebSite .

• You should use local storage for all  custom I/O tasks that exercise not require persistence of data. Consider using the storage business relationship for persisting information, but be aware that this approach can introduce a bottleneck in high performance environments.

• Microsoft Azure instances are volatile by design. Pattern your compages co-ordinate to this premise.

When you employ SQL Azure with Sitecore, you lot should consider the following:

• When accessing a SQL Azure database from a remote location, the performance depends on network conditions and other factors.

• Utilise an encrypted connection over port 1433 when accessing SQL Azure remotely, (outbound access from the content editing environment).

• The maximum database size in SQL Azure depends on the service tier that you cull.

• If SQL Server 2008 R2 is installed information technology must be with SP1.

• SQL Azure uses IP address restrictions for database security.

• If SQL Server is installed on a separate server, an appropriate Microsoft SQL Server Shared Management Objects package must exist installed on the server where the Sitecore CMS is deployed.

The deployment proper noun must be globally unique and tin can be used for multiple purposes in an Azure implementation. The deployment name is assigned using the following pattern:

[projectname][environmenttype][location][Subcontract Blazon][Xx]Role[20]Sc[first 3 chars of subscription id][UTCTimeStamp]

For example, a deployment name such as myprojectDevWeCd01Role01Sc561201304181010, indicates a project named: myproject is running as a development environment, using the West Europe  hosting location, and the deployment blazon is a content delivery  subcontract.

If yous find that some Dynamic Link Libraries (DLLs), were not automatically copied over, you lot must manually add together the following DLLs to the bin binder of your website. Sitecore Azure will automatically include them in the next deployment.

System.Web.Mvc.dll iii.0.0.0

Organisation.Web.Helpers.dll 1.0.0.0

System.Web.WebPages.dll i.0.0.0

System.Web.WebPages.Deployment.dll 1.0.0.0

System.Spider web.WebPages.Razor.dll one.0.0.0

Microsoft.Web.Infrastructure.dll 1.0.0.0

The package for Sitecore Azure is encrypted by default. If you want to disable encryption, in the/App_Config/Include/Sitecore.Azure.config file, set theAzure.Package.NoEncryptPackage to true. For example:

<setting name="Azure.Package.NoEncryptPackage" value="true"/>

You can notice Sitecore settings that control SSL in theService Configuration andService Definition fields of the deployment detail. Before y'all offset deploying, add the appropriate information in these fields to enable SSL. For more data, see Where Sitecore Azure stores configuration information. You lot can notice basic information about using SSL with Microsoft Azure on Microsoft'south website.

Sitecore Azure does non back up file media.

Sitecore Azure uses the aforementioned process as on-premise Sitecore solutions to clear caches. Subsequently completing a publishing functioning, the Sitecore Azure content editing server writes a time stamp to the publishing target database. The Sitecore Azure content delivery server checks the time stamp on each asking, and clears the caches appropriately.

Earlier you can configure a Sitecore Azure content delivery environment for multiple sites, y'all must configure a Web Role for Multiple Sites. To apply the Sites department in the service definition file to configure a Web Part for multiple sites, refer to the WebRole Schema documentation on MSDN.

Note

The service definition configuration is stored in theService Definition field of the Azure Deployment item. To apply the service definition changes you must redeploy.

Exam a Sitecore Azure content commitment environment for multiple sites on your local machine:

1. In Sitecore Azure, on the map, click the deployment that is running. In the Farm menu select Properties.

2. In the Properties dialog box, copy the value of your Windows Azure host name from the Webrole section.

3. In the Windows host file, map your hostname (hostname and hostHeader attributes value) to your Windows Azure host name.

By default, Sitecore Azure extends theMicrosoft.WindowsAzure.ServiceRuntime.RoleEntryPoint course to add functionality to configure the diagnostics. Sitecore Azure does this by using the Microsoft Azure Storage Business relationship when the office instance is initialized (on offset).

The RoleEntryPoint grade is namedSitecore.Azure.WebRole, and  is located in the\bin\Sitecore.Azure.WebRole.dll assembly of the Sitecore website.

To implement a custom web role entry point:

1. Implement a class that extends the defaultSitecore.Azure.WebRole.WebRole class from theSitecore.Azure.WebRole.dll assembly. You can discover this associates in the\Website\bin folder afterwards the Sitecore Azure installation completes.

2. Override the methods that execute when a role instance is initialized (OnStart), run (Run), and stopped (OnStop), in your class.

3. Compile your code into a new assembly and put it in the \Website\bin folder of your solution.

4. Update the assembly name in theService Definition field of the deployment item:

   <EntryPoint> <NetFxEntryPoint assemblyName="bin\Sitecore.Azure.WebRole.dll" targetFrameworkVersion="4.5" /> </EntryPoint>

5. Create a new deployment, or upgrade an existing one, by using Sitecore Azure to use the changes.

• Restart ASP.NET.

• Articulate the browser cache.

• Investigate the Sitecore logs in theSitecore Deployment server environment for errors.

• Remove the instances from the environment and deploy again.

• After deploying, configure the$(dataFolder)\AzurePackages\(хх)Azure\SitecoreWebSite subfolder as the certificate root of an IIS web site, and diagnose that site.

• Temporarily prepare thefashion attribute of the/configuration/system.web/customErrors element in theweb.config file toOff.

Alarm

If you lot fix the fashion attribute toOff, information technology can expose detailed error data in the Microsoft Azure environment. Consider other techniques to protect the application whilefashion isOff. Remember to ready way toOn orRemoteOnly afterwards diagnosis, and recall to deploy that change.

Sitecore Azure but supports automatic deployment to SQL Azure databases. You can change the configuration settings to deploy to databases on Azure virtual machines (IaaS).

During a deployment, if you lot get a TooManyRequests fault, you can increase the Get Performance Status interval. To change the Get Operation Status interval, open theSitecore.Azure.config file in theInclude binder (\website\AppConfig\) and so adjust theAzure.CheckAsyncOperationStatusIntervalInMS value.

To employ your own domain proper noun you must create a CNAME record with your internet provider. Using the tool provided past your cyberspace provider, create an entry that maps the desired allonym, such as www, for your domain to the host name that was assigned to information technology when your Microsoft Azure awarding was created, for example: sitecoreassignedpolicyname.trafficmanager.internet. Then utilize the tool supplied by your internet provider to forwards the root domain to the subdomain that you have mapped to your Microsoft Azure host name.

Y'all must e'er map CNAME records to a specific subdomain; you lot cannot map to the root domain itself or map a wildcard accost.

Important

Never map directly to a Virtual IP address (VIP), considering in certain instances Microsoft Azure may change the underlying VIP.

Sitecore Azure stores configuration information in a number of locations, with bones configuration details stored in the /App_Config/Include/Sitecore.Azure.config file.

Sitecore manages configuration information using the Azure item ( Sitecore/Organisation/Modules/ ) and its descendants. The installed environments and the relevant deployment items comprise configuration settings that are under the /Sitecore/System/Modules/Azure  item. A few levels down is the Azure deployment item: Editing01 , which contains configuration settings for deployment. You lot can access this through the Content Editor or by clickingMore than Options in theNew Deployment dialog box.

You can manually customize several fields that comprise configuration data for deployment.

Under each Azure deployment detail, the Database References  folder contains database projects for deployment to SQL Azure. By default, the delivery farm contains a core and web database, and the editing subcontract contains a core, master, and web database. If you demand to deploy some other database to SQL Azure, y'all can create some other database particular.

While Sitecore Azure is preparing the environment, the SQL Azure database servers and storage are as well existence created, (if they do non already exist). They will exist used during the deployment process.

sledgepribary.blogspot.com

Source: https://doc.sitecore.com/xp/en/developers/sa/81/sitecore-azure/troubleshooting-sitecore-azure.html

Share this post