I have some familiarity with DTS packages, and find them easy ( generally) to debug as you can run them step by step and simply find the offending step. when they fail they also put a message box with the error in the centre of the screen. My system has recently been updated and now uses DTSX packages. I can open and veiw these in visual studio, but i cannot run them one step at a time, and they dont give a nice error message when they fail. how do you debug a DTSX package, or at least make debugging it a little easier?
I have spent the last couple of weeks going through about 15-20 different examples/tutorials on running DTS packages from inside a C# Windows app (and even asp.net). I must have a mental block, because I can't seem to make it click in my head. I have hundreds of DTS packages saved as .dtsx files. I can double click on them and run them perfectly. What I need to do is be able to run them conditionally from inside a windows app. Could anyone point me to a tutorial or example that could help me with this? I've even looked at some VB source to see if I could work it out, but I keep running up against a wall. I'd appreciate any help anyone can provide.
First off, can you post .dtsx packages to the forum? I always end up cutting and pasting code, which is by is nature incomplete, as it generally has external dependencies (connections, variables).
Perhaps you cannot do so for security reasons?
Second, is there a good blog site that allows you to post .dtsx packages?
I'd rather post .dtsx links than cut and paste code (which half the time formats the code un-recognizably), or even worse, post package xml, which contains the layout information and possibly IL that makes it all but unreadable.
I am trying to build a package that is comprised of 100+ dtsx packages but cannot seem to get it to work. I have created a new connection where the connectionmanagertype = file and the file path is equal to the folder in which my dtsx files are located. I (location = fileSystem). No matter what I do I get an access denied error that shows the folder location but no package. I manually typed the name of the package in the PackageName property and have pasted in the PackageID in the appropriate property as well but I don't see anything in the PackageNameReadOnly. I have read the MSDN information but I don't see a step by step way to build a package of packages against which I can compare. Can anyone set me straight?
I'm experiencing some frustration with my active/passive SQL cluster not running my .DTSX packages. I am hoping someone can shed some light on what I need to do.
I've created some .DTSX packages with the SQL Server Business Intel Dev Studio. I initially built & tested these packages in a non-SQL cluster environment without any problems. I'm now re-creating them to work on our SQL cluster. If I run the package through the Dev Studio it works great.
The packages basically grab .txt files from one of the shared drives (which is a resource of the sql cluster group) and imports the data into the one of the databases. The database does not have any special settings (right-click -> new database... -> enter name -> click ok).
I've setup a SQL Server Agent Job with 1 step with the following properties. Step name: I Offices Type: SQL Server Integration Services Package Run as: SQL Agent Service Account Package source: File system Package: G:ImportRAGFLOffices.dtsx
When I run the SQL Server Agent Job through MSSQL Server Management Studio (right-click -> start job) I get an error on "Execute job 'RAGFL TestJob'".
These are the 2 messages that show up when I view the history of the SQL Server Agent job.
*********************************************************************************************** Date 9/25/2007 1:16:13 PM Log Job History (RAGFL TestJob)
Step ID 0 Server BADBOYS Job Name RAGFL TestJob Step Name (Job outcome) Duration 00:00:01 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message The job failed. The Job was invoked by User sa. The last step to run was step 1 (I Offices). ***********************************************************************************************
*********************************************************************************************** Date 9/25/2007 1:16:13 PM Log Job History (RAGFL TestJob)
Step ID 1 Server BADBOYS Job Name RAGFL TestJob Step Name I Offices Duration 00:00:01 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message Executed as user: THEISLANDAdministrator. The package execution failed. The step failed. ***********************************************************************************************
Based on advice from this board, I am setting up our newly-converted DTSX packages (sql server 2000 (DTS) to 2005 (SSIS) package conversion) to utilize package configurations to make it easier to run them in multiple environments (dev, testing, production, etc...). This seems to be working just fine, but I now have another question.
We have approximately 12 DTSX packages which need to be executed in a specific sequential order. I was wondering what the best / most widely accepted method is to allow for running them as an automated process. If you double click on each DTSX file individually, the "Execute Package Utility" pops up, and you can run the package. I'd like to know the best way for us to be able to run each package, one after the other (each one waiting until the previous one completes before it begins), until they have all processed. It would be nice if it did not rely on SQL Server being installed on the machine on which it is being run...
I have a project with 48 packages. When I press the green button for Start Debug, it seems like Integration Svcs. is re-loading or some type of validation occurs (screen flashes with each package being highlighted in solution manager) for all packages in the project before executing the specific package.
Also, If I close all the packages except one that is to be executed and press the green start debug button, all the packages are loaded before executing the specific package. There is always a delay before the actual package is executed when using the green start debug button.
If I right click on the specific package in solution manager and execute it, the package is executed immeadiately without any delay.
I did not have this issue until I tried to build and deploy the package.
Does anyone know why this happens? When I run one of the packages in my project (by hitting the play button in the designer), all of the other packages in that project open before it starts running?
I have a dtsx package that is calling another dtsx package, however, if the called upon dtsx package fails with errors or what not, then the calling package does not continue as well. Is there any way to override this such that if the called upon package fails, the downstream actions in that package can stop, but the calling packages downstream actions to continue?
I've run into a problem with SSIS packages wherein tasks that write or copy files, or create or delete directories, quit execution without any hint of an error nor a failure message, when called from an ASP.NET 2.0 application running on any other machine than the one where the package was created from. By all indications it appeared to be an identity/permissions problem.
Our application involves a separate web server and database server. Both have SQL Server 2005 installed, but the application server originally only had Integration services. The packages are file system-deployed on the application server, and are called using Microsoft.SqlServer.Dts.Runtime methods. For all packages that involve file system tasks, the above problem occurs.
When the above packages are run using the command prompt (either DTEXEC or DTEXECUI) the packages execute just fine. This is expected since we are using an administrative account. However when a ShellExecute of the same command is called from ASP.NET, the same problem occurs.
I've tried giving administrative permissions to the ASPNET worker process user to no avail.
I have likewise attempted to use the SQL Server Agent job approach but that approach might not be acceptable for our clients since it means installing SQL Server 2005 Database services on the application server.
I have read the relevant threads in this forum, namely http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1044739&SiteID=1 and http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=927084&SiteID=1 but failed to find any solution appropriate for our set up.
We manage some SSIS servers, which has only SSIS and SSIS tools installed on them and not the sql server DB.
SSIS packages and configuration files are deployed on a NAS. We run the SSIS packages through DTEXEC by logging in to the server.
We want to allow developers to run their packages on their own on the server, but at the same time we dont want to give them physical access on the server i.e we do not want to add them into RDP users list on server properties. We want them to allow running their packages remotely on the server.
One way We could think of is by using powershell remoting and we are working on that. But is there any other way or any tool already present for the same.
I have been trying in vain to get a DTSX to return to a vb.net application that it has failed, all i get back is a
ReturnResult = success.
In the dtsx is the following;
Secquence
- Transaction Option set to Required - FailParentonFaluire set to True - FailPackageonFaluire set to True - MaximumErrorCount set to 0
Inside the sequence Container DataFlowTask - Transaction Option set to Required - FailParentonFaluire set to True - FailPackageonFaluire set to True - MaximumErrorCount set to 0
ExecuteSQLTask - Transaction Option set to Required - FailParentonFaluire set to True - FailPackageonFaluire set to True - MaximumErrorCount set to 0
I have run the package from my vb.net application and it runs fine, importing data from a file. I tried running it with a bogus file name that doesnt exsist and it still returned a ReturnResult = success. I need it to return a failed result on any errors, which is what i thought it would do as i have it sey to fail the package on errors throughout each task ... am i missing something ?
I am having more luck editing the dtsx files directly than using configs. Also for documentation purposes this would be helpful as I don't know enough about xml to find or build a tool to create a style sheet for me.
After a while I'm come back to SSIS but a drawback appears.
I€™ve copied from our server a folder which contains a few dtsx on my local folder and when I€™m going to open dtproj and then choose any of them:
Error 1 Error loading 'M_Hac_Modelo187.dtsx' : Error al recuperar un generador de clases COM para el componente con CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} debido al siguiente error: 8000401a.. c:ssishacienda_anualM_Hac_Modelo187.dtsx 1 1 .. .. ..
(I think that is not necessary to translate into english due to simpleness of the message.)
What the hell is happening? I perfectly remember have been doing the same a month ago and I was able to open them without problems.
I have a SSIS-package with Excel Connection Manager that fails on our x64-platform with error: Error: 2006-12-08 06:46:23.77 Code: 0xC0202009 Source: dpd2_philips Connection manager "Excel Connection Manager" 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: 2006-12-08 06:46:23.77 Code: 0xC020801C Source: Copy Data from Blad1$ to dpd2 dbo philips Task Excel Source [107] Description: The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. End Error
It's works fine on my computer (x86) and if I start the package manually on the x64-server. But I noticed that it runs under 32bit (DTExecUI.exe *32 in taskmanager) when it's started manually.
Any idea? The server use dtexec.exe to start the packages. Maybe it runs under 64bit then?
Hello, Please, help me.. I'm trying to execute a packge.dtsx that be save in folder. How can i do, to execute it? I create a job, but always give me errors..
Ok, I'm actually adding a SSIS job to my job agent on my test SQL server. Noticed that when I go to my job agent --> add new job, under the steps option, I click new. this then takes me to the new job step window. When I select
Type as SQL Server Integrated Services, I then see some new tabs at the bottom of the form. Under package source I can select File System, SQL Server, or SSIS Package Store, then I have to select the location of the dtsx file.
So my question is, since I can select the actual file (package) I want to run from here, do I really have to import a package to the file system or MSDB under the SQL Integration Services on the server?
It appears to me that its kind of the same thing.
I'm new to this SSIS, SQL DB work, so I'm learning as I go. . . .
I created a dtsx with my user account and when I had imported it in SQL server I get the following error when trying to execute:
Executed as user TESTGISSYSTEM Failed to decrypt protected XML node, Key not vallid for use in specified state.
Even when I remove the password for the dtsx I still get the same error.
I saw the reply's on this Re: DTSX package will not run from SQL server agent Thread Starter: jschroeder Started: 13 Aug 2007 10:08 PM Replies: 2 but it was no solution for my problem.
When I execute the RSExecutionLog_Update.dtsx, I get an error saying "The task "Set Time period" cannot run on this edition of Integration Services. It requires higher level edition". I am using the Proffesional Edition of SQL2005 and the Integration Services Version is 9.00.1399.00. I have configured the target database RSExecutionLog correctly. Wat could be the problem?
I understand that I can use dtutil to provide a password to encrypt the package. However, when I run the encrypted package, I need to provide the same password in order to run it. Is there a way that I can encrypt the package but allow anybody to run it without providing the password? That is, I want the package to be encrypted so that nobody can load and modify the code in Visual Studio, but I want people to be able to execute it. Is there a way to do this? Similar to generating a exe file?
This is the situation: I've a dtsx package wich creates a tab delimited txt file from a sql server 2005 databasetable. Now this all works just fine. But what I want to do is that the user can choose the destination path of that created txt-file. Right now I've declared the path when I created the flat file source.
On the net I found that a config file for a dts package (sql server 2000 - Dynamic Property Task) could do the trick...
SSIS package created from the wizard couldn't be run from the visual studio editor? The run button is disabled. Is it not possible to run from inside editor as well?
when i start SQL Server business intelligence developer and create new Integration Service project, i will see following error:
Error loading 'Package.dtsx' : Object reference not set to an instance of an object.. C:SairiMy DocumentsVisual Studio 2005ProjectsIntegration Services Project12Integration Services Project12Package.dtsx
this error occures just on my PC and i reinstalled VS2005 and SQL2005 again and unfotunately the problem existes.
please someone helps me (just don't tell me to format my PC!!!)
How dow you schedule a file(.dtsx)(I think it is a package) that was created in the SQL Server BI Design Studio to run? I can locate the file I created in SQL Server Management Studio and see it in the right hand pane and even edit it. I can run it in the Design Studio, but cant see how to do that in Management Studio nor how to schedule it.
This is my first attempt at recreating a DTS package using SQL Server tools instead of the Legacy conversion wizard, and I think my brain has overheated. I just cant find it on the Management Screen or the Design. I am also not searching correctly anymore on books online because I cannot find it.
Thanks for pointing me to where I need to go or do.
