SQL Server Agent fails to connect to DB after enabling mirror on failover cluster

Hello:
We have multiple databases running in a Failover Cluster instance: SQL 2012SP1 on Server 2008 R2 failover cluster (NOT AlwaysOn). We are trying to add a high-performance mirror in a standalone instance for DR. My understanding is that should be a perfectly
normal, supported configuration.
The mirroring is working properly; however, the clustered SQL Server agent is unable to run jobs that run in the mirrored databases.
We get the following in the job log: Unable to connect to SQL Server 'VIRTUALSERVERNAME\INSTANCE'. The step failed.
There is a partner message in the agent log: [165] ODBC Error: 0, Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. [SQLSTATE IMH01]
The cluster is not a mulitsubnet cluster. All hosts are connected to the same subnets and there is no storage replication. I can not find any place where I can adjust the connect string options for SQL Agent.
Any guidance or suggestions on how to resolve this would be appreciated.
~joe

SQL Team - MSFT:
Thank you for taking the time to research and provide a clear answer.
This seems very much a workaround and very unsatisfactory.
You are correct, there is an IP dependency with OR condition. Moving to an AND condition is not viable for us. The whole point is to provide network redundancy. With an AND condition, if EITHER network interface fails, the service will go offline or fail
to come online without manual intervention. This is arguably worse for uptime than having a single interface available.
We are in process of rewriting all our SQL jobs to start in tempdb before transitioning to the appropriate target database. If this works for all of our jobs, I will mark the above response as answer.
Again, thank you for the answer.
Regards,
Joe M.

Similar Messages

SQL Server Agent Failed to decrypt protected XML node

I'm getting the below error when trying to run sql server agent to run an SSIS package. I've updated folder security to allow sql server agent access, but cannot get the package to execute within SQL Management Studio. The package runs find in SSIS.
11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 12:12:00 PM Error: 2014-11-30 12:12:02.65 Code: 0xC0016016 Source: LoadStgProspects 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: 2014-11-30 12:12:03.88 Code: 0xC0016016 Source: LoadStgProspects 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: 2014-11-30
12:12:04.74 Code: 0xC0209303 Source: LoadStgProspects Connection manager "Excel Connection Manager" Description: The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered. If the 64-bit driver
is not installed<c/> run the package in 32-bit mode. Error code: 0x00000000. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
End Error Error: 2014-11-30 12:12:04.74 Code: 0xC020801C Source: Load prospect files Prospect xls [231] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection
method call to the connection manager "Excel Connection Manager" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error:
2014-11-30 12:12:04.74 Code: 0xC0047017 Source: Load prospect files SSIS.Pipeline Description: Prospect xls failed validation and returned error code 0xC020801C. End Error Error: 2014-11-30 12:12:04.74
Code: 0xC004700C Source: Load prospect files SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2014-11-30 12:12:04.74 Code: 0xC0024107 Source:
Load prospect files Description: There were errors during task validation. End Error Error: 2014-11-30 12:12:04.74 Code: 0xC00220DE Source: LoadStgProspects Description: Error
0xC0012050 while loading package file "C:\Users\Jim\Documents\Visual Studio 2010\Projects\SSISTraining\SSISTraining\LoadStgProspects.dtsx". Package failed validation from the ExecutePackage task. The package cannot run. . End Error DTExec:
The package execution returned DTSER_FAILURE (1). Started: 12:12:00 PM Finished: 12:12:04 PM Elapsed: 4.337 seconds. The package execution failed. The step failed.,00:00:04,0,0,,,,0

