Oracle SSIS Runs In DTExecUI, But Not In 32-bit DTExec

Aug 28, 2007



I've worked for awhile to get an SSIS package that connects to Oracle to succesfully run via DTExecUI from a 64 bit SQL Server. I completely understand that DTExecUI runs in 32 bit mode, but I need to initiate the package from a stored proc so I need to be able to utilize the 32 bit DTExec from either a xp_cmdshell call or from an sp_start_job (thanks to MatthewRouche for the suggestion). Both Ora92 and 10g were installed on the SQL Server.

Here's what I've tried unssuccessfully

1. SQL Job - Just calling the package from an SSIS step. I wouldn't expect this to run because it is 64 bit DTExec.
2. SQL Job - A job that calls the 32 bit version of dtexec from cmdexec. Here is 2 examples I have tried, the first is because I came across several postings saying that there is a problem with the "(x86)" for the Oracle driver.


\server_nameE$ProgramFilesLegacyMicrosoftSQLServerX8690DTSBinnDTExec.exe /DTS "PackageName" /SERVER "SERVER_NAME" /SET Package.Variables[PLT].Value;"8H" /CONFIGFILE "\SERVERConfigFile.dtsConfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW

\server_nameE$Program FilesMicrosoft SQL Server (x86)90DTSBinnDTExec.exe /DTS "PackageName" /SERVER "SERVER_NAME" /SET Package.Variables[PLT].Value;"8H" /CONFIGFILE "\SERVERConfigFile.dtsConfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW

Both of these give me the error below:


System.Exception: System.Data.OracleClient requires Oracle client software version 8.1.7 or greater.


I'm assuming that it is running in 32 bit mode because this was at the beginning of the job history log:

Executed as user: "XXX". ....3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved

3. I then tried to call the package from a batch file on a file server that had integration services installed on. Got the same error as above.

I'm obviously missing something if I can get it to work in DTExecUI but not DTExec 32-bit.

Any ideas? Below are some postings I have already visited several times:

Windows 64 bit and Oracle
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=358365&SiteID=1

Connecting to Oracle on 64-bit (x64) machine
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=159581&SiteID=1

One paragraph that stands out on this posting is:

Find the location of the application that is generating the error. Check the path to this location and see if it contains any parenthesis. If so, you must relocate the application to a directory without any parenthesis in the path.
This didn€™t work for me, unless I was doing it wrong.

Error retrieving numeric data from Oracle 10g on 64 bit Itanium SSIS server
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1183296&SiteID=1

Connection Problems to Oracle Database
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1307460&SiteID=1

If this posting was complete, it looks like what I was looking for.

View 9 Replies


ADVERTISEMENT

DTEXEC Runs In Its Own Command Shell ?

Nov 29, 2007



Does anyone know if DTEXEC runs in its own command shell area? The reason I am asking this question is that we have hundreds of old DTS packages that fetch data from Source Progress double-byte and standard databases. When we fetch from a double-byte Progress database, the first thing we do is to set System Environment variables and within the same command prompt session invoke DTS packages via DTSRUN utility. THis method works like a charm using the old DTS packages. We are trying to accomplish the same thing using SSIS and are unable to do so. The SSIS package works fine while fetching data from a non Double Byte Progress database but fails miserably while using a Double Byte Progress database. Has anyone experienced something like this? Any solution for this problem?

Thanks

Jagannathan Santhanam

View 25 Replies View Related

Problem: SSIS Package Failure Using 32-bit DTExec And 64-bit DTExec

Apr 17, 2008

Hi all,


I have a serious problem with my SSIS Package while executing using 32-bit DTExec and 64-bit DTExec.


Here are the details:

Environment:

Windows Server 2003 64-bit (Build 3790: Service Pack 2)
SSIS 32-bit & 64-bit installed
SQL Server 2005 (Microsoft SQL Server 2005 - 9.00.1399.06 (X64) - RTM)

SSIS Package details (compiled in 64 bit)

Script tasks only
Microsoft Visual Basic .NET (using TRY...CATCH block)
PreCompileScriptIntoBinaryCode = TRUE
Run64BitRunTime = TRUE

Execution

Batch file that uses DTExec to execute the Package.

SCENARIO
I am trying to exeucte the above SSIS package using both 32-bit and 64-bit DTExec to make it failure by providing invalid connection string. Here are the details,


Wrong connection String using 32-bit Execution

