2008R2 SQL Agent error 14258

Hi,
I recently enabled database mail in SQL (2008R2), setup a mail profile, set SQL Agent to use it and restarted SQL Agent. SQL Agent starts ok but when trying to look at job properties or history I get the error:
Error 14258: Cannot perform this operation while SQLServerAgent is starting. Try again later.
I have checked lightweight pooling mode is not enabled and also that no databases are in recovery mode. I have also disabled database mail and unticked the SQL Agent mail option and restarted, to no avail.
The SQL Agent service was running quite happily as an unpriveleged domain user. The only way I have found to get SQL Agent running correctly again is to set the service to run using a domain admin account. Running as local system gives the same
error.
Please can someone advise?
Thanks,
Edd Parsons

Date,Source,Severity,Message
08/19/2014 16:22:37,,Warning,[396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
08/19/2014 16:22:37,,Error,[355] The mail system failed to initialize; check configuration settings
08/19/2014 16:22:37,,Error,[260] Unable to start mail session (reason: Microsoft.SqlServer.Management.SqlIMail.Server.Common.BaseException: Mail configuration information could not be read from the database. ---> System.Data.SqlClient.SqlException: profile
name is not valid<nl/> at System.Data.SqlClient.SqlConnection.OnError(SqlException exception<c/> Boolean breakConnection)<nl/> at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)<nl/>
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior<c/> SqlCommand cmdHandler<c/> SqlDataReader dataStr)
08/19/2014 16:22:35,,Information,[129] SQLSERVERAGENT starting under Windows NT service control
08/19/2014 16:22:35,,Error,[364] The Messenger service has not been started - NetSend notifications will not be sent
08/19/2014 16:22:35,,Information,[432] There are 7 subsystems in the subsystems cache
08/19/2014 16:22:35,,Information,[339] Local computer is PLANNINGDB running Windows NT 6.1 (7601) Service Pack 1
08/19/2014 16:22:35,,Information,[310] 2 processor(s) and 8192 MB RAM detected
08/19/2014 16:22:35,,Information,[103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
08/19/2014 16:22:35,,Information,[102] SQL Server ODBC driver version 10.50.4000
08/19/2014 16:22:35,,Information,[101] SQL Server PLANNINGDB version 10.50.4000 (0 connection limit)
08/19/2014 16:22:35,,Information,[100] Microsoft SQLServerAgent version 10.50.4000.0 ((Unknown) unicode retail build) : Process ID 9840
08/19/2014 16:22:34,,Information,[098] SQLServerAgent terminated (normally)
08/19/2014 16:22:33,,Information,[131] SQLSERVERAGENT service stopping due to a stop request from a user<c/> process<c/> or the OS...
08/19/2014 16:21:51,,Information,[129] SQLSERVERAGENT starting under Windows NT service control
08/19/2014 16:21:51,,Error,[364] The Messenger service has not been started - NetSend notifications will not be sent
08/19/2014 16:20:49,,Information,[432] There are 7 subsystems in the subsystems cache
08/19/2014 16:20:49,,Information,[339] Local computer is PLANNINGDB running Windows NT 6.1 (7601) Service Pack 1
08/19/2014 16:20:49,,Information,[310] 2 processor(s) and 8192 MB RAM detected
08/19/2014 16:20:49,,Information,[103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
08/19/2014 16:20:49,,Information,[102] SQL Server ODBC driver version 10.50.4000
08/19/2014 16:20:49,,Information,[101] SQL Server PLANNINGDB version 10.50.4000 (0 connection limit)
08/19/2014 16:20:49,,Information,[100] Microsoft SQLServerAgent version 10.50.4000.0 ((Unknown) unicode retail build) : Process ID 4000

Similar Messages

Error Using New-WebServiceProxy cmdlet with SQL Agent Powershell Subsystem

I created a powershell script to connect to SSRS via web service so I can cache reports in the database and expose them directly through our application. The script works fine when I run it through Powershell directly, but when I try running it through the
SQL Agent Powershell subsystem I am getting a strange error:
"A job step received an error at line 61 in a PowerShell script. The corresponding line is '$RS = New-WebServiceProxy -Class 'RS' -Namespace 'RS' -Uri $reportServerURI -UseDefaultCredential '. Correct the script and reschedule the job. The error
information returned by PowerShell is: 'Could not load file or assembly 'file:///C:\WINDOWS\TEMP\yfqiivtg.dll' or one of its dependencies. The system cannot find the file specified. '. Process Exit Code -1. The step failed."
I am using SQL Server 2014, SSRS 2014, Windows 8.1. The only difference I can think of is that when I run Powershell from the OS, I am using v 4.0 whereas when I run it from SQL Agent it loads v 2.0. My understanding is that v 2.0 supports the New-WebServiceProxy
cmdlet, so I'm not convinced the version discrepancy is the culprit. Any ideas what might be causing this?
On a side note, is there a way to have SQL Agent use Powershell 4.0 for the subsystem? v 2.0 feels a little dated for SQL Server 2014.

Hi WilliamW,
When creating a PowerShell job step, there is only one security context available, which is the "SQL Server Agent Service Account." That means that if you intend to execute PowerShell scripts from SQL Agent Job steps, the SQL Server Agent
service account must have appropriate permissions.
According to your error message, I recommend to check if the SQL Server Agent service account has access to the folder where the scripts live, as well as the folder C:\WINDOWS\TEMP.
In addition, when we execute a PowerShell job step in SQL Server, SQL Server Agent subsystem run the sqlps utility, and the sqlps utility launches PowerShell 2.0 and imports the sqlps module. If you need to run a PowerShell v4.0 script from a SQL Server
Agent job, you can create a proxy account to run the agent job which contains PowerShell script. For more details, please review this similar blog:
Run a PowerShell v3 Script From a SQL Server Agent Job.
Thanks,
Lydia Zhang

Sql agent job getting file access denied error

I'm not sure if this question belongs in this forum. Please move it if you want to.
Here is my question. I have an ssis package that is running into an error at the file system task trying to move a file. The package is deployed to the catalog and I am running the package using the stored procedure
[SSISDB].[catalog].[start_execution] @execution_id
When I execute this stored proc in Management Studio while logged in under a sysadmin, everything works fine. But when I call the same TQL in SQL Agent job, I get a file access denied error. This has something to do with the id that is getting used
to run the package and I am not sure how to track that down. Any help would be appreciated.
I've check the windows permission on both the id that is running the SQL Agent and SQL SSIS Service. Both seem to have the right windows permission.

Please see:
http://support.microsoft.com/kb/918760

Errors running SQL Agent Jobs for 64 bit SSIS packages on a 64 bit server, but Source server 32 bit

Hi,
I can able ran the SSIS package in BIDS, since set to false in Run64BitRuntime property.
Then I created SQL server Agent job I tried the following ways
Step 1:
Type is set as SQL Server Integration Services Packages,
Run as - SQL Server Agent Service Account
Package source - FileSystem
then Execution option tab I selected 32 bit runtime
and then run the job I am getting the below error
Message
Executed as user: CIT\svc_CS_SS2008Agent. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 7:29:17 AM Error: 2013-11-28
07:29:18.57     Code: 0xC0014020     Source: Example Connection manager "DataSource.DataExtract"     Description: An ODBC error -1 has occurred. End Error Error: 2013-11-28 07:29:18.57
Code: 0xC0014009     Source: Imports20_OAC_Gifts Connection manager "DataSource.DataExtract"     Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the
database server. End Error Error: 2013-11-28 07:29:18.59     Code: 0x0000020F     Source: DFT_Example ODBC_SRC Example [11]     Description: The AcquireConnection method call to the connection
manager DataSource.DataExtract failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2013-11-28 07:29:18.59
Code: 0xC0047017     Source: DFT_Example SSIS.Pipeline     Description: ODBC_SRC Example failed validation and returned error code 0x80004005. End Error Error: 2013-11-2
Step 2:
Type - Operating sytem (CmdExec)
Run as - Sql Server agent service account
Command - C:\Program Files\Microsoft SQL Server\110\DTS\Binn\dtexec.exe /FILE "D:\Example\Example.dtsx" /x86 /CHECKPOINTING OFF /REPORTING E
then run the job I am getting the below error
Message
Executed as user: MIS\svc_CS_SS2008Agent. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 6:37:58 AM Error: 2013-11-28
06:37:58.94     Code: 0xC0014020     Source: Example Connection manager "DataSource.DataExtract"     Description: An ODBC error -1 has occurred. End Error Error: 2013-11-28 06:37:58.96
Code: 0xC0014009     Source: Example Connection manager "DataSource.DataExtract"     Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server.
End Error Error: 2013-11-28 06:37:59.01     Code: 0x0000020F     Source: DFT_Example ODBC_SRC Example [11]     Description: The AcquireConnection method call to the connection manager DataSource.DataExtract
failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2013-11-28 06:37:59.07     Code: 0xC0047017
Source: DFT_Example SSIS.Pipeline     Description: ODBC_SRC Example failed validation and returned error code 0x80004005. End Error Error: 2013-11-28 06:37:59.12     Code: 0xC004700C
Source: DFT_Example SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2013-11-28 06:37:59.16     Code: 0xC0024107     Source: DFT_Example
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1).Started: 6:37:58 AM Finished: 6:37:59 AM Elapsed: 1.373 seconds. Process Exit Code 1.
The step failed.
Note:
My source server is 32 bit and development environment in 64 bit
if anybody have idea please share your knowledge

Hi BIRam,
Based on the current information, the issue may be caused by the factor that the SQL Server Agent Service Account doesn’t have access to the MySQL server. Try to create a SQL Server Agent Proxy account that has sufficient permission on the MySQL server.
In addition, also pay attention to the package protection level setting.
For more information, please see:
http://social.technet.microsoft.com/Forums/sqlserver/en-US/e13c137c-1535-4475-8c2f-c7e6e7d125fc/how-do-i-troubleshoot-ssis-packages-failed-execution-in-a-sql-agent-job?forum=sqlintegrationservices.
Regards,
Mike Yin
TechNet Community Support

Report Subscription by email error - The SQL Agent service is not running

Hello All,
This may be an easy answer, so please excuse my ignorance if I am overlooking something simple. I a simply trying to setup Report Subscriptions to be emailed to me. We currently have essentially 3 servers in use in our environment - a CAS, a Site server
and a SQL 2012.
I have configured the email settings in Reporting Services Configuration Manager on the Site server and was finally able to see the email option in the Create Subscription Wizard, but it errors out with:
System.Web.Services.Protocols.SoapException: The SQL Agent service is not running. This operation requires the SQL Agent service. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SchedulerNotRespondingException: The SQL Agent service is not running.
This operation requires the SQL Agent service. at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateSubscription(String Report, ExtensionSettings ExtensionSettings, Boolean isDataDriven, DataRetrievalPlan DataRetrievalPlan, String
Description, String EventType, String MatchData, ParameterValueOrFieldReference[] Parameters, Guid batchId, String& SubscriptionID) at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateSubscription(String Report, ExtensionSettings
ExtensionSettings, String Description, String EventType, String MatchData, ParameterValue[] Parameters, String& SubscriptionID)
We do not have SQL installed locally, therefore it makes sense that the Agent service is not running. How do I subscribe to alerts in SCCM without a local installation of SQL?
-Brad

I am positive - see screenshots below of services on the SQL server:
Yes, reports work perfectly otherwise... Just cannot subscribe.
-Brad

Error with SSIS package running as SQL Agent job

I have a strange issue.
I have a SQL Agent job that execute 5 steps, each step is an SSIS package that imports a CSV file to a temp table, then executes a SQL script to update a production table.
This job runs every 3 mins, every day, and has been for over a year.
Every once in a while it will start failing on step 2. Sometime it only happens for a couple of runs, other times I have to restart the SQL server. Once it corrects itself, it could be months before it happens again, but usually happens every
few weeks.
The error in the job history is: "Unable to bulk copy data. You may need to run this package as an administrator"
Obviously I have all the permissions correct, as it was running successfully every 3 mins before this error suddenly starts. I'm at a loss as to what the problem is. It is always on step 2, which is identical to step 1 except its a different CSV file
going to a different table. As I typed this, it failed twice, then was successful afterwards.
Any ideas where to look for further information? I've checked the event viewer and looked in the SQL logs, nothing stands out at this time.

Hi Kerberos35,
It seems to be caused by the UAC feature which makes SSIS use the low-permissions token of the administrator Windows account under which the job runs. This issue is described in the following KB article:
http://support.microsoft.com/kb/2216489/en-us
To resolve the issue, you can install the latest service pack for your SQL Server. To work around this issue, you can also use one of the following two methods:
Method 1: Replace the SQL Server Destination components in the Data Flow Tasks that are failing with OLE DB Destination components that point to the same SQL Server connection manager.
Method 2: Create a SQL Server Agent proxy by using a Windows account that is not a member of the local Administrators group after you assign Create Global Objects permissions to that account.
To do this, follow these steps:
Click Start, point to Administrative Tools, and then click Local Security Policy.
Expand Local Policies, and then click User Rights Assignment.
In the details pane, double-click Create global objects.
In the Local Security Policy Setting dialog box, click Add.
In the Select Users or Group dialog box, click the user accounts that you want to add, click Add, and then click OK two times.
Regards,
Mike Yin
TechNet Community Support

Get error from SQL AGENT: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024

I am running SQL Agent that executes an SSIS process from sql server1. The SSIS process executes its SQL/tables/sp’s against another sql server2.
I get an error after adding data flow tasks with transaction supported within a sequence with transaction required. The error, “The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024 "The transaction
manager has disabled its support for remote/network transactions"
Prior to adding this sequence everything was working from sql agent, and there were other sequences with oledb destinations.
Everything works when running within SSIS Package.
I see this article on similar issue,
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/0bfa2569-8849-4884-8f68-8edf98a9b4fe/problem-to-execute-a-package-and-tasks-with-a-certain-transactionoption-property-i-need-help?forum=sqlintegrationservices
“I had similar issue and solved by setting the following on both the machines. Allow Remote Clients, Allow Remote Administration,
Allow Inbound Clients, Allow Outbound Clients, and TIP are enabled in Component Services/My Computer/Properties/MSDTC/Security Configuration.”
I don’t want to remove transaction required for the “Remove Duplicates from Staging” sequence.
Anyone seen this?
Greg Hanson

DTC was running on remote computer. The problem was it was no longer accepting transactions from remote servers. This was in SSIS so I had to turn to "Transaction Supported" for all Data Flow Transactions.
Greg Hanson

[SQLSTATE 42000][Error 4834] - SQL Agent Job failing

Hello,
I have started getting the below error message on a bulk insert job that has been running over several months.
Error is:
Executed as user: domain\svc_sql. You do not have permission to use the bulk load statement. [SQLSTATE 42000] (Error 4834). The step failed.
Domain\svc_sql is also service account for SQL Server. Both the SQL server and SQL agent are running under this account and it has sysadmin and bulkadmin privileges.
Bulk insert is from csv file in a folder for which domain\svc_sql has full permission.
I've now ran out of ideas.
Could anybody advise?
Many thanks,
Mohan

Hi Mohan,
According to the error message, it can be caused by that when SQL Server Agent performs EXECUTE AS USER, you are by default sandboxed into the database, and therefore you don't have access to server-level tasks.
To work around the issue, as Praveen’s post, you can set the database TRUSTWORTHY to ON, however it might cause some security issues. For more details, please review this article:
Giving Permissions through Stored Procedures Ownership Chaining, Certificates and the Problematic EXECUTE AS.
Personally, I recommend you create the bulk insert job as a CmdExec job which uses SQLCMD to run scripts. For more information about CmdExec job, please review this article:
Create a CmdExec Job Step.
There is also a discussion about the error 4834 in the following thread.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/48621876-11a0-468c-95b4-2a682f0134aa/bulk-insert-not-working-through-an-agent-job
Thanks,
Lydia Zhang

SSIS error authenticating proxy with SQL Agent

Hello,
I'm a BI Analyst (not DBA) and I've asked our IT department for access to SSIS and SQL Server Agent to deploy packages to import data from Oracle nightly and transform it into a dataset in SQL Server 2012 using SSIS.
I've written several packages, deployed these to a SQL Server. These run fine when ran locally through Object Explorer > Integration Services Catalog > SSIDB by right clicking/execute.
However our DBA has set up an SSIS Proxy that I can use in conjunction with SQL Server Agent to run these packages. However, when I try to use this proxy I get the error message:
'Unable to start execution of step 1 (reason: error authoenticating proxy ad\[name removed], system error. The username or password is incorrect. The step failed.'
I've tried packages with security for 'dontsavesensitive' and 'encryptsensitivewithuserkey' but neither work. I'd like to rule anything out that I'm not doing, however I think it is a permissions issue (happy to be proven wrong though).
Can anyone offer suggestions for next steps please?
Thanks,
ZP

Hi V,
Thanks again.
I went to the general tab and it is all greyed out and the credentials box is empty - though I can click on the button with three dots on. However, it just takes me to a credentials form but doesn't give me any options to select from. The box for SSIS is
ticked though.
It is all greyed out - I presumed this is because I haven't got permissions to set what the proxy can do?
I tried select * from sys.credentials - didn't return any information (zero rows).
I'm (mostly!) convinced the packages are fine - I've created several simple packages to demonstrate the same thing to our DBA and these simple packages all run fine when executed directly through SSMS but never work through SQL Agent with SSIS Proxy. His
thinking is that its because I need to run them with security as 'dontsavesensitive' but these dont work either.
Do you know if I should be asking for a specific permission/credential?
Thanks!

Error 17058 Unable to start a service account on MSSQLServer and SQL Agent

hi
I am intalling SQL 2008 standard with SP1 on a Windows Server 2003 R2 SP2.
I installed as "local service account" for MSSQLServer (SQL database engine) and SQL agent.
But I want to change to "service account" as [domain\svc_XXX] for MSSQLserver and SQL agent.
I add the [domain\svc_XXX] in local security policy - "Log as a service"
and also add in SSMS - Security - New Login (windows authentication.
When I started the MSSQLserver and SQL agent using the [domain\svc_XXX], I got an error 17058. Initerrlog: could not open error log file." Operating system error=3 (The system cannot find the path specified).
I don't know where else to look at..
Also, how do I find the cumulative service pack for SQL server 2008 standard?
thanks
Irene

Hi Irene:
By seeing your error message "When I started the MSSQLserver and SQL agent using the [domain\svc_XXX],
I got an error 17058. Initerrlog: could not open error log file." Operating system error=3 (The system cannot find the path specified)."
Please provide access to domain\svc_XXX on
log file directory.
Thanks,
Satish Kumar.
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

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

Getting Error while trying to execute SSIS package through sql agent

Hi,
I have created a package in SSIS 2008.
I have created sql Agent job which runs perfectly on my Pc.
I tried to create anew job on another pc which doesnot have SSIS.
When i tried to run the Job,
i am getting folowing error:
Executed as user: LT-MAGFIH$. tion. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:51:31 PM Finished: 8:51:35 PM Elapsed: 4.024 seconds. The package execution failed. The step failed.
Please let me now how can i solve.

Hi AjayChigurupati,
I would suggest you check you are install or use the dtexec utility correctly:
On a 64-bit computer, Integration Services installs a 64-bit version of the
dtexec utility (dtexec.exe). If you have to run certain packages in 32-bit mode, you will have to install the 32-bit version of the
dtexec utility. To install the 32-bit version of the
dtexec utility, you must select either Client Tools or Business Intelligence Development Studio during setup.
By default, a 64-bit computer that has both the 64-bit and 32-bit versions of an Integration Services command prompt utility installed will run the 32-bit version at the command prompt. The 32-bit version runs because the directory path for the 32-bit
version appears in the PATH environment variable before the directory path for the 64-bit version. (Typically, the 32-bit directory path is
<drive>:\Program Files(x86)\Microsoft SQL Server\100\DTS\Binn, while the 64-bit directory path is
<drive>:\Program Files\Microsoft SQL Server\100\DTS\Binn.)
For detail information, please see:
http://technet.microsoft.com/en-us/library/ms162810(v=sql.105).aspx
To using SQL Server Agent to Run a Package, please refer to the steps in th article below:
http://technet.microsoft.com/en-us/library/ms138023(v=sql.105).aspx
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

SQL Agent and Oracle Error

Hello,
This is the error I'm getting:
Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation. Provider is unable to function until these components are installed.
I only have ODAC installed and that's all, not the full-blown Oracle database. This is on a Windows Server 2003 (32-bit) Developing on this server was fine, I could run packages within BIDS, create a deployment utility and actually run the package from Integration Services, it's when creating a SQL Agent Job and trying to execute the steps where I get the above error.
Any advice would be appreciated.
Thanks.

SQL Agent is a SQL Server tool... it is looking for an extremely old version of the Oracle client, one that is no longer supported. Since this is the support forum for the Visual Studio tools, I don't know anything about that.
Based on the fact that SQL Agent is looking for such old software, I would naively suggest:
1) Upgrade SQL Agent to a new version
2) If you do not intend it to connect to Oracle anyway, try to find out where in the configuration it is attempting to do so.

SQL Server Agent Error

we are constantly getting this error from event log: what is the remedy.
Unable to read local eventlog (the parameter is incorrect)

Hi Madalo,
Did the issue resolved?
What's the version and service pack level of the SQL Server instance did you installed? Please try to install the latest service pack. You can download and install SQL Server service pack from the following link:
Update Center for Microsoft SQL Server
If the issue persists, please post the SQL Server error log for further analysis.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

7-zip SSIS task run with SQL agent gives "This operation requires an interactive window station" error.

I have set up the 7-zip parameters to not require a response, and the process task object to have a "hidden" window. This is also running with a proxy on the SQL agent. Is there some other proxy setting, or package or job setting that
needs to be done to let this run with the SQL agent? It works fine running under BIDS.
Thanks,
John

Actually you can implement zipping unzipping functionality without using any third party tools if you want. You'll just need to include j# redistributable functions for that in a script task.
See
http://microsoft-ssis.blogspot.in/2011/01/unzip-files-with-ssis.html
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

2008R2 SQL Agent error 14258

Similar Messages

Maybe you are looking for