SSIS Writing To MSMQ Fails Only When Scheduled By Agent Job

Feb 12, 2008



Hi All,

I'm a bit lost on this...

I have an SSIS package which writes to a configured public MSMQ. When run directly through Visual Studio, file system or msdb it works fine (I guess these use me as the user).
However, when I schedule it through an SQL Agent Job it fails with the following:

Failed to write message ... to the queue.

This seems like a permissions thing to me, but I've tried giving full control to everyone in the MSMQ permissions, also explicitly giving full control to the user that the agent job executes as. Neither made a difference.

Any help would be greatly appreciated.
Cheers,
Tony Vaughan.

View 2 Replies


ADVERTISEMENT

SSIS Package Scheduled In SQL Agent Fails On Occasion

May 13, 2008

I have one SSIS package that fails on occasion. And I can then run this in the job by itself after it fails and it runs fine. Any ideas? Any ideas on what is causing this. It is not every day but about once a week lately but it just happened again today to this is 2nd time in 4 days this has happened. It is always on this same part in the SSIS that it fails when it does fail. 4 times in last 2 weeks.

This step it is on here has a OLE DB - DB2 source and SQL server as destination. It does a couple data conversion, derived columns and then just copies the data from the db2 table to the sql server table.


Message
Executed as user: PERFORMANCEstacyadmin. 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: 6:06:12 AM Error: 2008-05-13 06:09:22.84 Code: 0xC0202071 Source: Copy SalesTender Retail TmpSalesTenderRetail [97] Description: Unable to prepare the SSIS bulk insert for data insertion. End Error Error: 2008-05-13 06:09:23.42 Code: 0xC004701A Source: Copy SalesTender Retail DTS.Pipeline Description: component "TmpSalesTenderRetail" (97) failed the pre-execute phase and returned error code 0xC0202071. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 6:06:12 AM Finished: 6:09:23 AM Elapsed: 191.157 seconds. The package execution failed. The step failed.


Stacy

View 2 Replies View Related

FTP Task Fails - SSIS Scheduled With SQL SERVER AGENT As JOB

Nov 21, 2006

Hi,
I have created a SSIS package and tested it in V.Stdio where it runs fine and uploads file on the remote server.

Now I have scheduled it to run as a job in SQL SERVER AGENT as JOB, but it fails when it comes to the upload task?

I am quite sure as it is something with FTP connection string or security, but can't figure it out.

I have simply added the IP/login/password in the connection manager for upload task.

Any help/ guidance would be great.

Thanks,
Ad

View 4 Replies View Related

DTS Job Fails When Scheduled From SQL Agent

Mar 31, 2004

Folks,
I have a DTS job that imports data from text files (specified as odbc connections) from a remote server into a sql table on the same SQL server that the job has been created on.
The job runs fine if execute directly from the server. If I schedule the same job on the server (through jobs) executing under the same user, the job fails with..

Executed as user: mydomainmylogin . ...art: DTSStep_DTSActiveScriptTask_1 DTSRun OnFinish: DTSStep_DTSActiveScriptTask_1 DTSRun OnStart: DTSStep_DTSDataPumpTask_1 DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error string: [Microsoft][ODBC Text Driver] '(unknown)' 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 OLE DB Provider for ODBC Drivers Help file: Help context: 0 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 1023 (3FF) Error string: Error source: Help file: Help context: 0 DTSRun OnFinish: DTSStep_DTSDataPumpTask_1 Error: -2147220440 (80040428); Provider Error: 0 (0) Error string: Package failed because Step 'DTSStep_DTSDataPumpTask_1' failed. Error source: Microsoft Data Transformation Services ... Process Exit Code 1. The step failed.

How come it loses the path to the file when I dont run it directly?
Cheers
Mick

View 4 Replies View Related

Should We Allow SSIS To Be Scheduled Via SQL Agent

May 5, 2006

Hi,

Can we allow SSIS to be scheduled via SQL Agent. Is there any security concerns.

Thanks & Regards

Shri.DBA

View 4 Replies View Related

SSIS Package Fails As Scheduled Job

Apr 17, 2007

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



What am I missing??



Thanks

Mike Allen

View 7 Replies View Related

SSIS Package With An FTP Task Fails When Scheduled

May 7, 2006

I have a SSIS package with an FTP task to download a Excel file and populate a table using an excel connection mnager and a SQL Server Destination and it always fails with the following error when scheduled:

