NO dvr

Help and support for HDHomeRun DVR and HDHomeRun software for Windows 10, Mac, Android, XBox, etc.
collector of junk
Posts: 6
Joined: Mon Oct 30, 2017 5:21 pm

NO dvr

Postby collector of junk » Thu Jan 10, 2019 7:25 pm

HD Homerun is installed on my computer and i also installed the software for the dvr, but i cannot record to my computer because the dvr software, according to the software, is not installed? WTF :twisted: :twisted: :twisted:

why does it not acknoledge the dvr software? and how do i correct it?

signcarver
Expert
Posts: 7806
Joined: Wed Jan 24, 2007 1:04 am
Device ID: 131B34B7 13231F92 1070A18E 1073ED6F

Re: NO dvr

Postby signcarver » Thu Jan 10, 2019 7:57 pm

Do you have a dvr subscription?

Describe your setup... the win 7 software will always state that as it is expected to use kodi and the addon. If on windows 10 you might need to run the loopback fix if the dvr engine is on the same computer.

Is there a log file in the directory you told the dvr to record in? (I ask this as one main issue is if the directory isn't ready when the dvr starts, it won't start). If there is, what does it say? (Paste long logs in code blocks as it must discover tuners to be authorized with the subscription.

RockandRoller70
Posts: 987
Joined: Mon Aug 29, 2016 9:43 am
Device ID: 1311127E / 1322D7A7

Re: NO dvr

Postby RockandRoller70 » Thu Jan 10, 2019 7:58 pm

Did you run the loopback?

collector of junk
Posts: 6
Joined: Mon Oct 30, 2017 5:21 pm

Re: NO dvr

Postby collector of junk » Thu Jan 10, 2019 10:29 pm

1. yes, i have a dvr subscription
2. this is a copy of the log file on the drive with the dvr recorder on it (supposidly)
3. what is the loopback?

HDHomeRun RECORD 20180921 Windows
20190111-00:00:22 Status: Resource: nbk=0 dmk=240
20190111-00:00:23 Recorded: directory D:\ with 7 subdirs and 13 recordings
20190111-00:02:22 Status: Resource: nbk=0 dmk=240
20190111-00:03:16 Recording: discover on 192.168.1.255
20190111-00:03:16 Recording: 132723BF lineup request success (found 354 channels)
20190111-00:03:16 Recording: discover on 192.168.1.255
20190111-00:03:17 Recording: discover response from 132723BF: lineup url = http://192.168.1.4:80/lineup.json
20190111-00:03:17 Recorded: recorded sync to record-api.hdhomerun.com
20190111-00:03:17 Recording: event download from record-api.hdhomerun.com
20190111-00:03:17 System: server time = Fri Jan 11 00:03:17 2019 (correction of -2s)
20190111-00:03:17 Recorded: recorded sync success
20190111-00:03:17 System: server time = Fri Jan 11 00:03:17 2019 (correction of -2s)
20190111-00:03:17 Recording: event download success
20190111-00:03:17 Recording: disk space available = 875GB
20190111-00:03:17 Recording: current time = Fri Jan 11 00:03:17 2019 (correction of -2s)
20190111-00:03:17 Recording: no timer events planned
20190111-00:04:22 Status: Resource: nbk=0 dmk=240
20190111-00:06:22 Status: Resource: nbk=0 dmk=240
20190111-00:08:22 Status: Resource: nbk=0 dmk=240
20190111-00:10:22 Status: Resource: nbk=0 dmk=240
20190111-00:12:22 Status: Resource: nbk=0 dmk=240
20190111-00:14:22 Status: Resource: nbk=0 dmk=240
20190111-00:16:22 Status: Resource: nbk=0 dmk=240
20190111-00:18:22 Status: Resource: nbk=0 dmk=240
20190111-00:20:22 Status: Resource: nbk=0 dmk=240
20190111-00:22:22 Status: Resource: nbk=0 dmk=240
20190111-00:24:22 Status: Resource: nbk=0 dmk=240
20190111-00:26:22 Status: Resource: nbk=0 dmk=240
20190111-00:28:22 Status: Resource: nbk=0 dmk=240
20190111-00:30:22 Status: Resource: nbk=0 dmk=240
20190111-00:32:22 Status: Resource: nbk=0 dmk=240
20190111-00:34:22 Status: Resource: nbk=0 dmk=240
20190111-00:36:22 Status: Resource: nbk=0 dmk=240
20190111-00:38:22 Status: Resource: nbk=0 dmk=240
20190111-00:40:22 Status: Resource: nbk=0 dmk=240
20190111-00:42:22 Status: Resource: nbk=0 dmk=240
20190111-00:44:22 Status: Resource: nbk=0 dmk=240
20190111-00:46:22 Status: Resource: nbk=0 dmk=240
20190111-00:48:22 Status: Resource: nbk=0 dmk=240
20190111-00:50:22 Status: Resource: nbk=0 dmk=240
20190111-00:52:22 Status: Resource: nbk=0 dmk=240
20190111-00:54:22 Status: Resource: nbk=0 dmk=240
20190111-00:56:22 Status: Resource: nbk=0 dmk=240
20190111-00:58:22 Status: Resource: nbk=0 dmk=240
20190111-01:00:22 Status: Resource: nbk=0 dmk=240
20190111-01:02:22 Status: Resource: nbk=0 dmk=240
20190111-01:04:22 Status: Resource: nbk=0 dmk=240
20190111-01:06:22 Status: Resource: nbk=0 dmk=240
20190111-01:08:22 Status: Resource: nbk=0 dmk=240
20190111-01:10:22 Status: Resource: nbk=0 dmk=240
20190111-01:12:22 Status: Resource: nbk=0 dmk=240
20190111-01:14:22 Status: Resource: nbk=0 dmk=240
20190111-01:16:22 Status: Resource: nbk=0 dmk=240
20190111-01:18:22 Status: Resource: nbk=0 dmk=240
20190111-01:20:22 Status: Resource: nbk=0 dmk=240
20190111-01:22:22 Status: Resource: nbk=0 dmk=240
20190111-01:24:22 Status: Resource: nbk=0 dmk=240
20190111-01:26:22 Status: Resource: nbk=0 dmk=240
20190111-01:28:22 Status: Resource: nbk=0 dmk=240
20190111-01:30:22 Status: Resource: nbk=0 dmk=240
20190111-01:32:22 Status: Resource: nbk=0 dmk=240
20190111-01:34:22 Status: Resource: nbk=0 dmk=240
20190111-01:36:22 Status: Resource: nbk=0 dmk=240
20190111-01:38:22 Status: Resource: nbk=0 dmk=240
20190111-01:40:22 Status: Resource: nbk=0 dmk=240
20190111-01:42:22 Status: Resource: nbk=0 dmk=240
20190111-01:44:22 Status: Resource: nbk=0 dmk=240
20190111-01:46:22 Status: Resource: nbk=0 dmk=240
20190111-01:48:22 Status: Resource: nbk=0 dmk=240
20190111-01:50:22 Status: Resource: nbk=0 dmk=240
20190111-01:52:22 Status: Resource: nbk=0 dmk=240
20190111-01:54:22 Status: Resource: nbk=0 dmk=240
20190111-01:56:22 Status: Resource: nbk=0 dmk=240
20190111-01:58:22 Status: Resource: nbk=0 dmk=240
20190111-02:00:22 Status: Resource: nbk=0 dmk=240
20190111-02:01:42 Recording: discover on 192.168.1.255
20190111-02:01:42 Recording: 132723BF lineup request success (found 354 channels)
20190111-02:01:42 Recording: discover on 192.168.1.255
20190111-02:01:43 Recording: discover response from 132723BF: lineup url = http://192.168.1.4:80/lineup.json
20190111-02:01:43 Recorded: recorded sync to record-api.hdhomerun.com
20190111-02:01:43 Recording: event download from record-api.hdhomerun.com
20190111-02:01:43 System: server time = Fri Jan 11 02:01:43 2019 (correction of -2s)
20190111-02:01:43 Recorded: recorded sync success
20190111-02:01:43 System: server time = Fri Jan 11 02:01:43 2019 (correction of -2s)
20190111-02:01:43 Recording: event download success
20190111-02:01:43 Recording: disk space available = 875GB
20190111-02:01:43 Recording: current time = Fri Jan 11 02:01:43 2019 (correction of -2s)
20190111-02:01:43 Recording: no timer events planned
20190111-02:02:22 Status: Resource: nbk=0 dmk=240
20190111-02:04:22 Status: Resource: nbk=0 dmk=240
20190111-02:06:22 Status: Resource: nbk=0 dmk=240
20190111-02:08:22 Status: Resource: nbk=0 dmk=240
20190111-02:09:40 Recorded: directory D:\ with 7 subdirs and 13 recordings
20190111-02:09:41 Recorded: directory D:\ with 7 subdirs and 13 recordings


HDHomeRun RECORD 20180921 Windows
20190111-02:11:19 Recording: RecordPath[0] = 'D:\'
20190111-02:11:19 Recording: RecordPath D:\ = ntfs
20190111-02:11:19 System: LocalIP: 192.168.1.3 255.255.255.0
20190111-02:11:19 System: website port = 62449
20190111-02:11:19 Recorded: RecordPath 'D:\' (ntfs)
20190111-02:11:19 Recorded: directory D:\$RECYCLE.BIN\S-1-5-21-53040107-2543322028-3660897993-1001\ with 0 subdirs and 0 recordings
20190111-02:11:19 Recorded: directory D:\$RECYCLE.BIN\ with 1 subdirs and 0 recordings
20190111-02:11:20 Recorded: directory D:\MENCS\01\ with 0 subdirs and 0 recordings
20190111-02:11:20 Recorded: directory D:\MENCS\02\ with 0 subdirs and 0 recordings
20190111-02:11:20 Recorded: directory D:\MENCS\ with 2 subdirs and 0 recordings
20190111-02:11:20 Recorded: directory D:\System Volume Information\ with 0 subdirs and 0 recordings
20190111-02:11:20 Recorded: directory D:\videos to render\ with 0 subdirs and 0 recordings
20190111-02:11:20 Recorded: directory D:\videos to render i\ with 0 subdirs and 0 recordings
20190111-02:11:20 Recorded: directory D:\videos to render ii\ with 0 subdirs and 0 recordings
20190111-02:11:20 Recorded: directory D:\videos to render iii\ with 0 subdirs and 0 recordings
20190111-02:11:20 Recorded: directory D:\ with 7 subdirs and 13 recordings
20190111-02:11:20 Recording: discover on 192.168.1.255
20190111-02:11:20 Status: Resource: nbk=0 dmk=168
20190111-02:11:20 Status: ticks = 115529078
20190111-02:11:20 Recording: 132723BF lineup request success (found 354 channels)
20190111-02:11:20 Recording: discover on 192.168.1.255
20190111-02:11:20 Recording: discover response from 132723BF: lineup url = http://192.168.1.4:80/lineup.json
20190111-02:11:20 Recorded: recorded sync to record-api.hdhomerun.com
20190111-02:11:20 Recording: event download from record-api.hdhomerun.com
20190111-02:11:19 System: server time = Fri Jan 11 02:11:19 2019 (correction of -2s)
20190111-02:11:19 Recorded: recorded sync success
20190111-02:11:19 System: server time = Fri Jan 11 02:11:19 2019 (correction of -2s)
20190111-02:11:19 Recording: event download success
20190111-02:11:19 Recording: disk space available = 875GB
20190111-02:11:19 Recording: current time = Fri Jan 11 02:11:19 2019 (correction of -2s)
20190111-02:11:19 Recording: no timer events planned
20190111-02:13:19 Status: Resource: nbk=2 dmk=186
20190111-02:15:19 Status: Resource: nbk=2 dmk=186
20190111-02:16:58 Recorded: directory D:\ with 7 subdirs and 13 recordings
20190111-02:16:59 Recorded: directory D:\ with 7 subdirs and 13 recordings


HDHomeRun RECORD 20180921 Windows 5042f062-4e1f-4730-a2d0-d53ed7d4e4ae
20190111-02:19:03 Recording: RecordPath[0] = 'D:\'
20190111-02:19:03 Recording: RecordPath D:\ = ntfs
20190111-02:19:03 System: LocalIP: 192.168.1.3 255.255.255.0
20190111-02:19:03 System: website port = 50902
20190111-02:19:03 Recorded: RecordPath 'D:\' (ntfs)
20190111-02:19:03 Recorded: directory D:\$RECYCLE.BIN\S-1-5-21-53040107-2543322028-3660897993-1001\ with 0 subdirs and 0 recordings
20190111-02:19:03 Recorded: directory D:\$RECYCLE.BIN\ with 1 subdirs and 0 recordings
20190111-02:19:03 Recorded: directory D:\MENCS\01\ with 0 subdirs and 0 recordings
20190111-02:19:03 Recorded: directory D:\MENCS\02\ with 0 subdirs and 0 recordings
20190111-02:19:03 Recorded: directory D:\MENCS\ with 2 subdirs and 0 recordings
20190111-02:19:03 Recorded: directory D:\System Volume Information\ with 0 subdirs and 0 recordings
20190111-02:19:03 Recorded: directory D:\videos to render\ with 0 subdirs and 0 recordings
20190111-02:19:03 Recorded: directory D:\videos to render i\ with 0 subdirs and 0 recordings
20190111-02:19:03 Recorded: directory D:\videos to render ii\ with 0 subdirs and 0 recordings
20190111-02:19:03 Recorded: directory D:\videos to render iii\ with 0 subdirs and 0 recordings
20190111-02:19:03 Recorded: directory D:\ with 7 subdirs and 13 recordings
20190111-02:19:03 Recording: discover on 192.168.1.255
20190111-02:19:03 Status: Resource: nbk=0 dmk=168
20190111-02:19:03 Status: ticks = 115992531
20190111-02:19:03 Recording: 132723BF lineup request success (found 354 channels)
20190111-02:19:04 Recording: discover on 192.168.1.255
20190111-02:19:04 Recording: discover response from 132723BF: lineup url = http://192.168.1.4:80/lineup.json
20190111-02:19:04 Recorded: recorded sync to record-api.hdhomerun.com
20190111-02:19:04 Recording: event download from record-api.hdhomerun.com
20190111-02:19:02 System: server time = Fri Jan 11 02:19:02 2019 (correction of -2s)
20190111-02:19:02 Recorded: recorded sync success
20190111-02:19:02 System: server time = Fri Jan 11 02:19:02 2019 (correction of -2s)
20190111-02:19:02 Recording: event download success
20190111-02:19:02 Recording: disk space available = 875GB
20190111-02:19:02 Recording: current time = Fri Jan 11 02:19:02 2019 (correction of -2s)
20190111-02:19:02 Recording: no timer events planned
20190111-02:21:01 Status: Resource: nbk=2 dmk=186
20190111-02:23:01 Status: Resource: nbk=2 dmk=186
20190111-02:25:01 Status: Resource: nbk=2 dmk=186
20190111-02:27:01 Status: Resource: nbk=2 dmk=186
20190111-02:29:01 Status: Resource: nbk=2 dmk=186
20190111-02:31:01 Status: Resource: nbk=2 dmk=186
20190111-02:33:01 Status: Resource: nbk=2 dmk=187
20190111-02:35:01 Status: Resource: nbk=2 dmk=187
20190111-02:37:01 Status: Resource: nbk=2 dmk=187
20190111-02:39:01 Status: Resource: nbk=2 dmk=187
20190111-02:41:01 Status: Resource: nbk=2 dmk=187
20190111-02:43:01 Status: Resource: nbk=2 dmk=187
20190111-02:45:01 Status: Resource: nbk=2 dmk=187
20190111-02:47:01 Status: Resource: nbk=2 dmk=187
20190111-02:49:01 Status: Resource: nbk=2 dmk=187
20190111-02:51:01 Status: Resource: nbk=2 dmk=187
20190111-02:53:01 Status: Resource: nbk=2 dmk=187
20190111-02:55:01 Status: Resource: nbk=2 dmk=187
20190111-02:57:01 Status: Resource: nbk=2 dmk=187
20190111-02:59:01 Status: Resource: nbk=2 dmk=187
20190111-03:01:01 Status: Resource: nbk=2 dmk=187
20190111-03:03:01 Status: Resource: nbk=2 dmk=187
20190111-03:05:01 Status: Resource: nbk=2 dmk=187
20190111-03:07:01 Status: Resource: nbk=2 dmk=187
20190111-03:09:01 Status: Resource: nbk=2 dmk=187
20190111-03:11:01 Status: Resource: nbk=2 dmk=187
20190111-03:13:01 Status: Resource: nbk=2 dmk=188
20190111-03:15:01 Status: Resource: nbk=2 dmk=188
20190111-03:17:01 Status: Resource: nbk=2 dmk=188
20190111-03:19:01 Status: Resource: nbk=2 dmk=188
20190111-03:21:01 Status: Resource: nbk=2 dmk=188
20190111-03:23:01 Status: Resource: nbk=2 dmk=188
20190111-03:25:01 Status: Resource: nbk=2 dmk=188
20190111-03:27:01 Status: Resource: nbk=2 dmk=188
20190111-03:29:01 Status: Resource: nbk=2 dmk=188
20190111-03:31:01 Status: Resource: nbk=2 dmk=188
20190111-03:33:01 Status: Resource: nbk=2 dmk=188
20190111-03:35:01 Status: Resource: nbk=2 dmk=188
20190111-03:37:01 Status: Resource: nbk=2 dmk=188
20190111-03:39:01 Status: Resource: nbk=2 dmk=188
20190111-03:41:01 Status: Resource: nbk=2 dmk=188
20190111-03:43:01 Status: Resource: nbk=2 dmk=188
20190111-03:45:01 Status: Resource: nbk=2 dmk=188
20190111-03:47:01 Status: Resource: nbk=2 dmk=188
20190111-03:49:01 Status: Resource: nbk=2 dmk=188
20190111-03:51:01 Status: Resource: nbk=2 dmk=188
20190111-03:53:01 Status: Resource: nbk=2 dmk=189
20190111-03:55:01 Status: Resource: nbk=2 dmk=189
20190111-03:57:01 Status: Resource: nbk=2 dmk=189
20190111-03:59:01 Status: Resource: nbk=2 dmk=189
20190111-04:01:01 Status: Resource: nbk=2 dmk=189
20190111-04:03:01 Status: Resource: nbk=2 dmk=189
20190111-04:05:01 Status: Resource: nbk=2 dmk=189
20190111-04:07:01 Status: Resource: nbk=2 dmk=189
20190111-04:09:01 Status: Resource: nbk=2 dmk=189
20190111-04:11:01 Status: Resource: nbk=2 dmk=189
20190111-04:13:01 Status: Resource: nbk=2 dmk=189
20190111-04:13:36 Recording: discover on 192.168.1.255
20190111-04:13:36 Recording: 132723BF lineup request success (found 354 channels)
20190111-04:13:36 Recording: discover on 192.168.1.255
20190111-04:13:37 Recording: discover response from 132723BF: lineup url = http://192.168.1.4:80/lineup.json
20190111-04:13:37 Recorded: recorded sync to record-api.hdhomerun.com
20190111-04:13:37 Recording: event download from record-api.hdhomerun.com
20190111-04:13:37 System: server time = Fri Jan 11 04:13:37 2019 (correction of -2s)
20190111-04:13:37 Recorded: recorded sync success
20190111-04:13:37 System: server time = Fri Jan 11 04:13:37 2019 (correction of -2s)
20190111-04:13:37 Recording: event download success
20190111-04:13:37 Recording: disk space available = 875GB
20190111-04:13:37 Recording: current time = Fri Jan 11 04:13:37 2019 (correction of -2s)
20190111-04:13:37 Recording: no timer events planned
20190111-04:15:01 Status: Resource: nbk=0 dmk=190
20190111-04:17:01 Status: Resource: nbk=0 dmk=190
20190111-04:19:01 Status: Resource: nbk=0 dmk=190
20190111-04:21:01 Status: Resource: nbk=0 dmk=190
20190111-04:23:01 Status: Resource: nbk=0 dmk=190
20190111-04:25:01 Status: Resource: nbk=0 dmk=190
20190111-04:27:01 Status: Resource: nbk=0 dmk=190
20190111-04:29:01 Status: Resource: nbk=0 dmk=190
20190111-04:31:01 Status: Resource: nbk=0 dmk=190
20190111-04:33:01 Status: Resource: nbk=0 dmk=190
20190111-04:35:01 Status: Resource: nbk=0 dmk=190
20190111-04:37:01 Status: Resource: nbk=0 dmk=191
20190111-04:39:01 Status: Resource: nbk=0 dmk=191
20190111-04:41:01 Status: Resource: nbk=0 dmk=191
20190111-04:43:01 Status: Resource: nbk=0 dmk=191
20190111-04:45:01 Status: Resource: nbk=0 dmk=191
20190111-04:47:01 Status: Resource: nbk=0 dmk=191
20190111-04:49:01 Status: Resource: nbk=0 dmk=191
20190111-04:51:01 Status: Resource: nbk=0 dmk=191
20190111-04:53:01 Status: Resource: nbk=0 dmk=191
20190111-04:55:01 Status: Resource: nbk=0 dmk=191
20190111-04:57:01 Status: Resource: nbk=0 dmk=191
20190111-04:59:01 Status: Resource: nbk=0 dmk=191
20190111-05:01:01 Status: Resource: nbk=0 dmk=191
20190111-05:03:01 Status: Resource: nbk=0 dmk=191
20190111-05:05:01 Status: Resource: nbk=0 dmk=191
20190111-05:07:01 Status: Resource: nbk=0 dmk=191
20190111-05:09:01 Status: Resource: nbk=0 dmk=191
20190111-05:11:01 Status: Resource: nbk=0 dmk=191
20190111-05:13:01 Status: Resource: nbk=0 dmk=191
20190111-05:15:01 Status: Resource: nbk=0 dmk=192
20190111-05:17:01 Status: Resource: nbk=0 dmk=192
20190111-05:19:01 Status: Resource: nbk=0 dmk=192
20190111-05:21:01 Status: Resource: nbk=0 dmk=192
20190111-05:23:01 Status: Resource: nbk=0 dmk=192
20190111-05:25:01 Status: Resource: nbk=0 dmk=192

signcarver
Expert
Posts: 7806
Joined: Wed Jan 24, 2007 1:04 am
Device ID: 131B34B7 13231F92 1070A18E 1073ED6F

Re: NO dvr

Postby signcarver » Thu Jan 10, 2019 11:09 pm

As I said, please put long logs in code blocks (since they are there already, edit the post and select the part with the log (you can do it all as one or break them up and repeat) and click Code (above between Quote and List)

Personally, I would suggest not using d:\ with all that junk on the drive (including some folders it should never try to navigate through)... make a folder on drive D: (call it whatever you want but I suggest HDHomeRun) then run setup and enable the DVR with D:\HDHomeRun (or whatever you called it) as the RecordPath. Then make sure to restart the engine (on a windows PC I would suggest restarting but I usually bring up the services and turn it off and back on- you should also be able to do the same in setup but sometimes I don't trust it (at least when initially setting the path).

However you did not describe the system. What version of windows? Any non-microsoft anti-virus/anti-malware or security software/firewall. If you are using windows 10, did you do the loopback fix (if viewing on the same machine). If not using windows 10, that is expected as the viewing app does not support the DVR and one is to use kodi with the add-on (or unofficial add-on)

collector of junk
Posts: 6
Joined: Mon Oct 30, 2017 5:21 pm

Re: NO dvr

Postby collector of junk » Fri Jan 11, 2019 12:13 am

Windows 10 is what i am using
Webroot SecureAnywhere

i moved the dvr to another drive, drive H:/TV1

again, what is the "loopback fix". i have not idea what it is.

here is the log from the new drive

Code: Select all

HDHomeRun RECORD 20180921 Windows 5042f062-4e1f-4730-a2d0-d53ed7d4e4ae 20190111-06:47:24 Recording: RecordPath[0] = 'H:\TV1\' 20190111-06:47:24 Recording: RecordPath H:\TV1\ = ntfs 20190111-06:47:24 System: LocalIP: 192.168.1.3 255.255.255.0 20190111-06:47:24 System: website port = 62183 20190111-06:47:24 Recorded: RecordPath 'H:\TV1\' (ntfs) 20190111-06:47:24 Recorded: directory H:\TV1\ with 0 subdirs and 0 recordings 20190111-06:47:24 Recording: discover on 192.168.1.255 20190111-06:47:24 Status: Resource: nbk=0 dmk=146 20190111-06:47:24 Status: ticks = 132093250 20190111-06:47:24 Recording: 132723BF lineup request success (found 354 channels) 20190111-06:47:24 Recording: discover on 192.168.1.255 20190111-06:47:25 Recording: discover response from 132723BF: lineup url = http://192.168.1.4:80/lineup.json 20190111-06:47:25 Recorded: recorded sync to record-api.hdhomerun.com 20190111-06:47:25 Recording: event download from record-api.hdhomerun.com 20190111-06:47:23 System: server time = Fri Jan 11 06:47:23 2019 (correction of -2s) 20190111-06:47:23 Recorded: recorded sync success 20190111-06:47:23 System: server time = Fri Jan 11 06:47:23 2019 (correction of -2s) 20190111-06:47:23 Recording: event download success 20190111-06:47:23 Recording: disk space available = 3023GB 20190111-06:47:23 Recording: current time = Fri Jan 11 06:47:23 2019 (correction of -2s) 20190111-06:47:23 Recording: no timer events planned 20190111-06:49:22 Status: Resource: nbk=2 dmk=165
when i run the HDHomeRun program and i try to go into the bottom right part of the screen like this Image
and when i run the HDHomeRun program and all it says is "NO DVR Configured"

RockandRoller70
Posts: 987
Joined: Mon Aug 29, 2016 9:43 am
Device ID: 1311127E / 1322D7A7

Re: NO dvr

Postby RockandRoller70 » Fri Jan 11, 2019 7:00 am

DVR record engine on the same PC:

By default, Windows 10 blocks Windows Store apps from communicating with other apps/services on the same PC. This can prevent the Windows 10 app from finding a DVR running on the same PC. The HDHomeRun installer changes a setting that should bypass this issue. Should you find that you can access the DVR from other devices but not from the Windows 10 PC it is running on, do the following:
Right click on your Start menu icon and choose Windows PowerShell (Administrator) or Command Prompt (Admin)

Run the following command:
CheckNetIsolation LoopbackExempt -a -n="ef712ba7.hdhomerundvr_23nna27hyxhag"

collector of junk
Posts: 6
Joined: Mon Oct 30, 2017 5:21 pm

Re: NO dvr

Postby collector of junk » Fri Jan 11, 2019 8:45 am

DVR record engine on the same PC:

By default, Windows 10 blocks Windows Store apps from communicating with other apps/services on the same PC. This can prevent the Windows 10 app from finding a DVR running on the same PC. The HDHomeRun installer changes a setting that should bypass this issue. Should you find that you can access the DVR from other devices but not from the Windows 10 PC it is running on, do the following:
Right click on your Start menu icon and choose Windows PowerShell (Administrator) or Command Prompt (Admin)

Run the following command:
CheckNetIsolation LoopbackExempt -a -n="ef712ba7.hdhomerundvr_23nna27hyxhag"
this worked....thank you very much :D :D :D :D

RockandRoller70
Posts: 987
Joined: Mon Aug 29, 2016 9:43 am
Device ID: 1311127E / 1322D7A7

Re: NO dvr

Postby RockandRoller70 » Sun Jan 13, 2019 8:58 am

this worked....thank you very much :D :D :D :D
: thumbs up :

HDHRBevo
Posts: 105
Joined: Thu Apr 16, 2009 9:40 am

Re: NO dvr

Postby HDHRBevo » Sun Jan 13, 2019 10:37 am

Run the following command:
CheckNetIsolation LoopbackExempt -a -n="ef712ba7.hdhomerundvr_23nna27hyxhag"
Anyone know why this isn't done as a part of the SD DVR install? Seems like this could/should be done when a setup client is installed?

Gar

Online
nickk
Silicondust
Posts: 15183
Joined: Tue Jan 13, 2004 9:39 am

Re: NO dvr

Postby nickk » Sun Jan 13, 2019 11:56 am

Run the following command:
CheckNetIsolation LoopbackExempt -a -n="ef712ba7.hdhomerundvr_23nna27hyxhag"
Anyone know why this isn't done as a part of the SD DVR install? Seems like this could/should be done when a setup client is installed?
It is done automatically by the SD DVR install (the HDHomeRun Windows Installer).

My guess is it failed for the OP for some reason. The installer doesn't abort if invoking CheckNetIsolation fails.

Nick

HDHRBevo
Posts: 105
Joined: Thu Apr 16, 2009 9:40 am

Re: NO dvr

Postby HDHRBevo » Sun Jan 13, 2019 12:08 pm


My guess is it failed for the OP for some reason. The installer doesn't abort if invoking CheckNetIsolation fails.

Nick
I can appreciate not aborting, but how about an error message, pointing to CheckNetIsolation with the error return code? That would at least better define why the "No DVR" is occurring (IMO).

Gary


Return to “HDHomeRun Software Setup & Troubleshooting (Live & DVR)”

Who is online

Users browsing this forum: kdavis11_1 and 6 guests