I have created a package that do a file search on an AS400 box using activex scriptand UNC path to do the file search. When I run it locally, it's fine. When I run it on the server, it fails. The login setup for the sql server agent service and the job is the same and they both have admin rights.
In addition, I also have another package pointing to the same path, but the job is to create a text file to the UNC path. It works even when I schedule it.
May someone please help me to solve this problem ?
My database resides on my ISP SQL server, in Colorado. My new data can be found as a TXT file on the C: drive of the shipping PC in my Florida office. I created a DTS package to import the data from the TXT file to a table in my database. The package works fine, until I schedule it to run. The package uses the UNC address to find the TXT file. As a result, I can go to any PC in my office and execute the package. But, when I schedule it to run unattended, it fails.
I have a package that has its source as an Oracle DB on another server. This package will feed data from that source to a SQL Server 2005 DB. So far, the package works fine if it is executed manually even in SQL Mgmt Studio. It's only failed when I tried it as a scheduled job. I guess I need to do "Package Configurations" which includes the UserID and password for accessing Oracle DB ... but I don't know how. Please help.
Regards,
dnncpt
----------------------------------
Here is the error message:
Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted 05/08/2007 09:49:00,DataFeed,Error,0,<MyDBServer>,DataFeed,(Job outcome),,The job failed. The Job was invoked by Schedule 8 (Schedule DataFeed Grant Tables). The last step to run was step 1 (DataFeed Grant Tables).,00:00:02,0,0,,,,0 05/08/2007 09:49:00,DataFeed,Error,1,<MyDBServer>,DataFeed,DataFeed Grant Tables,,Executed as user: <MyDBServer>SYSTEM. ....3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:49:00 AM Error: 2007-05-08 09:49:00.81 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTSassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2007-05-08 09:49:01.86 Code: 0xC0202009 Source: AWARDS Connection manager "SourceConnectionOLEDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x80004005 Description: "ORA-01005: null password given; logon denied". End Error Error: 2007-05-08 09:49:01.86 Code: 0xC020801C Source: Feed data t... The package execution fa... The step failed.,00:00:02,0,0,,,,0
I've managed to get the basics coded into my package. Nothing fancy, it is all quite literally embedded inside the package. No config files, parameters, variables, etc. I've imported the package into SSIS. I can right click on the package and select Run Package. The package fires off, validates, runs through the entire process, and completes successfully. However, when I set up the package to run as a scheduled task, it fails almost immediately with the following output.
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: 3:28:07 AM Error: 2007-04-25 03:28:07.41 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTSroperty" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2007-04-25 03:28:11.36 Code: 0xC001602A Source: Package Connection manager "FTP Connection Manager" Description: An error occurred in the requested FTP operation. Detailed error description: The password was not allowed . End Error Error: 2007-04-25 03:28:11.36 Code: 0xC002918F Source: Card10 FTP Task Description: Unable to connect to FTP server using "FTP Connection Manager". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:28:07 AM Finished: 3:28:11 AM Elapsed: 4.297 seconds
I'm pulling my hair out. After several attempts I got the sp_OAMethodto execute without error. Unfortunately the DTS package isn'texecuting. It also isn't returning any error. What could I be doingwrong? Any help would be appreciated.This is theEXEC @hr=sp_OACreate 'DTS.Package', @oPKG OUTPUTIF @hr<>0BEGINEXEC sp_OAGetErrorInfo @oPKG,@src OUT, @desc OUTSELECT hr=convert(varbinary(4),@hr), Source=@src, Description=@descRAISERROR (@desc,16,1)RETURNENDEXEC @hr=sp_OAMethod@oPKG,'LoadFromSQLServer',NULL,@ServerName='CAMDEV 0',@PackageName='TestPkg',@Flags=256IF @hr<>0BEGINEXEC sp_OAGetErrorInfo @oPKG,@src OUT, @desc OUTSELECT hr=convert(varbinary(4),@hr), Source=@src, Description=@descRAISERROR (@desc,16,1)RETURNEND--Execute the pkgEXEC @hr=sp_OAMethod @oPKG,'Execute'IF @hr<>0BEGINEXEC sp_OAGetErrorInfo @oPKG,@src OUT, @desc OUTSELECT hr=convert(varbinary(4),@hr), Source=@src, Description=@descprint @descRAISERROR (@desc,16,1)RETURNEND
I have this SSIS package which just doesn't seem to run when executing as a sql job and I keep getting this error:
"The command line parameters are invalid. The step failed."
I read some of the comments in forums and they were suggesting to verify the command line for the sql job since there is known bug in the command line for sql job.
But that didn't seem to resolve it and the reason could be one of the variable values that I am trying to set.
In this package one of the variables that I am trying to set is the connection string and my command line looks like this
When I try to run this from the command line I get the error as:
Argument " package.variables[User::MetaDataConnectionString].Value;Data Source=[SVRNAME];Initial Catalog=[DBNAME];Integrated Security=True;"" for option "set" is not valid.
I think the issue is in the set parameter where it seems to be intepreting the ;'s in the connection string as part of its command (which I seem to be escaping by putting them in quotes but it seems to be stripping them off)
Has anyone else encountered this issue? Is there any other escape character that I should be using?
I have scheduled a job in Management Studio, but it doesn't work. However, when I run it maually in Visual Studio it works. I have connected an outside server by mapping it to mine. Maybe this is the problem?
I have also tried to configure a linked server, but I cannot find out how to connect my SSIS package to the linked server.
I have an SSIS package that successfully runs a Teradata connection query. However, when I schedule the job to run in the SQL Server Agent I get the following error:
Executed as user: SERVER_NAMEAdministrator. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.   Started: 7:53:26 AM Error: 2015-06-08 07:53:26.78    Code: 0x00000216    Source: Package1 Connection manager "Teradata"
[Code] ....
Why would a connection work in SSIS but not in a scheduled SQL Server Agent job?
Hi , I have an schedueled job which runs a DTS . This job is executing everyday at 2:00 Pm and it transfers data from oracle to the SQl server. In some cases data in Oracle is not ready at 2:00 , sometimes it is ready at 11:00 AM so what I need is to run that Scheduled job from an exe file . I can write a code to run the DTS jobs but the problem in this case is I will lose the History Information I have with my schedueled job.So I need to run The Scheduled job to kep the history . I researched the Internet and all I get is how to create a job but I dont have a clue how to run it . I'm using Visual basic 6 . Thanx .
I have a job that runs a SQL script and creates a flat file. I use an FTP task to send the file to a specific FTP site. The job work beautifully when is is completed in the development environment.
After I build the package and deploy on the SQL server and set it up to run as a job it will not work on the SQL server. The error appears to be in the FTP connection. I get two separate errors:
'Unable to connect to FTP Server using FTP Connection Manager' and
'An Error Occured in the requested FTP operation. Detailed error description: The Password was not allowed'
I have SQLServer 7, and have used Enterprise Manager to schedule local packages. The package that I'm trying to do is run a SQL script on a nightly basis. The problem that I'm having is that I need to be able to install the scheduled script customer box using an installer. I have access to execute command line programs in the installer. Do anyone know if you can schedule local packages (using SQL Scripts) from the command line? Or if a 3rd party application can do this. Any help or direction would be greatly appreciated. I've tried to use sp_add_job and sp_add_jobschedule, but haven't been able to get them to work.
I have a DTS package that consist of approximately 50 steps which pulls data from an as400 and populates a SQL 7.0 database. The package works perfect flawlessly when executed manually but won't run when scheduled.
The DTS package starts but hangs when it tries to connect to the as400, this is where the problem lies. The preceeding steps work fine but they execute against the SQL 7.0 database. I have client access installed on the server and configured. I checked and made sure the SQL server agent service was started and running also,I just can't figure why it works fine manually,but not when scheduled.
Hello. I am using SQL Server Management Studio (SQL 2005) and created a daily backup job. Inside the job, i have an "Operating system" step to copy backuped up files onto another directory. However, the job kept on failing with an error "Executed as user ... Access is denied." With this error, how can i change the user used to execute the job? Thanks.
I'm looking for a way to refer to a package variable within any Transact-SQL code included in either an Execute SQL or Execute T-SQL task. If this can be done, I need to know the technique to use - whether it's something similar to a parameter placeholder question mark or something else.
FYI - I've been able to successfully execute Transact-SQL statements within the Execute SQL task, so I don't think the Execute T-SQL task is even necessary for this purpose.
I have a master package, which executes child packages that are located on a SQL Server. The Child packages execute other child packages which are also located on the SQL server.
Everything works fine when I execute in process. But when I set the parameter in the mater package ExecutePackageTask to ExecuteOutOfProcess = True, I get the following error
Error: 0xC00470FE at DFT Load Data, DTS.Pipeline: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Row Count" (5349).
Error: 0xC00470FE at DFT Load Data, DTS.Pipeline: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "SCR Custom Split" (6399).
Error: 0xC00470FE at DFT Load Data, DTS.Pipeline: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "SCR Data Source" (5100).
Error: 0xC00470FE at DFT Load Data, DTS.Pipeline: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "DST_SCR Load Data" (6149).
The child packages all run fine when executed directly, and the master package runs fine if Execute Out of Process is False.
I have an SSIS package composed of several sequence containers; each of these executes fine if I individually right-click them and select "Execute" - however, when I press F5 (but it did in the beginning) none of them executes :|
I have created a DTS package on a developement server that connects to our Exchange server and downloads customer service e-mail and inserts them into a table. This is done using a VB script.
When I right click on the job and execute it, it runs fine and we can see the mails after they show up in the table.
However, when I schedule the job to run at 15 minute intervals it fails with a vb runtime error. When I copy the job to my personal machine and schedule it, it runs just fine and again we see the mails in the table.
The server has the latest version of the scrrun.dll as well as IE 5.0.
I have messed around with this for 3 days now and have gotten MSFT involved as well.
Anyone seen this before? Any ideas or help will be greatly appreciated.
When I run DTS from SQL Enterprise Manager its running fine.But When I Scheduled it then it takes lot more time. What is the differenace between when we run it from Enterprise manager and run it from Schedule? Why Scheduled DTS running very slow? Is there any solution of it? If anyone know Please replt as soon as possible.
I have created a package that takes a Visual FoxPro .dbf and imports into SQL7. If I run the job, it works fine. If I schedule the job it fails stating that I can't find the .dbf, the same one that it just found when run manually. What gives?
I have a DTS package which when I execute it manually, it executes perfectly. I need to schedule it and therefore had to use the scheduler which would creata a job for the package. The problem is that job. It does not execute; it fails every time. The error message is: Sql server does not exist or access is denied.
I have tried to trouble-shoot by setting up an alias for the server in the client network utility for sql server. I also create a new dsn with the new alias. It still failed with the same error message. I edited the properties of the dts package to connect to the server's ip instead of it's alias or logical name. Still fails.
The package has 15 DTS 2000 tasks that execute sequentially, depending on 15 successes. The 15th task then invokes 11 more DTS 2000 tasks simultaneously which each invoke a mail task on their success. The package is saved as part of a valid project. The entire package is successful executing within Visual Studio -- 37 green boxes. I move the package as file system .dtsx to my database as a stored package within MSDB and then schedule it as a job via SQL Agent invoking the MSDB stored package.
The package has a log file referenced in the scheduled job for errors and diagnostics while each of the 26 Transforms Data Tasks within the DTS 2000 packages writes to a fully qualified exception file on my server. The log and exception files have valid data when the package runs in Visual Studio but the exception files are untouched when the job fails and the log only references one of the 11 dependent steps with a job failed message. SQL tables are updated and files created from the Visual Studio execution but nothing is created when the job fails.
I am assuming there is a disconnect with the way I am moving the package to the scheduled job but I don't know what the problem is. Can anyone help?
Hi,A DTS package which is running fine when execute ,always fails asscheduled job.I read from the previous posts about MS KB article 269074, securityand MDAC, but I don't understand and don't know how to solve it.Please help.My scenerio:SERVER : MS Windows 2000 server is in a PRODUCT DOMAINMS SQL SERVER 7.0 SP2- Agent started up by SYSTEM ACCOUNT andConnection as NT AuthenticationWORKSTATION (Enterprise Manager as Tool to connect MS SQL SERVER andwrite and schedule DTS Package): MS Windows XP connect as NT Authenticationbut in WORKGROUP DOMAINBest RegardsNipon Wongtrakul
I have a large number of SSIS packages, which I have developed over the last few months.
Having written and tested them locally, running in VS05 etc - I have moved them to a server, stored in the MSDB database.
I am having real troubles with packages that move tables from one database to another.
I am working on a migration project, so I have several packages that move tables from the source database, into my staging database.
One package which will not run at all, basically just moves 15 tables from database A on my server to database B.
The package is essentially a few SQL tasks to create tables, then a data flow.
The data flow contains the table movements as an OLE DB source to an OLE DB destination. No intermediate processing.
In an attempt to get some meaningful logs of the reasons for failre I ran the package from the commandline with the output piped to a text file. That text file contained the following error:
Error: 2006-11-20 11:48:47.78 Code: 0xC0202009 Source: Data Flow Task Source - tblParking [1641] Description: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Shared Memory Provider: No process is on the other end of the pipe. ". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Shared Memory Provider: No process is on the other end of the pipe. ". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Shared Memory Provider: No process is on the other end of the pipe. ". End Error Error: 2006-11-20 11:48:47.78 Code: 0xC0047038 Source: Data Flow Task DTS.Pipeline Description: The PrimeOutput method on component "Source - tblParking" (1641) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. End Error Error: 2006-11-20 11:48:47.84 Code: 0xC0047021 Source: Data Flow Task DTS.Pipeline Description: Thread "SourceThread1" has exited with error code 0xC0047038. End Error
I've googled for most of the error messages there, and tried applying some of the things I found.
I've set the commit size on the OLE DB destination to 10k rows.
I've set the number of engine threads to 2.
The SQL Agent service is started by a domain user that has sufficient server and database roles to do what it needs - other packages run fine.
I'm really stumped here now - this package will run perfectly in visual studio, but fails when ran as a scheduled task, and I'd really appreciate any advice or pointers
I'm having problems scheduling a package and using the "Set Values" option. I'm setting a variable value to a connection string for a Connection Manager (I couldn't set it to keep the password using the "Data Sources" tab), however, this raises an error on SQL Server Agent:
Executed as user: SEQM001SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Argument ""Package.Variables[LogDBConnString].Value;Data Source=123.456.789.000;Initial Catalog=myDB;Provider=SQLNCLI.1;Uid=myUser;Pwd=myPassword;Auto Translate=False;"" for option "set" is not valid. The command line parameters are invalid. The step failed.
However, if I copy the command line generated and run it using dtexec, it all goes perfectly fine. Any clue to what's wrong?
Hello, I have put together a simple SSIS package that runs fine both via BIDS and via Mgt Studio. The problem I have is that I can't get a scheduled job to run it. My scheduled job has only 1 step - and that step runs the package.When I right click in Mgt Studio (SQL Agent) and choose "Start Job" I get this error :
------------------------------------------------------------------------------------------ Executed as user: NMR044BRASQL886SYSTEM. ....3033.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 14:10:56 Error: 2007-01-09 14:10:56.50 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Property" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2007-01-09 14:10:57.04 Code: 0xC0202009 Source: B2B_Sales_Territory_Send_Back Connection manager "b2b_datamart" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'NT AUTHORITYANONYMOUS LOGON'.". End Error Error: 2007-01-09 14:10:57.04 Code: 0xC020801C... The package execution fa... The step failed. ------------------------------------------------------------------------------------------
Can anyone help please? I'm new to SSIS so clear+simple answers appreciated.
I have created a DTS package to read data from a SQL Server table and copy it to an Excel file on one sheet. I have tested the DTS package manually and it runs. I scheduled the package but it keeps failing giving the following error message. The path to the Excel file is valid and the SQL server is connected to the server where the Excel file resides.
... DTSRun: Executing... DTSRun OnStart: Copy Data from vw_Symbols to vw_Symbols$ Step DTSRun OnError: Copy Data from vw_Symbols to vw_Symbols$ Step, Error = -2147467259 (80004005) Error string: 'S:Mission Critical EnterprisesCurrent ProjectsJPMC Aperture Rollout 05-100-1-0001Symbol RequestsJPMC - Symbols Added.xls' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. Error source: Microsoft JET Database Engine Help file: Help context: 5003044 Error Detail Records: Error: -2147467259 (80004005); Provider Error: -534774783 (E01FFC01) Error string: 'S:Mission Critical EnterprisesCurrent ProjectsJPMC Aperture Rollout 05-100-1-0001Symbol RequestsJPMC - Symbols Added.xls' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. Error sour... Process Exit Code 1. The step failed.
I have a for each loop that populates from a set of flat files into a Sql Server table, I run the Flat file Import via a dts package embedded into Execute DTS 2000 Task. I want to pass the Sourcefile Name that is fetched by the For Each Loop to assign it Global Variable in DTS. how this can be made ?
I have a SSIS job, one of the last steps it performs is to execute a SQL 2000 DTS package. This has to be done as a SQL 2000 DTS package as it is performing rebuilds of SQL 2000 Analysis Services dimensions and cubes. We've found that when the DTS fails the SSIS job is happily completing showing as a success, we would prefer to know it went wrong.
As far as I'm aware SSIS merely starts the DTS off and doesn't care about it's result. I've taken a look in to turning on the logging for the execute DTS package and thought that the ExecuteDTS80PackageTaskTaskResult would give me the answer I need...but is merely written to the log not available as an event-handler. It also looks like it is not safe to put a SQL task in as the next item to go look at the SQL 2000 system tables to look at the log for the DTS package as the SSIS documentation warns that the DTS package can continue to run after the execute DTS package task has ended.
Ideally I want any error raised within the DTS package to cascade up to be an error in the SSIS job, I can then handle it appropriately. I cannot find a way to do this. Is there a way?
If not, can anyone suggest how in the remainder of the SSIS tasks I can be sure that the DTS has completed before I start any other tasks that will check for the SQL 2000 log of its execution?
I am having problems executing a child package from a parent package using the Execute Package Task. I am attempting to run the master package through a SQL Server Agent job.
The SQL Server Agent job is owned by sa. The step that runs the parent package is configured to load the package from the SSIS Package Store on the same server that the job is running.
I have the Execute Package Task configured as follows:
Location: SQL Server ExecuteOutOfProcess: True Connecting as a SQL Server login (let's say TestEtl)
I have added the db_dtsoperator database role to both the TestEtl login and the login that SQL Server Agent connects through. I have also configured the child package's reader role to include db_dtsoperator. Per http://msdn2.microsoft.com/en-US/library/ms141053.aspx, this should allow these logins to run the child package.
I have enabled logging of all events in both the parent and child packages. I see the following in the logs when the Execute Package Task executes (omitted portions unrelated to the execution of the child package task):
450939 OnPreExecute ChildPackage 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 450940 OnPreValidate ChildPackage 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 450941 OnPostValidate ChildPackage 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 450942 User: Diagnostic ETL 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 ExternalRequest_pre: The object is ready to make the following external request: 'IDataInitialize::GetDataSource'.450943 User: Diagnostic ETL 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 ExternalRequest_post: 'IDataInitialize::GetDataSource succeeded'. The external request has completed.450944 User: Diagnostic ETL 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 ExternalRequest_pre: The object is ready to make the following external request: 'IDBInitialize::Initialize'.450945 User: Diagnostic ETL 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 ExternalRequest_post: 'IDBInitialize::Initialize succeeded'. The external request has completed.450946 User: Diagnostic ETL 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 ExternalRequest_pre: The object is ready to make the following external request: 'IDBCreateSession::CreateSession'.450947 User: Diagnostic ETL 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 ExternalRequest_post: 'IDBCreateSession::CreateSession succeeded'. The external request has completed.450948 OnError ChildPackage 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 Error 0x80070005 while preparing to load the package. Access is denied. . 450949 OnError ParentPackage 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 Error 0x80070005 while preparing to load the package. Access is denied. . 450950 OnTaskFailed ChildPackage 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 450951 OnPostExecute ChildPackage 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 450952 OnWarning ParentPackage 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. 450953 OnPostExecute ParentPackage 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 450954 PackageEnd ParentPackage 2007-06-08 13:35:17.000 2007-06-08 13:35:17.000 End of package execution.
I am sure that what I am doing is quite common, and I obviously have something misconfigured somewhere - but I'm not sure what my misconfiguration is. Can anyone enlighten me?
I have a Local DTS Package that I created that runs fine. I have scheduled it to run daily but it errors out when run it from the agent. This is an excerpt of the error from the Job history.
Delete from Table [Intranet].[dbo].[Employees] Step, Error = -2147217887 (80040E21)
This Local DTS Package, deletes the records in the file and reimports the data from an AS400 file that is recreated for me daily.
The only thing that has occured to me so far is that perhaps the SQL Agent Service Account needs permission to delete the records. (I'm using NT Security).
Am I on the right track or do you think it's something else?
I have a SSIS package that consists of 3 Script Tasks, two Data Flow Tasks. Each script tasks executes a FTP command. The first one renames the file, the second gets the renamed file and third resets it back to original name for testing.
When I run via BIDS or DTSExec all work fine. When I schedule it, only the first script runs. It never downloads the file.
Setup - SQL 2005 SP2, SSIS is running, 32 bit OS, SQL Agent Account is local admin. Package protection level is DontSaveSensitive. PrecompileScriptIntoBinaryCode = True
I found some similar threads and guides but they didn€™t help me with my special problem.
I converted a dts package (built in SQL 2000) to SQL 2005. Right now it€™s a legacy package. (I tried the Tool Microsoft SQL Server 2000 DTS Designer Components to open the package. It€™s going well)
I would like to build a scheduled job which runs this dts package. In SQL 2000 you can right click on the package and create the job. SQL created string like this: Dtsrun ASDFHJKSF56A4DFSLAKDHFJKS65646ASDFHSF (very long sting, it€™s the ID of the dts package)
How can I make something like this in SQL 2005? Where I can get the ID of a dts package from?
Best Regards, Alex
p.s. - I red the thread from Jamie Thomason and will directly mark as answer after I get a answer - of cource I will delete my thread too if I overlooked a thread with the same issue
