Post reply

SQL Server does not exist or access denied. [SQLSTATE 42000] (Error 17). The step failed.

  • September 15, 2005 at 7:51 am

    #165982

    Hello All,

    I got error message when my scheduled job trying to run overnight. The error message is :

    SQL Server does not exist or access denied. [SQLSTATE 42000] (Error 17).  The step failed.

    I couldn't figure out y it fails.

    I might be wrong, i'm thinking coz of network connection broke.

    Please help me.

    Thanks

  • September 15, 2005 at 7:53 am

    #590139

    What's the authentication method to access that server?

    How are you trying to access it?

    Is the server started?

  • September 15, 2005 at 8:00 am

    #590140

    I'm using Sql Server and Windows authentication.

    Sql server was up that time.

    This job ran for 44 second before it failed.

    Thanks

  • September 15, 2005 at 8:11 am

    #590153

    Can you manually rerun he job step by step to find which one failed? Maybe that'll give you a better error message to go on... or maybe there's some logging option I never explored that can help.

  • September 15, 2005 at 8:32 am

    #590164

    We occacionally get that when trying to connect to one of our small sites over an ADSL link, when the link is down it can't connect and returns that message.

  • September 16, 2005 at 7:15 am

    #590554

    Hi,

    Maybe it's not the SQLServer you are being denied access to but rather the table you are trying to access.

    Check the owner of the tables in question. I have gotten errors like this when creating a table and forgetting to make .dbo the owner. The table ends up with me as the owner which is fine when testing from my console but not fine when it finally runs on the production server with the production login.

    That's my guess and I'm sticking to it.

    Teague

  • September 16, 2005 at 8:27 am

    #590613

    I have seen this when you run this job as a global user (myself) and active directory was running in native mode.  For some reason sqlserver agent can not access active directory in native mode for the authorisation.  I could solve it by changing the user running the job to sa.

    Joachim.

  • September 16, 2005 at 10:09 am

    #590658

    42000 errors are almost always user/password issues whether it is 'mixed' or Windows Authentication. You could use the 'advanced' tab and capture the actual execution output in a file from the scheduled task. This additional information, with the task start/end times from the execution history, will give you a window to look at in the event logs to see what occurs just prior to and during the execution of the task until it fails. My guess is that you'll then have a detectable (but fixable) cause for the error.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Viewing 8 posts - 1 through 7 (of 7 total)

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