SSIS Job is failing when scheduled.

Hello,
I'm getting error when running an ssis package in sql agent Job in sql server 2008. Error message as shown below.
Message
Executed as user: ANSWERS\administrator. The process could not be created for step 1 of job 0x71B1306CBCCA6846A4E345640CFAE163 (reason: The system cannot find the file specified). The step failed.
Any help would be appreciated ASAP.
Thanks,
Vinay

Hi Vinay,
According to the error message” The system cannot find the file specified”, it seems that there are some files are invalid or the account has no access to the files.
Considering you are used excel file in the package, please pay attention to the following tips:
If SQL Server Agent is 64-bit version, we should run a package in 32-bit mode from in the Job Step dialog box, on the Execution options tab, select Use 32 bit runtime.
Make sure the script in command line is correct, for example the quotation marks.
The path of the excel file or other files is valid.
The path should contains the files.
SQL Server Agent should has access to the files.
If the Job is running under a proxy account, then that proxy should has access to the files.
Restart SQL Server Agent.
References:
https://social.msdn.microsoft.com/forums/sqlserver/en-US/76d14c97-ad3e-4c18-9465-cded95c612f7/job-fails-with-the-system-cannot-find-the-file-specified
https://ask.sqlservercentral.com/questions/108260/unable-to-run-dts-package-from-sql-server-agent-jo.html
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Similar Messages

WebI does not return failed when scheduling a report which only holds parti

WebI does not return failed when scheduling a report which only holds partial results.
We have scheduled reports which take some time to run. When they are scheduled they sometimes show successful even though the report only holds partial results. The only indication is when you open the report as webi report you see the warning that it holds partial results.
When running the report manually, it works file.
The issue is not in the no of rows in the universe settings because we this unselected. The issue is that it times out.
The reason that it times out is that a lot of resources are used for loading and processing data when the report is scheduled. When running it manually, it works because at this time the serverload is less. the time in the universe is set to 10 min.
The version we have is BOXIR2-SP4.
Ok. Issue identified.
The question is - why is the report successful when it holds partial results? If this is normal behavior, noone can really trust the scheduled reports, especially when you save it to excel and send it by mail.
Is there a solution for this except increasing the allowed query time which would not solve the issu but only allow more reports to complete?
Edited by: Karlgren Michael on Sep 17, 2009 1:22 PM

Hi ,
Currently this problem exists in XI R2. This feature will be part of thenext Service Pack i.e XI R2 SP6.
This CER will be delivered from IDC Webi and BIP Platform as part of Jupiter Sp6.
Problem Statement:
Scheduled WebI Reports which are partially refreshed are distributed to the destinations for Users to View and make decisions. These users arenu2019t usually aware that these reports have u201CPARTIAL RESULTSu201D
Recomended Solution:
Allow the Schedule Creator / Modifier to set a parameter to stop the distribution of the u201CPARTIALLY REFRESHEDu201D WebI report.
Thanks
Salini

SSIS Package Fails when Scheduled as a SQL Server Agent Job

