Microsoft Virtualization Discussions

Get-NcCifsSessionFile not working

TomCheese
104 Views

Hi all, I'm experiencing an issue with the Netapp.ONTAP powershell module. Any time I run Get-NcCifsSessionFile, I get this error:

 

PS C:\Users\user> Get-NcCifsSessionFile
Get-NcCifsSessionFile: Error converting value 15619890882604747598 to type 'System.Nullable`1[System.Int64]'. Path 'session.identifier', line 26, position 38.

 

Other commands do work, but this one and a few others (I don't remember which offhand) all get this integer conversion error. 


Per a thread back in March, this was supposedly resolved, but I am getting this today.


For reference we're running a AFF C30 on 9.16.1P5.

 

Thanks!

1 ACCEPTED SOLUTION

RobDBA
59 Views

The thread from March mentions it's a PSTK fix, so the version of Netapp.ONTAP you're using matters.  I assume the fix was to change from using a signed int to an unsigned int, which would accommodate that larger value:

[int64]15619890882604747598 # throws error
vs
[uint64]15619890882604747598 # works fine

 

View solution in original post

4 REPLIES 4

RobDBA
60 Views

The thread from March mentions it's a PSTK fix, so the version of Netapp.ONTAP you're using matters.  I assume the fix was to change from using a signed int to an unsigned int, which would accommodate that larger value:

[int64]15619890882604747598 # throws error
vs
[uint64]15619890882604747598 # works fine

 

TomCheese
49 Views

Ah, thanks for that. It looks like I'm using version 9.16.1.2501 of PSTK. I've tried in both Powershell 5 windows native version and Powershell 7 latest from MS. 

 

Looking here, it looks like the latest version is 9.17.1.2509. Not sure how I got 9.16.1.2501, as I downloaded it a month ago. I guess I can try to download 9.17 and see if it fixes it.

Holy mackerel, it was the PSTK version. How did I get the old one before?! 
Anyway, thanks for your insight! 

We released PSTK version 9.17.1 GA on September 9, 2025.
If you downloaded PSTK after this date, your version will be 9.17.1.
The issue mentioned above has been resolved in this release.

Public