Hello,
We are currently trying to do a side-by-side migration from 1.6 to 2.0.
When running the import wizard we receive the following error.
A fatal exception occurred
System.InvalidOperationException: The maximum number of requests (30) allowed for this session has been reached.
Raven limits the number of remote calls that a session is allowed to make as an early warning system. Sessions are expected to be short lived, and
Raven provides facilities like Load(string[] keys) to load multiple documents at once and batch saves (call SaveChanges() only once).
You can increase the limit by setting DocumentConvention.MaxNumberOfRequestsPerSession or MaxNumberOfRequestsPerSession, but it is
advisable that you’ll look into reducing the number of remote calls first, since that will speed up your application significantly and result in a
more responsive application.
at Raven.Client.Document.InMemoryDocumentSessionOperations.IncrementRequestCount() in c:\Builds\RavenDB-Stable\Raven.Client.Lightweight\Document\InMemoryDocumentSessionOperations.cs:line 324
at Raven.Client.Document.DocumentSession.LoadInternal[T](String[] ids, KeyValuePair2[] includes) in c:\Builds\RavenDB-Stable\Raven.Client.Lightweight\Document\DocumentSession.cs:line 366 at Raven.Client.Document.MultiLoaderWithInclude1.Load[TResult](String id) in c:\Builds\RavenDB-Stable\Raven.Client.Lightweight\Document\MultiLoaderWithInclude.cs:line 182
at Raven.Client.UniqueConstraints.UniqueConstraintExtensions.LoadByUniqueConstraint[T](IDocumentSession session, Expression1 keySelector, Object value) in c:\Builds\RavenDB-Stable\Bundles\Raven.Client.UniqueConstraints\UniqueConstraintExtensions.cs:line 31 at Octopus.Server.Legacy.LegacyOctopusImporter.<>c__DisplayClass1461.b__145(List1 batch) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Legacy\LegacyOctopusImporter.cs:line 785 at Octopus.Server.Legacy.LegacyOctopusImporter.LoadAll(String prefix, Action1 paginator) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Legacy\LegacyOctopusImporter.cs:line 864
at Octopus.Server.Legacy.LegacyOctopusImporter.DoTheMigration(Nullable1 tentaclePort) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Legacy\LegacyOctopusImporter.cs:line 272 at Octopus.Server.Legacy.LegacyOctopusImporter.ImportFromBackup(String ravenDbBackupFilePath, Nullable1 tentaclePort) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Legacy\LegacyOctopusImporter.cs:line 89
at Octopus.Server.Commands.MigrateCommand.Start() in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Commands\MigrateCommand.cs:line 87
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: 100
Error: The command that failed was: “C:\Program Files (x86)\Octopus 2.0\Server\Octopus.Server.exe” migrate --instance “OctopusServer” --no-prompt --backup “\OldServerName\d$\OctopusBackups\20131220-145928.octobak” --tentacle-port “10934”
We also receive the same error if we copy the backup file locally.