I have an SSIS package that runs without any problems when executed through BIDS.
However, when I schedule the SSIS as an Agent job, it fails completely or part way through. When it partially runs, the part that it is failing on is a Script Task that moves the source data file to an archive folder (on the same server).
I have tried using my domain account as the owner of the job, then the job fails straight off and I get an error:
Unable to determine if the owner (Domain\MyID) of job JobName has server access (reason: Could not obtain information about Windows NT group/user 'Domain\MyID'
If I change the owner to the 'sa' account , then the job partially runs, but then fails because 'sa' is a SQL account and does not have access to the filesystem.
I have managed to get it to work by using the SQL2008_Local account and granting modify permissions to the affected folders.
My question is - what is the advised way of doing this?
Thanks
Gary

Hi Garyv.King,
When you see a SSIS package fails running in a SQL Agent job, you need to first consider the following conditions:
1. The user account that is used to run the package under SQL Server Agent differs from the original package author.
2. The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
For more detailed information about the issue, please following this KB article:
An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step
http://support.microsoft.com/kb/918760
You can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues.
The following 4 issues are common encountered in the SSIS forum.
1. The package's Protection Level is set to EncryptSensitiveWithUserKey but your SQL Server Agent service account is different from the SSIS package creator.
2. Data source connection issue.
3. File or registry access permission issue.
4. No 64-bit driver issue.
For more information about it, please see:
How do I troubleshoot SSIS packages failed execution in a SQL Agent job:
http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e13c137c-1535-4475-8c2f-c7e6e7d125fc
Thanks,
Eileen

Full optimize Failed when scheduled

Hi everyone,
I got an issue with a full optimize package in SAP BPC 7.0 MS when scheduled.
The package admin_Optimize i use is the standard one. They are no overlapping package scheduled at the same time.
When i manually run the package for a Full optimize on one application it works.
When i manually run the package for a Lite optimize on one application it works.
When i schedule the package for a Lite optimize on one application it works.
When i schedule the package for a Full optimize on one application the package failed and stay stuck. Then the application stay unavailable.
This issue takes place in the production environment so i can't make a test during the day. and some people are using the application very early in the morning so they stay stuck in the morning.
Have you ever meet this issue ? What can i do ? What could be the test ?
Best regards,
Paul

When i start the full optimize by hand it's working fine (But we are supposed to launch it at 4h15 in the morning so i would prefer to schedule it !)
Are you receiving any error message or actually the statusof package show that was not completed and no erro mesage is provided?
The package stay stuck, it never ends even after 4 hours. We are obliged to kill it.
Did you check tbllogs durin the time when the package is running ? It can provide very usefull information.
Yes we did, nothings appears in this table ... all the other package are correclty recorded even the LiteOptimize that is run 30 minutes after ... byt the way this Lite optimize doesn't failed.
Also please check the event viewer from BPC servers during the period when the full optimize was running.
No error related to bpc. But i had an error 45 minutes before related to Osoft data manager

SSIS package is failing when using SQL server agent

I am trying to execute an SSIS package through an SQL server agent and receiving the following error:
Message
Executed as user: serv-syst\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started: 1:56:53 PM Error: 2014-04-21
13:56:54.81     Code: 0xC0202009     Source: PACKAGEWMG Connection manager "DestinationConnectionOLEDB"     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 Server Native Client 11.0" Hresult: 0x80040E4D Description: "Login failed for user 'hsnzha'.". End Error Error: 2014-04-21
13:56:54.82     Code: 0xC00291EC     Source: Drop table(s) SQL Task 1 Execute SQL Task     Description: Failed to acquire connection "DestinationConnectionOLEDB". Connection may not be configured
correctly or you may not have the right permissions on this connection. End Error Error: 2014-04-21 13:56:54.82     Code: 0xC0202009     Source: PACKAGEWMG Connection manager "DestinationConnectionOLEDB"
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 Server Native Client 11.0" Hresult: 0x80040E4D Description: "Login
failed for user 'hsnzha'.". End Error Error: 2014-04-21 13:56:54.82     Code: 0xC00291EC     Source: Preparation SQL Task 1 Execute SQL Task     Description: Failed to acquire connection
"DestinationConnectionOLEDB". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:56:53 PM
Finished: 1:56:54 PM Elapsed: 0.844 seconds. The package execution failed. The step failed.
My SSIS package retrieves a excel file and saves the vales into an SQL table. When I run the package by itself in my server it works fine but when it's called from a SQL agent, it fails with the above error. Please help me resolve it.

That's the issue. If it's a SQL login the password cannot be retrieved by account executing the package from the job which is why login fails. In that case best thing would be set password in job properties or pass it using configuration created in the package
See
HTTP://blogs.msdn.com/b/runeetv/archive/2011/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs
My package is saved with ServerStorage which appears under \\server\Stored Packages\MSDB\PACKAGE and when I run it, it works fine.
There is a new error message that I get now after following the steps from the link...
Message
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.1600.1 for 32-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 3:34:22 PM
Error: 2014-04-21 15:34:23.82
   Code: 0xC0202009
   Source: PACKAGEWMG Connection manager "SourceConnectionExcel"
   Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Office Access Database Engine" Hresult: 0x80004005 Description: "Unexpected error from external database driver (????????).".
End Error
Error: 2014-04-21 15:34:23.82
   Code: 0xC020801C
   Source: Data Flow Task 1 Source - 'Contact Center$' [1]
   Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionExcel" failed with error code 0xC0202009. There may be error
messages posted before this with more information on why the AcquireConnection method call failed.
End Error
Error: 2014-04-21 15:34:23.82
   Code: 0xC0047017
   Source: Data Flow Task 1 SSIS.Pipeline
   Description: component "Source - 'Contact Center$'" (1) failed validation and returned error code 0xC020801C.
End Error
Error: 2014-04-21 15:34:23.82
   Code: 0xC004700C
   Source: Data Flow Task 1 SSIS.Pipeline
   Description: One or more component failed validation.
End Error
Error: 2014-04-21 15:34:23.82
   Code: 0xC0024107
   Source: Data Flow Task 1
   Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 3:34:22 PM
Finished: 3:34:23 PM
Elapsed: 1.25 seconds

Offline backup failing when scheduled using DB13

Hi,
We have done our backup schedule of our BI 7 system running on AIX 5.3 and Oracle 10.2 using DB13.The activities like online backup and datbase check is executing correctly but offline backup is failing with status unknown.
If i check in sm37 for the DBA job offline backup is showing status completed successfully but in brbackup logs there is no log for the offline backup activity.
Kindly provide your suggestion on how i can resolve this issue.

Hi Ammey,
Thanks for your reply.
When I trigger the backup directly from brtools offline backup is happening successfully.The issue is happening only for the db13 scheduled offline backup.The same thing happened for Update statistics but check db is executed.
So what has to be checked in backint settings pls provide you suggestion.
rgds,
vinayak

Webi Report Against SAP BW Query Fails When Scheduled

Hi all,
I'm facin a problem with all my Web intelligence Reports. When i refresh them on demand from view or design mode, everything works fine, but when i schedule them all instances fails with this error:
A database error occured. The database error text is: The MDX query SELECT { [Measures].[DF4LK70NQJ0KRU6XHODIE9TGA], [Measures].[3EG3OC7QZBODSE9J2JI4OLOPI], [Measures].[CXDGYOWE9FJFHS72KIO78WGTT], [Measures].[12C28AI1LLXSDEHMWCDUMJWCW], [Measures].[E2OE5J39YBUPP4IPZCX1HNHZX], [Measures].[5X2TIT4FSFEBHYFDEFACO2DCF], [Measures].[E6WGO3AACYBZ20ZIHZF28Y9TT], [Measures].[CB1PAR1H2KF21CWAY6G3NP2WK], [Measures].[8GZAGANUUZA7B2V59A5FBB5BO] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [ZSOLTYPE].[LEVEL01].MEMBERS, [0CALMONTH].[LEVEL01].MEMBERS ), [0MATL_GROUP].[LEVEL01].MEMBERS ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ), [0COMPL_DEL].[LEVEL01].MEMBERS ), [0BBP_STATUS].[LEVEL01].MEMBERS ), [0PLANT].[LEVEL01].MEMBERS ) ON ROWS FROM [CUBE_NAME/QUERY_NAME] SAP VARIABLES [ENTFINAL] INCLUDING X [0I_CALZ2] INCLUDING ENE 2008 : MAR 2008 failed to execute with the error FUNCTION_NOT_FOUND. (WIS 10901) .
BO is XI3.0, BW 3.5, Universe made from a SAP BW Query.
Thanks in advance!