While establishing the connection the error message has been nicely captured in to my Exception block and writes into the log file.

Wrong connection String using 64-bit Execution

While establishing the connection the error has not been catpured anywhere (although I have TRY CATCH block) and it haults there itself with the message "Process is terminated due to StackOverflowException". Later I found that the error is due to the connection string along with the unhandled exception.

Please suggest any one of the following my findings, also if you have any other advice would be very much appreciated.

1. Shall I go ahead and fix the issue by handling those unhandled errors? (e.g Appdomain, application). I tried several but still not working using 64-bit DTExec.

2. Shall I go ahead and use 32-bit DTExec to execute the package? If so, is there any other major issue...like performance or anyother bug?


P.S: We cannot apply any service pack for SQL Server 2005 at the moment. Sorry abt it. If you have any specific hotfix for DTExec (without affecting SQL Server) then we can decide.

Sorry for the lengthy one and Thanks very much for you help in advance .



Thanks again!

Suresh






View 13 Replies View Related

Package Runs Fine From BIDS But Dtexec On Same Box Gives Insufficient Product Level Error

Mar 16, 2006

Running eval. edition of Sql Server Standard 2005. "Insufficient product level" error is thrown during validation phase of an OleDBCommand data flow task. This task type is not licensed in Sql Server 2005 standard? The component runs a very simple sql update statement against a one row table in Sql Server 2005.

If it works from BIDS, should it not work from dtexec.exe on the same box?

Does dtexec run under the security context of the logged in user?

Thanks,

Ken

View 6 Replies View Related

Dtexec Problem For Excel Source -- Runs Fine Using Execute Package Utility

Mar 3, 2008

I have this problem executing an SSIS pkg using dtexec.



dtexec /f d:smappsssis_pkgsdts_SOAR.dtsx /REP E





Code Snippet

Started: 10:28:58 PMEnd Error



Error: 2008-03-03 22:28:59.00

Code: 0xC0202009

Source: dts_SOAR Connection manager "SourceConnectionExcel"

Description: An OLE DB error has occurred. Error code: 0x80040154.

An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".

End Error

Error: 2008-03-03 22:28:59.00

Code: 0xC020801C

Source: Data Flow Task Source - CHANNEL_DATA [1]

Description: The AcquireConnection method call to the connection manager "SourceConnectionExcel" failed with error code 0xC0202009.


Code Snippet







However, it runs fine when I double click the package and execute it using the Execute package utility. That really puzzles me.


The package transfers data from worksheets in excel to SQL Server 2005 DB.

Both source and destination are on the same system.
Please advise.

View 4 Replies View Related

Problem With SSIS (dtexecui?) After Sp2

Nov 12, 2007

I installed SP2 yesterday on our production server. I had some
problems with that but it seemed to have installed so that the Datbase
engine and the Integration Services is patch at least.

But after the update we can no longer bring up the "properties" of
SSIS packages. If we connect to the integration service and choose run
package the GUI just wait for a while and then nothing happens. We get
an error in the event log thou ..


Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 2007-11-12
Time: 10:51:07
User: N/A
Description:
EventType clr20r3, P1 dtexecui.exe, P2 9.0.242.0, P3 45cd726d, P4
microsoft.sqlserver.manageddts, P5 9.0.242.0, P6 45cd7534, P7 21, P8
14, P9 qg0f5oshpmqbs2pm34uokrbhqqrfhscr, P10 NIL.


Anyone can make any sense of that?

If we open a package that we have scheduled in the SQL Agent we get an
error messages saying "No description found" .. really strange stuff
is going on here ..?

Please, any help would be appreciated ..

View 8 Replies View Related

SQL Server Agent And X64 Using OraOLEDB.Oracle.1: Dtexec From Cmd Works, But Job Fails

Aug 16, 2007

I am extracting data from an Oracle database and have installed the latest x64 ODAC. When I run the 64 bit dtexec in cmd the package runs fine with no errors, but when creating and executing a SSIS job in the agent it fails. I've tried creating the job using CmdExec as well and I get the same errors:

Microsoft (R) SQL Server Execute Package Utility
Version 9.00.3042.00 for 64-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 11:12:43 AM
Error: 2007-08-15 11:12:45.63
Code: 0xC0202009
Source: Load Dimension Data Connection manager "ora"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x800703E6.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x800703E6 Description: "Invalid access to memory location.".
End Error
Error: 2007-08-15 11:12:45.65
Code: 0xC020801C
Source: CopyCustomers CustomerSource [1]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "ora" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
End Error
Error: 2007-08-15 11:12:45.65

The CmdExec job step uses the _exact_ same command as the one I execute successfully in cmd:
"c:Program FilesMicrosoft SQL Server90DTSBinnDTExec.exe" /FILE "C:PackagesLoad Dimension Data.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW


I have managed to find two work arounds, but they are quite ugly:

1) Schedule the package execution using Windows Task Scheduler, basically create a bat file which runs the package.
2) Schedule the package in SQL Server agent, but as T-SQL script and use xp_cmdshell, i.e. EXEC xp_cmdshell 'dtexec /FILE "C:PackagesLoad Dimension Data.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW'

Both work and use the 64 bit dtexec. Not that elegant though..

CmdExec and the 32 bit version of dtexec works, but is not good enough for me since we bought new hardware and 64 bit software just to be able to address more memory. Has anyone managed to execute a SSIS package successfully using the agent and the 64 bit OraOLEDB.Oracle.1?


Any help would be greatly appreciated. Thanks!

Btw, I am using Windows Server 2003 x64 and SQL Server with SP2.

View 9 Replies View Related

Execute DTExec Without Installing SSIS !!!!!!!

Apr 5, 2007

Hello :

On my server, I did not install the SQL Server 2005, I have SQL server 2000, thus I did not install Integration Services.

I want to execute one package by line of command DTExec.

I need what to execute this command without installed SSIS?

Thank you.

View 4 Replies View Related

Only One SSIS Job Runs...

Feb 12, 2007

Hi,

Currently I have two SSIS jobs on my machine. The problem I'm having is, only one of the jobs executes succesfully, the other one fails for incorrect user login. Both jobs use the same configuration database and all the packages on both jobs have the protection level set to "DontSaveSensitive". Both jobs have been deployed in the exact same manner, yet only one succeceeds and the other fails.

Can anybody tell me why this is going on?

View 2 Replies View Related

Error Running SSIS Pkg From Dtexec Utility

Feb 21, 2008

Hi All,

I developed my package in BI studio and tested runnning it through BI. Now when i have to deploy the package to main server it will be executed via batch job. This package requires an input file name too.
Now when i am trying to run the package on my loacal box using following command on command prormpt i get error given below.

COMMAND USED BY ME: DTExec /FILE 'C:ProjectIntegrationServicesSFRIntegrationServicesinpkgSFRLocation.dtsx' /SET Package.Variables[InputParamFileName].Value;'C:DataDumpInputLOC00022'

ERROR MESSAGE:
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.1399.06 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

Started: 1:29:54 PM
Error: 2008-02-22 13:29:54.96
Code: 0xC0011007
Source: {9B1FAA88-A6FA-44CF-A2E2-DB3F737FDA65}
Description: Unable to load the package as XML because of package does not ha
ve a valid XML format. A specific XML parser error will be posted.
End Error
Error: 2008-02-22 13:29:54.96
Code: 0xC0011002
Source: {9B1FAA88-A6FA-44CF-A2E2-DB3F737FDA65}
Description: Failed to open package file "'C:ProjectIntegrationServicesSFR
IntegrationServicesinpkgSFRLocation.dtsx'" due to error 0x800700A1 "The speci
fied path is invalid.". This happens when loading a package and the file cannot
be opened or loaded correctly into the XML document. This can be the result of
either providing an incorrect file name was specified when calling LoadPackage o
r the XML file was specified and has an incorrect format.
End Error
Could not load package "'C:ProjectIntegrationServicesSFRIntegrationServices
inpkgSFRLocation.dtsx'" because of error 0xC0011002.
Description: Failed to open package file "'C:ProjectIntegrationServicesSFRInt
egrationServicesinpkgSFRLocation.dtsx'" due to error 0x800700A1 "The specifie
d path is invalid.". This happens when loading a package and the file cannot be
opened or loaded correctly into the XML document. This can be the result of eit
her providing an incorrect file name was specified when calling LoadPackage or t
he XML file was specified and has an incorrect format.
Source: {9B1FAA88-A6FA-44CF-A2E2-DB3F737FDA65}
Started: 1:29:54 PM
Finished: 1:29:54 PM
Elapsed: 0.047 seconds

PLease let me know solution to creating batch job for executing this pkg with input param.

View 4 Replies View Related

Run SSIS Package With Alternate Configuration Via DTEXEC?

