SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Windows batch file executions within SSIS fail when run from SQL Job Agent


Windows batch file executions within SSIS fail when run from SQL Job Agent

Author
Message
Chris Schmidt
Chris Schmidt
Valued Member
Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)

Group: General Forum Members
Points: 54 Visits: 120
Windows batch file executions do not fail within SSIS when SSIS run using DTExec
The account we are using to execute the jobs is a local admin on the server
The jobs ran successfully in the past, but have been failing for 2 weeks

We are running SQL Server 2008 R2 on a 64-bit server. We had a successful job execution when we ran the job using 32-bit mode while trying to solve the problem.

The specific batch job that fails maps drives to allow access to a password protected folder so we may resolve the “file connection string” in the connection manager.

Anybody have any thought on this?
WillyWonka
WillyWonka
SSC-Enthusiastic
SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)

Group: General Forum Members
Points: 103 Visits: 118
Open the SQL Agent job and the step where you call the SSIS Package.

On the "Execution Options" tab...check the box "Use 32 bit Runtime" and see what happens. When using Excel or some ODBC drivers you need this setting to emulate the 32-bit environment or the job will fail.

-Eric
Chris Schmidt
Chris Schmidt
Valued Member
Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)

Group: General Forum Members
Points: 54 Visits: 120
Thanks of the suggestion. We aleady tried running the job in 32-bit mode via the job agent.

The big picture is that we have to connect to password protected Samaba folders to retrieve files. We need to map drives(shares) with the password to resolve the connection string in the flat file connection manager. Ultimately the issue was that the batch job was mapping letter drives and as the batch file was getting reused from different developers, either the letter drives eventually ran out, or the letter drive was already mapped and the batch job failed.

The solution was to rewrite the batch file more intelligently.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search