Problem Running SSIS Package As Job On Remote Machine

Sep 28, 2007

Hi,

I have created a SSIS package on my local machine.
I need to deploy this package on a Test Server and it should execute as a scheduled job.

I am not sure of the steps I need to follow and things I need to be careful about.

I have the following doubts:
1) While developing the package, I have referred to the local SQL Server with Windows credentials.
2) The package, once deployed on the Test Server needs to point to the test server database with SQL Server credentials.
3) I know how to create a deployment utility. However, I am not sure if the deployment manifest will run without errors on the remote machine.
4) Even if the deployment manifest executes successfully and deploys the packages, how do I generate a script to create a Job and schedule the package?
5) I am using a File DSN to connect to IBM DB2 database in one of my Data Flow Tasks in this package. How do I configure it automatically on the remote machine? Won't there be any issues with it?

Please help me...

Thanks and Regards,
B@ns


View 5 Replies


ADVERTISEMENT

Ssis Package Hangs On Script Transformation When Running On One Machine Not Developing Machine

May 4, 2007

Help!
I am using Script Transformation to output a new column as image[DT_IMAGE]
field to store serialized object. In the VB script, the sample code as

Row.serializedobject.AddBlobData ( binaryArrayReturnedFromC#dll )

The package always runs fine on my developing machine and will halt on other
machine at AddBlobData after certain number row records were processed. I am
stuck here. Anyone has any suggestion?

What I need is reading data from mutiple tables in one database and writing
into a single table in another datable. In order preserve all the columns
data, I use input column fields to construct a new object and then serialize
it, and store the serialize data into detination db table. (The object and
serialization function is coming from c# dll.)

Dim b As BusinessLicense = New BusinessLicense()
b.ApprovalDate = Row.approvaldate
b.BusinessId = Row.busid
b.BusinessName = Row.busname
b.NaicsCode = Row.naicscode
b.NaicsDescription = Row.naicsdescr
b.OwnerName = Row.ownername
b.Phone = Row.phone
b.Pkey = Row.pkey
b.RenewalDate = Row.renewaldate
b.StartDate = Row.startdate
b.Suite = Row.suite

Row.serializedobject.AddBlobData(Serializer.Serialize(b)) '''----This is blocking line
Row.infoType = BusinessLicense.TYPE



Both machine is xp with sp2. and standard SQL Server 2005 - 9.00.1399.06

Thanks!

View 4 Replies View Related

SQL 2012 :: Can't Execute SSIS Package From Remote Machine

Mar 19, 2013

OS: Windows 2012, standard, 64-bit
SQL: 2012 + SP1 + CU2 = 11.0.3339

We recently decided to "break apart" our BI environment. We used to have everything on one box, DB Engine, SSIS, SSAS & SSRS. Everything has been running fine, but we now have other projects using these services, so we decided to break them apart into their own boxes.

We now have DB Engine on one Server, SSIS & SSRS on another server and SSAS on yet another server, so we now have three boxes that replaced one box. All are Windows 2012, standard, 64-bit with SQL Server 2012 + SP1 + CU2.

Since some of our SSIS packages have to access external resources, we used a domain account for it's service account. The DB Engine and SSAS box are using the default service accounts when installed. I can execute the packages fine on the SSIS server, I can even execute them via SQL Agent jobs on the SSIS box (we did install a default instance of SQL on the SSIS box), however when I try to execute a package from my laptop, it fails with the ugly "Login failed for user 'NT AUTHORITYANONYMOUS LOGON'".

I immediately double checked my SPNs and they all looked correct for the SSIS server and the service account we are using (and we had no duplicates). I also double checked the User Rights Assignment in the Local policy editor and all the correct Rights have been assigned (Log on as a service, Bypass traverse checking, Impersonate a client after authentication).

View 3 Replies View Related

Execute SSIS Package Stored In Remote SQL Server From A Client Machine.

Mar 3, 2006

I have written a VB component to execute a SSIS package stored in SQL server.

I am using the Microsoft.sqlserver.dts.dtsclient, dtsconnection/dtscommand

and executereader and everything works perfect on the local machine. This is descibed in a msdn site .

But my customer have a remote SQL server and want no extra BI clients/SQL server clients etc on the client machine, only an ordinary windows client and network connection to the SQL server.

My question is: Can you still use dtsclient or do you have to do in some other way?

rose-marie

View 4 Replies View Related

Running Ssis Package With A Remote Sql Agent?

Jan 18, 2007

hi all,

thanks for the valuable information all the time!!! saved me a lot of time...

our team developes a system for text data improvement using ssis .

we have a few heavy packages that we want to execute on two separate "SSIS servers" that will be dedicated to runnung these packages only, and repeatedly. the main sql server will be placed on a different server machine .

my question is:

what is the best way to do this?

if we schedule these packages as a job of the Sql Ajent- does that mean that the packages will be executed on the sql server machine (which is not what we want) ? or could we define a remote machine to run the package on, and specify our "SSIS servers"?

or- should we use a simple scedualer on the "SSIS servers" using a dtexec command? but then i loose the benefits in using the sql agent- such as logging, notifications, etc.

do we need to install sqlserver on these "ssis servers"?

thanks for your replies!

View 9 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

Permissions Used To Connect To SSIS On Remote Machine

Jun 27, 2006

We are trying to take advantage of the new Security Context for SSIS but users are unable to connect remotely to the SSIS Service unless they have been added to the Administrators Users Group on the server. I have tried adding them to Guests, Power Users, Remote Desktop Users, Users and SQLServer2005DTSUser$machine but the user is unable to connect.

The message received when the user is unable to connect is:

Cannot connect to 192.x.x.x
Additional Information
-> Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
-> Connect to SSIS Service on machine "192.x.x.x" failed:
Access is denied

What is the list of permissions and privileges that a user that does not belong to the server's Administrator group and have sysadmin server role, must have to allow them to create and run a package through SSIS.

View 6 Replies View Related

Error On Executing SSIS Packages On A Remote Machine Using Code

Apr 10, 2007

Hello all,



I am trying to execute the ssis packages using code.These packages are hosted on remote server under MSDB in local Network.



Below is the code tried to Execute
--------------------------------------------------

DTSExecResult execRslt = _dtsxPackage.Execute();

foreach (DtsError dtserr in _dtsxPackage.Errors)
{
Console.WriteLine("Source: " + dtserr.Source + ", Description: " + dtserr.Description);
}


I get hte following Error
--------------------------------



"Dupaco Load MMAs"-------------"An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.".
"

"Data Flow Task" -------"The AcquireConnection method call to the connection manager "Dupaco" failed with error code 0xC0202009.
"

"Data Flow Task" ----------"component "OLE DB Destination" (119) failed validation and returned error code 0xC020801C.
"



"One or more component failed validation.
"



"There were errors during task validation.
"



When i try to execute the same code on the server where all the package are hosted. It is working fine.



More Info:

In thepackage we are using one "Source Flat file connection" and one "Oledb Destination connection"

Please help me to solve this problem, as my client needs it very badly


Thanks
Subin

View 9 Replies View Related

SSIS Job Execution Fails | Copy Files From Remote Machine

May 13, 2008

Hi All

One of the step in sql agent job is to execute the SSIS package to copy files from remote shared location to local server where sql server is installed. The account on which SQL agent runs as has access to remote shared location. However SSIS package always fails with following error:

An error occurred with the following error message: "Access to the path '\sharedlocationBCKTST105092008.csv' is denied.".

We have tried using proxies but same issue come with proxy also.
When using proxy, we created a proxy for a user who has access on that shared folder on Windows server(from which files are to be copied). If we login to SSIS server with the above user and execute SSIS package manually it works fine. However if we login with different user and run the job via SQL agent using proxy of the above user, then job fails throwing same above mentioned error


Any help is highly appreciated.





Thanks

View 3 Replies View Related

Loading And Running A Remote Package Programmatically

Sep 13, 2007

Hi!

I have to run a remote dtsx-package programmatically.....with Visual Basic 6.0.

Is this possible? I've only found this .net code:

http://msdn2.microsoft.com/en-us/library/ms403355.aspx

Thanks
Chris

View 3 Replies View Related

Integration Services :: How To Access Remote System Folder In Local Machine Using SSIS

Aug 12, 2015

I have to access the remote system folder files in local machine using SSIS.

View 2 Replies View Related

Several Different Errors When Creating And Running SSIS Package. Package Runs Successfuly Sometimes.

May 2, 2008

Hi All,



I am in the process of moving from a 32-bit SQL Server 2005 Enterprise (9.0.3054) to a 64-bit SQL Server 2005 Enterprise (9.0.3054 with 4 CPUs and 8GB of memory on Win 2003 SP2) and the process has been very frustrating to say the least. I am having a problem with packages that I created on my 64-bit SQL Server. I am importing a few tables from the 32-SQL Server into the 64-bit SQL Server using the Task --> Import to create the package.



Sometimes when I am creating a package I get the following error in a message box:



SQL Server Import and Export Wizard

The SSIS Runtime object could not be created. Verify that DTS.dll is available and registered. The wizard cannot continue and it will terminate.

Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (System.Windows.Forms)





Other times when I run a package that has run successfully before I get the following error:



Faulting application dtexecui.exe, version 9.0.3042.0, stamp 45cd726d, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0x025d23f0.





Other times I get this error message:



.NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error (79FFEE24) (80131506)





And still other times



The package appears to hang when running. By this I mean that the Package Execution Progress shows progress up to a point then it just stops. (The package takes about 17 seconds to run normally) CPU usage is at 1% and the package cannot be stopped.





I have deleted and re-created the package several times and I have also re-installed the service pack on the SQL Server (9.0.3054) but that did not help.





Does anyone have any other suggestions to try?





Thanks.



View 4 Replies View Related

Problem When Running A SSIS Master-package-child Package On Non Default Sql-server Instance

Dec 6, 2007

Hi there

We have a SSIS run which runs as follows


The master package has a configuration file, specifying the connect strings
The master package passes these connect-strings to the child packages in a variable
Both master package and child packages have connection managers, setup to use localhost. This is done deliberately to be able to test the packages on individual development pc€™s.
We do not want to change anything inside the packages when deploying to test, and from test to production. All differences will be in the config files (which are pretty fixed, they very seldom change). That way we can be sure that we can deploy to production without any changes at all.

The package is run from the file system, through a job-schedule.

We experience the following when running on a not default sql-server instance (called dkms5253uedw)

Case 1:
The master package starts by executing three sql-scripts (drop foreign key€™s, truncate tables, create foreign key€™s). This works fine.

The master package then executes the first child package. We then in the sysdtslog get:

Error - €œcannot connect to database xxx€?
Info - €œpackage is preparing to get connection string from parent €¦€?

The child package then executes OK, does all it€™s work, and finish. Because there has been an error, the master package then stops with an error.

Case 2:
When we run exactly the same, but with the connection strings in the config file pointing to the default instance (dkms5253), the everything works fine.

Case 3:
When we run exactly the same, again against the dkms5253uedw instance, but now with the exact same databases defined in the default instance, it also works perfect.

Case 4:
When we then stop the sql-server on the default instance, the package faults again, this time with


Error - €œtimeout when connect to database xxx€?
Info - €œpackage is preparing to get connection string from parent €¦€?

And the continues as in the first case

From all this we conclude, that the child package tries to connect to the database before it knows the connection string it gets passed in the variable from the master package. It therefore tries to connect to the default instance, and this only works if the default instance is running and has the same databases defined. As far as we can see, the child package does no work against the default instance (no logging etc.).

We have tried delayed validation in the packages and in the connection managers, but with the same results (error).

So we are desperately hoping that someone can help us solve this problem.


Thanx,
/Nils M - Copenhagen

View 3 Replies View Related

Running A Package Programmatically On The Server By Using A Web Service Or Remote Component

Mar 7, 2007

Hi,

I am trying to apply the sample provided by Microsoft in the following article:

http://msdn2.microsoft.com/en-us/library/ms403355.aspx

I am trying to call a SSIS package from a web service hosted on the same machine as the package file is sitting. The package is running fine from the Agent and also by the "Integration Services Project" in VS.NET.

I had a lot of problems with permissions but they are resolved, at least I have no error messages to point to that direction. Now I am getting these results:

1. Error: -1073659874 / Description: The file name "\Diver-svrInputDataFilesdn_cust.txt" specified in the connection was not valid.

2. Error: -1073659875 / Description: Connection "bdn_cust" failed validation.

3. Error: -1073659874 / Description: The file name "\Diver-svrInputDataFilesdn_cust.txt" specified in the connection was not valid.

4. Error: -1073659875 / Description: Connection "SourceConnectionFlatFile" failed validation.

Where \DiverMInputFilesdn_cust.txt" is a file processed by the package.

Is there anybody who can give me some directions.  Thank you in advance.

 

 

 

View 4 Replies View Related

Running Remote SSIS Packages Dynamically

Dec 19, 2007

I seem to be missing something with SQL 2005 SSIS and I am wondering how I would accomplish my taks. With SQL 2000 and DTS we designed our DTS packages so that we could load one file or database from start to finish. We then have controlling programs written in VB that will monitor directories, when a file shows up in a directory it loads the package, changes the necessary properties and executes it. These programs handle all of our error notifications and dealing with the files afterwards, making sure files are complete in the directory before the DTS runs, etc. With .NET and SQL 2005 I have learned that I can change the properties by using variables and expressions, which I think would handle all of our situation but I can not run them remotely. The documentation says that I could setup a scheduled job and then call sp_start_job from my program. That seems like it would require a lot of scheduled jobs and then I still need to get the parameters into the packages. The other option is to use a web service, that would require IIS on my SQL box which everywhere says I don't want. Am I using SSIS for something I am not supposed to be or how do I accomplish this in 2005?
I have noticed that you can not even run packages through the SQL Server Management Studio. We have a number of packages that are built that are run on demand when needed. In SQL 2000 I could just click and execute the package. In 2005 is my only option to setup some sort of fake job in the job scheduler?

View 6 Replies View Related

Running Ssis Package With Ssis Run Time Compoenents And Sql Server 2000...

Jan 22, 2007

running ssis package with ssis run time compoenents and sql server 2000...

Is it possible to run ssis packages that point to servers on sql server 2000
without installing sql server 2005 ?

Can we just install runtime for ssis and run the packages ?

Please explian with links if possible

thanks a lot

View 18 Replies View Related

Failure When Executing SSIS Package From C# On Machine Different Then SQL Server

Apr 7, 2008

Hi everybody,
I'm newby in SSIS. I have been using DTS in SQL 2000.
Trying to learn how to execute SSIS package from C# code of ASP.NET web server.
Here's my case:
1. SSIS package with simple data transformation from one table to CSV is stored in SQL Server 2005 storage
2. CSV is for simplicity placed in C: .txt
3. I haven't used SSIS configuration files
4. Protection level of package = EncryptSensitiveWithUserKey
5. Executes OK from Bussiness inteligence studio
6. I've created console application with this code:

...
sqlServeruser = "sa"
...

Package package = app.LoadFromSqlServer("Export_vw_TestConsumerPerson", sqlServer, sqlServerUser, sqlServerPassword, null);
DTSExecResult result = package.Execute();
Console.WriteLine("Package Execution results: {0}",result.ToString());
...

7. When I connect through Remote Desktop Connection I successfully execute this console application on SQL server host machine.
8. When I try execution from computer where I develop package and where I successfully executed it from Bussiness inteligence studio I'm geting FAILURE was a result

Connection params for SQL are same in console application and in SSIS project of Bussiness inteligence studio.

Thanks for any hints

Sinisa

View 9 Replies View Related

SQL Server Job Fails When SSIS Package Is Having Excel Connection On 64 Bit Machine

May 29, 2008

Hello,

I've SQL Server running on 64 bit. When I schedule a package to run every night which has excel data transformation, it fails. Initally I had a problem running through BIDS also but then I found in project properties you can switch this off by specifying property Run64BitRuntime by false. After going through some forums, many have suggested that when scheduling a package, modify the command arguments to run as 32bit runtime. These command argumnents can be generated from making use of tool DTExecUI.exe Even after using generated command arguments from this tool, it doesn't help.

Below is my command argument and the error message generated.

/FILE "D:DevDWLoadAll.dtsx"
/CONFIGFILE "D:DevDWdevCongig.dtsConfig"
/CONNECTION "customers.dtsx";"D:DevDWcustomers.dtsx"
/CONNECTION "Addresses.dtsx";"D:DevDWAddresses.dtsx"
/CONNECTION "Counties.dtsx";"D:DevDWCounties.dtsx"
/CONNECTION "Countries.dtsx";"D:DevDWCountries.dtsx"
/CONNECTION "ExcelLoad.dtsx";"D:DevDWExcelLoad.dtsx"
/CONNECTION Test;""Data Source=TestDW;Initial Catalog=TestStagingDW;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;"" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E



Message
Executed as user: DWUserSQLServiceAcc. ...0.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 00:05:00 Error: 2008-05-28 00:06:02.31 Code: 0xC0202009 Source: Excel Load Connection manager "Excel Connection Manager" Description: SSIS Error Code DTS_E_OLEDBERROR. 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-05-28 00:06:02.31 Code: 0xC020801C Source: Copy Data Excel Source [5052] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End... The package execution fa... The step failed.

Any suggestions???

Circuit

View 3 Replies View Related

Open Up 32bit SSIS Package In 64 Bit Machine ( 64bit Sql Server)

Sep 11, 2007

I have designed a packege using my local machine ( 32bit) and am trying to deploy this package to 64bit machine and open it up.. are there any issues that I need to aware of? 32 bit ssis and 64bit ssis are comparable each other?

View 14 Replies View Related

Running A Stored Proc On A Standalone Machine From Another Machine In A Domain

Oct 2, 2000

Hullo all
I have two machines,
One is a standalone machine and the other is on a domain network. How can I run a stored procedure/job on the standalone machine from the domain machine ?
running the procedure as a Domain user results in a failed job/stored proc.
also creating an sql login and attempting to run it as that user also fails. How can I solve this problem ?
please e-mail me at wayde@sunnygrp.com if you have any thoughts...

View 1 Replies View Related

Running SSIS Package From SQL Job

Aug 18, 2006

I'm trying to run a SSIS package (dtsx) from inside an sql job (SQL Server agent). This works fine if the user running (run as) the step is a local admin on the server. If it's not, I get the error message "The package could not be loaded. The step failed". This happens even if the user has all possible serverroles such as "sysadmin" etc in SQL.

So, my question is, is there any way to load an SSIS package without being local admin on the machine? In case it is, what is needed?

regards Andreas

View 3 Replies View Related

JOb Running SSIS Package

Nov 8, 2006

I have an issue when a job is scheduled to run a SSIS package. The package (exporte a table to a text file) runs fine from microsoft visual studio but when i create a job and run it, i get the following error:

[298] SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'VOLCANOAdministrator', error code 0x534. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

View 5 Replies View Related

Running SSIS Package

Dec 8, 2005

My boss want to close access to xp_cmdshell for any logins including sa.

View 1 Replies View Related

Running SSIS Package

Feb 27, 2008



Can a SSIS Package be run as a job or a maintance tool. I need it to run nightly. Also in that same job can sql queries be added as well.

Thank you
Dee

View 27 Replies View Related

Error When Running SSIS Package

Apr 9, 2008

Hi i get a error when i run my SSIS package. Here is the message

Error: 0xC02020A1 at import file, Flat File Source [1]: Data conversion failed. The data conversion for column "su_supplier_code" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
Error: 0xC020902A at import file, Flat File Source [1]: The "output column "su_supplier_code" (61)" failed because truncation occurred, and the truncation row disposition on "output column "su_supplier_code" (61)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.


The funny thing about this is when i run the job a 2nd time it works fine.

Has any one any idea about this error or why the job would work fine the 2nd ?

View 1 Replies View Related

Running SSIS Package Through SQL Agent

Jun 18, 2008

Hello,

I'm new here and hope you will be able to help me.

I have created several SSIS packages with Visual Studio 2005.
They all work fine in debug mode.
I have been able to make them work with a ODBC connection by using a ADO.NET connection.

Then I exported them to the file system in my SQL Server 2005 database and created a task in SQLAgent to run them.

All the packages using the ODBC connection fail with the following error :

Login failed for user XXX
Error : 18456; Severity : 14 , State : 8

This error is a password mismatch.

I tried several database users and checked the passwords multiple times.

It looks like SQL Agent is not able to retrieve the password although it is stocked in both the ODBC connection and the SSIS connection.

Can you help me?

Thanks,

Ares

View 19 Replies View Related

Automatically Running The SSIS Package Once In A Day

Mar 7, 2007

hi frnds,

i have SSIS package, i would like to schedule the SSIS package inorder to run automatically once in a day.

can anyone suggest me the solun. pls its urgent.

thnkx in adavance..

View 3 Replies View Related

Requirements For Getting An SSIS Package Up And Running

Apr 17, 2008

Hey guys I have a simple SSIS package up and running locally i.e i have Visual Studio 2005 and SQL Server 2005 installed.

Now If i wish to deply this SSIS package to a new server what do i require to be installed on the new server.

I.e SQL server 2005 will be there but will i also need Visual Studio 2005 to be installed ?

Also to actually run the package do i only need the .sln file

View 8 Replies View Related

Error When Running SSIS Package As A Job

Jun 12, 2007

I am running into an error when running a package using a scheduled job under SQL Server Agent account. I am getting following error:

Date 6/12/2007 4:19:15 PM
Log Job History (VistaODSFeed)

Step ID 0
Server 006-DEVSQL2005
Job Name VistaODSFeed
Step Name (Job outcome)
Duration 00:00:00
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
The job failed. Unable to determine if the owner (ACIsnasir) of job VistaODSFeed has server access (reason: Could not obtain information about Windows NT group/user 'ACIsnasir', error code 0x6ba. [SQLSTATE 42000] (Error 15404)).


ACIsnasir is not the account under which SQL Server Agent service runs. However ACIsnasir has sa priveleges. not sure why am I getting ACIsnasir in the error and not the account under which sql server agent runs.



ideas?

View 1 Replies View Related

Error Running Ssis Package

Sep 16, 2007


I run an ssis task with right click in the BIDS.
the task transform data of the tables between sql2005 DB to another sql2005 DB.
this is the error I get:




Code Snippet
An OLE DB error has occurred. Error code: 0x80004005.
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:
"TCP Provider: The semaphore timeout period has expired.
".
helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
Task failed: CopyTables2







i have a similar task, only diffrent tables that being transfered, same settings. this task run succesfully.
for the task that fails it takes a long time to run (something like half an hour, maybe more) and then it falils. the task that succeeds finish fast (something like 5 minutes). the data in the tables that being transeferred in the good task is much smaller than the data in the tables in the failed task.

Anyone knows the reason to the error.

Thanks.

View 14 Replies View Related

SSIS Package Not Running Under Proxy

Sep 5, 2007



I have a SSIS package that reads from a remote directory on another server that is on the same domain. When I run the package under my domain user, it runs fine, however when I try to start the SQL job which has the package as the first step, the job fails. I created a proxy account with domain user credentials, set it to be active under "SSIS Package Execution" and set the SSIS package to run as the proxy account, but I get the following error message:

"Unable to start execution of step 1 (reason: Could not get proxy data for proxy_id = 2). The step failed."

I'm not sure what to do at this point, so any help would be appreciated.


View 8 Replies View Related

Error Running Ssis Package

Sep 10, 2007



Hello,

I created a ssis package to transfer data between tables of sql2005 DB to another sql2005 database.
when i run it from BIDS with right click -- > execute package i get this error:




Code Snippet
Error: 0xC002F325 at CopyTables1, Transfer SQL Server Objects Task: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".





anyone can help here.

Thanks.

View 4 Replies View Related

Running An SSIS Package As A Job That Connects To A DB

Aug 4, 2006

I have a package that I want to run as a scheduled job in sql server 2005. The job runs fine in the studio. I am convinced that it is not a password or security issue as I set the protectionlevel to do not save sensitive data and can still run the job in the studio. The User running the job has SA privileges as does the SQL Server Agent. The job reads a flat file, runs it through a script and than inserts the rows into a table. The job runs successfully only if the flat file is empty. The job history says: The return value was unknown. The process exit code was -1073741795. The step failed.


There are no OnError lines in the logging.

Anyone have any Ideas or tricks to try.

View 9 Replies View Related







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