Jan 31, 2008

It looks like you can run an SSIS package via the DTEXEC command. You can also specifiy a configuraiton file flag on the command. Is there anyway to specify a configuraiton filter if you stored it into a table vs and xml file?

View 1 Replies View Related

Error Executing SSIS Package With DTEXEC Utility

Feb 29, 2008

Hi All,

I developed my package in BI studio and tested runnning it through BI. Now when i have to deploy the package to main server it will be executed via batch job. This package requires an input file name too.
Now when i am trying to run the package on my loacal box using following command on command prormpt i get error given below.

COMMAND USED BY ME: DTExec /FILE 'C:ProjectIntegrationServicesSFRIntegrationServicesinpkgSFRLocation.dtsx' /SET Package.Variables[InputParamFileName].Value;'C:DataDumpInputLOC00022'

ERROR MESSAGE:
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.1399.06 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

Started: 1:29:54 PM
Error: 2008-02-22 13:29:54.96
Code: 0xC0011007
Source: {9B1FAA88-A6FA-44CF-A2E2-DB3F737FDA65}
Description: Unable to load the package as XML because of package does not ha
ve a valid XML format. A specific XML parser error will be posted.
End Error
Error: 2008-02-22 13:29:54.96
Code: 0xC0011002
Source: {9B1FAA88-A6FA-44CF-A2E2-DB3F737FDA65}
Description: Failed to open package file "'C:ProjectIntegrationServicesSFR
IntegrationServicesinpkgSFRLocation.dtsx'" due to error 0x800700A1 "The speci
fied path is invalid.". This happens when loading a package and the file cannot
be opened or loaded correctly into the XML document. This can be the result of
either providing an incorrect file name was specified when calling LoadPackage o
r the XML file was specified and has an incorrect format.
End Error
Could not load package "'C:ProjectIntegrationServicesSFRIntegrationServices
inpkgSFRLocation.dtsx'" because of error 0xC0011002.
Description: Failed to open package file "'C:ProjectIntegrationServicesSFRInt
egrationServicesinpkgSFRLocation.dtsx'" due to error 0x800700A1 "The specifie
d path is invalid.". This happens when loading a package and the file cannot be
opened or loaded correctly into the XML document. This can be the result of eit
her providing an incorrect file name was specified when calling LoadPackage or t
he XML file was specified and has an incorrect format.
Source: {9B1FAA88-A6FA-44CF-A2E2-DB3F737FDA65}
Started: 1:29:54 PM
Finished: 1:29:54 PM
Elapsed: 0.047 seconds

PLease let me know solution to creating batch job for executing this pkg with input param.

View 8 Replies View Related

Saving SSIS Results To Log Or Text File Using Dtexec

Jun 5, 2006

Hi,

How to save the SSIS package results to log file using dtexec command............please help regaridng this...........



Thanks in advance,

View 5 Replies View Related

Running SSIS-packages In Stored Procedure Using Dtexec

Apr 2, 2008



Hi,

I'm running several SSIS-packages in stored procedure using dtexec. Actually, there is a software that is running the procedure, but that's not important here.

The problem: if some of the packages failes, the whole procedure does not fail and I don't know if all the packages are successfully completed.

Here is a sample list of ssis-packages from procedure:


exec xp_cmdshell 'dtexec /f "E:SSISSourcedataSourcedataaaa.dtsx"'

exec xp_cmdshell 'dtexec /f "E:SSISSourcedataSourcedatabb.dtsx" '

exec xp_cmdshell 'dtexec /f "E:SSISSourcedataSourcedataccc.dtsx"'

exec xp_cmdshell 'dtexec /f "E:SSISSourcedataSourcedataddd.dtsx"'

exec xp_cmdshell 'dtexec /f "E:SSISSourcedataSourcedataeee.dtsx"'


So, if eg bbb.dtsx would fail, is it possible to get the whole procedure failing?

View 5 Replies View Related

Usage Of Dtutil And Dtexec In SQL Server 2005 SSIS

Nov 22, 2006

1) We are migrating data from SQL Server 2000 to 2005 DB.

2) We are developing SSIS packages in client, build, deploy and install and copying to SQL Server 2005 server to execute for migration.

3) For this we encrypt all packages with password, then decrypt all while executing in a batch file using dtexec. This works fine.

4) What does not work is executing a master execute task in which are individual execute tasks. This is so since the other packages are still encrypted.

