locate Temp directory of the SQL Server Agent Service startup account

  • does anyone know where is "Temp directory of the SQL Server Agent Service startup account" or how to locate it?

    Error:
    An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.The AcquireConnection method call to the connection manager "<Name>" failed with error code 0xC0202009.
    Symbolic Name: DTS_E_OLEDBERROR
    The hexadecimal value for this error number = 0x80004005.
    Cause:
    The owner of the job determines the security context in which the job is run. If the job is owned by a SQL Server login account that is not a member of the Sysadmin fixed server role, the SSIS package runs under the context of the SQL Server Agent proxy account.
    If you want the SQL Server Agent proxy to run jobs that connect to an instance of SQL Server, the SQL Server Agent proxy account must have correct permissions to the instance of SQL Server.
    If you want the SQL Server Agent proxy account to run a job that runs as an SSIS package, the SQL Server Agent proxy account must have the Read permission and the Write permission to the Temp directory of the SQL Server Agent Service startup account.
    Resolution:
     To resolve this issue, you must change the permissions for the Temp directory of the SQL Server Agent Service startup account. Grant the Read permission and the Write permission to the SQL Server 2005 Agent proxy account for this directory.
    References:
    Error message when an SSIS package runs that is scheduled to run as a SQL Server Agent job: "An OLE DB error has occurred. Error code: 0x80004005": http://support.microsoft.com/kb/933835

  • try running this from within a SQL Agent job:
    exec xp_cmdshell 'echo %temp%'

  • Chris Harshman - Thursday, July 19, 2018 12:41 PM

    try running this from within a SQL Agent job:
    exec xp_cmdshell 'echo %temp%'

    thanks, I ran xp_cmdshell "set", it gave me TEMP and TMP and more..

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

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