Known Issues

This page describes the issues with Manage ONTAP SDK 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 using the API na_server_set_debugstyle, an error message gets added to the API response. The error message is "debugging bypassed xml parsing", and the error number is 13001.

 

 

Problem: Refreshing the Help by clicking Reload on Mozilla hides the Table of Contents.

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

 

 

Problem: Utilities and sample programs might not run correctly in the Windows NT 4.0 while using remote procedure call as the transport mechanism.

 

Problem: -s option in the apitest utility fails.

Cause: Net::SSLeay is not available to apitest.

Solution: Install Net::SSLeay, or update the PATH, so that Net::SSLeay is accessible from apitest.

 

 

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

Cause: This is a browser-specific issue.

Solution: Click on the search keyword more than once to go to the destination topic.

 

 

Problem: Microsoft .NET core API documentation (DotNet.chm) does not open in Firefox.

Cause: This is a browser-specific issue.

Solution: You can open DotNet.chm file through Internet Explorer.

 

 

Problem: The SDK does not support the IPv6 feature in VMware ESX Server 3.0.

Cause: The IPv6 feature is not supported in VMware ESX Server 3.0.