Hi selfdestruct80,
According to your description, you created SSIS package and it works fine. But you got the error message when the SSIS package was called from a SQL Server Agent job.
According to my knowledge, the package may not run in the following scenarios:
The current user cannot decrypt secrets from the package.
A SQL Server connection that uses integrated security fails because the current user does not have the required permissions.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses.
A registry-based SSIS package configuration uses the HKEY_CURRENT_USER registry keys. The HKEY_CURRENT_USER registry keys are user-specific.
A task or a connection manager requires that the current user account has correct permissions.
According to the error message, the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword as ArthurZ mentioned. To solve the problem, you need to go to Command Line tab, manually specify the paassword in SQL Agent Job with the command like below:
/FILE "\"C:\Users\xxxx\Documents\SQL Server Management Studio\SSIS\Package.dtsx\"" /DECRYPT somepassword /CHECKPOINTING OFF /REPORTING E
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
Wendy Fu
TechNet Community Support

SSIS Import XML task running in SQL Server Agent fails

I have created an SSIS package to import some XML files into my SQL2014 datawarehouse. If I run this package through the visual studio designer it works fine. The XML files are stored on a remote share accessed via UNC path. When I schedule the package to
run using SQL server agent it fails with the following errors :-
Executed as user: SPRINGFIELD\MSSQL. Microsoft (R) SQL Server Execute Package Utility Version 12.0.2000.8 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 12:01:53 Error: 2014-11-18 12:01:59.78
Code: 0xC02090CF     Source: Import Screen XML XML Source [199]     Description: There was an error setting up the mapping. The device is not ready. End Error Error: 2014-11-18 12:01:59.78
Code: 0xC0047019     Source: Import Screen XML SSIS.Pipeline     Description: XML Source failed the prepare phase and returned error code 0xC02090CF. End Error DTExec: The package execution returned DTSER_FAILURE
(1). Started: 12:01:53 Finished: 12:03:32 Elapsed: 98.859 seconds. The package execution failed. The step failed.
The user MSSQL has been granted full permissions to the remote share. If I remove these permissions then I don't get an error - but I also don't get any data imported. I have granted the MSSQL user xp_cmdexec permission. Both my SQL server database engine
and agent are running as the MSSQL user.
There must be some permission step I am missing - can anyone tell me what it may be ?

FYI: The XSD path is hardcode... if you want it to be more flexible you can add an expression on that property:
http://microsoft-ssis.blogspot.com/2014/09/xsd-location-hardcoded-in-xml-source.html
Please mark the post as answered if it answers your question | My SSIS Blog:
http://microsoft-ssis.blogspot.com |
Twitter

I cant re-start sql server (2008 developer) on win 7 workstation after enabling tcpIP -- been running fine for a year

I had successfully installed sql server 2008 Developer edition on a win7 pro workstation about a year ago. I has been running fine for the last year (locally and running .Net 4.5 framework). All services (RS, Analysis) running fine.
Then today someone decided to enable tcpIP and went to services to restart the server on my workstation but it would not restart. I ran repair from the sql server installation center x64 - still nothing - the server wont restart. But Analysis server and Reporting
services work fine -- these services can restart fine ... Just not the main server. I'm also running Sql Server express. that runs OK too. But I need my sql server 2008 Developer to run. I looked at the system event viewer -- it said this:
The SQL Server (SQLDEVELOPER) service terminated with service-specific error The specified module could not be found..
I went to Control panel ... services and looked at the properties for Sql Server Developer -- the path was listed as:
C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLDEVELOPER\MSSQL\Binn\sqlservr.exe" -sSQLDEVELOPER
Everything in windows explorer appears to be in order. How can I restart the server? Do I need to uninstall it and then reinstall it? Any suggestions appreciated.
I rebooted the entire workstation a few times already also, but still server won't restart. What to do?
Rich P

