Update to 6928 - Sandbox fails to Start Server


#21

6940 Sandbox
I have set the regedit under 2012 new, but the thing is the sandbox don t Crash, they still hang so I don t get here a result like hoped too.
https://keybase.pub/sbin/log.txt
btw CrashDumps Folder are enable by default since win 10 again.

Info only links for People how like to know to enable the CrashDumps Folder.
I have know it without Google not-)
https://msdn.microsoft.com/de-de/library/windows/desktop/bb787181(v=vs.85).aspx


#22

#23

Same problem here with 6940.
Everything is fine with sandbox on local machine, but can’t start it on remote server: actually it runs, but doesn’t start (the try icon is stuck to the loading icon - the one with the orange circle in the bottom right).

Local machine (working): Windows 10 64bit;
Remote server (not working): Winows Server 2012 R2 64bit.


#24

Seem to have the same problem. No Interface on the machine, just Sandbox. Setting port manually.


#25

It s near the same on a fresh win 2016 with the 6946 Release https://keybase.pub/sbin/6946log.txt


#26

6946 is broken too. Any idea when this will be fixed or should I re-purpose the server for something else?


#27

This may be a long shot but could you try installing https://go.microsoft.com/fwlink/?LinkId=746572? (it’s the last download on this page: https://www.visualstudio.com/downloads/)? This would remove the doubt that something is wrong with VC++ libraries.


#28

Ok ty, sure look s a bit better now but I stuck again (https://keybase.pub/sbin/6946-2log.txt )

neu https://keybase.pub/sbin/6946-3log.txt
https://keybase.pub/sbin/visual.JPG


#29

@marko8904, I installed vc_redist.x64.exe from the link you provided, installed the previously failing 6940 Sandbox again, and this time it starts up automatically after launch fine, and I can visit my domain region from the Interface on my other system.

I updated both the Interface on one system and the Sandbox on the other to the latest 6946 and all seems to work.


#30

The backup instructions on the system tray icon menu though are wrong. There is no directory with the indicated folder name…

C:\Users…\AppData\Roaming\High Fidelity\Server Backup

The model backups are I believe (for me) in this folder… is that right?

C:\Users…\AppData\Roaming\High Fidelity\assignment-client

Does the restore backup message need changing in the popup that appears from the tray icon?


#31

Seems to work. Now running version 6954.


#32

Sandox
I have try out that Version too without success https://keybase.pub/sbin/6954log.txt


#33

I installed the Sandbox only (Windows 6946) on a completely new system, and it also did not start the server automatically after installing and downloading the new Home contents. Manually trying to start the server from the system tray icon also has no effect.

I installed vc_redist.x64.exe and rebooted but it still does not appear to start the server.

As before Logs tabs in pop up window are empty, and log directory files are being created but are 0KB and empty.


#34

Hi @Ai_Austin or anyone else having an issue with the server not starting. Here is a potential fix, could you try and install this and confirm the server starts? : https://github.com/highfidelity/hifi/pull/11108#issuecomment-320032875 direct link to the exe: https://deployment.highfidelity.com/jobs/pr-build/label%3Dwindows/2231/HighFidelity-Beta-PR11108-4756d4af66a44bd194188c1c038b816d822baf6a.exe


#35

Hello, I m just unsure while I can start the exe on my Desktop Win 10
There the Viewer is working.

On the Win 2016 the exe doesn t start.
Here should run the Sandbox.

Protokollname: Application
Quelle: Microsoft-Windows-Immersive-Shell
Datum: 03.08.2017 21:01:42
Ereignis-ID: 5973
Aufgabenkategorie:(5973)
Ebene: Fehler
Schlüsselwörter:
Benutzer: H2419624\Administrator
Computer: h2419624
Beschreibung:
Bei der Aktivierung der App „Microsoft.Windows.Apprep.ChxApp_cw5n1h2txyewy:App.AppXc99k5qnnsvxj5szemm7fp3g7y08we5vm.mca“ ist folgender Fehler aufgetreten: Diese App kann vom integrierten Administratorkonto nicht aktiviert werden… Weitere Informationen finden Sie im Protokoll „Microsoft-Windows-TWinUI/Betriebsbereit“.
Ereignis-XML:



5973
0
2
5973
0
0x2000000000000000

1492


Application
h2419624



Microsoft.Windows.Apprep.ChxApp_cw5n1h2txyewy:App.AppXc99k5qnnsvxj5szemm7fp3g7y08we5vm.mca
-2144927149


#36

@chris… I installed initially the Sandbox in the custom install of High Fidelity - PR11108, that’s made no difference. The server does not start and cannot be started from the system tray menu. As before the log tabs are empty. Even though this machine only is intended to have the Sandbox on it, no Interface, as a further test I uninstalled that and did a FULL express install of the Interface and Sandbox from the installer link. That also does not allow the Sandbox to start.

This (clean install) test machine has aleady had vc_redist.x64.exe installed and that made no difference, but for some reason doing that on my previous (main) host made it work.

Winver on BOTH systems is Windows 10 Pro 1703. Firewall ports are all set fine, and have been throughout.


#37

@Chris… I went back and installed the last working version I had on my original host/Sandbox setup which was HighFidelity-Beta-6896.exe.

That installed on my new machine just a Sandbox (no Interface) starts fine after installing. I can access it from the Interface fine too (even with the latest versions as its not (yet) indicating its incompatible.

So something has broken the installation process after HighFidelity-Beta-6896.exe (and before HighFidelity-Beta-6928.exe which was the next version I tried and that started to show the issue for me).


#38

@Ai_Austin, could you install Dependency Walker (http://www.dependencywalker.com/) and load domain-server.exe in it (domain-server.exe lives in your High Fidelity installation folder)? This should be domain-server.exe from a build that can’t run Sandbox on your system. You could then save the output of it to a dwi file and PM it either to me or @b. This will give us an idea as to what may be missing. Thanks!


#39

@marko8904 and @b … I was getting the .dwi logs for you off the system that was failing but began working (Arran) using 6946 , and the system that was working on 6896 and failing on e.g. 6946 (Shuna) but now (unfortunately for the purpose of finding the cause !! ) Shuna also has started working on 6946. I am not sure what the change is as I had installed vc_redist.x64.exe on Shuna and rebooted before and that did not clear the issue. But for some reason now that I cannot explain 6946 is also working on Shuna, much like it did on Arran.

One change to the system is that I had installed and then uninstalled HighFidelity-Beta-PR11108 and even though that also did not work on Shuna that MAY have left some changes.

Anyway… in case they are useful I placed the .dwi log files for Arran (6946) and Shuna (6396 and 6496) in a temporary location at http://www.aiai.ed.ac.uk/~ai/EXPORT/TEMP/HiFi/

Dependency Walker did show some errors while running. but these were for all versions, i.e. the working versions as well. But it may be worth eyeballing those.

Let me know when you have those files and I will remove them.


#40

Getting the same problem with 6946. Works fine on my Win 10 system, but won’t start on my Server 2K R2 system. Logs empty. I thought it was security settings on the W2012 machine, but it looks like it’s something else based on this. Watching.