This topic lists errors that are most commonly encountered when running Kentico CMS in the Azure environment, and describes solutions to them.

 

Poor performance on local machine

 

When running Kentico CMS in a local emulated environment, you may experience slow performance of the system, e.g. pages take long to load.

 

This issue is caused by insufficient system resources. We recommend deploying the application to the cloud or running the emulator on a machine which provides enough performance.

 

Role discovery data is unavailable

 

When running Kentico CMS in a local emulated environment, you may encounter the following exception:

 

System.InvalidOperationException: role discovery data is unavailable

 

To resolve the issue, you can try some of the following solutions:

 

•Verify that you have set the correct start-up project for the Kentico CMS solution. Open the solution in Visual Studio, right click the CMSAzure project in the Solution Explorer and choose Set as StartUp project from the pop-up menu.

•Verify that the Windows Azure Compute Emulator is running and that it is configured correctly. See the Application structure and configuration topic to learn how to configure the application to run in the emulated environment.

•The occurrence of the problem may be limited to machines which do not have enough resources to handle the load of the SDK. We recommend deploying the application to the cloud or running the emulator on a machine with sufficient performance.

 

 

The specified path, file name, or both are too long

 

When packaging or publishing the application, you may get the following error while building the project in Visual Studio:

 

The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

 

This error is caused by paths to some files, particularly web template files, being too long. You can solve the issue with one of the following procedures:

 

•Rename the project folder to a shorter name.

•Move the project higher in the folder tree (e.g. from C:\inetpub\wwwroot\ to C:\).

•Delete sample website templates:

1.Run the Web installer.

2.In Step 2, choose to modify an existing installation.

3.In Step 3, select the path to your project.

4.In Step 4, expand the Web templates node of the component tree.

5.Deselect all templates and click Next.

 

 

Dynamically generated web farm servers don't get deleted after stopping emulator

 

If you're running your application in multiple Azure instances, the system creates a web farm server for each of the instances. If you're testing the application on the emulator and stop the emulator, the servers don't get deleted automatically.

 

To solve this, restart your application from Site Manager -> Administration -> System.