Nest - Page 3

DadGoneMad · 01-12-2017, 02:36 PM

I had the same problem when I upgraded to v.39. I first thought it was some sort of permissions issue but could never resolve it. Instead what I did was log on with a (Win10) local account (instead of my admin account), then ran the installation (run with admin rights) and did not receive any oleaut32.dll error during installation. I do however seem to have some sort of issue that's surfaced where my HALUltra crashes repeatedly for about 10-12 times after starting. Then, after going through several WatchDog automatic restarts the crashing stops and it runs just fine. I have been trying to troubleshoot what the problem might be, the only error I see in WatchDog is "Alive Registry not set" or something along those lines. I will give tech support a call if I can ever work from home and able to be there for someone to help me determine root cause here. For Christmas I got an Amazon Echo and Dot, I configured the HA Bridge with very little issues at all. Seems to run great, am still learning how to create commands, but overall I like it a lot!

TimShriver · 01-12-2017, 02:47 PM

Please do contact support... I'm sure they'll be able to help resolve your problem.

If the Alive Registry option in WatchDog is enabled it basically is one of the many ways WD checks to make sure HAL Server is responsive. HAL Server writes a 1 to a particular Registry Entry, WD checks to make sure that the entry has be updated. If it has, WD then resets it to 0 and the process checks again after so many seconds. If the Alive Registry is not updated after 2 or 3 passes, WD will then begin the designated recovery option.

It sounds like you have something hanging HAL. To discover the culprit, you could disable a couple of things in System Settings, liek your Security, Lighting, Telephone... start HAL and if all is fine, start re-enabling items one by one to identify what is causing the problem.

Tim

dtomcat · 01-12-2017, 04:25 PM

I've had the WD alive thing the first time I booted into .39... have not had any cases since it rebooted itself. and it only happened after the first boot into .39 (after the troubleshooting noted above. Happened overnight that first night. and not since. nothing out of the ordinary occurred.

-Rob

TimShriver · 01-12-2017, 05:44 PM

Sure sounds like the install did not go correctly...

01-12-2017, 02:36 PM	#1
DadGoneMad Advanced Member Join Date: Jun 2007 Location: Katy, TX Posts: 199	Re: Nest I had the same problem when I upgraded to v.39. I first thought it was some sort of permissions issue but could never resolve it. Instead what I did was log on with a (Win10) local account (instead of my admin account), then ran the installation (run with admin rights) and did not receive any oleaut32.dll error during installation. I do however seem to have some sort of issue that's surfaced where my HALUltra crashes repeatedly for about 10-12 times after starting. Then, after going through several WatchDog automatic restarts the crashing stops and it runs just fine. I have been trying to troubleshoot what the problem might be, the only error I see in WatchDog is "Alive Registry not set" or something along those lines. I will give tech support a call if I can ever work from home and able to be there for someone to help me determine root cause here. For Christmas I got an Amazon Echo and Dot, I configured the HA Bridge with very little issues at all. Seems to run great, am still learning how to create commands, but overall I like it a lot!

01-12-2017, 02:47 PM	#2
TimShriver Administrator Join Date: Jul 2003 Location: Laurel, MD Posts: 1,588	Re: Nest Please do contact support... I'm sure they'll be able to help resolve your problem. If the Alive Registry option in WatchDog is enabled it basically is one of the many ways WD checks to make sure HAL Server is responsive. HAL Server writes a 1 to a particular Registry Entry, WD checks to make sure that the entry has be updated. If it has, WD then resets it to 0 and the process checks again after so many seconds. If the Alive Registry is not updated after 2 or 3 passes, WD will then begin the designated recovery option. It sounds like you have something hanging HAL. To discover the culprit, you could disable a couple of things in System Settings, liek your Security, Lighting, Telephone... start HAL and if all is fine, start re-enabling items one by one to identify what is causing the problem. Tim __________________ Tim Shriver Home Automated Living

01-12-2017, 04:25 PM	#3
dtomcat Advanced Member III Join Date: Aug 2008 Posts: 391	Re: Nest I've had the WD alive thing the first time I booted into .39... have not had any cases since it rebooted itself. and it only happened after the first boot into .39 (after the troubleshooting noted above. Happened overnight that first night. and not since. nothing out of the ordinary occurred. -Rob __________________ HALpro v7.2.7 Win 7 HAL voices US/UK HAL DMC Tell Me v2.7.0

01-12-2017, 05:44 PM	#4
TimShriver Administrator Join Date: Jul 2003 Location: Laurel, MD Posts: 1,588	Re: Nest Sure sounds like the install did not go correctly... __________________ Tim Shriver Home Automated Living

Currently Active Users Viewing This Thread: 8 (0 members and 8 guests)