Hey Guys, In my SSIS package i run a script to check a folder for new PDF files. If they are found in store the pdf in my database in varbinary using sql BLOB and move to a different folder. Now when the SSIS Package gets to a stage where it has to check the folder path, it connects to my SQL database using windows authentication. And I am getting access is denied errors. What I am wondering is what windows account is trying to view the folders with ? Since I dont specificy a username in the SSIS when i can select Windows Authentication, would it be the SSIS Job owner login since this is run a sql server agent job ? Or ?

turn on logging and post the messages.

THis was in the "View History" of the Job Executed as user: SERV3412\SYSTEM. ...on 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 09:17:52 Error: 2008-09-01 09:17:53.46 Code: 0xC002F304 Source: Retrieve New PDFs, move to Archived File System Task Description: An error occurred with the following error message: "Access to the path is denied.". End Error Progress: 2008-09-01 09:17:53.46 Source: Retrieve New PDFs, move to Archived Operation Complete: 100% complete End Progress Error: 2008-09-01 09:17:53.46 Code: 0x00000009 Source: Parse File Name Description: The task cannot execute in 64-bit environment because the script is not pre-compiled. Please turn on the option to pre-compile the script in the task editor. End Error Error: 2008-09-01 09:17:53.46 Code: 0xC0024107 Source: Parse File Name Description: There were errors during task validation. End Error Error: 2008-09-01 09:17:53.79 Code:... The package execution fa... The step failed. So the user its trying to use for Windows Authenication is "SERV3412\System" ? Is that like the default user or something ?

afew things: the SERV3412\System account doesn't have permission to access the folder. do you have a proxy account configured? http://support.microsoft.com/kb/912911 also, it would behoove you to use the sql server agent cmdexec subsystem to call dtexec to run your package. the benefit of this is that you will get much more robust messages if you have ssis logging implemented. hth

i overlooked something. in the script task, make sure that PrecompileScriptIntoBinaryCode = TRUE.

Could I not just set permissions for the windows account SERVexample\System on the folder i am trying to access.

Hey Duane, Thanks for your help man, I should probably explain I am pretty new to this. This all worked locally now trying to get working on a development server and the problems appear when u say " overlooked something. in the script task, make sure that PrecompileScriptIntoBinaryCode = TRUE." Where actually do is et this ? In the Visual Studio where I am creating the package or in SQL Server Agent Jobs where i am creating the job ?

Velnias wrote: Could I not just set permissions for the windows account SERVexample\System on the folder i am trying to access. i suppose you could. but this isn't a best practice. the system account should be granted access to a folder unless it's absolutely necessary. bad things could happen if that account is compromised by a hacker. it is far less likely that this would happen with a proxy account.

Velnias wrote: Hey Duane, Thanks for your help man, I should probably explain I am pretty new to this. This all worked locally now trying to get working on a development server and the problems appear when u say " overlooked something. in the script task, make sure that PrecompileScriptIntoBinaryCode = TRUE." Where actually do is et this ? In the Visual Studio where I am creating the package or in SQL Server Agent Jobs where i am creating the job ? open the script task editor in visual studio. under the script tab, you'll see the PrecompileScriptIntoBinaryCode property. then re-save and redeploy the package to the dev server.

Well, I kind of ran into a similar problem where I was to Move *.wmv files from my FTP folder to a hosting folder. I was getting error that Access to Path denied. I tried everything from changing the security level at the folders to my domain account but still my job was failing. At last I went into the SQL Server Agent service. It was running as Network Service account. I changed it to local system with desktop access and it started working. I hope this will help others. Thanks, Talha