5) We decrypted them separately first using dtutil using Decrypt and Copy/Move option but while executing error is thrown that these other packages are still protected by password.

6) Do we need to decrypt, then encrypt using default package protection level and then decrypt again.

7) How exactly to just execute a master package when packages are developed on client.

View 1 Replies View Related

An SSIS Job Runs Synchronous Or Asynchronous?

Mar 19, 2008

Porting an existing SQL 2k DTS job over to a SQL 2k5 SQL Server running SSIS.

Background:
The job loads data into an empty work table and performs some work before clearing out the work table.
This job runs every minute.

Question:
If the job happens to take longer than a minute, does SSIS create a second instance of the job?
Or perhaps it does what DTS did and reschedules the job for the next iteration?

Concern:
I need to know because there would be key contraint violations if another instance of the job started before the working table was cleared out.

Thanks in advance


View 1 Replies View Related

SSIS Package Runs Slowly

Mar 13, 2008



Hi,
I need to transfer the data in A table on a 2005 instance to B table which has the same structure as A table on a 2000 instance. There are 200,000 records in A table. If I use <insert B select * from linkedserver.....>, it takes only 30 seconds. I create a SSIS package to do this. But it is very slow. After it runs 10 minutes I have to stop it. And I find that it transfers about 100 records every second. Then I change the source server and destination server. That is transferring the same data from the 2000 instance to the 2005 instance. It takes only 50 seconds. why? How to make the package used for transfer data from the 2005 instance to the 2000 instance run fast?

Thanks!

View 8 Replies View Related

SSIS Runs Locally, But Not On Server - Help!

Aug 4, 2006

My team is using SqlServer 2005 SSIS to develop package for Consolidated Views. This works fine on my machine in Visual Studio when they run it as a script from command prompt from their desktop. However, when they move this package to ETL box, the package runs fine Visual Studio environment but fails when run from the script with the errors:


Started: 12:57:45 PM
Error: 2006-08-04 12:57:45.87
Code: 0xC0011007
Source: {519D338B-8874-40A8-A385-0D53E868A57C}

Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted.
End Error

--
Error: 2006-08-04 12:57:45.87
Code: 0xC0011002
Source: {519D338B-8874-40A8-A385-0D53E868A57C}

Description: Failed to open package file "C:SM_BI_EXTRACTS_SHAREDSharedInt
egrated ViewsIntegrated ViewsCV_Product.dtsx" due to error 0x800C0006 "The system cannot locate the object specified.". This happens when loading a package a nd the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
End Error

--
Could not load package "C:SM_BI_EXTRACTS_SHAREDSharedIntegrated ViewsIntegrated ViewsCV_Product.dtsx" because of error 0xC0011002.

Description: Failed to open package file "C:SM_BI_EXTRACTS_SHAREDSharedIntegr
ated ViewsIntegrated ViewsCV_Product.dtsx" due to error 0x800C0006 "The system cannot locate the object specified.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
Source: {519D338B-8874-40A8-A385-0D53E868A57C}
Started: 12:57:45 PM
Finished: 12:57:45 PM
Elapsed: 0.016 seconds

C:SM_BI_EXTRACTS_SHAREDShared>rem "C:Program FilesMicrosoft SQL Server90DT
SBinndtexec" /f "C:SM_BI_EXTRACTS_SHAREDSharedSSISIntegratedViewsIntegrat
edViewsCV_Sales_Rep.dtsx"

C:SM_BI_EXTRACTS_SHAREDShared>rem "C:Program FilesMicrosoft SQL Server90DT
SBinndtexec" /f "C:SM_BI_EXTRACTS_SHAREDSharedSSISIntegratedViewsIntegrat
edViewsCV_Sales.dtsx"

Can someone help us understand the problem? We are new to SSIS. We also want to know exactly what needs to be on the Server that will be running our SSIS ETL programs (that is, what components of SSIS -- SQL Server 2K5 is already loaded).

We are using SQL 2005 on Dell Servers running Win 2003, with the latest service packs. Microsoft SQL Server Integration Services Designer Version 9.00.2047.00

View 2 Replies View Related

SQL 2012 :: SSIS Dtexec Return Code 5 Error In Cluster

Apr 18, 2014

We made SSIS package in dev environment in windows 2008R2 and SQL server 2012. Same packages were placed on SAN disks in cluster environment and are invoked with security contexxt of admin user and wih dtexec utility ( we call this using an sp). rarely but procedure completed i see the log text file by SSIS package and find the return code 5 means package is unable to load. i canst found what are the exact reasons for return code 5.

