Afternoon All, 

I'm trying to get a new server up and running and i'm having issues. I currently run this on esxi 6.7 using windows 10 as the OS. I'm getting alot of errors when attempting to get it to run.

C:\Users\Rust\Desktop>echo off
Redirecting stderr to 'C:\steamcmd\logs\stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...OK
Success! App '258550' already up to date.
Mono path[0] = 'C:/rustserver/RustDedicated_Data/Managed'
Mono config path = 'C:/rustserver/MonoBleedingEdge/etc'
Initialize engine version: 2018.3.3f1 (393bae82dbb8)
Forcing GfxDevice: Null
GfxDevice: creating device client; threaded=0
NullGfxDevice:
    Version:  NULL 1.0 [1.0]
    Renderer: Null Device
    Vendor:   Unity Technologies
FMOD initialized on nosound output
Begin MonoManager ReloadAssembly
- Completed reload, in  2.292 seconds
WARNING: Shader Unsupported: 'Hidden/Internal-ScreenSpaceShadows' - Pass '' has no vertex shader
WARNING: Shader Unsupported: 'Hidden/Internal-ScreenSpaceShadows' - Pass '' has no vertex shader
WARNING: Shader Unsupported: 'Hidden/TerrainEngine/Splatmap/Diffuse-AddPass' - Pass 'Meta' has no vertex shader
WARNING: Shader Unsupported: 'Hidden/TerrainEngine/Splatmap/Diffuse-AddPass' - Pass 'Meta' has no vertex shader
UnloadTime: 10.333600 ms
3D Noise requires higher shader capabilities (Shader Model 3.5 / OpenGL ES 3.0), which are not available on the current platform: graphicsShaderLevel (current/required) = 30 / 35

(Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)

Bootstrap Startup
System
        Name: 
        OS:   Windows 10  (10.0.0) 64bit

CPU
        Model:  Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
        Cores:  2
        Memory: 12286 MB

GPU
        Model:  Null Device
        API:    NULL 1.0 [1.0]
        Memory: 128 MB
        SM:     30

Process
        Memory:   79 MB

Mono
        Collects: 16
        Memory:   1 MB



Unable to open archive file: Bundles/Bundles

(Filename:  Line: 587)

Couldn't load root AssetBundle - Bundles/Bundles

(Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)

ThrowError: Couldn't load root AssetBundle - Bundles/Bundles

(Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename:  Line: 388)

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

(Filename:  Line: 390)

​

If your server is running fine then your good. All those erros are from engine and can be ignored. If your server is not starting post your .bat file the one you use to start the server.

Blocks my attempt to pste the command

https://pastebin.com/JkDd96ED

Your suppose to use two different bat file but you put the same “command” in the same bat file.

in your code that you paste.
from “echo till line 4 “quit” it should be in in different bat file. Usually the call it update.

then make another bat file and paste the rest till the end. Usually they call it start.

then you will have two different bat file one called update and one called start.

start - starts the server.
update- updates your server when there is an update. 

interesting, I usually have both ion the same file. i'll try your way

I think your file directory is wrong for the update.bat try C instead of c. Make sure when you run the update.bat it will create new files 

update is working properly. unable to connect via local lan using IP and port. firewall is off for testing purposes.

have you done port forwarding ?

Yes, the port forwarding is done.

have you tried pressing f1 client.connect localhost:28015 ?

Yes, I have tried and it fails... It has to be something with my batch file.. if i just click on restdedicated.exe it starts up