There were several Error 2014-07-14 12:57:31.27 Server Apr 2 2010 15:48:46
Copyright (c) Microsoft Developer Edition (64-bit) 2014-07-14 12:57:31.27 Server 2014-07-14 12:57:31.27 Server 2014-07-14 12:57:31.27 Server 2014-07-14 12:57:31.27 Server 2014-07-14 12:57:31.28 Server 2014-07-14 12:57:31.28 Server 2014-07-14 12:57:31.28 Server 2014-07-14 12:57:31.28 Server -d C:\Program Files\Microsoft -e C:\Program Files\Microsoft -l C:\Program Files\Microsoft 2014-07-14 12:57:31.29 Server 2014-07-14 12:57:31.29 Server 2014-07-14 12:57:31.38 Server 2014-07-14 12:57:31.40 Server 2014-07-14 12:57:31.41 spid7s 2014-07-14 12:57:31.46 spid7s 2014-07-14 12:57:31.46 spid7s 2014-07-14 12:57:31.46 spid7s 2014-07-14 12:57:31.51 spid7s 2014-07-14 12:57:31.51 spid7s 2014-07-14 12:57:31.51 spid7s 2014-07-14 12:57:31.52 spid7s 2014-07-14 12:57:31.54 spid7s 2014-07-14 12:57:31.55 spid7s 2014-07-14 12:57:31.58 spid7s 2014-07-14 12:57:31.78 spid10s 2014-07-14 12:57:31.78 Server 2014-07-14 12:57:31.78 spid7s 2014-07-14 12:57:31.82 spid10s 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.89 Server 2014-07-14 12:57:31.97 spid10s 2014-07-14 12:57:32.19 spid14s 2014-07-14 12:57:32.22 spid13s 2014-07-14 12:57:32.22 spid10s 2014-07-14 12:57:32.22 spid17s 2014-07-14 12:57:32.22 spid15s 2014-07-14 12:57:32.22 spid18s 2014-07-14 12:57:32.22 spid14s 2014-07-14 12:57:32.22 spid19s Cannot close event log Rich P Logs (for today) since I tried restart several times. They appear to say the same thing:
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Corporation
on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
(c) Microsoft Corporation.
All rights reserved.
Server process ID is 4452.
System Manufacturer: 'Dell Inc.', System Model: 'OptiPlex 9010'.
Authentication mode is WINDOWS-ONLY.
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLDEVELOPER\MSSQL\Log\ERRORLOG'.
This instance of SQL Server last reported using a process ID of 2640 at 7/14/2014 12:55:59 PM (local) 7/14/2014 7:55:59 PM (UTC). This is an informational message only; no user action is required.
Registry startup parameters:
SQL Server\MSSQL10_50.SQLDEVELOPER\MSSQL\DATA\master.mdf
SQL Server\MSSQL10_50.SQLDEVELOPER\MSSQL\Log\ERRORLOG
SQL Server\MSSQL10_50.SQLDEVELOPER\MSSQL\DATA\mastlog.ldf
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
Detected 4 CPUs. This is an informational message; no user action is required.
Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
Starting up database 'master'.
1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
Resource governor reconfiguration succeeded.
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
SQL Server Audit has started the audits. This is an informational message. No user action is required.
FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLDEVELOPER'.
SQL Trace ID 1 was started by login "sa".
Starting up database 'mssqlsystemresource'.
The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
Starting up database 'model'.
Warning: Support for the VIA protocol is deprecated and will be removed in a future version of Microsoft SQL Server. If possible, use a different network protocol and disable VIA.
Server name is 'WKS308\SQLDEVELOPER'. This is an informational message only. No user action is required.
Clearing tempdb database.
A self-generated certificate was successfully loaded for encryption.
Error: 26055, Severity: 16, State: 1.
The SQL Server failed to initialize VIA support library [QLVipl.dll]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: 0x7e.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x7e, status code 0x60. Reason: Unable to initialize the VIA listener. The specified module could not be found.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x7e, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The specified module could not be found.
Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Starting up database 'tempdb'.
A new instance of the full-text filter daemon host process has been successfully started.
Starting up database 'ReportServer$SQLDEVELOPER'.
Starting up database 'msdb'.
Starting up database 'Sales_DW'.
Starting up database 'DB1dev'.
Starting up database 'ConferenceData'.
Starting up database 'ReportServer$SQLDEVELOPERTempDB'.
Starting up database 'SubsDBstuff'.
because there are still event handle users active.

Unable to start SQL server agent service

