Server Not Updating to Build 237

whocareswhowhocareswho Join Date: 2012-07-13 Member: 154104Members
in Server Discussion
Hello, I was able to update to Build 236 last night, but have been unable to update to version 237 today. I've posted my command file and the errors it is receiving while trying to update to see if anyone can make sense of it.

<a href="http://postimage.org/" target="_blank"><img src="http://s13.postimage.org/dsw72l16f/Issue.png" border="0" class="linked-image" /></a>
<a href="http://postimage.org/" target="_blank">free image hosting</a>
Off Topic Disagree Agree Awesome

Comments

  • krazekraze Join Date: 2012-10-26 Member: 163744Members
    What happens when you open SteamCMD normally and type in the commands by hand?
    Off Topic Disagree Agree Awesome
  • whocareswhowhocareswho Join Date: 2012-07-13 Member: 154104Members
    Does the same thing.
    Off Topic Disagree Agree Awesome
  • krazekraze Join Date: 2012-10-26 Member: 163744Members
    Unless you edited it out are you adding "verify" to the end of app_update 4940?
    Off Topic Disagree Agree Awesome
  • oldassgamersoldassgamers Join Date: 2011-02-02 Member: 80033Members, Squad Five Blue, Reinforced - Shadow
    edited January 2013
    I was thinkin on the same thing kraze. :)

    whocareswho, you must validate after the command. Write this --> app_update 4940 validate.

    So lets start from the beginning:
    1. Start up the program called <b>steamcmd.exe</b>
    2. <b><u>Type:</u></b> Login -<b>your account</b>- and -<b>your password</b>- <i>(example: login blabla 1234)</i>
    3. <i><b>Type:</b></i> force_install_dir -your directory where you want to install your server in-
    4. <i><b>Type:</b></i> app_update 4940 validate
    Off Topic Disagree Agree Awesome
  • strikerx22strikerx22 Join Date: 2013-01-17 Member: 180178Members
    For everyone having issues with build 237 I have found the issue and the solution.

    When doing the app_update 4940 you will have issues. It looks like 4940 is for a SteamCMD app-update for users who are running servers with Steam credentials that do not own NS2. What you have to do to work around this is use the login credentials of a NS2-enabled account and do an app_update 4920. This will update to the correct build and will fix your issues.

    Thanks!
    Off Topic Disagree Agree Awesome
  • WhosatWhosat Singapore Join Date: 2006-11-03 Member: 58301Members, Reinforced - Shadow
    Aye mate, your picture is incredibly small. strikerx22's solution poses a security problem if you are using a script to run the updates and server as you are exposing your paid steam account's username and password in plain text.

    4940 should work as it has for many server providers.
    Off Topic Disagree Agree Awesome
  • SeeVeeSeeVee Join Date: 2012-10-31 Member: 165206Members
    <!--quoteo(post=2062168:date=Jan 17 2013, 01:59 PM:name=strikerx22)--><div class='quotetop'>QUOTE (strikerx22 @ Jan 17 2013, 01:59 PM) <a href="index.php?act=findpost&pid=2062168"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->For everyone having issues with build 237 I have found the issue and the solution.

    When doing the app_update 4940 you will have issues. It looks like 4940 is for a SteamCMD app-update for users who are running servers with Steam credentials that do not own NS2. What you have to do to work around this is use the login credentials of a NS2-enabled account and do an app_update 4920. This will update to the correct build and will fix your issues.

    Thanks!<!--QuoteEnd--></div><!--QuoteEEnd-->


    I made a separate account for steam just to update my server software and it always updates no problem. I do not use my steam account credentials that I purchase games with. Worse case scenario on the server not updating, I'd delete the server install directory and re-install it fresh from steamcmd.

    Just back up any configs you want to keep and put them in the newly DL server.

    "When in doubt, wipe it out"
    Off Topic Disagree Agree Awesome
  • strikerx22strikerx22 Join Date: 2013-01-17 Member: 180178Members
    My updates have been working fine on all other builds as well which is why I prefaced it with the fact that this is a Build 237 solution only. The only reason that I changed the app number is because I realized that they were different and it would make sense for UWE to have a second one that does not require a paid account to allow server owners to update.
    Off Topic Disagree Agree Awesome
Sign In or Register to comment.