View 2 Replies View Related

Saving Passwrod In SSIS | Error When Using Command Line Dtexec.exe

Sep 13, 2007

Hi All,

In one of my SSIS package (which connect to DB2) i save the DB2 username and password in SSIS packge itself by using option "EncryptAllWithPassword".
When I try to run the packge using dtexecui.exe it works perfectly fine. It prompts me for package password and then run fine.

Now I am trying to run it using command line dtxece.exe and i get fooolwoing error. Please suggest and help!!!
DTExec.exe /FILE C:pkgDB2Load.dtsx /CONFIGFILE C:ConfigpkgConfigMaster.dtsConfig /Decrypt mypassword /CHECKPOINTING OFF /REPORTING EWCDI

Error Message:
----------------------
Description: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "IBM OLE DB Provider for DB2 Servers" Hresult: 0x80040E21 Description: " SQL30082N Attempt to establish connection fa
iled with security reason "17" ("UNSUPPORTED FUNCTION"). SQLSTATE=08001
"



Thanks
Sid

View 1 Replies View Related

EncryptSensitiveWithPassword Protection Option Cannot Be Used With DTexec Execution Of SSIS Packages

Nov 6, 2006

Our SSIS packages use the Web Service Task to call services to send email and write package failure data to a department wide database. These Web Service Calls are failing with HTTP 401 errors. It was caused by the passwords for the HTTP connections not being saved when the SSIS pkgs were saved to .dtsx files. I have tried saving the package with a password and the EncryptSensitiveWithPassword protection option. This password can be supplied when the package is called from another package or a package is executed in Visual Studio but cannot be supplied to DTexec to execute the package in a job. DTexec does have a /Password parameter but it is rejected if the package is loaded from a .dtsx file.
This appears to be a bug in DTexec. It only accepts the /Password parameter when the package is loaded with the /SQL option. Specifying /Password and /File is not supported.

Is this a known bug? Are there any workarounds?
Has anyone successfully called a Web Service from SSIS executed via DTexec?

View 1 Replies View Related

Job Running SSIS Package Keeps Failing But The SSIS Package By Itself Runs Perfectly Fine

Aug 30, 2006

Hey, I've a few jobs which call SSIS packages. If I run the SSIS package, it runs fine but if I try to run the job which calls this package, it fails. Can someone help me troubleshoot this issue? None of my jobs that call an SSIS package work. All of them fail.

Thank you

Tej

View 7 Replies View Related

Using SSIS For ETL From Oracle 10g ODS Into Oracle DW And From There Into SSAS Cubes

May 2, 2007

Hi,





This might seems a little 'out there', but has anyone tried doing ETL from an Oracle 10g ODS into an Oracle 10g DW, and from there into SSAS2005 cubes?



Any caveats houghtscomments on doing this?



Thanks,

JGP

View 1 Replies View Related

SSIS Package Runs Fine Except As A Scheduled Job

Mar 14, 2006

I have an SSIS package created from a SQL 2000 DTS using the Migration Wizard. The package imports data from a MySQL database to a SQL 2005 64-bit database running on 64-bit windows server 2003. The package runs fine when executed from SQL Server Management Studio but when I schedule it as a job it fails with:

Executed as user: [the domain admin account]. The package execution failed. The step failed.

I've tried a lot of different ways to make this work including creating a new SSIS package. Again, the package ran fine except when it was scheduled as a job.

Any ideas would be appreciated.

thanks!

View 20 Replies View Related

SSIS Job Runs Great Manually, But Not Using SQL Agent

Oct 16, 2006

I am using SQL 2005.  I have created a SSIS package that basically executes another SSIS package (as part of a larger package) .  It runs fine in SSBIDS but will not run if I save it and schedule it using SQL Agent.   I should mention I am using a domain/admin account with SQL Agent, so I don't think that is the problem.

When I execute the job in SSBIDS, the Execute Package Utility window pops up, at which point I click on the Execute button, the job runs successfully and then I click on the close button. 

I suspect it is not running via SQL Agent because of the user intervention required to complete the task (i.e. clicking on execute as described above).  Is this correct?  If so, is there a way to override the requirement for any user intervention.  Or, could it be from something else?

 

 

Thanks for any insight.

 

View 2 Replies View Related

SSIS Package Runs In Development Studio But Not As A Job

