Refresh-SmSnapLock -All errors on non-English formatted Snaplock dates

Last updated

Mar 21, 2025
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 17

Visibility:: Public

Votes:: 0

Category:: snapcenter

Specialty:: snapx

Last Updated:: 3/21/2025, 10:28:17 AM

Applies to

SnapCenter Server 6.0.1

Issue

After connecting to SnapCenter Server with Open-SmConnection, when running the CmdLet Refresh-SmSnaplock -All, the following error can occur:

SnapManagerWeb_<JOB-ID> PID=[<PROCESS-NUMBER>] TID=[<THREAD-NUMBER>] System.FormatException: String 'dd.MM.YYYY HH:mm:ss' was not recognized as a valid DateTime.

   at System.Convert.ToDateTime(String value)

   at SnapManager.SMSDALHelper.SnapLockHelper.<>c.<FindMaxSnapLockExpTime>b__1_2(String s)

   at System.Linq.Enumerable.SelectListIterator`2.MoveNext()

   at System.Linq.Enumerable.Max[TSource,TResult](IEnumerable`1 source, Func`2 selector)

   at SnapManager.SMSDALHelper.SnapLockHelper.FindMaxSnapLockExpTime(List`1 getSnapshotResponse)

   at SnapManager.SMSDALHelper.SnapLockHelper.UpdateSnaplockSettings(Dictionary`2 snapshotDetails)

where dd.MM.YYYY HH:mm:ss actually shows a real date, with, in this example in german/dutch default format.

Additionally the following message will be shown for the resource for which the snapshot was taken:

SnapManagerWeb_<JOB-ID> PID=[<PROCESS-NUMBER>] TID=[<THREAD-NUMBER>] Updating the job (<JOB-ID>) task (Processing SnapLock Settings for '<HOST-FQDN>\<RESOURCE>') status as Failed

This does not happen with the weekly scheduled SnapCenter_RefreshBackupSnapLock job when running on schedule, or triggered from the SnapCenter GUI.