The job failed. The Job was invoked by User sa. The last step to run was step 1 (FTP-DM-CRN_ALLOCATION_COMMENTS).


Executed as user: WEB-INTSQLSYSTEM. The package execution failed. The step failed.

The box on which SQL Server is installed is on a workgroup on the domain and the SQL Server is started up by the Local System user on the box.

I am thinking this has to do with windows security based on all the information that I have read on these kind of error messages. Any input on resolving this will be much appreciated.

Thanks,

MShah

View 1 Replies View Related

Scheduled SQL Server Agent SSIS Package Job Problem

May 9, 2006

HELP! I have been banging my head against a brick wall on this one all this morning AAAAAAGGGHHH!

1. I have an SSIS package that runs a simple SQL script and then updates a few tables by downloading some XML of the web. It runs fine when I kick it off manually under SSMS.

2. I created a SQL Server Agent job to run it every day. This always fails. The error information in the log is useless ("Executed as user: domainuser. The package execution failed. The step failed." - I had already figured that out!). It fails almost straight away, and when I enable logging for the SSIS package, no info is ever logged (text file, windows event log, whatever).

3. Out of desperation I have changed Agent to run under the same domain user account that I created the package with. No use.

My questions:

1. How can I get more detailed logging from SQL Server Agent?

2 Any ideas about why it's failing in the first place.

Many thanks in advance.

Ben

View 17 Replies View Related

SSIS Package Fails Giving That Com.interop Exception When Scheduled.

Apr 16, 2008



Hi,

I have one SSIS package which is written in Visual studio business intelligence tool. For that SSIS packages i have scheduled a job from SQL server management studio 2005. I mean i have scheduled a job in SQL server agent.
This job which i have scheduled contains 6 SSIS packages and the other 5 SSIS packages executes successfully but this only fails giving sone com.Interop exception.

But it is failing giving some com.interop exception. Not sure what type of error is this?

It give following type error:

Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:00:00 PM Error: 2008-03-27 23:00:00.81 Code: 0x00000000 Source: Execute DTS 2000 Package Task Description: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user. at DTS.PackageClass.Execute() at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread() End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:00:00 PM Finished: 11:00:00 PM Elapsed: 0.579 seconds. The package execution failed. The step failed.

I get the same error when i try to execute the package from Visual studio Business Intelligence tool.

Can you please help me out as to what is this "System.Runtime.InteropServices.COMException" exception occuring when scheduling or executing the job.

Thanks,
Ashok

View 1 Replies View Related

Scheduled SSIS/DTS Package Fails Periodically With Exit Code -1073741819

Oct 2, 2007

We have a vendor who has an SSIS package that executes a DTS package. We've asked that they migrate the DTS code completely to SSIS, but that is something that will not be done in the near future. The package is scheduled to run every 5 minutes through a SQL Server scheduled job. 95% of the time the package executes without an error, but occassionally the following error is reported.


Date 10/2/2007 7:35:00 AM
Log Job History (Pyxis - Data Load)

Step ID 1
Server DEVSQL1V5
Job Name Pyxis - Data Load
Step Name Run SSIS Package
Duration 00:00:03
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0


Message
Executed as user: Domain_NameSQLService. The return value was unknown. The process exit code was -1073741819. The step failed.



When I look at the DTS and SSIS package logs no errors are reported and each log indicates the package completed successfully.

Any ideas what this exit code is indicating or how to further troubleshoot the problem?

Thanks, Dave

View 4 Replies View Related

SSIS - Process Task Exit Code 4 - Via SQL Agent Scheduled Job Only - Works If Manually Started....

Oct 10, 2007

We have a Process Task component setup in a couple SSIS jobs to call a command batch file to support transfering a file via Secure FTP to other servers and the process works fine if we start the SQL Agent job manually, however when the job is started via the scheduler, it fails with an exit code of 4. Even though there is a proxy setup on the agent job, is there a different user account being invoked by the scheduler??? We're on 2005 SP1 Hotfix 1 (2153). Thanks

Some more info...have found that if we leave a login session open on the server (login is the proxy account) the process works. It appears the issue is associated with a need to render/create a command window for the command line/batch process to run in and without an active windows session it fails....would seem to be that a product setup to run on a server in a batch mode would be able to work without this...is this the case? if so, how? Thanks.

