When I start the new server, it pops up two copies of SteamCMD. Anyone know if this is supposed to happen? If it’s not supposed to happen, any clues as to why it’s launching two?
It doesn’t seem to be causing any trouble, but if it’s not supposed to, then I would like to prevent it.
Minor update. It IS actually trying to launch it twice. I just noticed there was a popup hidden behind the server app. It was warning that the server is already running and that it will close the app. (The second copy that is)
Another update. Today when it reset the server, it wasn’t coming up. I checked the computer and the popup was sitting there. When I closed the popup, it launched the server. So, this is starting to be a problem.
Anyone at all having this issue? I’m still having problems and it is stopping the automatic restart of the server from completing.
You should ask on the thread I think, you’ll get an answer. Know it is weekend 
As that thread is for .16, and I’m using .15 it would be thread hijacking. While I would probably get an answer more quickly, I prefer to abide by standard forum etiquette. Thanks though. =)
As it stands I’ve gone back to manually resetting the server so I know it’s up and running. Not ideal, but this way there is less chance my players will be without a server while I’m sleeping lol
@Sierrebrarc It’s not a .16 thread, it’s the “official thread” that happens to be updated to match the latest changes (in this case the 1.0.16).
Now regarding your problem, I need to actually understand what happens 
Ok, so you already had the Dedicated Server Launcher 1.0.15 running, and you started another one, which told you that there was already one running and when clicking OK closed.
That’s the expected behavior, except the part about being hidden behind this was not supposed to happen, so I guess it’s a bug I need to check.
What are “it” and “it” in the sentence?
Are you using the auto starting preference menu option to start the launcher?
What would help is if you could describe your setup, because normally if you want your server to auto-restart, all you need to do is to let the Dedicated Server Launcher running and it will take care of that for you: This feature is not supposed to work with the launcher app being stopped and restarted.
1 Like
Thanks for the info about the thread, I’ll check into it shortly.
Here is what happens. The server is running, at 6 am it restarts (using the automated system) and launches 1-2 coppies of the steamcmd. The CMD window(s) closes, and I get the warning popup.
(Alternately, say the PC has been running for several days, and I decide to reboot the whole system. So now I’m starting the computer, launching the app, clicking the switch to start the server, and it does the same thing.)
As a partial fix, I turned off the auto restart and manually reset my server for now so that I can just go ahead and OK it and no one is left wondering what’s going on. Also, the only thing that “was” automated was the reset. The rest of the stuff is off until I know everything else is running right.
As it happens, I’m having another issue today, and I’m working on it as we speak. So while I was checking into what’s going on, I thought… wait… Is it running as admin? It wasn’t. I ran it as admin, and it didn’t give me the error popup. I can’t explain that one, but if it fixes the problem, I’m happy.
Now I just need to find out why it’s crashing over and over My IT guy says the SteamCDM error is typical with a java update issue. Sussing that out now.
It just ran two CMD’s again, while it was run as admin.
Blockquote
[2018.10.04-20.40.31:808][ 0]LogWindows:Error: Fatal error: [File:C:\p4\Engine\4.15-dw-StableBranch\Engine\Source\Runtime\CoreUObject\Private\Serialization\AsyncLoading.cpp] [Line: 3400]
[2018.10.04-20.40.31:808][ 0]LogWindows:Error: Could not find SuperStruct InteractableMenu to create InteractableMenu
[2018.10.04-20.40.31:808][ 0]LogWindows:Error:
[2018.10.04-20.40.31:808][ 0]LogWindows:Error:
[2018.10.04-20.40.31:808][ 0]LogWindows:Error: !0x0000000000000000
[2018.10.04-20.40.31:808][ 0]LogWindows:Error:
[2018.10.04-20.40.31:808][ 0]LogWindows:Error: Crash in runnable thread FAsyncLoadingThread
[2018.10.04-20.40.31:817][ 0]LogExit: Executing StaticShutdownAfterError
I think I’m going to make a copy of the save files, and the config files. Delete everything else related to the server, and reinstall the server. I might uninstall steam too. A fresh start might do me good.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.