Skip to content

Commit 2f5d56d

Browse files
github-actions[bot]KB BotIvetNikolovaDimitarNikolovv06
authored
Added new kb article resolving-fips-error-exporting-excel-telerik-reporting (#1738)
* Added new kb article resolving-fips-error-exporting-excel-telerik-reporting * Update resolving-fips-error-exporting-excel-telerik-reporting.md * Update resolving-fips-error-exporting-excel-telerik-reporting.md --------- Co-authored-by: KB Bot <[email protected]> Co-authored-by: IvetNikolova <[email protected]> Co-authored-by: Dimitar Nikolov <[email protected]>
1 parent d457dfc commit 2f5d56d

File tree

1 file changed

+59
-0
lines changed

1 file changed

+59
-0
lines changed
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
title: FIPS Implementation Error When Exporting to Excel(XLS)
3+
description: "Learn how to resolve the error encountered when exporting reports to Excel(97-2003) with FIPS mode enabled."
4+
type: how-to
5+
page_title: Fixing FIPS Error When Exporting Reports to Excel in Telerik Reporting
6+
meta_title: Fixing FIPS Error When Exporting Reports to Excel in Telerik Reporting
7+
slug: resolving-fips-error-exporting-excel-telerik-reporting
8+
tags: fips,error,excel,telerik-reporting,export,xlsx,xls
9+
res_type: kb
10+
ticketid: 1692320
11+
---
12+
13+
## Environment
14+
15+
<table>
16+
<tbody>
17+
<tr>
18+
<td> Product </td>
19+
<td> Progress® Telerik® Reporting </td>
20+
</tr>
21+
<tr>
22+
<td> Rendering Format </td>
23+
<td> Excel 97-2003(XLS) </td>
24+
</tr>
25+
</tbody>
26+
</table>
27+
28+
## Description
29+
30+
When exporting reports to Excel 97-2003(XLS), the error message `'This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms'` may appear. This issue occurs in environments with `FIPS` mode enabled, as the Excel 97-2003(XLS) export renderer utilizes cryptographic algorithms that are not FIPS-compliant.
31+
32+
## Solution
33+
34+
To resolve the issue, render the reports into the Excel 2007(XLSX) format instead. The `XLSX` renderer does not rely on the same cryptographic routines as the `XLS` renderer and is fully compatible with **FIPS-enabled environments**. Follow these steps to enable the `XLSX` export format in your application:
35+
36+
1. Install the required dependencies for **OpenXML** formats (DOCX, XLSX, PPTX). Refer to the [OpenXML and XPS options missing]({%slug missing-docx-xlsx-pptx-xps-export-options%}) article for instructions on enabling **OpenXML** formats.
37+
1. (*Optional*) Configure the report export settings to hide the **XLS** format through the [extension element]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-report-engine/extensions-element%}) so that users cannot trigger an export in that format.
38+
39+
````XML
40+
<configuration>
41+
<configSections>
42+
<section name="Telerik.Reporting" type="Telerik.Reporting.Configuration.ReportingConfigurationSection, Telerik.Reporting" allowLocation="true" allowDefinition="Everywhere" />
43+
</configSections>
44+
<Telerik.Reporting>
45+
<extensions>
46+
<render>
47+
<extension name="XLS" visible="false">
48+
</extension>
49+
</render>
50+
</extensions>
51+
</Telerik.Reporting>
52+
</configuration>
53+
````
54+
55+
56+
## See Also
57+
58+
* [Excel Rendering Design Considerations]({%slug telerikreporting/designing-reports/rendering-and-paging/design-considerations-for-report-rendering/excel-rendering-design-considerations%})
59+
* [OpenXML and XPS Options Not Visible]({%slug missing-docx-xlsx-pptx-xps-export-options%})

0 commit comments

Comments
 (0)