hi,
We have 2 Node SQL Cluster that was working fine. Then We migrated the Linux DNS to Windows DNS successfully.Now restarted the SQL Server after it when we try to start the SQL Server Agent service its says the below msg while machine name and cluster
entries are in windows dns and resolving the IP to name and name to IP
Error msg: The MSSQLSERVER service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service." error message.
But whenever we set the Linux DNS Server ip in SQL Servers then it successfully starts the service. Now i want to know why its happening and what are the requirements or DNS entries/SPN which we missing when we migrated the linux DNS to windows
dns
Sagar

I was experiencing this issue or one just like it on one of our SQL clusters (SQL Server 2008 R2, two node).
The fix for us was the database Security Login for: NT SERVICE\SQLAgent$<instancename> was missing. The actual service account assigned to the SQL Agent service was a valid domain account and we had the credentials correct in the service
configuration, so no changes were needed there.
Using SQL Server Management Studio we manually added this BUILT IN account ( NT SERVICE\SQLAgent$<instancename> ) to the instance, and then assigned it user role = sysadmin (to go along with the default role = public).
Once this was done, we tried to restart the clustered SQL Agent service and it started and remained started.
Hope this helps someone, we spent over a day pouring over the installation trying to find the cause.
This worked for me, thanks:-)

DPM failing SQL backups due to error: "the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F85)

I ran across this error starting on 6/4/2011 and have been unable to find the root of the problem. In our environment, we have a DPM 2010 server dedicated to backing up all our SQL envrionment (about 45 SQL Servers total). All of the SQL
environment is backing up fine except for a SQL Cluster Application. This particular SQL Instances is part of a 6 node failover cluster with 6 SQL Instances distributed amongst them. The other 5 SQL instances in the cluster are backing
up fine; only one instance is failing. The DPM Alerts section shows this error when attempting to do a SQL backup of one of the databases on this SQL instance:
Affected area: KEN-PROD-VDB001\POSREPL1\master
Occurred since: 6/11/2011 11:00:56 PM
Description: Recovery point creation jobs for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com have been failing. The number of failed recovery point creation jobs =
4.
If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
The DPM job failed for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com because the SQL Server instance refused a connection to the protection agent. (ID 30172 Details:
Internal error code: 0x80990F85)
More information
Recommended action: This can happen if the SQL Server process is overloaded, or running short of memory. Please ensure that you are able to successfully run transactions against the SQL database in question and then retry the failed job.
Create a recovery point...
Resolution: To dismiss the alert, click below
Inactivate alert
I have checked the cluster node this particular SQL instance is running on using Perfmon and the machine is nowhere near capacity on CPU, memory, network, or Disk I/O.  I have failed this SQL Application to another node in the cluster and
receive the same error (this other node has another clustered SQL application on it that is actively running as well as backing up fine). The only thing that I am aware of that has changed is that we installed SP2 for SQL 2008 about 2 weeks prior
to when the failures started to occur. However, we updated all six clustered SQL Instances at the same time and only this one is having this issue so I don't believe that caused the problem. We are running SQL 2008 SP2 (version 10.0.4000.0)
on all clustered instances along with DPM 2010 (version 3.0.7696.0) on this particular DPM server that has the issue.
One last thing, I have also noticed errors in the event log pertaining to the same SQL backups that are failing (but the time stamps are not concurrent with each backup attempt):
Log Name:      Application
Source:        MSDPM
Date:          6/13/2011 1:09:12 AM
Event ID:      4223
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KEN-PROD-BS002.aarons.aaronrents.com
Description:
The description for Event ID 4223 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.
Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSDPM" />
    <EventID Qualifiers="0">4223</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-06-13T05:09:12.000000000Z" />
    <EventRecordID>68785</EventRecordID>
    <Channel>Application</Channel>
    <Computer>KEN-PROD-BS002.aarons.aaronrents.com</Computer>
    <Security />
