Known Issues

This page describes issues with the NetApp Manageability SDK that are known at the time of publishing this page.

 

Problem: If the debug style is set to NA_PRINT_DONT_PARSE or NA_DONT_PRINT_DONT_PARSE by using the API na_server_set_debugstyle, an error message is added to the API response. The error message is "debugging bypassed xml parsing", and the error number is 13001.

 

 

Problem: Sample codes and utilities in C fail in Windows Debug mode with the following error message: "The system cannot execute the specified program."

Cause: The debug runtime libraries of Microsoft Visual Studio 2005 SP1 8.0.50727.762 are not installed in the system.

Solution: You must install the debug runtime libraries of Microsoft Visual Studio 2005 SP1 8.0.50727.762.

 

 

Problem: On Data ONTAP, when SSLv2 is disabled, and either SSLv3 or TLSv1 is enabled, API communication fails. This is a known issue of Data ONTAP in C, Perl, Python (except 3.2.x), Ruby (except 1.9.2), and Java.

Workaround: Enable both SSLv3 and TLSv1 in Data ONTAP.

Note: This workaround does not apply to Data ONTAP 8.0.x as Data ONTAP 8.0.x because TSLv1 is not supported in this version.

 

 

Problem: Certificate-based authentication is supported only on the following Python versions:

Python 2.6.6 and later, Python 3.1.3 and later, and Python 3.2 and later.

 

 

Problem: In the Mozilla and Firefox browsers, refreshing the Help by clicking Reload hides the Table of Contents.

Cause: Unknown

Solution: To refresh the Table of Contents in Mozilla Firefox, click the Location Bar and press Enter.

 

 

Problem: In the Mozilla and Firefox browsers, the first click on a search keyword takes you to a topic that is listed above the destination topic.

Cause: This is a browser-specific issue.

Solution: Keep clicking the search keyword till you reach the destination topic, where the search keywords are highlighted.

 

 

Problem: Microsoft .NET core API documentation (DotNet.chm) cannot be opened in Firefox.

Cause: This is a browser-specific issue.

Solution: Open a DotNet.chm file by using Internet Explorer.

 

 

Problem: Microsoft .NET core API documentation does not open.

Cause: This is an issue with the security settings of the browser.

Solution: Open the DotNet.chm file or open the Properties tab of the browser, and select the unblock option.