Jump to content

Help with Windows Service


Dysan
Go to solution Solved by Luke,

Recommended Posts

No, i think your system is just having issues in general. I think the actual problem is that ffmpeg can't access the file path. Notice there are internal emby server functions that are also unable to access them:

The directory name \\192.168.1.8\kinder\disney is invalid.
	System.ArgumentException
	   at System.IO.FileSystemWatcher..ctor(String path, String filter)
	   at MediaBrowser.Server.Implementations.IO.LibraryMonitor.<>c__DisplayClassf.<StartWatchingPath>b__e()

That error means the operating system is throwing errors when trying to access that path.

Link to comment
Share on other sites

Strange,  can browse to the share without any problems, also theres a drive mapping made, that also doens't give issues.

manually entering the ffmpeg command starts the transcoding without a problem.

could it be that emby is running as a service which has no access to the NAS?

Edited by Dysan
Link to comment
Share on other sites

  • Solution

you're running the server as a service, so you need to look at the account that the service runs under. or just keep it simple and use the tray icon instead

  • Like 1
Link to comment
Share on other sites

Yep log on as a service rights granted to the user, 

Tray icon is not really an option, because the server has weekly reboots and doesn't login automatically

Link to comment
Share on other sites

  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...