Hi Ingo,
All the authorizations for crystal report to fetch data is in place, and crystal report refresh and schedule runs success fully. The issue is only in Web Intelligence.
If it is same as crystal report we should see similar results for crystal report, which is not the case as of now. Crystal report refreshes without any error and we can able to schedule it without any problem.
As it is said earlier, SAP secuirty guy doesnt find any missing authorizations. It is very difficult to say which authorization is missing.
Edited by: Raghavendra Barekere on Nov 7, 2008 6:42 PM

Job powershell fail through scheduler

I have a dilemma. I am using the Windows Server 2012 scheduler to execute powershell scripts.
To experiment, poured a new W2012, has created a new domain test.wan isolated network
- Created by user adm, appointed him as the domain administrator.
- Create a directory c:\temp
- Created script d:\backup\test.ps1 with content:
get-date >> c:\temp\log.txt
Login as test\adm and create scheduled job by executing powershell code:
Set-ExecutionPolicy RemoteSigned unRegister-ScheduledJob -Name Backup
$t = New-JobTrigger -Weekly -DaysOfWeek 1,2,3,4,5 -At 11:00PM
$cred = Get-Credential test\adm
$o = New-ScheduledJobOption -RunElevated
Register-ScheduledJob -Name Backup -FilePath d:\backup\test.ps1 -Trigger $t -Credential $cred -ScheduledJobOption $o
- Start the scheduler and manually run the task - write to the file worked.
- Then i
logout test\adm
Logged under test\Administrator
- Start the scheduler and manually run the task - write to a file does not work in the job log all ok .
- Launched cmd as test\adm
- Start the scheduler and manually run the task - write to the file worked.
Why ??
ps: On Windows Server 2008R2 is no such problem.