View 11 Replies View Related

SSIS Package Fails From SQL Agent Job

Mar 12, 2008

Hi,
I created a SSIS Package and now i want to run this package from SQL Agent Job. I set up the job and when i run it, it failed

Job Properties:
Type: SQL Server Integration Services Package
Run As: SQL Agnet Service Account
Package Source: File System
Package: \pc17917c$Documents and Settingskdesai1DesktopSSISTest1Test1Package.dtsx

Error i got when i execute the job.

Description: Fauiled to decrypt protected XML node "PassWord" 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: 2008-03-12 10:50:54.48 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Password" 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: 2008-03-12 10:50:55.07 Code: 0xC0048006 Source: Drop Table ActiveX Script Task ... The package execution fa... The step failed.


I'm new to the SQL 2005 SSIS. Can you please help resolve this problem?

Thanks,
KD

View 13 Replies View Related

SSIS Package Fails In SQL Agent

Sep 27, 2006

Okay, I see that dozens of posters have this problem, but none of the threads has a solution: Why does an SSIS package run perfectly fine in VS and in Integration Services, but fail with no details in SQL Agent? Is there another way to have an SSIS package run regularly?

Thanks.

View 5 Replies View Related

SQL Agent Fails To Run A Ssis With All Accounts But One

Nov 10, 2005

Hello,

View 4 Replies View Related

Executing SSIS Package From Agent Fails

Feb 7, 2007

Hi,

I have an SSIS package that utilises a 3rd party ftp program to transfer files (over HTTPS). This software stores details in the users profile relating to addresses, user names and password for transfers. As this is the case the Package needs to be executed by the domain user who has the details set in their profile. The package needs to be executed at a scheduled interval - so I have set up an Agent job to do this, and have the the 'Run As' setting, as a proxy which maps to the required domain user.

The package works fine when executing manually when the required user is logged in. If, however, the user is not logged in - ie when the job kicks off at the schecduled time, the file transfer fails. On debugging I can see that the agent job does not load the user's profile -but instead uses the 'Default User' profile.

The job owner is set as the same domain user that the Run As setting for the step is set. The SQL Server Agent services runs as a different Domain user.

Has anyone else had similar problems - Are there any extra permissions I need to set?

cheers..

View 4 Replies View Related

SQL Agent Job Fails Running SSIS Packages

Oct 16, 2006

I need some help from you on a problem with SQL Server Agent that I believe many of you have experienced. When searching on the web I find some loose answers, but it would not solve my problems. So here is my story.

1. I have created two SSIS packages, package 1 and package 2. Both packages have a Execute SQL Task making a select sql statement to a table, say Customer in AdventureWorks DB. Package1 also makes a Execute Pacakge Task to Package 2. Both packages have protectionlevel property set to EncryptSensitiveWithUserKey

2. Then I created two package configuration files per package, one indirect xml configuration and one xml configuration file. The former I created an environment variable called pack1, which was specifying the path and file name of second config file. Likewise, I did for package2. Maybe I could have reused thie first configuration file, but I am not sure since package1 calls package2.

3. Now I build and deploy my packages. Then I run my manifest file, going through the deployment wizard setting the necceccary properties like server name, user, password, I have also create the same environment variables on the deployment machine. I ensure that the package1 and package2 can be run under integration services (file system). And both package works. So far so good

4. Now I want to create a SQL server agent job that runs package1 and package2. Here I found an article that decribed How to Schedule and Run a SSIS package ( DTS ) Job in SQL Server 2005 http://www.codeproject.com/useritems/Schedule__Run__SSIS__DTS.asp

5. I created a job executor account and then Create SQL proxy account and associate proxy account with job executor account as described. I created a new ssis job, specifying type ssis integration services, run as proxy, setting package source to SSIS package store, naming the server and package name (package2).

6. Now, I try running job1 which runs package2. ANd it works. I was aware if I needed to give file permission on users (read and execute) on my dtsx/dtsconfig/log files. So far so good

