MediaMonkey forum

Hi folks,

I tried to install the current beta today, the program doesn't start, not as an update installation over my existing 5.0.4.2690, nor as a portable installation into a separate path and with an empty database.

Are there known problems working with Windows Server 2016?
5.0.4.2690 runs fine.

Maybe the Windows server 2016 feature blocking service that blocks all new exe's by default is the issue?

Right click on the MM .exe select properties, then click unblock at the bottom.

That feature doesnt hurt any other of my Music-Tools, MP3Tag, MP3Diag, etc. ...

To try anyway: Where exactly should I unblock something? I can't find such a function under the file properties.
Thx for the help!

Should look like this: https://imgur.com/b42Yld6

Copying win server 2016 virtual machine from my NAS to my local machine now, willl test it aswell.

Just tested it in win server 2016, and here it does also not start, i do see the Mediamonkey splash screen for a fraction of a second and then closes automaticly.

https://youtu.be/XYfGb8vDPL8

Would suggest making a support ticket for it, and also refer to this topic.

Full debug log from startup:

00000001 0.00000000 [3652] Suspending
00000002 1.60990047 [4332] FTH: (4332): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***
00000003 3.34242892 [4484] FTH: (4484): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***
00000004 3.34857368 [4492] FTH: (4492): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***
00000005 3.47650719 [4524] FTH: (4524): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***
00000006 3.59559441 [4548] FTH: (4548): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***
00000007 3.60348010 [4556] FTH: (4556): *** Fault tolerant heap shim applied to current process. This is usually due to previous crashes. ***
00000008 3.61482000 [4332] ************************************************************************
00000009 3.61491799 [4332] Total process Kernel time: 531.25 ms
00000010 3.61498690 [4332] Total process User time: 265.63 ms
00000011 3.61505127 [4332] Main thread Kernel time: 296.88 ms
00000012 3.61510301 [4332] Main thread User time: 171.88 ms
00000013 3.61518574 [4332] ************************************************************************

On my test system FTH is Disabled, so that cannot generate this error.

CrashMonkey wrote: ↑Mon Jul 08, 2024 2:37 pm Should look like this: https://imgur.com/b42Yld6

Thats some third party software, and not available in an standard installation.

CrashMonkey wrote: ↑Mon Jul 08, 2024 2:55 pm Just tested it in win server 2016, and here it does also not start, i do see the Mediamonkey splash screen for a fraction of a second and then closes automaticly.

same behavior on Server 2019.
Edit: same behavior on Server 2022.
Edit: Ticket #7331 is open.

Andre_H wrote: ↑Tue Jul 09, 2024 12:19 am Thats some third party software, and not available in an standard installation.

Its not third party software, but a microsoft protection feature based on zone indentifiers. Thats why i tought it was turned on because the app did not start.
Here a video i just made with MediaMonkey installers not starting up because of this;
https://youtu.be/vcSdPcG9hdA

Back on topic, i am curious what the devs will say about supporting windows servers.

There is no official support. You are more than welcome to capture a debug log (step 4b) on Windows Server though: https://www.mediamonkey.com/forum/viewtopic.php?t=86643

Lowlander wrote: ↑Wed Jul 10, 2024 1:24 am There is no official support.

That means what? Basically no support at all for Windows Server?

Lowlander wrote: ↑Wed Jul 10, 2024 1:24 am There is no official support. You are more than welcome to capture a debug log (step 4b) on Windows Server though: https://www.mediamonkey.com/forum/viewtopic.php?t=86643

Debug log is already in this topic, it only generated like 12 lines of code.

Hi,
Is it possible that there is Virtual Store folder with MM files? I ask because even FTH is disabled existing entries are followed unfortunately.

Have you tried to install MM Portable in separate folder and cancel Library imports? Also do you have DirectX installed (Some Server installations omits DirectX libraries?

Have you tried any other player app and see if WASAPI playback is Available?

Sorry for so many questions, but I am trying to figure pout what is different of rest of 99% (% is maybe wrong, but we have not received many Win Server users feedback) of MM users.

Peke wrote: ↑Thu Jul 11, 2024 2:17 pm Is it possible that there is Virtual Store folder with MM files? I ask because even FTH is disabled existing entries are followed unfortunately.

Not sure what you mean here. My Windows 2016 Server is a virtual maschine, running on a Windows 2016 HyperV. Beside Mediamonkey, a driver for a virtual soundcard, some tools like MP3Tag no further software.

Peke wrote: ↑Thu Jul 11, 2024 2:17 pm Have you tried to install MM Portable in separate folder and cancel Library imports? Also do you have DirectX installed (Some Server installations omits DirectX libraries?

yes, first i tried a normal update installation over 5.0.4.2690, which fails. the installation goes through without any problems, i just cant start MM2024.

Then an portable; different path, empty DB, no import, no old config files. Same here: installation goes through, but cant start MM2024.

even tried a portable installation on another 2016 and an 2019 without any mediamonkey or mediafiles. same behavior.

i simply cant import anything because MM2024 wont even start. a blink of the splash screens, and thats it.

i tried "run as admin", nope.
i tried compatibly mode for windows 7 / 8 with the mediamonkey.exe, nope.

Peke wrote: ↑Thu Jul 11, 2024 2:17 pm Have you tried any other player app and see if WASAPI playback is Available?

MM 5.0.4.2690 is running on the maschine, without problems. so, yes.

Peke wrote: ↑Thu Jul 11, 2024 2:17 pm Sorry for so many questions, but I am trying to figure pout what is different of rest of 99% (% is maybe wrong, but we have not received many Win Server users feedback) of MM users.

No reason to apologize, I'm also interested in a solution.

wasn't the debug.log i send any helpful?

Thanks for all the info. Tracking at https://www.ventismedia.com/mantis/view.php?id=21077

-Rusty

Hi,

Andre_H wrote: ↑Fri Jul 12, 2024 2:57 am wasn't the debug.log i send any helpful?

Partially, as I amd investigating this further (Win 10 not Win Server 2016) I stumbled on various articles explaining how to remove specific app from FTH without Disabling it overall.

I identified this by finding that Windows created 2 registry keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\FTH\State]
“Path\\to\\app.exe”=hex:0E,00,00,00,10,00,00,00,18,……
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
“Path\\to\\app.exe”=”FaultTolerantHeap”

Deleting those two entries removed APP from FTH and after restart app started normally.

Also when I set this registry value to 0: HKEY_LOCAL_MACHINE\Software\Microsoft\FTH\Enabled which disabled FTH for the whole system.

Also some suggested renaming eg. MediaMonkey.exe -> 1MediaMonkey.exe and trying to start it.