Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Unable to use DMT. #176

Open
jenkins123 opened this issue Feb 26, 2025 · 3 comments
Open

Unable to use DMT. #176

jenkins123 opened this issue Feb 26, 2025 · 3 comments
Labels
question Further information is requested

Comments

@jenkins123
Copy link

I have downloaded the data migration tool on Mac machine, and tried to execute the dmt.
but I am unable to execute the dmt from terminal, I see error

sudo: dmt: command not found

I tried setting up the dmt file in the path , still no use. Not sure what need to be done to run this tool.

@philnach
Copy link
Collaborator

@jenkins123 thank you for reaching out have you seen this part of the README: https://github.com/AzureCosmosDB/data-migration-desktop-tool#using-the-command-line.

I just double checked on macOS Sequoia that the current release of dmt works. Here's output from my terminal:

Image

If you are running the release out of your Downloads folder make sure:

  1. The file has execute permissions chmod +x dmt
  2. The file isn't being blocked by macOS Gatekeeper: Open a Mac app from an unidentified developer or from a command line: [Gatekeeper Exception command line.md]

@philnach philnach added the question Further information is requested label Feb 27, 2025
@jenkins123
Copy link
Author

jenkins123 commented Feb 27, 2025

Hi Mr Phil, Thank you for the response, yeah I figured it out that it was a permissions issue and could run the tool.
Now I see a different problem connecting to cosmos db .
Using Cosmos-nosql Source
Using JSON Sink
fail: CosmosDataSourceExtension[0]
Failed to connect to CosmosDB. Please check your connection settings and try again.
Microsoft.Azure.Cosmos.CosmosException : Response status code does not indicate success: NotFound (404); Substatus: 0; ActivityId: 00000000-00
00-0000-0000-000000000000; Reason: (
RequestUri:xxxxx
Any pointers if there is any thing I am missing here.

the config I am using is

{
"Source": "cosmos-nosql",
"Sink": "json",
"SourceSettings": {

   "ConnectionString": "AccountEndpoint=abcd.com:443/;AccountKey=xxxx===",
  "Database":"osco-perf",
  "Container":"order",
  "IncludeMetadataFields": false

},
"SinkSettings":
{
"FilePath": "/Users/someuser/Downloads/Backup/xyz.json",
"Indented": true
}
}

@philnach
Copy link
Collaborator

philnach commented Mar 2, 2025

Hi, I just confirmed on the same Mac with the latest 2.2.0 release and your settings file that I was able to transfer data from Cosmos DB to JSON. It sounds like perhaps your connection string isn't correct. You can copy the connection string directly from the Settings->Keys section in Azure Cosmos DB account (https://learn.microsoft.com/azure/cosmos-db/nosql/tutorial-dotnet-console-app#create-api-for-nosql-resources).

Can you also check that you can access the database from Azure Portal and view data in the Data Explorer?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants