Octopus Deploy not coming online after moving home location

http://docs.octopusdeploy.com/display/OD/Move+the+Octopus+Home+folder+and+the+Tentacle+Home+and+Application+folders

Getting below error.
System.NullReferenceException: Object reference not set to an instance of an object.
at Octopus.Tools.OctopusConfiguration.OctopusManagerModel.Reload(ApplicationInstanceRecord applicationInstance) in y:\work\refs\heads\master\source\Octopus.Tools\OctopusConfiguration\OctopusManagerModel.cs:line 173
at Octopus.Tools.OctopusConfiguration.OctopusManagerView.b__0() in y:\work\refs\heads\master\source\Octopus.Tools\OctopusConfiguration\OctopusManagerView.xaml.cs:line 107
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

This is the list of steps i followed from the mentioned link,
$oldHome = “C:\Octopus”
$newHome = “D:\Octopus”
$octopus = “C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe”
$newConfig = $newHome + “\OctopusServer.config”
& “$octopus” service --stop
mv $oldHome $newHome

&"$octopus" delete-instance --instance=OctopusServer
&"$octopus" create-instance --instance=OctopusServer --config=$newConfig

& “$octopus” configure --home="$newHome"
& “$octopus” service --start

Hi Jabraham,
What version of Octopus deploy are you using and are you moving the default instance or is it a named instance?
Just to confirm, it sounds like the files have moved successfully, the old service stopped, removed and the new one added (double check the path of the .exe that the service points to) and the new one starts successfully?
The error looks like its coming from the Manager tool so I’m curious to know if the service itself is able to start manually, indipendant of the Manager UI.
Thanks,
Robert

The service started. But i am not able to hit the website either. Version is Octopus.2.6.5.1010-x64.msi

I spun up a new instance and restored the backup from yesterday. Is there a way to restore the Packages from the old server also?

Hi Jabraham,
I have just downloaded and tested moving a server from C:\ to D:\ using Octopus.2.6.5.1010-x64.msi without any problems. Are there any further details in the windows event logs? Does the service appear to start for a while then crash? Are there any further octopus server logs generated?
Could you perhaps just make sure that the .config file path used during this script is pointed correctly at the new location.

Unfortunately as of 2.6 there is no simple way to restore all packages stored in the internal NuGet repository without some scripts to hit the API directly to automate the upload process. Our latest versions however support the ability to be able to copy your packages to the right directory and then allow the server to rescan the directory on startup.
Robert

Thanks for that update…

This is one of the error i saw in the Event Viewer.

Faulting application name: Octopus.Server.exe, version: 2.6.5.1010, time stamp: 0x551cc357
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
Exception code: 0xe0434352
Fault offset: 0x0000000000008b9c
Faulting process id: 0xe68
Faulting application start time: 0x01d107a5ab757a9d
Faulting application path: C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: ecd48bf0-7398-11e5-80ef-0e0d21bf2da5
Faulting package full name:
Faulting package-relative application ID:

Here is another one next to the previous one.

Application: Octopus.Server.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
Stack:
at Octopus.Shared.Startup.WindowsServiceAdapter.RunService()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

Hi Jabraham,
I am so far unable to reproduce your error. Have you confirmed that there is no permissions issue regarding the directory/config in the new drive location. Could you try access these files using the user credentials that the Windows Service runs under?
As 2.6.5.1010 is an older version of Octopus Deploy that we no longer support, is it possible for you to upgrade to one of the later 3.x builds? This includes quite a few new features and many pieces have been largely rebuilt.
Cheers
Robert

I will check into that. Thanks for checking.