Re: Sql Server Agent (2000) erroring out on DTS Packages

From: Thomas Scheiderich (tfs_at_deltanet.com)
Date: 07/08/04

  • Next message: Darren Green: "Re: Exporting DTS Packages"
    Date: Thu, 8 Jul 2004 12:36:23 -0700
    
    

    "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
    news:OaUW5hMZEHA.3844@TK2MSFTNGP10.phx.gbl...
    > Have a look at this article Thomas and it should help
    >
    > http://support.microsoft.com/?kbid=269074

    I looked at it and tried all kinds of permissions and still get the problem.
    The program also won't run from Query using this command:

    exec master.dbo.xp_cmdshell 'dtsrun /S "OPENWORX" /N
    "VDW_CostGrp_No_DropCreate" /E '

    I get the following message:

    ****************************************************************************
    *******
    output
    ----------------------------------------------------------------------------
    ----------------------------------------------------------------------------
    ----------------------------------------------------------------------------
    ---------------------------
    DTSRun: Loading...

    DTSRun: Executing...

    DTSRun OnStart: Copy Data from CostGrp to [VDW].[dbo].[CostGrp] Step

    DTSRun OnError: Copy Data from CostGrp to [VDW].[dbo].[CostGrp] Step, Error
    = -2147467259 (80004005)

       Error string: Specified driver could not be loaded due to system error
    126 (MERANT 3.60 32-BIT Progress SQL92 v9.1D).

       Error source: Microsoft OLE DB Provider for ODBC Drivers

       Help file:

       Help context: 0

    Error Detail Records:

    Error: -2147467259 (80004005); Provider Error: 160 (A0)

       Error string: Specified driver could not be loaded due to system error
    126 (MERANT 3.60 32-BIT Progress SQL92 v9.1D).

       Error source: Microsoft OLE DB Provider for ODBC Drivers

       Help file:

       Help context: 0

    DTSRun OnFinish: Copy Data from CostGrp to [VDW].[dbo].[CostGrp] Step

    DTSRun: Package execution complete.

    NULL

    (20 row(s) affected)

    ****************************************************************************
    *******

    I also found that others have similar problems. One was on IBM Websphere
    and a problem with a missing MDAC dll (not sure if this is related to DTS).

    Here is the response I gave to my client as well as the URL from DataDirect
    that talks about the problem.

    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    +++++
    Chris,

    Been looking into the DTS problem.

    There are a couple of possibilities that may be causing our problems. One
    is the Permissions problem. Sql Server 2000 should need a special user to
    run. On Sql Server 7, this was SQLAgentCmdExec. This is apparently
    different for 2000 ( you have one called SqlExec). This should work - but
    doesn't seem to.

    The owner of VDW_CostGRP was Prairie/clantz. I thought that might have been
    the problem and changed it to my name as well as SqlExec - but that still
    didn't work. Also, if running from your machine or mine, the program is
    actually executing on our machines (which is why we needed the ODBC drivers
    on our machines). I did notice in the event log that when I ran the
    scheduled package directly from my machine the person that ran it was
    Prairie/tom (not the schedular).

    Another question. When you run the VDW_CostGrp package from the Web page -
    do you get the 126 error? I seem to remember that when I came in last week,
    it didn't. I do get the error when I run it from here. If this is the
    case, it could be a permissions problem

    Here is the article from MS talking about exactly the problem we are having
    (although I have tried changing accounts on the package and it still seems
    to have the problem), maybe you can see something I didn't.

    http://support.microsoft.com/?kbid=269074

    I also found an interesting article having to do with MDAC in a couple of
    places. MDAC may not be our problem, but it may have some drivers that the
    schedular needs. The article talks about IBM Websphere and their problem
    problems. I realize we are not using this, but if the .dll is the problem,
    it could be affecting us also.

    Here is one snippet of an article I ran into:

    ****************************************************************************
    ************************************
    For SQL Server 2000 on Windows NT, there is a problem with Microsoft Data
    Access Componentry(MDAC) Version 2.6. The ODBC driver for SQL Server,
    embedded with SequeLink 5.x, requires dlls that are no longer shipped in
    MDAC Version 2.6. Therefore, if you install SQL Server 2000 on a clean
    Windows machine, the following error displays:

    Specified driver could not be loaded due to system error 126 (MERANT MSSS
    Driver for SequeLink 5.0) Windows NT The SQL Server 7 driver requires dlls
    that are not required by the SQL Server 2000 driver and no longer ship with
    MDAC Version 2.6 or higher.

    To fix this problem, install the MDAC version that is shipped on the
    DataDirect SequeLink CD(or version 2.1 from the Microsoft website). Here is
    a link to the Microsoft website for MDAC Version 2.1:

    http://www.microsoft.com/data/download_21242023.htm
    ****************************************************************************
    ************************************

    Here the article from DataDirect that goes into their problem in greater
    detail. They are directly talking about Merant and the Sql Server 2000 MDAC
    missing DLL. Not sure if this is our problem, but it looks the same. If it
    is, no amount of Permissions are going to solve the problem.

    http://knowledgebase2.datadirect.com/kbase.nsf/SupportLink+Online/27864?Open
    Document

    I am still looking for other answers.

    Tom
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    +++++

    We have to find a solution to this as we are dead in the water, here.

    Thanks,

    Tom.

    >
    > --
    >
    > ----------------------------
    >
    > Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
    > www.SQLDTS.com - The site for all your DTS needs.
    > I support PASS - the definitive, global community
    > for SQL Server professionals - http://www.sqlpass.org
    >
    >
    > "Thomas Scheiderich" <tfs@deltanet.com> wrote in message
    > news:10eq23ense7glba@corp.supernews.com...
    > > I have various DTS packages that copy data from our Progress Database to
    > our
    > > Sql Database. The packages work fine when running from the Enterprise
    > > manager, either by right-clicking the package and executing or from
    inside
    > > the package.
    > >
    > > When we try to execute it from the schedular (Sql Server Agent), it
    fails.
    > > We get an error from the Merant ODBC driver for th Progress that it
    can't
    > > load it. Why does it work from the Enterprise Manager and not the
    > > Schedular?
    > >
    > > Is there some type of special User setup we need to do? And if so where
    > > would we do it. I know in 6.5, you had to set up a special user, but I
    > > can't find anything in my books that mention it.
    > >
    > > Thanks,
    > >
    > > Tom.
    > >
    > >
    >
    >


  • Next message: Darren Green: "Re: Exporting DTS Packages"

    Relevant Pages

    • Re: different mdac, different sql server behaviour
      ... ODBC is part of MDAC and you are using the SQL Server ODBC driver. ...
      (microsoft.public.sqlserver.server)
    • Re: Strange behaviour of DTS
      ... I can only presume that this is like the issues with MDAC. ... an Upstream version of MDAC saves a package then the properties of his/her ... upstream version has properties not available in the lower version. ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ...
      (microsoft.public.sqlserver.dts)
    • Re: Can not install MSDE 2000A
      ... CNVGSFV.OUT is showing that it is trying to use the SQL Server driver to ... MDAC Component Checker that you can download at ... properly (since you previously stated that running the MDAC 2.8 install does ...
      (microsoft.public.sqlserver.msde)
    • Re: DTS packages in SQL 2000 slow to open
      ... MDAC? ... > SQL Server to the new and faster SQL Server. ... But then I created a test package directly on the new SQL ... >> What happens if you save the package to a structured storage file and do ...
      (microsoft.public.sqlserver.dts)
    • Re: Install SQL server 2000
      ... But I can't install MDAC because the setup program says MDAC is allready in ... You can install the ... I install SQL server, so SQL server must ... >>installed any other ODBC driver. ...
      (microsoft.public.sqlserver.setup)