7. Now, I try to run job test which runs package1 (which also runs package2). But now the job fails :-(. The job runs for some seconds, but fails. I have to say that I have some script tasks with message boxes inside!!! hope this doesn't matter. I have created all neccessary accounts, proxies, credentials and so on. here is the view history

Date 17.10.2006 00:50:53
Log Job History (test)

Step ID 1
Server ABEO-GEIR
Job Name test
Step Name test
Duration 00:00:07
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: abeo-geir
as_jobuser. The package execution failed. The step failed.



Continue: This error is well known for you. It has been mentioned in many postings. Well, how do I go from here. Setting logging on the job results in only this information

PackageStart,ABEO-GEIR,ABEO-GEIR
as_jobuser,Package1,{3F5BD166-D24B-4838-B3F1-018B6C2C7523},{8E1B8E45-7F1D-4C24-852C-2694F993E6D2},17.10.2006 00:59:40,17.10.2006 00:59:40,0,0x,Beginning of package execution.

PackageEnd,ABEO-GEIR,ABEO-GEIR
as_jobuser,Package1,{3F5BD166-D24B-4838-B3F1-018B6C2C7523},{8E1B8E45-7F1D-4C24-852C-2694F993E6D2},17.10.2006 00:59:41,17.10.2006 00:59:41,1,0x,End of package execution.



Well, I read some place that I could run the job as type operating system (cmdexec). Here i could not choose Run as, but had to select SQL SErver agent account. NOw I got this message

Date 17.10.2006 01:05:21
Log Job History (test)

Step ID 0
Server ABEO-GEIR
Job Name test
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. The Job was invoked by User sa. The last step to run was step 1 (test).



As you see, I can't come any further. I NEED HELP FROM YOU. I AM STUCK. I know many of you have solved this and I hope you can guide me through thise. I don't know how many hours or days I have used on this.



Regards

Geir F

View 2 Replies View Related

SQL Server Agent Fails SSIS Package Execution At The End.

Oct 1, 2007

I have an SSIS ETL Package that runs perfectly in debugger.

It is saved to the local SQL Server using "rely on server security".

The SQL Server Agent job runs at night and the job fails right at the last step. It is actually loading the data, because I write a record with row counts to an audit table, and they are successfully incrementing.

The real issue to me is that it is failing randomly, sometimes it will run 7 times then fail once, others it will go 2 or 3 days then fail. The job runs at the same time every night, and takes within a minute or two variance.

I've looked at the logs, and done a trace, and I can't seem to find anything that would cause the failure. The closest thing to an error is a join parameter note in the trace that's on tthe MSDB database.

Not a lot to work with, I know... but does anybody have any advice for me? Thank you in advance!

View 2 Replies View Related

Executing SSIS Package Through SQL Server Agent Fails

Nov 28, 2007

Hello,

I try to run a job from SQL Server Agent to execute an SSIS package, but it always fails. However, if I execute the SSIS package directly, it will succeed.

The SQL Agent Job History shows "Unable to start execution of step 1 (reason: Error authenticating proxy DB1DB1_CREDENTIAL, system error: Logon failure: unknown user name or bad password.). The step failed."

P.S. DB1 is my server name, DB1_CREDENTIAL is the account creating the credential

The SQL Server Agent Error Log shows "[298] SQLServer Error: 22046, Impersonation error. [SQLSTATE 42000]"


I've created an account on OS and assigned it to a credential.
Then, I created a proxy with the credential and then created the SQL Server Agent job with that proxy.

P.S. My SSIS package protection level is created as "Rely on server storage and roles for access control", because if it is set as "Do not save any sensitive data", package execution will fail even I run it directly.

How can I successfully run SSIS package from SQL Server Agent?
Do I lose any setting steps?

Thanks for help.

Lilia

View 18 Replies View Related

Scheduling SSIS Package From SQL Server Agent Job Fails.

Feb 21, 2008



HI,

I am having a strange error coming in SQL server 2005.

I had a DTS package developed in SQl server 2000. Then i had migrated that DTS package to SSIS package using Execute DTS 2000 package. The conversion is successfull.

Then when i manullt execute this package it runs successfully without giving any error.
But then wheh i schedule a SQL server agent job for the same above SSIS package it fails giving me some cryptographic error as follows:

Message
Executed as user: CATOS-CGDBTUW02SYSTEM. ....3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:00:00 PM Error: 2008-02-20 23:00:00.66 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "PackagePassword" 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: 2008-02-20 23:00:00.66 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "SQLPassword" 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: 2008-02-20 23:00:01.00 Code: 0x00000000 Source: Execute DTS 2000 Package T... The package execution fa... The step failed.

Not sure why is this happening.

Manually running the SSIS package from Visual studio does not gives error, but the same SSIS package when is been schedule from SQL server 2005's SQL server agent job it fails giving above error.

Please help me out how to rectify whith this.

Thanks.. in advance

Regards,
Ashok

View 3 Replies View Related

Integration Services :: SSIS Package Which Read Excel Files Fails On Server Agent

Oct 19, 2010

I have a SSIS package which reads an excel file and loads data into a table using script component(C#) as a source. The package runs without any errors when I manually run it on my machine and on the server. But the package fails when run as a SQL Server Agent job.

I tried all the possible fixes I found on the web but still can't get it to work.

View 14 Replies View Related

Integration Services :: SSIS Fails To Load Files From Network When Executed Via Agent (2008 R2 SP2)

Aug 5, 2014

I have a simple SSIS package that reads a flat file and copies it into a SQL Server table.

When the flat fiel is on the C drive I have no problem runnign this package from SQL Server Agent, but as soon as I update the path to a network location the package only works when I run it manually, but fails when is executed via the SQL Server agent job.

The error says "cannot open the datafile", while the datafile location is valid.

Is this a kind of limitation of a SQL Server Agent that only local files are allowed to be processed?

View 4 Replies View Related

Package Fails When I Use ODBC Connection (Fails On SQL Server Agent, OK In Visual Studio)

Jun 11, 2007

I did a small package with only one ODBC connection (Merant 3.70 32-Bit Progess). This package runs well in Visual Studio and fails when runs by SQL Server Agent.

Configuration:

SQL Server Agent on a 32Bit server.

The ODBC connection configuration in available on System DSN on this server.

The user of Server Agent have full access (Admin).

Connect Manager Provider: ".Net ProvidersOdbc Data Provider"

SQL Server version: 9.0.3042



Error Message:

Executed as user: TEKCON cadmin. ...ion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 16:50:33 Error: 2007-06-11 16:50:33.62 Code: 0xC0047062 Source: Data Flow Task DataReader Source [1] Description: System.Data.Odbc.OdbcException: ERROR [HYC00] [MERANT][ODBC PROGRESS driver]Optional feature not implemented. ERROR [HY000] [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS ERROR [IM006] [MERANT][ODBC PROGRESS driver]Driver's SQLSetConnectAttr failed. ERROR [HYC00] [MERANT][ODBC PROGRESS driver]Optional feature not implemented. ERROR [HY000] [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS ERROR [IM006] [MERANT][ODBC PROGRESS driver]Driver's SQLSetConnectAttr failed. at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcCon... The package execution fa... The step failed.


I created a .bat file with this instruction and It's run well:

dtexec /f "C:Program FilesMicrosoft SQL Server90DTSPackagesIntegration Services Project estcom.dtsx"
pause

Why it's not running with SQL Server Agent???

View 7 Replies View Related

Can't Run The Scheduled SQL Agent Job?

Feb 17, 2007

Hi,

I'm tried to run the job that created from maintenance plan. It fail and give me the following message:

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


We are using the Windows Autheniciaton mode only and my id is set as sysadmin, setadmin, processadmin in the server roles.

I don't why I can't run the job, I check the SQL agent services is login using LOCALSYSTEM.


I try to the NT admin account to login the box, but still getting the same error message.

Any idea?





Thanks!

View 5 Replies View Related

Who Can Run The Server Scheduled Agent Job?

Feb 26, 2007

Ray writes "Hi,

I tried to ask the NT admin to login the SQL server and setup a scheduled job to "Shrink the db" for testing purpose.

I tried my ID even I'm not the NT admin, but setup as SQL server as sysadmin, setupadmin, processadmin.


Then the job start and got the error.

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


I have no idea why that happen to NT admin. then I check the Services for SQL Agent under the control panel- admin tools- services.

It shows using the LOCALSYSTEM as login for the SQL Agent service.


Any one have any idea. what security requirement to run a job other than use 'sa' account, since we are using on Windows authenciation mode only.


I must be something is missing? hope some experts here to answer my question.


Thanks!"

View 1 Replies View Related

DTS Job Fails When Scheduled

Sep 22, 2006

I have a DTS local package that transfer data from the host SQL server to another. If I run the package directly (i.e. Right click - Execute Package) everything works as it should.

However, if I try and execute this as a Server Agent job it fails, the job history step details shows the following error:


Executed as user: MYSERVERNAMESYSTEM. ...: Drop table customer Step DTSRun OnError: Drop table customer Step, Error = -2147467259 (80004005) Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 17 (11) Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 DTSRun OnFinish: Drop table customer Step DTSRun OnStart: Create Table customer Step DTSRun OnError: Create Table customer Step, Error = -2147467259 (80004005) Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. Error source: Microsoft OLE DB Provider for SQL Server... Process Exit Code 2. The step failed.


Whilst this is obviously a connection issue, I dont understand how this can work if executed directly and not if executed as an agent job.

Can anybody shed any light on this?

If it helps this is the sequence of events my DTS package uses

1) Connect to remote DB
2) Drop table customers
3) Create new remote customers table
4) Connect to to local DB (hosting the DTS package)
5) Select * from local customers table
6) Dump data from local select into remote DB

