12 April 2018
- Last edited 12 April 2018
thanks for the quick reply!
I was indeed using a custom user with granted admin rights. The folders have full permissions for the user thats installs and for network service.
just did wipe it again( 4th time ) and started from scratch. it installs just fine, i can create the first ads instance just fine. however it starts to go wrong when launching this first instance. ( which i installed as a service aswell )
it will not even display the "running" checkbox filled when its been started thru the app. there is also no way to stop it cause the app doesnt recogonise it as "running" -.-
the webinterface looks fine after first login, ADS instance is displayed as green. however when i spawn a new minecraft instance for example from the app ( not thru the webinterface ) it will not even show up on the webinterface, not even after a relog.
do i have to fire those instances up thru services or will a right click+ start instance as the installing user do?
*edit after starting and stopping both instances from services, the minecraft one atleast shows up no under "local instances" but is red no matter if started or not. also trying to start it from the webinterface will do sweet fck all, not even getting an "starting instance" popup.
there is ZERO errors in the log files as far as i can see. there is a .net error in the event log however i think i caused that when i forcefully closed it last night on a previous attempt before rage quitting.
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.Sockets.SocketException
at System.Net.Sockets.Socket.DoBind(System.Net.EndPoint, System.Net.SocketAddress)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
edit2* nvm found this in the log
You cannot start instances you do not own as a non-root user. You are *machinename*$ and this instance belongs to *username*.
( changed usrname and machinename )
any more good ideas for me before i trash this rig?