<p>There's not really any type of window during our release that would cause an issue like this. The update is a just a single package fire that is either available or not. &nbsp;The activity in GitHub is caused by us merging the latest update's changes into our 'master' branch which then automaticaly closes all the issues that were tagged as being fixed in that release ( we do this after the update has been released ).</p>

<p>As for the message your seeing... That is because there is an app_offline.htm at the root of your Rock install directory that contains that message. If your webserver (IIS) sees this file at the root, it will display the contents of that file for every request instead of the webpage that was requested. The update put that file there for other users accessing your site during the update. The update does the following...</p>

<ol>
	<li>Create the app_offline.htm file</li>
	<li>Unzip all the updated files and copy them to web server ( as it's copying the files, it also does some processing for special files ( i.e. to delete any old files, or update the web.config as neccessary &nbsp;)</li>
	<li>Delete the app_offline.htm file</li>
</ol>

<p>The update allow up to 15 minutes for the copying/updating of files due to this often taking a considerable amount of time (i.e. file temporarily in use, etc). After 15 minutes, if it's not done, it would report an error, and still delete the app_offline.htm file.&nbsp;</p>

<p>I would suggest manually deleting the app_offline.htm file. Then try to run Rock again. If it runs, check the version number (using the Information button in the admin toolbar at bottom). Then also go to the Rock update page and check to see if update still needs to be installed. If it does, try to update again. Your site is currently in one of three possible states...</p>

<ol>
	<li>None of the new files got copied to server. In this case, Rock will run normally, but it will still be the previous version, and you will be able to run the update again (but allow up to 15 minutes for it to complete )<span style="line-height: 20.7999992370605px;">.</span></li>
	<li><span style="line-height: 20.7999992370605px;">All the files got copied over. If this is the case, when you restart rock, it may take a minute to start as it will be running all the database migrations to update the database to be consistent with new files.</span></li>
	<li><span style="line-height: 1.6em;">&nbsp;Some of the new files got copied over ( this would be the least attractive option ). When you run rock, you may or may not get exceptions due to file incompatibilities. If Rock runs, I would check your version, and if neccessary try the update again. If it doesn't run, next question would be if you have a backup of the file system?</span></li>
</ol>

<p>Hope that helps.</p>

<p>Is the page where you initiated the update still processing? &nbsp;This probably means the update isn't complete and needs more time before the site can be loaded.</p>

<p>Ahh man. So I just happened to hit them at a weird time. Okay, is there a way for me to update outside of the GUI? Because as of now it seems as though I can't access the backend of the site.</p>

<p>We have not restarted the system. We host with Winhost. Do you mean reboot the server?</p>

<p>Thank you guys for all the help! I deleted the app_offline.htm file which then allowed me to reload the page and update the Rock RMS to 3.1.</p>

<p>&nbsp;</p>

<p>&nbsp;</p>