osql - access denied error

  • It seems like I have been here before, but here goes:

    I am outputting the results of a sp to a text file via a dts package that runs an osql command.

    If I run the package manually from dts by running execute now, it works OK.

    However, if I run it under the agent as a scheduled job, it falls over with the following error:

    The execution of the following DTS Package succeeded:

    Package Name: dtsDailyCheck

    Package Description: (null)

    Package ID: {CF579F9A-E7F2-4AB7-BCE7-887B1E0A818B}

    Package Version: {3F130DE7-5580-40EF-8D11-6960DE64EB32}

    Package Execution Lineage: {CA9EB880-C577-44FC-A3D4-EA10AB833E42}

    Executed On: DERVERNAME

    Executed By: SQL SERVER ADMIN ACCOUNT

    Execution Started: 05/07/2004 14:19:01

    Execution Completed: 05/07/2004 14:19:01

    Total Execution Time: 0.047 seconds

    Package Steps execution information:

    Step 'DTSStep_DTSCreateProcessTask_1' failed

    Step Error Source: Microsoft Data Transformation Services (DTS) Package

    Step Error Description:Access is denied.

    (Microsoft Data Transformation Services (DTS) Package (80070005): Access is denied.

    )

    Step Error code: 80070005

    Step Error Help File:sqldts80.hlp

    Step Error Help Context ID:1100

    Step Execution Started: 05/07/2004 14:19:01

    Step Execution Completed: 05/07/2004 14:19:01

    Total Step Execution Time: 0.031 seconds

    Progress count in Step: 0

    I have:-

    Run dcomcnfg.exe and added the SQL Service account to Default Access Permissions under Default Security tab and Default Launch tab; The server runs under a sql server admin account. I have in fact added 'everyone' as well.

    Hardcoded the unc path to the text file. I have given 'everyone' all permissions on the text file.

    I know it is a permission problem, but I have run out of places to look.


    ------------------------------
    The Users are always right - when I'm not wrong!

  • PLEASE IGNORE THIS THREAD.

    I finally spotted that the batch file I was calling did not go through a mapped drive. I used the full path via server name.

    I was concentrating so much on the destination file as this was where the error was when I was having trouble trying to create an excel object in the past.


    ------------------------------
    The Users are always right - when I'm not wrong!

Viewing 2 posts - 1 through 1 (of 1 total)

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