Develop Reference

What is the VS2022 eqivalent to "Azure Identity Plugin for Visual Studio Code Authentication"?

im trying to authenticate towards Azure using my local user in VisualStudio2022 in my local development environment using the following:
const { DefaultAzureCredential } = require("#azure/identity");
const credential = new DefaultAzureCredential();
but nothing is found, and I'm signed in in VS2022.
Should credentials be found automatically, or do i need to spesify that it is the VS2022 credentials i want to use?
Does https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/identity/identity-vscode/README.md work only for VS-Code, and not vs2022?
Edit 1: Elaboration: As i understand it, "credentials" can be from "EnvironmentCredentials", "DefaultManagedIdentityCredentials", "AzureCLI" or "AzurePowerSHell".
Beeing logged into azure with corret subscription in VS2022, i expected my credentials to be in one of these to contain my credentials.
Btw: i get a "DefaultAzureCredential => failed to retrieve a token from the included credentials. To troubleshoot, visit"
What is the "included credentials" ?
Edit 2: I can get a token using Azure CLI as descibed here: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/identity/identity/TROUBLESHOOTING.md#verify-the-azure-cli-can-obtain-tokens

This was solved using the azure sdk require("#azure/identity");
And i guess its fetching credentials though AzureCLI , event though its not visible when instantiating the credentials, which i was expecting. But its all undefined as can be seen in picture below.
Then, just trying to get the secret from keyVault it worked, although i'm not 100% sure how its working.
const client = new SecretClient(url, credential);
await client.getSecret(secretName);

Error: querySrv ENOTFOUND _mongodb._tcp.dbname.fzofb.mongodb.net

I'm learning Node.js and just started working with MongoDB.
I'm making a connection with the MongoDB Cluster I've created
const dbURI = 'mongodb+srv://testuser:test1234#nodelearning.fzofb.mongodb.net/mydb?retryWrites=true&w=majority';
mongoose.connect(dbURI, { useNewUrlParser: true, useUnifiedTopology: true })
.then((result) => console.log('connected to db'))
.catch((err) => console.log(err));
When I run it nodemon app I get this error:
Error: querySrv ENOTFOUND _mongodb._tcp.mydb.fzofb.mongodb.net
at QueryReqWrap.onresolve [as oncomplete] (node:dns:206:19) { errno: undefined, code: 'ENOTFOUND', syscall: 'querySrv',
hostname: '_mongodb._tcp.mydb.fzofb.mongodb.net' }

Also if you have your mongodb Atlas cluster inactive after a while. It could get paused and then when you run a server it returns the error you had.
So another bet is to login to your Atlas account and confirm if it hasn't been paused. Well this option of mine should only be considered after trying the options above.

The error indicates that there is no error in the code. This leaves you with three potential possibilities:
Ensure you have MongoDB installed on your computer.
Make sure you're connected to wifi that is not public.
Make sure you have allowed the IP in network access of MongoDB as shown in the image below:
In my case, I was connected to public wifi in a coworking space. I change my connection to my personal hotspot and it worked.

Try disabling VPN if enabled. It helped me.

You need to convert special characters in connection string password to percent encoding.
I had the same issue with mongodb-compass. For me it was incorrect connection string format. So in my case it required to convert # symbol in my password to %40 (percent encoding).
You can read more about this in here. and here.

I had the same issue. I was using the latest srv string. I don't know if this will help you. But using the olderve
mongodb://<username>:<password>#cluster0-shard-00-00.2pznz.mongodb.net:27017,cluster0-shard-00-01.2pznz.mongodb.net:27017,cluster0-shard-00-02.2pznz.mongodb.net:27017/myFirstDatabase?ssl=true&replicaSet=atlas-s5orlv-shard-0&authSource=admin&retryWrites=true&w=majority```

This error happens if the IP Address you try to access the database with is not on the IP Access List. Go to MongoDB Login and under security click on the Network Access and check if your IP is added there.

In my case, the problem got solved when I sign in to my MongoDB atlas account.

In my case, I was re-using a string connection from another project.
I copied my original string connection from MongoDB site and worked fine.

FIX : : previously my cluster password was "chaudhary#786" which contained the
special character "#", due to which the compass string connecting
compiler got confused hence in the next turn I changed my password to
"gghjkl98", i.e without any special characters. and I got connected
without any errors.
SOLUTION : password of the cluster should not contain characters like \backslash
or # or any other characters

MongoDB atlas connection fails with error MongoServerSelectionError: connection <monitor> to 52.64.0.234:27017 closed

I have set up a mongodb Atlas free tier cluster. When I try to connect to it with node js, it throws an error. I have white listed my IP both manually and with select current. I have also tried adding +srv to my connection url but that just causes more errors.
Here is the node js code I was trying to connect with
const { MongoClient } = require("mongodb");
const url = "mongodb://user1:password1!#cluster0-shard-00-00-bc7dh.mongodb.net/test?retryWrites=true&w=majority&useNewUrlParser=true&useUnifiedTopology=true";
const client = new MongoClient(url);
async function run() {
try {
await client.connect();
console.log("Connected correctly to server");
} catch (err) {
console.log(err.stack);
}
finally {
await client.close();
}
}
run().catch(console.dir);
and here is the error I get
MongoServerSelectionError: connection to 52.64.0.234:27017 closed
at Timeout._onTimeout (C:\Users\YOUNG\node_modules\mongodb\lib\core\sdam\topology.js:430:30)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
people with a similar problem were able to solve it by whitelisting their ip addresses, but it hasn't worked for me. What could possibly be the problem?
I have tried allowing access for all ips but the error persists and when I use the uri with +srv, I get the following error
MongoServerSelectionError: Authentication failed.
at Timeout._onTimeout (C:\Users\YOUNG\node_modules\mongodb\lib\core\sdam\topology.js:430:30)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)

It is because your IP address is not whitelisted .
Go to network access in your mongodb atlas in your project and ADD IP ADDRESS . to test just add access from anywhere option
there you go get back and try again with the connection string .

Go to your network access at your cluster in MongoDB

Go to network access in mongo db and add in the Ip address 0.0.0.0, and everything will be okay.

You are missing tls=true URI option in the connection string.
You should also use the SRV URI that is provided by Atlas by default which takes care of this.

const client = new MongoClient(uri,
{
useNewUrlParser: true,
useUnifiedTopology: true,
});
client.connect(() =>
{
your_collection = client.db('your_db_name').collection('collection_name')
})
This worked for me.

