Does v5 support multiple recording directories?

[markn62]

Thanks Marvin. It would help to know if the service could be ran as other than "Local System" so I'm approaching it from the right side of the problem, the service account or the share permissions.

[mvallevand]

"Marvin"  says If you had searched the forum you would see that sub and others have recommended changing to another user

Martin

[sub]

You should be able to go into the windows Services control panel, view the properties of the service and change the login user.

[markn62]

Sorry Martin, multitasking a bit here. I did search the forum and didn't find that post, sorry. From Google I was getting mostly not to change any service from Local System" as it usually screws the client or other functions up. Glad you mentioned, I'm busily trying to solve the problem from the Nas permissions side.

[markn62]

Set NextPvr service to log on as admin and tried as user.  Both give me 1069 error, "Windows could not start the NextPvr Service service on Local Computer".  Group Admin and User is already in "Log on as a service" properties.  And user Admin and User is already in "Allow log on locally".  Should work as is.  Still googling.  Shouldn't be this much trouble to get NextPvr service to use network shares.  Btw, its not so easy to search the NextPvr forum when all the links in posts that direct to the answer are broken.

[mvallevand]

When you find a link you might have to use the words in title to find the original link. A pain but answering the same question many times is a pain too and users who find the answers don't like updating the wiki.

FWIW I just tried v5 as a service with my name and my password and it worked fine. Keep digging.

Martin

[sub]

Shouldn't be this much trouble to get NextPvr service to use network shares.

This isn't something wrong with NextPVR - ultimately it comes down to whether whatever account you're running NextPVR as, can access whatever share you're trying to use.

[markn62]

Eight hours of effort later I finally arrived at a fix. Got no help from the Nas vendor/forum to create a transparent share even when user permission set to "everyone". Rather than fight MS I finally conceded to change the Nas share to have a matching user/pw to an account in the box running the NextPvr service. With this I was able to set the service log on from Local System to This Account without an error. Now I have another hour of work changing passwords & scripts in other devices to support this change. Domino effect...

[mvallevand]

I would have just run the NAS share with no password and saved all the headaches. Kind of a waste of time having security on a home LAN on video files you can open with NextPVR

Your problem is likely mistaking Everyone for Guest they are totally different in Windows.

Martin

[markn62]

I tried using both Everyone and Guest in the Nas in separate instances. Neither worked. I would have preferred to create a transparent share on the Nas but nobody seems to know how to do it in a qNap TS-251. Wasn't going to burn up any more time trying. I thought so long as the service "log on" matched an account's user/pw in the box it would take. My mistake was not knowing that setting a service "log on" to a share actually tries to connect to that share and throws an error if it can't. The choice is "This Account" not "This Share" so I assumed wrong.