PC Access 3.17 Unhandled Exception Setting Clock Omni Pro II

I never ran into this before after updating my firmware last year (don't recall if I tried to set the clock either). Below are Firmware and Software revisions:
 
 
PC Access: 3.17.0.843
 
 
Omni II Controller FW 4.0b
 
 
I connect PC Access using Network, and double-click "Controller Time" and I receive, "Unhandled exception error has occurred in your application........."
 
 
Value '1/2/2021 2.29:16 PM" is not valid for 'Value'. 'Value' should be
 
between 'MinDate' and 'MaxDate'.
 
Parameter name: Value.
 
 
 
I attached the screen capture.  Any ideas why I receive exception error, looks like it's looking for Date, not Time?
 
 
Happens on Windows 10 as well!
 
 
More detail:
 
 
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
 
************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '1/2/2021 2:47:00 PM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Parameter name: Value
   at System.Windows.Forms.DateTimePicker.set_Value(DateTime value)
   at PCAccess3.frmPopUpEditDateTime..ctor(clsHAC _HAC)
   at PCAccess3.frmStatusSystem.Command_SetTime(Object o, DataGridViewCellEventArgs e, String HelpKeyword)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.DataGridView.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
 
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8762 (QFE.050727-8700)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
PCA3D_EN
    Assembly Version: 3.17.0.843
    Win32 Version: 3.17.0.843
    CodeBase: file:///C:/Program%20Files%20(x86)/HAI/PC%20Access/PCA3D_EN.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8770 (QFE.050727-8700)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5495 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8771 (QFE.050727-8700)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5494 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
7as-nmm0
    Assembly Version: 3.17.0.843
    Win32 Version: 2.0.50727.8770 (QFE.050727-8700)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
tce8-9ah
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8770 (QFE.050727-8700)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
 
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
 
For example:
 
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
 
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

See the same running same version of PCA on Windows 2016 server.
 

 

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.


************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '1/6/2021 4:49:44 PM' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Parameter name: Value
   at System.Windows.Forms.DateTimePicker.set_Value(DateTime value)
   at PCAccess3.frmPopUpEditDateTime..ctor(clsHAC _HAC)
   at PCAccess3.frmStatusSystem.Command_SetTime(Object o, DataGridViewCellEventArgs e, String HelpKeyword)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.DataGridView.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)




************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8813 (QFE.050727-8800)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
PCA3D_EN
    Assembly Version: 3.17.0.843
    Win32 Version: 3.17.0.843
    CodeBase: file:///C:/Program%20Files%20(x86)/HAI/PC%20Access/PCA3D_EN.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8806 (QFE.050727-8800)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8813 (QFE.050727-8800)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8813 (QFE.050727-8800)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8771 (QFE.050727-8700)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8953 (QFE.050727-8900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8773 (QFE.050727-8700)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
rba8ikqg
    Assembly Version: 3.17.0.843
    Win32 Version: 2.0.50727.8806 (QFE.050727-8800)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
hjetlnug
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8806 (QFE.050727-8800)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------


************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.


For example:


<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>


When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

Guessing it will be the same with Windows 7 and Windows 10 and Linux (via PlayonLinux).
 
I rarely utilize PCA to set time / date these days.  I have Homeseer and Omnilinkbridge checking and setting the time.
 
I have no idea why this is happening.  

Thanks Pete!
 
I will try and contact Leviton but I bet they won't fix it.  I had to set from console. Yes, I saw it on my Windows 7 machine, I have an XP drive I doubt if I ever updated PC Access (more like change in Firmware Table), could stick in old laptop and try with that, but I have my doubts.
 
I don't have Homeseer.  I bet I didn't try this since upgrading to 4.0b last year. I didn't have this issue on prior firmware 3.2D.
 
At least I can upload Clock adjust, will take a while to see if that is still working.
 
-Bob

SierraTech said:

Thanks Pete!
 
I will try and contact Leviton but I bet they won't fix it.  I had to set from console. Yes, I saw it on my Windows 7 machine, I have an XP drive I doubt if I ever updated PC Access (more like change in Firmware Table), could stick in old laptop and try with that, but I have my doubts.
 
I don't have Homeseer.  I bet I didn't try this since upgrading to 4.0b last year. I didn't have this issue on prior firmware 3.2D.
 
At least I can upload Clock adjust, will take a while to see if that is still working.
 
-Bob

Click to expand...

Did you know windows 10 is free on the MS website now? They are trying to get everybody off Win, 7 & 8.

Here all of my laptops / desktops run dual booting Ubuntu / Windows 10 (except for one still running W7).
 
Mostly been running Ubuntu these days and just do an RDP to the W2016 server for running Windows stuff.  
 
Running Windows 10 Insider Preview 21286.1000 (rs_prerelease) on all of the computers.  
 
Installed PCA on one of these laptops and see the same error as above.  
 
Over the years here have kept a few installation PCA applications and updates.  
 
Looked this morning and all of them are really old now.  
 
Trying this version ==> Setup_HAI_Dealer_PC_Access_3-4.2.3.5600  
 
Assembly Version: 3.15.0.799
Win32 Version: 3.15.0.799
 
Same error.   

I was able to set the time in the panel via SnapLink.  No go w/ PC Access.

I have snaplink on my iPhone (along with HAIKU and SPACE).  Not sure if Snaplink on ios can set the time (I didn't see where you could perform that function). I assume you have the Windows version.
 
Thank you for the information!
 
-Bob

JonW said:

I was able to set the time in the panel via SnapLink.  No go w/ PC Access.

Click to expand...

I'm able to perform from console (as noted above this is how I set it). Do you have Snaplink style console? I have the older consoles with LCD screen.

pete_c said:

Here all of my laptops / desktops run dual booting Ubuntu / Windows 10 (except for one still running W7).
 
Mostly been running Ubuntu these days and just do an RDP to the W2016 server for running Windows stuff.  
 
Running Windows 10 Insider Preview 21286.1000 (rs_prerelease) on all of the computers.  
 
Installed PCA on one of these laptops and see the same error as above.  
 
Over the years here have kept a few installation PCA applications and updates.  
 
Looked this morning and all of them are really old now.  
 
Trying this version ==> Setup_HAI_Dealer_PC_Access_3-4.2.3.5600  
 
Assembly Version: 3.15.0.799
Win32 Version: 3.15.0.799
 
Same error.   

Click to expand...

I think this is something Leviton Engineers failed to test in later firmware.

I think it's a firmware issue.  I have tried to change the time through Dealer Access, which crashes, and the SnapLink USB key and Myro:Home, both of which report success even though the time doesn't change.
 
JonW: are you sure it took?
 
-Tom

I just set the time with my OnmiTouch 3.5" panel, and it worked.  It had been ~35 seconds slow.  My guess is that this is the accumulated time loss since Jan 1, and that the automated methods that I assumed were still working all stopped working on Jan 1.  I hope I'm wrong about that, because I doubt Leviton will do another firmware update.
 
-Tom

Wow.  Turns out I was completely wrong.  Both SnapLink USB and Myro:Home can reset the time.  It seems that SnapLink USB allows you to put in a value for seconds, but discards it, so every time change event resets the time to an exact minute.  Myro:Home synchronizes with the iPhone, but also only to the nearest minute.
 
Now I'm thinking the only problem is with PC Access.  That's good news.
 
-Tom

xlurkr said:

I think it's a firmware issue.  I have tried to change the time through Dealer Access, which crashes, and the SnapLink USB key and Myro:Home, both of which report success even though the time doesn't change.
 
JonW: are you sure it took?
 
-Tom

Click to expand...

Yes, I set it ahead by 10 minutes and then set it back to normal.  PC Access would show the changed values, but could not update it.

xlurkr said:

Wow.  Turns out I was completely wrong.  Both SnapLink USB and Myro:Home can reset the time.  It seems that SnapLink USB allows you to put in a value for seconds, but discards it, so every time change event resets the time to an exact minute.  Myro:Home synchronizes with the iPhone, but also only to the nearest minute.
 
Now I'm thinking the only problem is with PC Access.  That's good news.
 
-Tom

Click to expand...

I will try and notify Leviton, I doubt they will fix the issue!

I'm having the very same issue.  This is a programming issue with PC Access.  A kind of Y2K issue, the programmers didn't think that it would be used in 2021.  I'll bet if you set your PC clock back to 2020, it will work.  I would try it but, I don't want to set my controller back that far and not be able to correct it.
 
Hopefully Levitron hasn't slammed the door on Omni just yet and they will consider fixing it.