Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Sql Server Integration Services. Expand / Collapse
Author
Message
Posted Friday, July 18, 2008 8:31 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 11, 2011 6:14 AM
Points: 3, Visits: 67
I have done a package in the sql server integration services 64 bit and schedule the package in sql server job when running the job in sql server 2005 it is giving the error message.

Message
Executed as user: EASYERPRS1\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Argument "Excel" for option "connection" is not valid. The command line parameters are invalid. The step failed.

And this is the command line


/SQL "\TANIGHTLY" /SERVER EASYERPRS1 /CONNECTION "easyerprs1.PQNEW_RSAS";"\"Data Source=easyerprs1;Initial Catalog=PQNEW_RSAS;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;\"" /CONNECTION "Excel Connection Manager";"\"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\Feeds\NightlyReport.xls;Extended Properties=""EXCEL 8.0;HDR=YES"";\"" /CONNECTION "NightlyReport.xls";"D:\Feeds\Template\NightlyReport.xls" /CONNECTION "NightlyReport.xls 1";"D:\Feeds\NightlyReport.xls" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E

Please help.






Post #536858
Posted Friday, July 18, 2008 9:39 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: 2 days ago @ 7:58 AM
Points: 1,795, Visits: 2,167
It looks like the package is running in the 64 bit environment. Packages on a 64 bit server need to run in the WOW layer (32 bit) since SSIS is still a 32 bit process and there are no Jet drivers for 64 bit. I think it is a different command line but since I don't have any in SQL 64 bit, I'm not sure how to set it up.

MG

"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare

"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.

Post #536914
Posted Friday, July 18, 2008 9:46 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: 2 days ago @ 7:58 AM
Points: 1,795, Visits: 2,167
From BOL:

If you want to run a package from a 64-bit SQL Server Agent job in 32-bit mode, select a job step type of Operating system, and enter a command line or use a batch file that invokes the 32-bit version of dtexec.exe. You can use the dtexecui.exe utility to create the command line, and then copy and paste the command line into the job step.



MG

"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare

"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.

Post #536917
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse