setup.exe doesn't detect .net 4.6 on Windows Server 2016

[Tackyou 0]

Hi,

 

I have a new server with Windows Server 2016, 10.0.14393

 

That's the first official release of server 2016.

 

It comes with .net Framework 4.6.x pre-installed but when trying to install Emby Server it doesn't detect it and tries to download and install it, which doesn't work because you can't install net Framework with the installer on Windows Server.

 

Please optimize the detection of net framework.

 

I looked further into this and here are some information I can give you:

 

The property "DotNet462Full_Release" doesn't exist anywhere.

There is a property called "Release" which has the version number 394802, however the setup.exe seems to check for 394806. There are no updates available at this moment.

 

When running Emby Server from the zip provided on Github it works just fine.

 

If I can help you with any other details please let me know.

 

 

[Luke 42079]

Hi, unfortunately this is all happening by Microsoft components so you might just need to run the portable edition for now. The way the 4.62 bootstrapper works is that it always executes and if the framework is already there it just exits without doing anything. So by preventing it from executing in the first place, that's why you're unable to continue.

[Tackyou 0]

Well then I have a different problem.

The portable version doesn't seem to work with network shares or more specifically Netdrive2.

I had it working before with Emby installed via setup.exe

Maybe it's not caused by the portable version but by an update made to the Emby Server, I read that there was a big update making scanning faster etc.

 

However when I add a network location or local drive mounted via Netdrive2 now it doesn't scan it like the folder would be empty.

I didn't use Emby in some time so maybe this problem was introduced with recent updates.

Edited January 11, 2017 by Tackyou

[Luke 42079]

They will be the same in that regard. Please provide the Emby Server log. You can learn how to do that here:

 

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks.

[Tackyou 0]

I removed all libraries, enabled debug logging and restarted the server.

Then added the movie library and pressed scan button.

Log is attached, can't see any useful information in there.

We can Teamviewer if you want so you can take a look at this odd problem yourself.

 

server-63619765788.txt

[pa3x 1]

Hi,

 

having same problem as Tackyou.

Cannot install from exe. From zip it starts, but no client can connect to server, nor web browser can (yes, i added firewall exceptions on app)

 

Thanks in advace

 

EDIT:

Changed firewall exceptions from app to 8096 port and it worked...

Edited January 12, 2017 by pa3x

[PVTD 37]

Something they teached me before, and it fixed a lot:

 

You should not use mapped network drives, use the UNC path instead, its more reliable and faster. 

Edited January 12, 2017 by PVTD

[Luke 42079]

@@Tackyou did the advice from @@PVTD help? Let us know, thanks !

[Tackyou 0]

@@Luke no, I tried that. I wouldn't post here if I didn't try everything already.

[PVTD 37]

TBH, We have had little to no People who has Windows Server 2016, and I only tried it once, but gave me problems after problems.

If .NET doesn't work as intended, Emby is pretty worthless, I would (if I were you, and this is only my opinion) revert back to a well known Windows instance.

 

I see some other topics where people aren't really satisfied with 2016 (yet, everything needs some polishing at first) as they get problems after errors.

This is only MY opinion, and don't see much more to tell you and help you out. Sorry about that...

I will set up a 2016 test machine soon and try to recreate you problem if possible, but that is in a week or so...

PV

Edited January 16, 2017 by PVTD

[Luke 42079]

Thanks @@PVTD !

[rhodges 49]

I have it up and running on my windows 2016 machine. I don't remember doing anything special to get it working. The only thing I can think of, is maybe I started with a version that didn't require 4.6.2 (or whatever it needs now) and then it upgraded itself to a later version. Maybe trying that would get it "installed"?