Hi AnnaWY.
1. Scheduled jobs created by test\adm and with permissions of test\adm by the Credential parameter in the Register-ScheduledJob (see above).
2. Schleuded job run Elevated and regardless of the user logon.
3. User have permission to run the commands or scripts.
When user test\adm have active session or any process runs as test\adm job start (manually or by scheduler trigger) and work properly.
When user test\adm not logged in job start (manually or by scheduler trigger) but nothing happen but job complete normally by job log.
PS C:\> Get-ScheduledJobOption Backup
StartIfOnBatteries : False
StopIfGoingOnBatteries : True
WakeToRun : False
StartIfNotIdle : True
StopIfGoingOffIdle : False
RestartOnIdleResume : False
IdleDuration : 00:10:00
IdleTimeout : 01:00:00
ShowInTaskScheduler : True
RunElevated : True
RunWithoutNetwork : True
DoNotAllowDemandStart : False
MultipleInstancePolicy : IgnoreNew
JobDefinition : Microsoft.PowerShell.ScheduledJob.ScheduledJobDefinition

SSIS script task failing when deployed as project in SSIS 2012

Yes , it's the classic "my package works inside SSDT but dies when I deploy it". I have a fairly good idea what the problem is. I have a line of code that looks in a directory. My guess is that the account that is used to run packages out
of SSISDB doesn't have access to the directory in question. My question is, what exactly needs to be set properly in order for packages to run properly in the package deployment model.
Error message: Exception has been thrown by the target of an invocation.
Code:
using System;
using System.Data;
using System.IO;
using Microsoft.SqlServer.Dts.Runtime;
using System.Windows.Forms;
public void Main()
           String FilePath;
            FilePath = Dts.Variables["InitialDirectoryFullPath"].Value.ToString();
            if (Directory.GetFiles(FilePath).Length == 0)
                Dts.Variables["FilesExist"].Value = false;
            else
                Dts.Variables["FilesExist"].Value = true;
            Dts.TaskResult = (int)ScriptResults.Success;
        enum ScriptResults
            Success = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Success,
            Failure = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Failure

You need to give the account which is executing package the access to the directory. If its from SQL Agent job, it might be using SQL Agent service account by default. Then you've to give it required permissions
Alternatively you can create a proxy account with required permissions and configure the job to use it
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
Also you've not posted error message. Whatever I've suggested is by assuming that its a permission issue. If you can post error message we might be able to confirm on the actual cause of error.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

CUPS print job options fail when called from lp (UNIX command line)

Under Leopard this command-line print request fails to respect the specified job options:
lp -o number-up=2 -o page-border=double <filename>
Though it worked great in Tiger, the number-up and page-border job options are now disregarded. I have tried lots of things (and wasted lots of paper) such as setting them permanently with lpoptions (and they do appear changed when the lpoptions command is repeated), using lpr instead of lp, reinstalling the printer via the CUPS localhost web interface, enabling non-Bonjour scanning with the hack to the CUPS preference file, deselecting "Last Printer Used" for the default printer in the System Preferences -- nope.
I have not tried other job options; I assume that whatever is breaking these two is breaking all the others, and even if it isn't, these two are what I want.
Is something new in Leopard overriding lpoptions job options? How do I make it stop? It is sooooo aggravating when something that used to work fine breaks. The printer is an HP LaserJet 4000N connected by Ethernet and discovered with AppleTalk.
Thanks for any advice!