</System>
<EventData>
    <Data>DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.
Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
</Data>
    <Binary>3C00440070006D005700720069007400650072004500760065006E0074003E003C005F005F00530079007300740065006D003E003C00490044003E00330030003C002F00490044003E003C005300650071003E0031003800330033003C002F005300650071003E003C00540069006D00650043007200650061007400650064003E0036002F00310033002F003200300031003100200035003A00300039003A0031003200200041004D003C002F00540069006D00650043007200650061007400650064003E003C0053006F0075007200630065003E0066003A005C00640070006D00760033005F00720074006D005C0070007200690076006100740065005C00700072006F0064007500630074005C0074006100700065006200610063006B00750070005C006400700073007700720069007400650072005C00760073007300660075006E006300740069006F006E0061006C006900740079002E006300700070003C002F0053006F0075007200630065003E003C004C0069006E0065003E003800310035003C002F004C0069006E0065003E003C004800610073004500720072006F0072003E0054007200750065003C002F004800610073004500720072006F0072003E003C002F005F005F00530079007300740065006D003E003C00440065007400610069006C006500640043006F00640065003E002D0032003100340037003200310032003300300030003C002F00440065007400610069006C006500640043006F00640065003E003C002F00440070006D005700720069007400650072004500760065006E0074003E00</Binary>
</EventData>
</Event>
Any help would be greatly appreciated!

Don't know if this helps or not, but I also noticed another peculiar issue that is derived from this problem. If I go to "Modify protection group", then expand the cluster, then expand all six nodes in the cluster, five of them show "All SQL Servers"
and allow me to expand the SQL Instance and show all databases; the one that is having a problem backing up, when I expand the node, doesn't even show that SQL exists on the node, when in fact, it does.
I would also like to add that the databases on this node that will not backup are running fine. They run hundreds of transactions daily so we know SQL itself is OK. Even though it is a busy SQL Server, there is plenty of available resources as
the SQL buffer and memory counters show the node is not under durress.

Error: Failed to acquire connection while exporting a file using SSIS package through SQl Server Agent job.

Hi Team,
I am running a sql server job which is loading data to a sharepoint document library.File is an excel format and is getting loaded
when executed through SSDT solution .But when i am using an SQL Agent job to pick up the file it doesnt get the path and agent job fails with the error "Failed to acquire connection".I have deployed the SSIS Package through SQL Server 2012 deployment
methodologies.
I am not able to trace the error of loading data from a sharepoint library.library. Sql agent jobs works fine when i give local path.The
account which is running the sql agent job is the same who has access to document library.I also tried to run the job through proxy account. I am using a xml configuraion to store my credentials.I am able to palce the same file to a network drive in the same
server through sql server agent job. The only problem is when I am trying to load the file to a sharepoint folder.
Thanks,
Arsa..

Is that the WebDAV method that you are suggesting here to map the n/w drive?
Its kind of webdav but you will be using windows nw drive to store data
yes, I am able to create the file to D: , but didn't check with the C:.
Try with c:, as c: require special permisssions
If this helped you resolve your issue, please mark it Answered

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

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

Excel Import Fails in SQL Server Agent Job but not when executed in BIDS

We have a SQL Server agent job that has ran successfully for the past 6 months. It started failing about a week ago. I don't believe anyone installed anything on the server. The proxy account used to run the job is an admin on the server.
I've tried everything I can think of or that I found on searches. I even changed the connection manager from an Excel source to using an Microsoft office 12.0 Access Database Engine OLEDB connection and it still runs in BIDs and not as an agent job.
I also setup my LANID as a proxy account to see if the job would run (checking security) -- and it fails with the same error.   I also made sure the path is
\\server\share rather than a drive letter. Any ideas?
The package is executed in 32 bit mode. The package still runs fine in BIDS (where BIDs is opened on the server) but fails in the SQL Agent job with:
Executed as user: xxxxxx\xxxxxx. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 9:00:00 AM Error: 2014-12-01 09:00:02.46
Code: 0xC0202009     Source: xxxxxx Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE
DB record is available. Source: "Microsoft Access Database Engine" Hresult: 0x80004005 Description: "External table is not in the expected format.". End Error Error: 2014-12-01 09:00:02.65
Code: 0xC020801C     Source: Load File to Staging Excel Source [43]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager
"Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2014-12-01 09:00:02.77
Code: 0xC0047017     Source: Load File to Staging SSIS.Pipeline     Description: Excel Source failed validation and returned error code 0xC020801C. End Error Error: 2014-12-01 09:00:02.90
Code: 0xC004700C     Source: Load File to Staging SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2014-12-01 09:00:03.02     Code: 0xC0024107
Source: Load File to Staging      Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 9:00:00 AM Finished: 9:00:03 AM
Elapsed: 2.761 seconds. The package execution failed. The step failed.

