String was not recognized as a valid DateTime. about citrix HOT 8 CLOSED

Thanks! Looks like an issue when the day is 1 number vs 2. December 1 vs December 22

from citrix.

Should be fixed. Had to adjust how the date was looked at with double digit days. Please try #12 when you get a chance.

from citrix.

Exception calling "ParseExact" with "3" argument(s): "String was not recognized as a valid DateTime."
At C:\users\applebaumt\Desktop\Get-NSLicense.ps1:217 char:1
+ $nsdate = [DateTime]::ParseExact($currentdatestr,"ddd MMM dd HH:mm:ss ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : FormatException

Current NS Time:

Same exact error this time.

from citrix.

Can you add the line above line 217 and run again? Need to know what your date string is coming across as. Tried with a bunch of different dates on my end.

write-host $currentdatestr

Should look like.

$currentdatestr = $currentdatestr -replace "  "," 0"
write-host $currentdatestr
$nsdate = [DateTime]::ParseExact($currentdatestr,"ddd MMM dd HH:mm:ss yyyy",$null)```

from citrix.

That variable is null. I'll keep debugging it and see what I can come up with.

from citrix.

Ah, part of the problem:

http://'my ns IP'/nitro/v1/config/systemfile?args=filelocation:%2Fnsconfig%2Flicense

{ "errorcode": 1232, "message": "Invalid object name [systemfile]", "severity": "ERROR" }

from citrix.

Ahhhh. Looks like file operations weren't added until 10.5.

from citrix.

Not much I can do here since file operations aren't available until 10.5. Added some error handling and a Netscaler function to throw error if anything lower than 10.5

from citrix.