View 2 Replies View Related

DTS Job Fails When Scheduled?

Mar 26, 2004

I have a DTS job that moves a text file from a workstation to the SQL server, transforms the data, pumps into a table and then archives the file. It runs fine within EM on the SQL Server, but once scheduled fails immediately on Step 1. I have logged the error as follows:

************************************************** **********
The execution of the following DTS Package succeeded:

Package Name: Load LaserGauge Data Daily
Package Description: (null)
Package ID: {6E4E8DDC-3864-43E9-B82D-300FCBCCAE63}
Package Version: {4DFF3F73-1653-4896-8DA3-A4246D41EE51}
Package Execution Lineage: {E17CD8A1-9754-413B-B129-093711326C27}
Executed On: SEQUEL
Executed By: SQLSERVICE
Execution Started: 3/26/2004 1:12:17 PM
Execution Completed: 3/26/2004 1:12:17 PM
Total Execution Time: 0.031 seconds

Package Steps execution information:

Step 'DTSStep_DTSDataPumpTask_1' was not executed

Step 'DTSStep_DTSActiveScriptTask_1' failed

Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:The task reported failure on execution.
Step Error code: 8004043B
Step Error Help File:sqldts80.hlp
Step Error Help Context ID:700

Step Execution Started: 3/26/2004 1:12:17 PM
Step Execution Completed: 3/26/2004 1:12:17 PM
Total Step Execution Time: 0.031 seconds
Progress count in Step: 0