I logged on to the server with the account that the SQL Agent runs under and ran the following from a command
line to execute the package:
"D:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\DTEXEC.exe" /FILE
"\"K:\SSIS\xxxxxx\xxxxx.dtsx\"" /CHECKPOINTING OFF
/REPORTING EWCDI /X86
I wanted to see if it was a security issue with the agent account account - but
this ran fine.
I then updated the SQL Agent job to use an operating system command instead
of a SSIS package on the job step. This fails...
The issue is definately with the SQL Server Agent

Sql server agent job failing

Hi, I created a ssis package, that simply transfer an excel sheet into ole db, it works on its own, but when I try to use the sql server agent service, the first step is successful,but the second step of execution is not, but I don't have enough details
to check the problem.
when I check the database , a table is created, with only the column headers, but no rows.
please can some one guide me. cheers.
this was in the error log, i checked, and imake sure the file dtx, or the excel was not opened, but what i dont know is about the file permission
,ssa3,Error,1,USER-PC,ssa3,ssas3,,Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:38:23
Error: 2014-10-23 11:38:23.34
Code: 0xC0202009 Source: Package Connection manager "Excel Connection Manager" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.
Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "The Microsoft Jet database engine cannot open the file 'C:\Users\User\Desktop\dup.xls'. It is already opened exclusively by another user<c/>
or you need permission to view its data.".
Code: 0xC020801C Source: Data Flow Task Excel Source [2] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection
Manager" failed with error code 0xC0202009.

You can also create a proxy account in sql agent with required permissions to folder etc and configure it to run the job so that it always works
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SSIS package fails under SQL Server Agent job

Hi All
I have designed a SSIS package to encrypt a file using Cipher (EFS) it works fine from BIDS & Package Execution Utility.
But SQL Server Agent job is failing to do this. I am getting the error as
" In executing C:\Windows\System32\Cipher.exe /e /a C:\Test.txt at "",The Process Exit code was 1 while the expected was 0."
Please help me.
Thanks

Two things that usually come to mind when this happens from BIDS locally to the SQL Agent are
1. Security is not
adequate under the SQL Agent Service Account
Rule the security problem out by setting up a proxy account that you know ahs security to run the needed tasks in the package. Either that or give the service account the permissions needed.
2. 32bit BIDS development and running under a 64bit Platform in your SSIS installation
This can be fixed by selecting run in 32bit more or running the package with the 32bit installed version of DTEXEC found in the Program Files (x86) folder where you installed tools.
Next, setup logging in the package so you get a more detailed error message. Event handlers on the tasks will be much more detailed using the OnError event. you can write that to either a flat file with a data flow in the event handler or simply
insert the event into a table using the ? as the parms. If you need assistance setting that up, here are basic steps for a SQL Server table
1) Select the task and click the event handler tab in BIDS
2) Select OnError event handler in the list
3) Click the enable link and drag a Execute TSQL Task over to the window
4) Create a table in your SQL Server database (create one so you don't litter your user DBs if needed)
5) Open the task and add the connection as needed. Then add this statement
INSERT INTO dbo.TableYouCreated
(PackageName, SourceName, EventInfo)
VALUES (?,?,?)
6) Go to parameter mappings and add 4 new mappings as following
System::PackageName
Input
nvarchar
0
System::SourceName
Input
nvarchar
1
System::ErrorDescription
Input
nvarchar
2
Save and reimport the package and then the event of the errors should insert into the table in detail
Ted Krueger
Blog on lessthandot.com @onpnt on twitter

SQL Server Agent job fails with error : The package execution returned DTSER_FAILURE (1).

Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:00:01 AM Error: 2014-08-15 10:00:07.20
Code: 0xC0047062 Source: Data Flow Task LEAN [6761]
Description: Teradata.Client.Provider.TdException: [Teradata Database] [3006] Logons are disabled.
at Teradata.Client.Provider.WpMessageManager.CheckForError()
at Teradata.Client.Provider.WpMessageManager.ProcessResponse()
at Teradata.Client.Provider.WpLogonManager.Action()
at Teradata.Client.Provider.WpSession.ManagerAction(WpMessageManager manager, UtlStopwatchWrapper watch, Int32 connectionTimeout)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout, String password)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout)
at Teradata.Client.Provider.Connection.Open(UtlConnectionString connectionString, UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.CreateConnection(UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.GetConnectionFromPool(Object owningObject)
at Teradata.Client.Provider.ConnectionFactory.GetConnection(Object owningObject, UtlConnectionString connStr)
at Teradata.Client.Provider.TdConnection.Open()
at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction)
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)
End Error Error: 2014-08-15 10:00:07.35 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline
Description: component "LEAN" (6761) failed validation and returned error code 0x80004005. End Error Error: 2014-08-15 10:00:07.48
Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation.
End Error Error: 2014-08-15 10:00:07.60 Code: 0xC0024107 Source: Data Flow Task
Description: There were errors during task validation. End Error
DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:00:01 AM Finished: 10:00:07 AM
Elapsed: 6.692 seconds. The package execution failed. The step failed.
SQL Server agent job fails with above error, Please let me know process tohandle it.
Thanks,
Vishal.

The error message suggests its the issue with Teradata source database to which SSIS tries to connect within the data flow task. Make sure Teradata database is available and LOGON is enabled.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SSIS fails to load files from network when executed via SQL server Agent (SQL server 2008 R2 SP 2)

Hi All,
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?
Thanks,
Andrei
SSIS question

Hi All,
Thanks for your responses.
I configured the SQL agent service to use my domain account with which I have no porblems accessing the folder. However the issue persisted.
Thanks,
Andrei
SSIS question

SSIS package fails in sql server agent wirh 'Process exit code "-532459699" runs fine when run independantly

I have a SSIS package that fails when running via sql server agent. I can successfully run it from BIDS.    I have created a proxy account that is in the local server administrators group and is sysadmin. SQL Server Agent and SQL
Server Integration Services are running under the same account,
following the the error message:
Error: 2014-02-07 10:29:12.59
   Code: 0xC0029151
   Source: Execute De-linking Execute Process Task
   Description: In Executing "d:\cie\files\working\9426\PowerpointConsole.exe" " 60.ppt" at "d:\cie\files\working\9426", The process exit code was "-532459699" while the expected was "0".
End Error
This package ran successfully on a different server running windows 2003 and sql server 2008 r2. The new environment is windows 7 with sql server 2008 r2.

Hi Gaileg,
As Abhinav said, to check whether it is a 32-bit/64-bit issue, please check whether the package runs in 32-bit runtime mode or 64-bit runtime mode in BIDS by checking the Run64bitRuntime property of the project. Then, make sure the package runs in the same
runtime mode in the SQL Server Agent job by checking or unchecking the “Use 32 bit runtime” option for the Execution options of the job step.
If it is not the issue, please create another job that uses a CmdExec type job step to call the executable “D:\cie\files\working\9426\PowerpointConsole.exe”. If this job also fails, the issue is actually occurs because of the issue between executable and
SQL Server Agent rather than the SSIS package itself.
Regards,
Mike Yin
TechNet Community Support

SQL Server Agent fails to connect to DB after enabling mirror on failover cluster

Similar Messages

Maybe you are looking for