I also had the same problem you encountered and found out the IP address is not correct which is set in "Network Access".
Try the followings:
Go to your MongoDB Atlas Project page
Click "Network Access"
Click "ADD CURRENT IP ADDRESS" button (it's very useful!)
Click "Confirm"
And now, the right IP address to connect with your PC is shown in IP Access List.
That's all!

You can fix the issue in a few steps.

For me this error was occurring because my connection string was wrong.To be very specific - I copied the sample connection string from a course I was learning and just replaced the username and password with my credentials. So, the credentials were right but not the rest of the connection string.
Just for the sake of understanding. Please see below :
mongodb+srv://myusername:mypassword#courseproject.h1mpg.mongodb.net/?retryWrites=true&w=majority"
myusername and mypassword are correct i.e belongs to the cluster in my MongoDB atlas account, but the rest of the string is wrong as I copied it from somewhere instead of copying it from my own MongoDB atlas account.
So please make sure to double check if your entire connection string is correct.

There is a very simple and straight forward fix for this issue,
Goto your mongodb account dashboard,
Enter Network Access
Where you see add IP Address, add a global address, thats is access from anywhere.
The images below better illustrates this procedue
And thats its, your done

For Cloud DB Server:
This problem mainly occurs if you're using online cloud storage. This is because you are not adding the IP address correctly. Here you can add the IP address as 0.0.0.0 as shown in the figure. If you add an IP like this, it will auto-import your machine IP address.

What is a TransientTransactionError in Mongoose (or MongoDB)?

I have server.js and db.js The db.js file interacts with my database using Mongoose and I use server.js to call functions from db.js :
var mongoose = require('mongoose');
mongoose.connect('', { useNewUrlParser: true })
var Schema = mongoose.Schema;
module.exports = function () {
var db = mongoose.connection;
db.on('error', console.error.bind(console, 'connection error:'));
return db.once('open', function() {
console.log("Connected to DB")
var postschema = new Schema({
title: String,
intro: String,
body: String,
author: String,
timestamp: { type: Date, default: Date.now }
});
var post = mongoose.model('post', postschema);
return {
newPost(title, intro, body, author) {
var newpost = new post({
title: title,
intro: intro,
body: body,
author: author
})
},
getPostsAll() {
post.find({}, function (err, res) {
return (`Error:${err} Posts:${res}`)
})
}
}
})
}
And my server.js calls three functions from db.js :
var DB = require('./db.js')
var db = DB()
db.getPostsAll()
db.newPost()
I don't understand why I get this error :
connection error: { MongoNetworkError: connection 4 to black-test-shard-00-01-ewyaf.mongodb.net:27017 closed
at TLSSocket.<anonymous> (E:\HTML\black-box\node_modules\mongodb-core\lib\connection\connection.js:276:9)
at Object.onceWrapper (events.js:272:13)
at TLSSocket.emit (events.js:185:15)
at _handle.close (net.js:541:12)
at TCP.done [as _onclose] (_tls_wrap.js:379:7)
name: 'MongoNetworkError',
errorLabels: [ 'TransientTransactionError' ],
[Symbol(mongoErrorContextSymbol)]: {} }
What am I doing wrong? I found an article but can't make anything of it.

I had
'MongoNetworkError',
errorLabels: [ 'TransientTransactionError' ],
[Symbol(mongoErrorContextSymbol)]:
I added my current IP to whiteList following "main page > security section > network access > add IP" in MongoDB website.
I hope this helps.

What is a TransientTransactionError
A TransientTransactionError is a transactional error that is classified as temporary, and if retried it may be successful. Furthermore, a TransientTransactionError write conflict occurs prior to a commit when no write lock has been taken and the transaction (new data) is not reflected in the transaction snapshot (previous data.) As a result, these errors are completely safe to retry until there is a successful commit.
Transactions that retry in this scenario are retried from the beginning of the transaction.
Keep in mind This error label is different than commit errors that happen when the lock has been taken but the transaction can't complete its commit. The error label for this is UnknownTransactionCommitResult. The reference to this is notable due to the difference in understanding where in your application an error is occurring and what may be the underlying cause and how the application can and or will respond due to different error types.
If you're using MongoDB supported drivers, there are two possible cause the code is getting this error:
Any database command error that includes the "TransientTransactionError" error label in the "errorLabels" field.
Any network error encountered running any command other than commitTransaction in a transaction.
The code example in MongoDB Transactions: retry-transaction show cased how to handle TransientTransactionError.
If the error message is MongoNetworkError, it means the transient transaction error is related to the network connectivity between the client and the server. This could either be a one time network glitch which is retry-able, or there is no network access which require network configuration. If the error is encountered on the first time the client trying to access the server, it is likely that there is network configuration needed. If the server is on MongoDB Atlas, please see Configure Whitelist Entries.

Go to your mongoDB Atlas Dashboard
Open Network Access (its there in side navbar)
Click on ADD IP ADDRESS
Click on allow from Any IP Address ( it basically give access to your dynamic IP address)
Now you are done.

If there is no security issue and you are just doing it for connecting:
While setting up the IP Whitelist; format should be 0.0.0.0/0 , you will not face the issue.
Moreover, as you have answered yourself, we can add the ip for which we need access.

I had the same issue/error, albeit on a Windows machine. Even though I thought I had started the mongodb service, I didn't see it running in Windows Services. So, I manually started the mongoDB service inside Services and then the error went away. Hope this helps!

I encountered this error when running the populatedb.js script in the MDN tutorial for Express/NodeJS.
The script was looking for a db connection starting with mongodb://, however my connection string from mongo started with mongodb+srv://.
I edited the script to check for this syntax instead, which resolved the error.
I hope this helps someone.

I had similar problem...
All day I was able to connect via mongoose. Then bang I started getting 'TransientTransactionError' error. I could connect to mongoDB via shell so I knew the server was up and running as expected.
IPv6/localhost. My IP switched from IPv4 to IPv6. I resolved the issue by disabling IPv6 and getting regular IPv4 IP.
EDIT -- seems I can reliably re/create this issue by connecting to 'localhost' while my NIC is configured with a IPv6 IP. Changing localhost->127.0.0.1 seems to resolve the issue.

Make sure the server didn't run out of storage space.
In my case, none of the suggested answers helped. I was pulling out my hair until I've noticed that the server ran out of storage space. Clearing up a few megabytes of storage solved the error immediately.
The TransientTransactionError actually makes sense in this scenario due to its nature of being a temporary error that could be resolved upon an explicit retry - though it did take me a while to figure out it had to do with a storage issue.

For me, the transient transaction error came whenever I switched from my wifi network to my phone's hotspot. If this happens to you too, go to MongoDB website where you have made your database and white list your current IP address again. This will solve your problem.

If you are using MongoDB Atlas. You need to Whitelist your IP address on the Atlas Console in the security settings.

If you still have this error, another reason is that you forgot to restart nodemon server after changing config file. CTRL+C and start again, that's how i solved it.

Security > Network Acess> Add IP Adress > Add Current Computer IP address.
Solved my problem.

Using mLab -- When your cluster is created, you need to add a database user (under the users tab) and make sure to not click the Make read-only checkbox. Once I did this, the errors went away. I was getting the same errors as above. The database user can be your login user name and password.

Go to your MongoDb Atlas dashboard. Click on Network Access, Click on add Ip Address and allow connectivity from any Ip Address.
This should solve your problem.

I had this problem when trying to connect my Heroku app to a MongoDB Atlas database.
If you do a on you terminal
heroku logs --tail
You might see
ERROR: { MongoNetworkError:
connection 4 to cluster0-shard-40-01-qnwp8.mongodb.net:27017 closed
name: 'MongoNetworkError',
errorLabels: [ 'TransientTransactionError' ],
[Symbol(mongoErrorContextSymbol)]: {} }`
After whitelisting the server connection on MongoDB Atlas, the database connection error was resolved.

You can read about the error online but the solution for this problem is: go to you MongoDB atlas and add your IP address.
Go to:
main page > security section > network access > add IP
This problem is basically when the architecture do not know your own IP address.
Also, copy-paste directly to google to get straight forward solution.

How can I initialize MongoDB -object db in a browser console?

Suppose I want to execute 'db.things.insert({colors : ["blue", "black"]})' in browser. I can execute it in the Mongodb -shell but not yet understanding how to execute it like: open up the Google Chrome Console, initialize the DB -object with some connection and execute the command. Does there exist some plugin? Sorry I am totally new to MongoDB, trying to test just things fast with Browser shell. How can I do the initialization like that?
Trial 0: perhaps with REST -interface?
I have enabled the REST with "$ echo 'rest=true' > /etc/mongodb.conf;
$ sudo restart mongodb", works in Ubuntu. More about rest
here, not sure
yet whether needed here but perhaps with some POST/REST -method I can
do the init.
Trial 1: Oreilly's book about MongoDB and 50 Tips (page 47)
The book has some example
> db = connect ("ny1a:27017/foo")
> db = connect ("ny1a:27017/admin")
so now
> db=connect("localhost:27017/test")
ReferenceError: connect is not defined
Yes because I need to source the connect -command, some further examples here, where can I get it?
P.s. I am studying this tutorial here.

You cannot simply access mongodb from the browser console. Your browser is a client, and there isn't (as far as I know) a javascript client-side library. Any javascript library you will find will most likely be for Node.js (server).
The mongo console is its own type of compiled client. The native language is javascript, but those commands only pertain to the actual mongo command shell. connect is a command for the mongo command shell.
Enabling REST starts a port on your mongod that will accept REST http communication. You get a browser page here: http://localhost:28017/
This is a very basic page displaying data, but you can further run queries yourself. See http://www.mongodb.org/display/DOCS/Http+Interface#HttpInterface-SimpleRESTInterface
Note, the REST interface is READ ONLY. You cannot insert.
That being said, you need a proper driver for your language of choice.