Step 'DTSStep_DTSActiveScriptTask_3' was not executed
************************************************** **********

I have taken the following actions to resolve:
1. Tested DTS job on local SQL Server - executes without error
2. Checked security: The DTS job is owned by me, and I am a member sysadmins, etc... The SQL Job I have tried several differing accounts (Mine, Domain Administrator, and most recently a proxy account I setup called SQLDTSuser) All have failed with the same error.
3. I have checked the SQL Agent account to ensure that it has necessary rights, stopped and started SQL Agent service, same results.
4. As mentioned I setup a Proxy Account which is in Domain Admins, and Sysadmins on SQL and changed SQL Agent Properties to use this account. result was same error.
5. Set Workflow Properties on the DTS job ActiveXtask to "Execute on Main PAckage Thread" - result was same error.

I'm at a loss I have to be overlooking something obvious, but need someone to hopefully point me in the right direction. Thank you in advance for any help I can get!

The platform is SQL 2000 and I've included the first activex Task code below:

************************************************** **********
' Visual Basic ActiveX Script
'************************************************* **********

Function Main()
Dim fso
Set fso = CreateObject("Scripting.FileSystemObject")
Dim filePath
filePath = DTSGlobalVariables("gv_SourceDir").Value & "" & SourceFileName
If fso.FileExists(filePath) Then
fso.MoveFile filePath, DTSGlobalVariables("gv_WorkDir").Value & "" & DTSGlobalVariables("gv_WorkFileName").Value
Main = DTSTaskExecResult_Success
Else
Main = DTSTaskExecResult_Failure
End If
End Function

Function SourceFileName
Dim fileDate
fileDate = DateAdd("d", -1, Date)
SourceFileName = "LASERDATA" & PadLeft(DatePart("d", fileDate), 2) & PadLeft(DatePart("m", fileDate), 2) & Right(DatePart("yyyy", fileDate), 2) & ".CSV"
End Function

Function PadLeft(Value, Length)
Dim retval
retval = Value
Do While Len(retval) < Length
retval = "0" & retval
Loop
PadLeft = retval
End Function

