Azure-docs: Unable to proceed with request error

[aditya-gune]

I was able to create a CosmosDB database and collection on Azure successfully, but I get this error when trying to run the dot net app:

DocumentClientException: Unable to proceed with the request. Please check the authorization claims to ensure the required permissions to process the request.
ActivityId: f3c72700-95ac-4865-944f-20aca275e247, Microsoft.Azure.Documents.Common/2.1.0.0

I'm using the URI as the 'endpoint' and the Read-Write Primary Key as the 'authKey' values but am not able to get the app to work. Any help would be appreciated. Thanks!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4255f572-38cc-08aa-6fb7-08c919713cf9
• Version Independent ID: c04fe4dd-e75d-1028-8f2e-154d8c303da2
• Content: Build a .NET web app with Azure Cosmos DB using the SQL API
• Content Source: articles/cosmos-db/create-sql-api-dotnet.md
• Service: cosmos-db
• GitHub Login: @SnehaGunda
• Microsoft Alias: sngun

[CHEEKATLAPRADEEP-MSFT]

@agune001 Are you using the sample application?
If you are using sample application, make sure to update the connection strings.
In Visual Studio, open the web.config file.
Copy your URI value from the portal (using the copy button) and make it the value of the endpoint key in web.config.
"add key="endpoint" value="FILLME" "
Then copy your PRIMARY KEY value from the portal and make it the value of the authKey in web.config.
add key="authKey" value="FILLME"
Then update the database value to match the name of the database you have created earlier. You've now updated your app with all the info it needs to communicate with Azure Cosmos DB.
add key="database" value="Tasks"

OR

You can download and run your .NET app from the portal.

Download and extract the folder and you will find “todo.sln” file in the folder. Open the file in Visual Studio. Select CTRL + F5 to run the application.

The app works perfect without any issues.

Hope this helps.

[aditya-gune]

Hi, thanks for your reply. Yes, I followed those steps exactly and I get
the same error message. Additionally, I tried to use both "Tasks" and
"ToDoList" as the database, but neither of them worked. I have attached a
screenshot of the error message here.

Thanks,
Aditya

On Sun, Jan 20, 2019 at 10:08 PM CHEEKATLAPRADEEP-MSFT <
[email protected]> wrote:

@agune001 https://github.com/agune001 Are you using the sample
application?
If you are using sample application, make sure to update the connection
strings.
In Visual Studio, open the web.config file.
Copy your URI value from the portal (using the copy button) and make it
the value of the endpoint key in web.config.
"add key="endpoint" value="FILLME" "
Then copy your PRIMARY KEY value from the portal and make it the value of
the authKey in web.config.
add key="authKey" value="FILLME"
Then update the database value to match the name of the database you have
created earlier. You've now updated your app with all the info it needs to
communicate with Azure Cosmos DB.
add key="database" value="Tasks"

OR

You can download and run your .NET app from the portal.
[image: image]
https://user-images.githubusercontent.com/44426401/51455756-0c840780-1d71-11e9-82bd-d1c4634e218a.png

Download and extract the folder and you will find “todo.sln” file in the
folder. Open the file in Visual Studio. Select CTRL + F5 to run the
application.

The app works perfect without any issues.

[image: image]
https://user-images.githubusercontent.com/44426401/51455733-f0806600-1d70-11e9-8848-0885e8e0b519.png

Hope this helps.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/22889#issuecomment-455958735,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJNCFwh7zc-wwzKyFQkhKZbJ99BJZV1mks5vFVl3gaJpZM4aKD_w
.

[ab1234567]

+1.
I do get the same error.

[joelhulen]

Same issue here.

[CHEEKATLAPRADEEP-MSFT]

@SnehaGunda Could you please look into this issue, where the multiple customers are reporting?

[joelhulen]

This error also occurs after commenting out the following two lines:

CreateDatabaseIfNotExistsAsync().Wait();
CreateCollectionIfNotExistsAsync().Wait();

I had suspected the problem was with creating a database or collection, but I still receive the error within the GetItemsAsync method on the line where the query is executed (results.AddRange(await query.ExecuteNextAsync<T>());).

I have tried with a brand new Cosmos DB instance, and even run across this error when attempting to read or write to a different database and collection within that instance, from a different application. I've also attempted using older versions of the Microsoft.Azure.DocumentDB.Core NuGet package to no avail.

[djspringate]

I'm having the same issue. Followed the steps from the Azure Cosmos tutorial and get this issue at step 4:
https://docs.microsoft.com/en-gb/azure/cosmos-db/sql-api-get-started

I assume I don't need to create a collection to create a database?

[joelhulen]

This issue seems to only affect new Cosmos DB instances, not existing ones. My existing instances are still working correctly.

[rimman]

There is a regression in the portal that turns on firewall on on every newly created account. You can turn it off on the firewall blade. If you have further questions, please ping us at [email protected] Thanks!

[joelhulen]

@rimman That worked! How did I miss that? It is more obvious with Azure SQL where it tells you that you need to add your IP to the firewall. I've never seen that as an option for Cosmos DB. Would be nice if there was something that told you that you need to configure it on the Overview blade.

[rimman]

cool! thanks for the feedback!

[aditya-gune]

This works for me as well! Thanks!

[shraddhaagrawal]

we are getting same exceptions and we cannot allow all networks.
We are accessing cosmos db from azure functions and enabled following settings-

Accept connections from within public Azure datacenters

Allow access from Azure Portal

Day before it was working and now we are getting exception.
Thanks in advance.