Jul 10, 2006

When I run a package I created in the development Studio it runs fine but if I create a job and run it I get an error "The AcquireConnection method call to the connection manager "ODS" failed with error code 0xC0202009"



I have the package setup to use a XML config file and it works fine on all the other packages but this one will not work.

View 6 Replies View Related

SSIS Runs Out Of Temp File Names

Apr 24, 2007

Hi,



A collegue of mine is having some issues. I hope someone can help
















Hi all,

This is my first call for technical assistance so go easy on me.

I'm having a problem in one of my SSIS packages. In brief, the process involves copying the rows from an untyped table to a typed table. There are about 45,000 rows in this table and during the copy ("OLE DB source" to "OLE DB destination") the process appears to hang for about 5 minutes eventually crashing with a "The buffer manager could not get a temporary file name. The call to GetTempFileName failed."

After several attempts using all the trace info I could master this is the order of events with some interesting numbers and facts:

1. The SSIS package goes swifty through "Validation", "Prepare for Execution" and "Execution" in less than 1 second, with "Execute phase is beginning" being the last message on the "Progress tab".

2. Using Performance counters I note that in the next 5 mins the values for "BLOB bytes read" slowly rises and then after a couple of mins so does ""BLOB files in use" the latter reaching a figure of 65534

3. When this figure is reached, SSIS starts creating thousands of zero-size files with the name DTS####.tmp (where #### is hex e.g. DTSB4C1.TMP) in the TEMP folder (C:Documents and Settings<username>Local SettingsTemp in my case).

4. When I started running this package there were 130 files in my TEMP folder; As soon as the combined total of files in TEMP reaches 65664 (i.e. 65534+130), SSIS starts producing the errors list which includes the one I listed above and eventually it clears the TEMP folder down to the original 130 files.

5. My conclusion (thus far) is that SSIS creates all these 1000s of tmp files but in my case hits some kind of maximum (either a folder limit or runs out of hex combinations for the file names) and then crashes.

6. The only thread I found on the internet suggested setting up an environment variable "BLOBTempStoragePath" and assigning a value of "C:Temp1;C:Temp2;C:Temp3;C:Temp4" so that SSIS can span across a number of "temporary" folders instead of the 1 default folder contained in the "TEMP" environment variable.

7. Setting the above environment variable in Windows 2000 did not work for me (tried it as both a user variable and a system environment variable). So here are the facts so far - ANY assistance will be hugely appreciated - I have no idea why all these temporary files are being generated - I have created SSIS packages handling data sets 10 times bigger than this one without these problems so I don't think it's size related.

View 3 Replies View Related

A Procedure Runs Slow As A Job But Runs Fast Executed In A Query Window

Apr 23, 2008

Performance issue.


I have a very complex Stored Procedure called by a Job that is Scheduled to run every night.
It's execution takes sometimes 1 or 2 hours and sometimes 7 hours or more.

So, if it is running for more than 4 hours I stop the Job and I run the procedure from a Query Window and it never takes more than 2 hours.

Can anyone help me identify the problem ? I want to run from the Job and not to worry about it.

Some more information:
- It is SQL 2000 Enterprise with SP4 in a Cluster (It happens the same way in any node).
- The SQL Server and SQL Agent services run using a Domain Account that have full Administrative access.
- When I connect to a Query Window I also use a Windows Account.

- There is no locks or process bloking or being blocked while the job is running.
- Using the Task Manager the processor activity is ok, no more than 30 % in any processor.

View 15 Replies View Related

Any Clues Why DTExec.exe Is Slower Than Business Intelligence Studio(SSIS Shell)?

Sep 18, 2006

All,

I have a simple package in SSIS that reads approx 2.5million rows from SQL2k5 source and exports it into 4 Foxpro files.
The way I do it is as below
1) use and oledb source to read data from SQL2k5
2) use a conditional split component to divide the source into 4 streams ( I do a recId % 4 = 0, 1, 2, 3 to give 4 streams)
3) use an OLEDB destination to export to the 4 prexisting foxpro tables.

This thing runs amazingly fast when I run(F5) it from Business Inteligence studio, but it is atleast 10 times slower when rightclick the package and execute using dtexec.exe

I can't figure out why! any clues??

I would elimiate the 64 bit /32 bit problems because export to foxpro only works in 32 bit mode and my package has been configured to run in 32 bit mode.

Appreciate any insights

Thanks,
Saptagiri Tangudu
PNT Marketing Services