View 5 Replies View Related

SQL Server Agent: Job Not Running As Scheduled

Mar 6, 2007

I've tried finding an answer to this on this website but I don't see any. I'm running SQL Enterprise Manager v8.0 and have a job in the SQL server agent folder that won't run as scheduled nor will it run manually if I Right-Click and choose Start Job.

It's designed to run a DTS. I can run the DTS manually without errors but the job won't run it for me. I will try to provide as many details in this post as I can in hopes that someone who is more experienced at this can help me.

DTS DETAILS
The DTS is designed to transfer data from a table on one server and transfer it through a firewall to another server into a table on that server. Then delete the entries from the originating table. This works very well if I run it manually. The purpose of deleting entries from the web server is for security. Once the data in on the other side of the firewall it's safe.

The job however will not run either manually or from it's schedule. I've tried creating a new job and setting up a very simple schedule that runs daily every 2 minutes for example. I've played around with different times but no luck. So I will try and provide you with job details below:

JOB DETAILS
Name: TransferData
Enabled, Target = Local Server
Category: Uncategorized Local
Description: Execute package: TransferData

STEPS
ID: 1
Step Name: TransferData
Type: Operating System Command
On Success: Quit with Success
On Failure: Quit with Failure

PROPERTIES OF STEP
Step Name: TransferData
Type: Operating System Command (CmdExec)
Command: ( I have no idea what this translates to as I did not write it) DTSRun/~Z0xF6EE76ED6259A60AC370F465DE7F3095F4B37F7176C05B8E72E396DEBE60135E53ACFEDB00E1F216DD8EC8206782439BA435771E3C1E8A7A5D0DAE3F3AAA9F48BF08A9A9FA23C010A85573546F6B6B900323F76DC8A27EACAFD63904464DD5A9B28137

Nothing special in the advanced tab

SCHEDULES TAB
ID: 20
Name: TransferData
Enabled: No
Description: Occurs every 1 day(s), every 2 minute(s) between 12:00:00 AM and 11:59:59 PM
and is setup as Recurring
Nothing in Notifications Tab

I only have two SQL books to reference. This is a production fire to put out and I really need the help here as I am not a certified SQL guru.

I hope I have provided enough information here for someone to help. I'm happy to provide an email address for easier contact should you request it.

Thanks in advance for any assistance with this.

View 8 Replies View Related

Scheduled Job Fails 1 Out Of 3 Times

Sep 28, 1999

I scheduled a Bulk copy operation, and have been getting some inconsistent failures.

Last night the job was set to run every 3 hours, I expect it to take about 1 hour to finish.

The second itteration of the job failed, the first and third ran fine.
Here is the error from DTS

Any suggestions? Is there a better/stable Data Provider for SQL?

... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: DTSStep_DTSBulkInsertTask_1 DTSRun OnError: DTSStep_DTSBulkInsertTask_1, Error = -2147217900 (80040E14) Error string: The statement has been terminated. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147217900 (80040E14); Provider Error: 3621 (E25) Error string: The statement has been terminated. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error: -2147217900 (80040E14); Provider Error: 7399 (1CE7) Error string: OLE DB provider 'STREAM' reported an error. The provider did not give any information about the error. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error: -2147217900 (80040... Process Exit Code 1. The step failed.

View 2 Replies View Related

DTS Executed As A Scheduled Job Fails

Mar 6, 2003

I have a SQL 2000 DTS package which executes without errors when run from the DTS design screen or by right clicking the package and selecting execute.
When I schedule the package and get it to run at a certain time or highlight the job and select start, the package comes back with an error saying there was a problem with a transformation.
I have tried scheduling the DTS by right clicking on it and selecting schedule and creating a new job and using DTSRun with an operating system command. I get the same results! Help!

View 3 Replies View Related

DTS Package Scheduled To Run As Job Fails

Jun 22, 2004

Hi,

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.

Any ideas anyone?

Maria

View 1 Replies View Related

Scheduled DTS Package Fails

Jul 20, 2005

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

View 1 Replies View Related

Package Fails When Ran As A Scheduled Job

Nov 20, 2006

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

View 6 Replies View Related

FTP Task Fails When Run As A Scheduled Job

Jun 10, 2005

I've created an SSIS package that retrieves a file from an FTP

View 13 Replies View Related







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