Closed bcrobinson closed 5 years ago
I have the same problem with 1.8.2 but the problem does not exist in 1.8.1 (just run both versions)
I'm having the exact same problem with 1.8.2. I ran 1.8.1, as ngeor-sendasyou suggested, and it ran successfully.
I apparently have two different "versions" of 1.8.2. One of them does not work and gets the above error message, while the earlier 1.8.2 version works. A colleague downloaded 1.8.2 about a week before I did; the earlier download is the one that worked.
The only difference in the drops folder is that the version that doesn't work includes Microsoft.Azure.Documents.Client.TransientFaultHandling.dll and Microsoft.Azure.Documents.Client.TransientFaultHandling.xml.
Please take the latest binary drop for 1.8.2.
This happens with both
dt.exe
anddtui.exe
, full exception stack at end.Repro steps: 1) Set Source Information to
Azure Cosmos DB
1) Enter valid connection string, clickVerify
, this shows a success dialog. 1) Set Query toselect * from c
1) Set Target Information to a JSON file (it doesn't seem to have thing to do with target & Json file should rule out any errors here) 1) Start Import 1) At this point an error diaglog will appear with the following errorSystem.AggregateException: One or more errors occurred. ---> Microsoft.Azure.Documents.DocumentClientException: Server could not parse the Url., documentdb-dotnet-sdk/2.2.1 Host/64-bit MicrosoftWindowsNT/6.2.9200.0
(full stack trace at end)This consistently happens with multiple collections using V1.8.2, but the export runs successfully with V1.7 (as I happened to have that version lying around).
The only thing that could be unusual about my setup is that I just created a new database in the Cosmos account with database provisioning. So the account contains 2 databases, the original one with per-collection resource provisioning and the new one with database provisioning.
After telling the export to connect using HTTPS & turning on Fiddler I can see it successfully making requests to Cosmos (looks like fetching metadata about the collection) then fails with the following request
Which returns
From the successful export using V1.7 I can see the following request at this point instead
followed by
Full Stack trace