The transition to NetApp MS Azure AD B2C is complete. If you missed the pre-registration, you will be invited to reigister at next log in.
Please note that access to your NetApp data may take up to 1 hour.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

Software Development Kit (SDK) and API Discussions

.NET API - Invoke Failed (On only one of eight filers)

MORGANBLECK

I am using the NetApp Manageability SDK 5.0R1 in a .NET application. The basic function of the application is to create a volume in a standardized way for a set of users. I am able to connect to all the filers except one. When I try to connect to this one problem child, it returns an error "API Invoke Failed." The inner exception is "The underlying connection was closed: An unexpected error occurred on a receive."

The code used is below. This is part of a multi-threaded class and the username, password, and filer are set externally.

Any and all help would be appreciated. (Note, even though this is the Windows .NET API and not the web version, I still verified HTTPS, NDMP, SSL already).

public void GetAggs()

{

NetApp.Filer.Aggr.AggrListInfo aI = default(NetApp.Filer.Aggr.AggrListInfo);

NetApp.Filer.Aggr.AggrListInfoResult aO = default(NetApp.Filer.Aggr.AggrListInfoResult);

NetApp.Filer.Aggr.AggrInfo[] aV = null;

List<string> lA = new List<string>();

server = new NetApp.Filer.NaFiler(strFiler);

server.Credentials = new NetworkCredential(strUsername, strPassword);

server.ForceUseUnsecure = true;

aI = new NetApp.Filer.Aggr.AggrListInfo();

aI.Verbose = true;

aO = aI.Invoke(server);

aV = aO.Aggregates;

foreach (NetApp.Filer.Aggr.AggrInfo Ag in aV) {

lA.Add(Ag.Name);

}

aV = null;

aO = null;

aI = null;

if (GetAggsComplete != null) {

GetAggsComplete(lA);

}

}

1 ACCEPTED SOLUTION

MORGANBLECK

I sidestepped the issue. For anyone else that runs in to this issue... Change the protocol to HTTPS. Make sure you also set the port to 443 (or whatever you have it set to on the filer).

View solution in original post

1 REPLY 1

MORGANBLECK

I sidestepped the issue. For anyone else that runs in to this issue... Change the protocol to HTTPS. Make sure you also set the port to 443 (or whatever you have it set to on the filer).

View solution in original post

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public