Databases
StackOverflow2013
Postsdbo
PORavendb database export/import issue in versioning
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORavendb database export/import issue in versioning
    primarykey
    data
    text
    <p>We are using RavenDB 2.0 and bundle 2330. </p> <p>We have a problem in export/import of versioned documents. We did the following.</p> <ul> <li>We had a database with versioning bundle enabled</li> <li>We had a number of records with multiple versions</li> <li>exported the database to a dump file using Raven-Studio</li> <li>Tried importing the same in another server with versioning bundle</li> <li>But the server refused to import the documents and gave error as follows and stopped Import</li> </ul> <blockquote> <p>Server sent: at Raven.Studio.Infrastructure.InvocationExtensions.Catch(Task parent, Func<code>2 func) at Raven.Studio.Infrastructure.InvocationExtensions.Catch(Task parent, Action</code>1 action) at Raven.Studio.Commands.ImportDatabaseCommand.&lt;>c_<em>DisplayClass8.b</em>_1() at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute() at System.Threading.Tasks.Task.ExecutionContextCallback(Object obj) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task&amp; currentTaskSlot) at System.Threading.Tasks.Task.ExecuteEntry(Boolean bPreventDoubleExecution) at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()</p> <p>Client side exception: System.Net.WebException: [HttpWebRequest_WebException_RemoteServer] Arguments: NotFound Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See <a href="http://go.microsoft.com/fwlink/?linkid=106663&amp;Version=5.1.20513.0&amp;File=System.Windows.dll&amp;Key=HttpWebRequest_WebException_RemoteServer" rel="nofollow">http://go.microsoft.com/fwlink/?linkid=106663&amp;Version=5.1.20513.0&amp;File=System.Windows.dll&amp;Key=HttpWebRequest_WebException_RemoteServer</a> at System.Net.Browser.ClientHttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Func<code>2.Invoke(T arg) at System.Threading.Tasks.TaskFactory</code>1.FromAsyncCoreLogic(IAsyncResult iar, Func<code>2 endFunction, Action</code>1 endAction, Task`1 promise)</p> </blockquote> <ul> <li>So we removed the versioning bundle and then imported and then applied the versioning bundle.</li> <li>The import was successful. But all the versions of the documents are being treated as separate documents and not as different version</li> </ul> <p>We are on our alpha stage and suddenly recovering such issues in RavenDB. Any ideas please?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMuthu
    1. USMuthu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORavendb database export/import issue in versioning
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload