Post reply

sqlserver2005 job is failing

  • July 20, 2011 at 1:41 pm

    #240191

    Hi,

    One of my sqlserver2005 job is failing with the below error.

    Message

    Executed as user: *****. Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)". [SQLSTATE 42000] (Error 50000) OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" returned message "Unspecified error". [SQLSTATE 01000] (Error 7412). The step failed.

    please provide the fix.

    thanks.

  • July 20, 2011 at 1:43 pm

    #1355997

    Try running the code in SSMS and see if you get a mor specific error.

  • July 20, 2011 at 3:21 pm

    #1356063

    Hi,

    I ran it in SSMS and getting the below error .

    OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" returned message "Unspecified error".

    Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)".

    thanks.

  • July 20, 2011 at 3:29 pm

    #1356065

    Is the linked server for an Access database or a spreadsheet? If it's a spreadsheet, it may be a permissions issue.

  • July 20, 2011 at 3:35 pm

    #1356068

    it is for access database.

  • July 20, 2011 at 3:42 pm

    #1356073

    Then I would check the path to the Access database in the linked server definition and make sure it exists.

  • July 20, 2011 at 3:48 pm

    #1356077

    yes, it exists.

  • July 20, 2011 at 3:57 pm

    #1356082

    Then I would try executing the code that's in the job in SSMS. If it works, then it might be SQL Agent service account permission issue. Linked servers to Access databases can be a pain.

  • July 20, 2011 at 4:15 pm

    #1356088

    I have executed the code that's in the job in SSMS,and getting the below error.

    OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" returned message "Unspecified error".

    Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)".

  • July 20, 2011 at 4:30 pm

    #1356091

    The you might want to try adding a linked server to that database for testing/troubleshooting, preferably on a development server, and see if you can access it and execute queries. Make sure that you actually have access to the location of the Access database.

  • July 20, 2011 at 5:01 pm

    #1356098

    It might be useful to take a look at this too.

    http://www.aspfree.com/c/a/Microsoft-Access/Configuring-a-Linked-Microsoft-Access-Server-on-SQL-2005-Server/

  • July 20, 2011 at 5:31 pm

    #1356102

    job ran successfully after restart the sqlservice.

    but i am not able to find the root cause.

Viewing 12 posts - 1 through 11 (of 11 total)

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