Thanks John, I did search but somehow missed that thread.
However it did not help. With or without the "-p printername" argument lpoptions does make a persistent change to its own data:
+$ lpoptions+
+media=Letter sides=one-sided finishings=3 copies=1 job-hold-until=no-hold job-priority=50 number-up=2 auth-info-required=none job-sheets=none,none printer-info=Barrow printer-is-accepting-jobs=1 printer-is-shared=0 printer-location='Local Zone' printer-make-and-model='HP LaserJet 4000 Series' printer-state=3 printer-state-change-time=1209495301 printer-state-reasons=none printer-type=2134228 page-border=double+
You can see that the printer "Barrow" has remembered "number-up=2" and "page-border=double". Regardless if I give any of these commands:
+lpr <filename>+
+lpr -P Barrow <filename>+
+lp <filename>+
+lp -d Barrow <filename>+
none of them show the results of these option settings (and somewhere in the forest another tree is cut down).

How to mail to users when a report fail when scheduled in Infoview-BO XIR2

Hi,
We need to send a mail notification to the mail recipients when a report fail. Is this possible in Infoview.
Please suggest.
Thanks in advance.

it is not possible in infoview. but it can be done using CMC. if you go schedule a reports in CMC, goto notifications and add email notification and add email addresses.

SSIS Lookup Conversion failed when converting date and/or time from character string

Hi all,
I'm trying to do a lookup by passing a date, however (i'm guessing) one of the dates is in a bad format and is failing the component. How do I find the suspect row? I set both lookup outputs to flat file but it is just erroring and not outputting
anything. The date being passed in is in datetime format and destination is the same data type.

Thanks for your suggestions. I have used ISDATE and MIN, MAX to find the maximum ranges. ISDATE is not returning 0 in both Source and Destination (so it looks like they're all valid). it looks like there are some null dates in from date
column. Would these throw a conversion error? I'm still a bit stumped as to why i'm getting a conversion error, 1900-01-01 00:00:00.000 is still a valid date even if it's basically null.
-- SOURCE MIN DATE = 2009-12-21 00:00:00.000
-- SOURCE MAX DATE = 2015-06-08 00:00:00.000
-- DESTINATION MIN FROM DATE = 1900-01-01 00:00:00.000
-- DESTINATION MIN TO DATE = 2005-01-15 00:00:00.000
-- DESTINATION MAX FROM DATE = 2015-10-18 00:00:00.000
-- DESTINATION MAX TO DATE = 2145-12-31 00:00:00.000
I will also try JAKUB's suggestion to see if the package completes with a few rows.

SSIS packages are failing after upgrade to SQL server 2014

Hi,
I have some SSIS packages running on SQL server 2012 .
After I upgraded to SQL server to 2014 from 2012 , the SSIS jobs are failing on the SQL agent.
And i can see its related to Data source connectivity to the SQL agent. I hope it not able to identify the connection manager in SQL agent. And connection adapter is not upgraded.
I read some articles about this and they say it not able to connect to SQL server agent job.
And, I can see that the package is running if i run manually using SQL 2012 run time.
Why its not running on SQL 2014 ?
did i miss anything while upgrading SQL server 2014 ?
Please give me some suggestions to solve this issue.
And is there any way i can change the SQL server agent 2014 to adapt this and run ?
Below is the error :
The Package filed to load due to error 0XC00100014 " One or more error occurres. There should be more specific errors preceding this one that expalins the details of the erroes. This message is used as a return value from functions that encounter
errors.: This occures when CPackage::LoadFormXML fails.
Regards,
Vinodh Selvaraj.

I think you have typed this error message by yourself.
Anyway, as it says there should be more error preceeding to this. Do you have any other errors which describles the exact issue stating at what task it fails?
If not, then there are various reasons behind this issue. 3rd party connection manager such as Oracle Attunity or it may be 32/64 bit issue.
You may try executing package in 32 bit mode from SQL Agent Job.
Please refer:
http://blogs.msdn.com/b/farukcelik/archive/2010/06/16/why-package-load-error-0xc0010014-in-cpackage-loadfromxml-error-appears-while-trying-to-run-an-ssis-package.aspx
http://www.bidn.com/blogs/timmurphy/ssas/1397/package-failed-to-load-due-to-error-0xc0010014
-Vaibhav Chaudhari

SSIS package works in development environment but fails when job scheduler executes, file path invalid

SIS package works in development environment but fails when job scheduler executes, file path invalid
Relatively simple package to get OLE-DB connection to MS FoxPro 9.0 DB
The failure in the job log states that the path is invalid its a network path (\\192.168.1.xxx\foldername) this has been run several ways with the remote computer being mapped as a network drive and through the \\ notation described above.
Thinking it was a security issue between the SQL agent account and my account I tested by subsitution myself as a proxy account for the agent when running this job, again same result failed on network path.
One issue I see is that the remote computer is running Server 2000 (legacy software incompatable with newer versions)
Is it possible that this is a security issue, since if i understand correctly the current MS domain security model didn't exist until Server 2003.

Hi REIData,
Have you got the issue resolved? Based on your description, please make sure the target folder is shared properly. If the computer on which the SQL Server Agent job runs doesn’t join the domain as the server that hosts the shared folder, you have to share
the folder with everyone by adding “Everyone” to the people list on the File Sharing page of the folder and assign "Read/Write" permission to it.
Regards,
Mike Yin
TechNet Community Support

SSIS job runs in designer but fails in SQL Agent - timeout error

I have several SSIS packages that have been running without issue for well over a year. These jobs were imported into SQL Server and run on a schedule with SQL Agent.
Over the weekend these jobs failed with the message:
Description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated. Source: .Net SqlClient Data Provider Started: 8:13:01 AM
Finished: 8:13:31 AM Elapsed: 30.155 seconds. The package execution failed. The step failed.
When I look at the package history it doesn't even show that the job attempted to run over the weekend. As such I assume that the error is related to SQL Agent attempting to connect to the SSIS job.
As stated in the title, the jobs run without issue in the designer.
I did stop and restart SQL to see if that would have an effect - sadly it did not.
I attempted to reload one of the packages. More specifically I re-imported it and allowed it to overwrite the existing project, This step completed ok and moved to the next step - deploy the project. It fails to deploy the project with the following error
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2218&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
Server Name: XXXXXXX
Error Number: -2
Severity: 11
State: 0
Program Location:
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.SqlServer.IntegrationServices.Common.ObjectModel.SqlHelper.ExecuteSQLCommand(SqlStoreConnection storeConnection, CommandType cmdType, String cmdText, SqlParameter[] parameters, ExecuteType execType, Int32 commandTimeout)
   at Microsoft.SqlServer.Management.IntegrationServices.CatalogFolder.DeployProject(String projectName, Byte[] projectStream)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeployExportProjectHelper.DeployProject(CatalogFolder folder, Project project)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.Deploy(CatalogFolder folder, Project project)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.DeployProject()
   at Microsoft.SqlServer.IntegrationServices.Deployment.DeployProjectPage.DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
===================================
The wait operation timed out
It would seem to me that there is an environmental error, though I know of nothing that has changed. I don't know where to look. If you have seen this behavior before or have an idea, I welcome your input.
Thanks
Mike

Hi Mike,
Based on the error message, we can infer that the issue is caused by connection or command timeout.
To work around this issue, we can increase the connection timeout and command timeout, buffer size and create two indexes in the SSISDB catalog to improve the performance. For more details, please see:
http://capstonebi.blogspot.com/2012/09/ssis-2012-deployment-frustrations.html
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/804901/ssis-2012-deploying-new-versions-of-large-projects-runs-into-a-timeout-during-deployment-into-ssis-catalog
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SSIS Job is failing when scheduled.

Similar Messages

Maybe you are looking for