Skip to content

Latest commit

 

History

History
39 lines (33 loc) · 1.84 KB

azure-reporting-problems.md

File metadata and controls

39 lines (33 loc) · 1.84 KB
title description type page_title slug position tags res_type
Problems When Rendering Telerik Reports in Azure
Learn what are the major problems we have already hit when rendering Telerik Reports in Azure environment and how you may work around them.
troubleshooting
Telerik Reporting Problems on Azure Environment
azure-reporting-problems
Azure,Fonts,problems,issues,solutions
kb

Environment

Product Progress® Telerik® Reporting
Deployment Azure

Description

The purpose of this article is to list the already known issues when deploying Telerik Reporting on Azure environments, and let you find the link to the specific resource with the explaination and workaround for the particular problem.

Known Issues on Azure

  • [The Report Item is Rendered with an Incorrect Font on the First Render in Azure]({%slug font-is-incorrect-on-first-render-azure%})
  • [Preview Reports in Desktop Viewers Using REST Service Deployed in Azure]({%slug preview-reports-using-rest-service-deployed-in-azure.md%})
  • [SqlDataSource Connects to the Database when Running Locally but Fails on Azure]({%slug sql-data-source-cannot-connect-on-azure%})
  • [Unable to Print Reports from Azure Environment]({%slug unable-to-print-reports-from-azure-environment%})
  • [GDI+ Error or OutOfMemoryException on Exporting or Printing Telerik Report from Azure Web Apps]({%slug outofmemoryexception-on-exporting-or-printing-telerik-report-from-azure-webapps%})
  • [WebRole Starts Cycling after Deploying on Windows Azure]({%slug webrole-starts-cycling-after-deploying-to-windows-azure%})
  • [Operation Could Destabilize the Runtime Exception Occurs when Running on Windows Azure]({%slug operation-could-destabilize-the-runtime-exception-occurs-when-running-on-windows-azure%})