Import error from 1.6 to 2.1.3

Legacy Uncategorised
1

Hi we are getting an error whle importing our 1.6 backup to 2.1.3.
Has anyone faced that problem before?

A fatal exception occurred
System.ArgumentNullException: Value cannot be null.
Parameter name: source
at System.Linq.Enumerable.Any[TSource](IEnumerable1 source, Func2 predicate)
at Octopus.Platform.Util.PathSegmentValidator.IsValid(String name) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Platform\Util\PathSegmentValidator.cs:line 20
at CallSite.Target(Closure , CallSite , Type , Object )
at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
at Octopus.Server.Legacy.LegacyOctopusImporter.b__1a9(Document projectDocument) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Legacy\LegacyOctopusImporter.cs:line 1073
at Octopus.Server.Legacy.LegacyOctopusImporter.<>c__DisplayClass1ad.b__1ab(List1 documents) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Legacy\LegacyOctopusImporter.cs:line 1112 at Octopus.Server.Legacy.LegacyOctopusImporter.LoadAll(String prefix, Action1 paginator) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Legacy\LegacyOctopusImporter.cs:line 950
at Octopus.Server.Legacy.LegacyOctopusImporter.ValidateUniqueNames(String descr, String prefix, Func2 onItem) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Legacy\LegacyOctopusImporter.cs:line 1116 at Octopus.Server.Legacy.LegacyOctopusImporter.MakeSureEverythingIsReadyToBeMigrated() in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Legacy\LegacyOctopusImporter.cs:line 1061 at Octopus.Server.Legacy.LegacyOctopusImporter.ImportFromBackup(String ravenDbBackupFilePath, Nullable1 tentaclePort, String upnSuffix) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Legacy\LegacyOctopusImporter.cs:line 90
at Octopus.Server.Commands.MigrateCommand.Start() in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Commands\MigrateCommand.cs:line 116
at Octopus.Shared.Startup.ConsoleHost.Run(Action`1 start, Action shutdown) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Shared\Startup\ConsoleHost.cs:line 36

Error: The previous command returned a non-zero exit code of: 1
Error: The command that failed was: “C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe” migrate --instance=“OctopusServer” --no-prompt --backup=“C:\Octopus\Data\Backups\20140303-080024.octobak”

2

Thanks Jan, we have this bug noted down and it will be fixed in 2.3:

For now, you can go to RavenDB directly, find the ServerTask document for the currently running backup, and change the state to Failed manually. If you need help doing this please let me know.

Paul

3

Hi Paul,
We tried the suggested workaround. What did you expect to happen, when we change the task state to “Failed”? Should we try the import again (which we did, but the same exception occured) or what?

We also tried to migrate to version 2.0.x, but then we had a very early exception that the document “user-roles” could not be migrated.

Best regards

4

Hi Yannik,

Sorry for the delay, we’ve released a new version of Octopus here which should resolve the issue:

Paul