I checked our 23.4 lab box and it was not up to the task, I had a bunch of things to go back and clean up...but client said it was installed.  

Might be worth looking at the output just in case (as it's really buried in there) but you may be fine and don't think it's related....

That said, I looked at another system we have and I'm seeing the same thing you mentioned, but not just for that command.  

I took some scripts we use frequently in 2022.11 and none were working in the newer version of NA.  

What version were you guys on prior to 23.4?  

I'm curious and we'll hit this soon enough, so I'll post back what I find.  

I don't know if it's okey to post solutions from the support here.. So if that's not okey, sorry in advance :) 

for me I had problems with NAS:Client module and the NAS:Connect module as well in 23.4.

For the NAS:Client  I just tryed a "list_user" on which I got:

method [nas:list_user] has returned an error: Can't use string ("1") as an ARRAY ref while "strict refs" in use at (eval 126) line 1.

From the support I got the following:

in the client perl module on the server I had to add "openText" to the regex on line 599:

elsif( $self->{ -nas_brand } =~ /^Opsware.*$/ || $self->{ -nas_brand } =~ /^HP.*$/ || $self->{ -nas_brand } =~ /^HPE.*$/ || $self->{ -nas_brand } =~ /^Micro Focus.*$/ || $self->{ -nas_brand } =~ /^OpenText.*$/)

And after around like line 1076 add "OpenText" as well (just in the same matter as the other elsif statements):

} elsif( $txt =~ /^\s*(OpenText[\w\s]+)\s+(\d\S+)/i ) {

$self->{ -nas_version } = $2;

$self->{ -nas_brand } = $1;

But obviously it's risky to change the perl modules just based on my feedback, probably better to open a case as well for yours...

The NAS:Connect issue is still under investigation..

Thanks for posting.  Guess this slipped thru the cracks, and this might be in patch 1 whenever patch 1 comes out.  

Hard to say how many people may have found this as well....QA....

Again, thanks!

Thanks Guys , I wondered if you had received any more info on this issues or found any workarounds.?

I just checked and figured they'd have a patch out and that would contain an update / fix for this...but not seeing it.  That said, I've got to think they have a HF if you opened a case.  Or you could make the edit but personally, I'd first open a case and rule out them having this ready to hand out.  

If you had a non-prod NA instance, you could try to get either an older version of Client or newer.  Definitely downsides to doing that, but I've run older modules with newer versions of NA - not great but it "can" work.  I asked about this problem and 24,2 and was told it was fixed in 24.2 but haven't had a chance to update and try,