View 13 Replies View Related

SSIS Package Runs Fine; SQL Job Fails (DBF Involved)

Jun 14, 2007

I have created an SSIS package which, as its 2nd step, picks up a .dbf table and does a Data Flow Task of putting the .dbf table into a SQL Server 2005 table (which was just truncated in Step 1).



The Connection Manager that works on the .dbf table is Native OLE DBMicrosoft Jet 4.0 OLE DB Provider.



The entire SSIS package runs perfectly when i run it from my development environment.



I then assigned this Package to a SQL Server 2005 Job. The entire package is the sole step of the job.



But when I run the SQL Job, the Job fails immediately on Step 2.



Here is the error message in View History of the SQL Job:

-----------------------------------------------------------------------------

Executed as user: DBASE01SQLExec. ...on 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:48:37 AM Progress: 2007-06-14 11:48:37.91 Source: DBF to ScanUS_Process Validating: 0% complete End Progress Progress: 2007-06-14 11:48:37.91 Source: DBF to ScanUS_Process Validating: 33% complete End Progress Error: 2007-06-14 11:48:37.91 Code: 0xC0202009 Source: DBF to ScanUS_Process ScanUS DBF Output File [1] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E37. End Error Error: 2007-06-14 11:48:37.91 Code: 0xC02020E8 Source: DBF to ScanUS_Process ScanUS DBF Output File [1] Description: Opening a rowset for "scanus_process" failed. Check that the object exists in the database. End Error Error: 2007-06-14 11:48:37.95 Code: 0xC004706B Source: DBF to ScanUS_Process DTS.Pipeline Description: "component "ScanUS... The package execution fa... The step failed.

-----------------------------------------------------------------------------



Could someone suggest why this works OK within SSIS but not when the SSIS Pakcage is called from SQL?



thx very much/spirits.



seth j hersh

View 7 Replies View Related

SSIS Package Runs Slow On Virtual Server

May 24, 2008

I am using SSIS packages for data transfer, When i run the package on virtual server it takes more time as when run on a PC. After analysing i found that Package when run on Virtual server takes time in startup around (50 sec) or so.Could anyone help me with a little bit of detail description as to why it runs slow.

View 10 Replies View Related

SSIS Package Failing When Run As A Job But Runs Fine In BI Studio

Sep 12, 2007



I'm at a bit of a loss. I've written a package that has about a dozen data flow tasks and each one loads data from text files into tables in a db. It's possible that some of the fields in the text files may have data that would need to be truncated upon insert into the db.

In the data flows, I've set the fields in the data sources I know this could happen to to ignore truncation errors. When I run this within BI Studio, everything works fine. I then loaded the package into the SSIS store on the db server and if I attempt to run it from the SSIS store or if a job executes it, the package appears to be failing because of these truncation errors that I've told it to ignore.

Am I missing something? Thanks!

View 7 Replies View Related

SSIS Package Runs OK Manually But Not From SQL Server Agent...Permissions?

Dec 19, 2007

I have a problem where I have an SSIS package (SQL Server 2005) that won't run properly from SQL Server Agent, but it runs fine when kicked off manually from Integration Services -> Run Package or when run in debug from Visual Studio.

The first step in the package checks for the existance of a file via a script task. The script looks like this...





Code Block
Public Sub Main()

Dim TaskResult As Integer
Dim ImportFile As String = CStr(Dts.Variables("BaseDirectory").Value) + CStr(Dts.Variables("ImportDirectory").Value) + CStr(Dts.Variables("ImportFile").Value)

If Dir(ImportFile) = "" Then
Dts.TaskResult = Dts.Results.Failure
Else
Dts.TaskResult = Dts.Results.Success
End If

Return

End Sub






This script runs fine and the file is seen as expected when I run the package manually. But as a step in a SQL Server Agent job, it doesn't see the file.

The SQL Server Agent service is set to start up / log on as a Local System Account. I've also tried setting up a credential / proxy (using an account that I know can see and even move / rename the file) to run the job as but that didn't seem to help.

The package is being run from SQL Server (stored in MSDB) and is set to rely on SQL Server for sensitive information, so I don't think that's an issue; other packages are set up like this in terms of sensitive data and run fine.

Any ideas why my script can't "see" the file I'm looking at when it's kicked off by SQL Server agent? I've looked and looked...I can't seem to figure this out. I would really appreciate any help you might be able to offer up.

View 12 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved