2012-05-08, 11:35 PM
Need some help on this.
From the beginning: wireless router damaged in lightning storm leaving only one port working. No internet for HTPC. Installed spare Westell router and HTPC with original static ip address (on the correct subnet) would not connect. Changed to dynamic address and still would not connect. Futzed around with a TCP/IP stack "repair" using netsh winsock reset and netsh int ip reset. Finally got it to work by manually specifying the gateway address. NPVR was OK during this time. New Linksys router arrived and after installing, the HTPC would again not connect. Went through some more dynamic vs static address switching, and it finally connected. Has been OK since. There were other problems with the firewire devices disappearing, but some repairs and fiddling have them back, and they seem to be stable. Now, NPVR is sick.
The recording service dies when the machine wakes for a recording, and then cannot be restarted (the service, the computer seems to be fine). From the Services applet, a start request gives an Error 1067 Process terminated unexpectedly. From the NPVR start the service command, it gets a timeout message eventually. The event viewer reports the service stopped. There is some xml info I can provide if needed.
After a period (hours, at least) the service can be restarted, watch live TV etc. Then, when the HTPC sleeps and subsequently wakes to record, the service dies. Others have reported that a corrupt config.xml caused the 1067 error, so I deleted it to start over, but no help. This started with version 2.3.6, so I upgraded to 2.4.3 with the same results. Leads me to believe the problem is Windows rather than NPVR.
So, logs attached with what looks like an internal network problem. Windows firewall is off and there are no other firewalls. Hope somebody can point me in the right direction. (I probably should have reinstalled Win7, it would have taken less time than I have spent so far.)
From the beginning: wireless router damaged in lightning storm leaving only one port working. No internet for HTPC. Installed spare Westell router and HTPC with original static ip address (on the correct subnet) would not connect. Changed to dynamic address and still would not connect. Futzed around with a TCP/IP stack "repair" using netsh winsock reset and netsh int ip reset. Finally got it to work by manually specifying the gateway address. NPVR was OK during this time. New Linksys router arrived and after installing, the HTPC would again not connect. Went through some more dynamic vs static address switching, and it finally connected. Has been OK since. There were other problems with the firewire devices disappearing, but some repairs and fiddling have them back, and they seem to be stable. Now, NPVR is sick.
The recording service dies when the machine wakes for a recording, and then cannot be restarted (the service, the computer seems to be fine). From the Services applet, a start request gives an Error 1067 Process terminated unexpectedly. From the NPVR start the service command, it gets a timeout message eventually. The event viewer reports the service stopped. There is some xml info I can provide if needed.
After a period (hours, at least) the service can be restarted, watch live TV etc. Then, when the HTPC sleeps and subsequently wakes to record, the service dies. Others have reported that a corrupt config.xml caused the 1067 error, so I deleted it to start over, but no help. This started with version 2.3.6, so I upgraded to 2.4.3 with the same results. Leads me to believe the problem is Windows rather than NPVR.
So, logs attached with what looks like an internal network problem. Windows firewall is off and there are no other firewalls. Hope somebody can point me in the right direction. (I probably should have reinstalled Win7, it would have taken less time than I have spent so far.)
HTPC: Optiplex 7010, HDHR Prime/Avermedia Duet A188, NPVR 4.2.5, Win10 Pro
Test:
Test: