Oxide extension throwing error even on freshNot An Issue
bran

I see I am not the only one thankfully. I'm having the same issue on a test server. Tried a clean install, same issue. Not using staging branch.

BadImageFormatException: Could not resolve field token 0x040047d6, due to: Could not load file or assembly 'ApexShared, Version=*.*.*.*, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:ApexShared, Version=*.*.*.*, Culture=neutral, PublicKeyToken=null type:<unknown type> member:(null) signature:<none> assembly:D:\Servers\branservers\GameServers\TC78746565410862016023573\RustDedicated_Data\Managed\Assembly-CSharp.dll type:AiManager member:(null) signature:<none>
at PrefabPreProcess.ProcessObject (System.String name, UnityEngine.GameObject go, System.Boolean resetLocalTransform) [0x001bc] in <9357151e9e52423d80616f588927d318>:0
at PrefabPreProcess.Process (System.String name, UnityEngine.GameObject go) [0x0003a] in <9357151e9e52423d80616f588927d318>:0
at GameManager.FindPrefab (System.String strPrefab) [0x0002a] in <9357151e9e52423d80616f588927d318>:0
at FileSystem_Warmup.PrefabWarmup (System.String path) [0x00000] in <9357151e9e52423d80616f588927d318>:0
at FileSystem_Warmup+<Run>d__4.MoveNext () [0x00100] in <9357151e9e52423d80616f588927d318>:0
at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00026] in <c8dc2b468d1841099baa4dd8a110cc44>:0

(Filename: <9357151e9e52423d80616f588927d318> Line: 0)​


Merged post

Update: Tested on another machine and Oxide installed/started fine. I installed the Rust server + Oxide the exact same way on both the test and the 2nd machine.

I copied the 'RustDedicated_Data\Managed' folder from the working machine to the non-working test server and Oxide works after overwriting the Managed folder files.

I did run Rust update each time, maybe something changed with Rust Windows Server?

This fixed it! I spun up a server on a different machine and copy/pasted the Managed folder into my main server's folder and it is now working properly. Thank you for your help Wulf and bran!

Found the issue for anyone who experiences this in the future, it was in my SteamCMD command line, I had "validate" instead of "-validate".

bran

Found the issue for anyone who experiences this in the future, it was in my SteamCMD command line, I had "validate" instead of "-validate".

-validate doesn't exist with Steam CMD, just "validate" would be correct. The above issue is caused by mismatched DLLs; i.e. using older Oxide builds on newer Rust version and therefore mixing Rust versions.
app_update <app_id> [-beta <betaname>] [-betapassword <password>] [validate]​

See SteamCMD - Valve Developer Community (valvesoftware.com)
Locked automatically