Startup issue

[dcol 175]

Using 4.5.0.50. If I setup Emby to start with windows, It starts but embytray doesn't. If I start Emby manually it does. Tried with Emby setting, regedit, and task scheduler.

The only reason I want the tray is so I know Emby is running at a glance. What needs to be done?

[Luke 42078]

Try undoing those methods and simply using the option to run the server at startup.

[dcol 175]

That was the first thing I tried. With that option Emby didn't even startup.

[Carlo 4561]

Remove anything you added, reboot.

Install Emby on top of your existing installation.

Does it work now?

[Luke 42078]

2 hours ago, dcol said:

That was the first thing I tried. With that option Emby didn't even startup.

Was any server log file generated?

[Carlo 4561]

@dcol If you can't figure this out, send me a PM and I can likely help you out remotely.

[PenkethBoy 2068]

just for info - on Win 10 - when doing a manual start - the embytray.exe does not always appear in the task bar

its running but windows does not read the image and in task manager it has no icon (default TM icon) - i suspect its related in someway

Dcol - so see if thats whats happening

As this is my test server i dont care that much and usually the next time i use it / after a server update/ reboot the pc etc - things are back to normal

For me at least its an intermittent failure of low consequence

If i had to guess - i would suspect its the image file used during the build is not being embedded correctly/its damaged/some other issue with it/ windows version/certain update applied to windows - list could be very long

Dcol - Is there anything in the event log in windows - ive not looked as dont care - but might give Luke a clue

[dcol 175]

Thanks to all who responded.

I have just restarted the computer and looking at Task Manager, only embyserver.exe is reported. If I exit Emby and restart manually, embyserver.exe and embytray.exe is reported and the tray icon is there. There is nothing in the system logs pertaining to this issue.

In the logs below. embyserver1 is from a restart where the embytray did not start and embyserver2 is after manually exiting and starting Emby where the tray did start.

I do want to point out, I have seen this happen before when using an auto start method. Which is why I have a program running on my Windows Server 2019 production system that starts Emby delayed. So this is not new and happened on every Emby install I have done in recent memory. I am surprised it is not happening with everyone.

embyserver1.txt embyserver2.txt

Edited September 25, 2020 by dcol

[dcol 175]

Here are some more results from my testing the auto start

1. Using start Emby Server from Emby settings - Emby does not start

2. Using Startup folder - Emby does not start

3. Using regedit>run - Emby does not start

4. Using Task Scheduler no delay - Emby starts, no tray

5. Using Task Scheduler 30 second delay - Emby starts, no tray

6. Using Task Scheduler 1 minute delay - Emby starts, no tray

Tried Task Scheduler with highest privileges and other settings which made no difference. These systems are extremely fast using SSD drives. Boot time on these systems is less than 2 seconds. But doing the delayed tasks should eliminate the issue being speed.

 

Edited September 25, 2020 by dcol

[Luke 42078]

@arrbee99 is it able to run at startup for you?

[arrbee99 1815]

I'm on 4.6.0.1 now and latest Windows. Just restarting the PC and the tray is there and server and tray appear in task manager. Don't recall any problems with this except maybe occasionally in the dim and distant past. I pretty much never use the commands in the tray, just restart as required in the dashboard and occasionally start up from Windows toolbar.

This is what you're talking about I presume ?

[Carlo 4561]

Got enough stuff loaded?  Practically a connect 4 game board. 

[arrbee99 1815]

I'll have you know a good quarter of that is completely essential...

[dcol 175]

Well it is a real issue to me. Not really a big time important issue since I do have the server running on startup using task scheduler. What is more alarming is Emby server doesn't even start unless I run it as a task scheduler event. It must have to do with something Emby needs that isn't running yet. I bet if I run Emby as a service and set it to automatic delay, it will work, but I really don't want to run it as a service.

@arrbee99, is your system fast enough to startup in under 2 seconds? That may be why you don't see this issue

I am going to setup a test and run Emby on the same model system with a hard disk.

Edited September 25, 2020 by dcol

[Carlo 4561]

Your system isn't starting it 2 seconds.  It's doing a resume which is different.

Pull the electric cord after shutting down and now time your startup once plugged back in.  You'll be surprised how much different the time is when things actually have to load.

[dcol 175]

Not true. I have hibernation turned off and cold booting. As soon as the BIOS loads, 2 seconds later the system is running.

[Carlo 4561]

I've never seen windows load that fast regardless of hardware. I bet if you look at windows event logs you'll see it takes far longer than you think to load.
I'm not talking about getting a login screen, but loading the OS with all the processes load and running.  Some of these processes take longer than that to start with a system already running!

[dcol 175]

I setup another system and copied the Emby directory from the system that I was using here. it installed the MS packages than ran the firewall check. Emby started up and I set it to auto start in the setting. When I restarted, Emby and the tray worked as expected. This system is identical except that it is running a hard disk. Both system have freshly install Windows10 OS'es with no changes and only Emby is running. The only difference is one has hard disk and the other only SSD. I am using the same Emby directory copied from the other system.

Edited September 25, 2020 by dcol

[arrbee99 1815]

Probably won't help much, but...

Theoretically it should be quite fast as its a decent processor and has one of those nvme drive things. But being an Emby server PC its got, like a dozen HDDs attached, internal and usb external, which it takes ages to start and stop and start or whatever it does with them when rebooting.

[dcol 175]

The issue system has an Intel I7 and the one I just setup has an I5, so that is one hardware difference. Both are Dell Optiplex 9020's. My other production Emby server is even faster with dual NvME's and an I9 running Windows server 2019. That one has the same issue with Emby starting up. Also quick in booting once the I/O cards load in the BIOS. I measure the time from the spinning circle until all the tray icons are loaded. Ok, maybe 3 seconds. The production is twice that.

What I do on my production server is start Emby delayed with WinPatrol. That works.

So, I guess my question is, what needs to be loaded and running for Emby to startup? Even though I used a one minute delay in task scheduler and Emby did start, but not the tray.

Edited September 25, 2020 by dcol

[Carlo 4561]

Since you already know this. Just delay starting Emby for 10 seconds or so to allow the system to fully load and be ready.
Problem solved.

[dcol 175]

Yes that works for server, but not the tray. I have delayed for up to one minute and the tray does not start unless I start Emby manually. I do have work arounds with third party programs, I just wanted to report this issue and see if there was something I could do.

[letterman 40]

I start emby with the task scheduler before logging in. It works fine, but after logging in later, the embytray is missing. Is there a possibility to start embytray manually, too?
Or do I need to stop emby server again and then start it again manually?

[Luke 42078]

3 hours ago, letterman said:

I start emby with the task scheduler before logging in. It works fine, but after logging in later, the embytray is missing. Is there a possibility to start embytray manually, too?
Or do I need to stop emby server again and then start it again manually?

What is your command line with the task scheduler?

[letterman 40]

I just startet the EmbyServer.exe without parameters.
I did some research and the problem seems to be connected with windows session 0 operation of tasks started without being locked in.
https://www.coretechnologies.com/products/AlwaysUp/AlwaysUp_FAQ.html#SessionZeroIsolation
The Software "AlwayUp" explains this pretty nice.
Under these circumsstances it is best to restart the emby service after logging in again in the new session. And - voliá - the tray icon appears.

But I have one more question:
What is the command line / is there a parameter to stop (exit / shutdown) emby EmbyServer.exe?