Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

Question

0.00/5 (No votes)

See more:

In the query analyser inside Dev machine, I can run a sql query which connects to prod machine and retrieves data.
Note that I am the admin user...
If this query is run inside an application which is run by a standard user, then the user gets an error message which is login failed.
Note that the standard users do have access to prod data as they are currently using an app which points them to the prod machine.
The issue only arises when the standard users use that sql explained above inside the Dev app.
Question:
Do you know why the standard users can not run the sql (points to prod data) from within the Dev app whereas they can run it from the Prod app?
Thanks

Posted 24-May-12 7:21am

arkiboys

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Answer 1 · 2012-05-24T08:52:00

If the error message is correct, the user doesn't have access to the database at all. Meaning that there is no login/database user in the SQL Server for that user.

To your question, why this is different in another database, could it be that you either
- have a valid login/user in that server
- you're actually using public privileges.