Invalid Object Name error

  • I have users trying to use a web application that connects to a SQL Server 2000 DB using a ODBC DataSource. When I try to uss the application, I keep getting [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid Object Name 'aName'.

    If we try to use the app on the same server as the DB, I get the above error. I used the sql profiler and I see that the login name is NT AUTHORITY\SYSTEM, The applicationName is Service Runner. I tried to add NT AUTHORITY\SYSTEM to Logins but it didn't work.

    Additionally, When I try to use the app froma remote workstation, I get Login Failed for user 'domain\workstationName'.

    I have the datasource setup for Windows authentication using network login.

    Any ideas how to solve this issue?

    Thanks.

  • Are you logged in on the system with your credentials? If yes, is that credential having rights to that server instance? Which account is used for starting sql server service?

    MJ

  • Yes I am logged in using my credentials over a windows network. I am added to have access to the DB instance.

    The problem is that when I look at the logs, I see a login try with the workstation credentials and not mine.

    For example, if I am using workstation XYZ, in the logs, domain\XYZ tries to login and not domain\khskinsfan.

    domain\XYZ does not have access but domain\khskinsfan does.

    Thanks.

  • Stupid question, but have you checked to make sure the object still exists? Someone may have dropped it or maybe a DBA renamed it to see who squawks to find out if it's still used.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Yes ...It does exists. I I add the workstation to the SQL Server Logins, everything works. I want the login to be based on the user credentials, not the workstation credentials. Maybe it's the the DB is called in the code.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply