SQL Jobs failed

Hi DBA's
Please check the following error message and help how to troubleshoot this issue.
Date                      11/14/2014 9:30:00 AM
Log                         Job History (Accounts Update)
Step ID                 1
Server                   MSSQL\SEASONS
Job Name                            Accounts Update
Step Name                         Acct Update
Duration                              00:00:00
Sql Severity                        0
Sql Message ID                 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted                          0
Message
Executed as user: TEST\myDB. ... 9.00.5000.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started: 9:30:00 AM Error: 2014-11-14 09:30:00.41     Code: 0xC0016016
Source:       Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error
occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2014-11-14 09:30:00.61     Code: 0xC001401E     Source: Acct Connection manager "Flat File Connection
Manager 2"     Description: The file name "\\sybase03\ong_uploads\Accounts\Account.csv" specified in the connection was not valid. End Error Error: 2014-11-14 09:30:00.61     Code: 0xC001401D
Source: Acct      Description: Connection "Flat File Connection Manager 2" failed validation. End Error Error: 2014-11-14 09:30:00.67     Code: 0xC... The package execution fa...
The step failed.
DBA

Hi DBA,
Based on the error message that “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.”, it seems that the issue is related to Protection Level Settings.
During development, the default value of the protection level of packages is EncryptSensitiveWithUserKey. In this way, uses a key that is based on the current user profile to encrypt only the values of sensitive properties in the package. Only the same user
who uses the same profile can load the package. If a different user attempts to execute the package, package execution fails. To fix this issue, please change this:
Package Proprties Window >ProtectionLevel -- Change that to EncryptSensitiveWithPassword PackagePassword -- enter password-> somepassword
Then on SQL Agent Job Step, go the Command Line Tab, manually edit command line with the command below:
/De[crypt] password
As to the error message” Acct Connection manager "Flat File Connection Manager 2" Description: The file name "\\sybase03\ong_uploads\Accounts\Account.csv"
specified in the connection was not valid.”, the error occurs because of the UNC path is either does not exist or the access to it is denied to the current user. Please check this issue.
Reference:
Setting the Protection Level of Packages
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Similar Messages

Send error messages in DatabaseMail when SQL Job fails/succeeds

Hi ,
I have setup a profile and account for sending mail using DatabaseMail. I have a SQL JOB. If the job fails, I receive an Email.
Till this point, everything works fine. This is what the email looks like :
JOB RUN: 'GenerateJVForLabourAndOverheads_R11Testing' was run on 20-12-2012 at 10:10:50
DURATION: 0 hours, 0 minutes, 0 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by Schedule 58 (Execute SP). The last step to run was step 1 (Execute SP).
Now what I want is, if the job fails for any reason, that error message should appear in the email message body.
for example, FK_Constraint error , Conversion errors or any error that caused my sql job to fail.
Is this possible ?
Any help appreciated,
Thanks,
Lok..

This is one way to do, assuming your job has 2 steps and step 1 does the main part.
So,in your step 2 of the job, you can add the below code and
declare @body1 varchar(8000)
select top 1 @body1 = [Message] from msdb.dbo.sysjobhistory A INNER JOIN msdb.dbo.sysjobs B ON B.Job_id = A.Job_id
where B.Name = <<JobNaMe>> and A.step_id =1 order by instance_id desc
EXECUTE msdb.dbo.sp_send_dbmail @profile_name = <<YourMail profile>>
,@recipients = <<RecipeintEmail>>,@subject =<<Your subject>>,@body = @body1
I guess, you can also log the job step output to an outputfile and have it sent as an attachment to your mail... this might help if you have many steps in one job....
HTH!!
Please mark as 'Answer', if the solution solves your problem.

SQL Job failed on mirror failover

We have a SQL Server 2005 database mirroring configuration on two Windows Server 2008 R2 servers. There is a SQL Agent job that is triggered by a WMI Event Alert, using the query "SELECT * FROM DATABASE_MIRRORING_STATE_CHANGE WHERE State=8 AND
DatabaseName=[DB]".
The first step in the SQL job triggered by the alert is to execute a stored procedure in the database [DB] that has now just become principal on this server. On a recent automatic failover test, forced by rebooting the principal server, the mirror-turned-principal
fired the above alert, but the first job step failed with the error: "Unable to connect to SQL Server '(local)'. The step failed."
Subsequent job steps that executed other stored procedures in the same database were successful.
Some time line information:
9:50:34 SQL Log entry: "The mirrored database [DB] is changing roles from MIRROR to PRINCIPAL due to Auto Failover."
9:50:45 Alert fired
9:50:46 Job step 1 failed "Unable to connect to SQL Server '(local)'. The step failed."
9:51:32 Job step 2 "Changed database context to [DB]" (and the step succeeded)
This alert/SQL job combination has never failed in this manner on a similarly configured pair of mirror servers.
Can anyone shed light on why that first step would fail? Could the failover time be long enough that the database is not yet accessible? Yet the error refers to the server itself, not the database.
Since this is a production database, I have limited access to test the failover sequence, but any suggestions on what caused this job step to fail are welcome.

Hi,
I understand that it is the production environment, it is limited to take some testson it. Here are some comments:
1. When a job step fails, view the job history. Sometimesit will tell us more information aboutthe failure cause.
2. If you have a test environment, verify if the job are able to execute without the failover. I suspect it is failover that caused job step 1 to failed. In the test environment, we can change order of the job step and test the issue.
Regarding it is a production database, for quick and accurate answers to your questions, you can open a case with Microsoft, please contact Microsoft Customer Service.
http://support.microsoft.com/kb/295539
Thanks.
Tracy Cai
TechNet Community Support

Why is the SQL job failing on weekends while it successfully runs in weekdays?

I wrote a job to create a backup. But this seems to work fine in weekdays. After weekends I can't find any backups. History viewer shows only 1 day of history and therefore I can't see what happened to the job in weekends. How can I increase the amount
of history information from Job activity monitor? And is there a way to trace what happened in weekends? Please advice.
mayooran99

Have you checked the job current schedule ? is this scheduled for daily ? have you checked the backup location ? how many day backups are exist? is there any recent backups ?
backup details :
http://www.mssqltips.com/sqlservertip/1601/script-to-retrieve-sql-server-database-backup-history-and-no-backups/
Change sql agent jobs history retenions :
--Set new Limit size of job history
EXEC msdb.dbo.sp_set_sqlagent_properties @jobhistory_max_rows=-1,@jobhistory_max_rows_per_job=-1
--delete jobhistory older than 7 days and schedule following as a job or use gui
DECLARE @oldest_date DATETIME
SET @oldest_date = DATEADD(DAY,-7,GETDATE())
PRINT @oldest_date
EXEC msdb..sp_purge_jobhistory NULL,NULL,@oldest_date
OR
Rightclick on SQL Server Agent, properties-> History, You can increase the history log size(in rows) and max Job history rows per job .
OR
USE[msdb]
GO
EXEC[dbo].[sp_set_sqlagent_properties]
@jobhistory_max_rows=10000,
@jobhistory_max_rows_per_job=1000
GOReference :http://msdn.microsoft.com/en-us/library/ms189683.aspxhttp://sqlserverplanet.com/dba/increase-job-history
Raju Rasagounder Sr MSSQL DBA

[SCOM 2007 R2] Alert on every failed SQL job

We want alert on every failed SQL Agent job. However, we only get one alert.
We check that SQL 2000 would alert on every failed SQL job, but SQL 2005 & 2008 didn't behavior like that.
What should we do?
Thanks.

Hello Matt,
For auditing purposes we need to email every sql job failure and sql job success. What I've seen is if the out of box "A(n) sql job failed to complete sucessfully", it will generate only one alert until the alert is manually resolved.
And the alert if generated from a server with many Sql instances, it will generate for each windows event the same alert for each instance.
If I create a rule and use "sql jobs" as the "rule target" for each application event every job generates an alert.
So, if we use "Last Run Status", when it's working, I've seen that if two failures are generated within the frequency interval specified "600" seconds by default only one alert is generated.
The MOM rule that uses this criteria from the Application event log:
Event Number equals '208'
Source Name matches regular expression 'SQLServerAgent|SQLAgent.*'
Parameter 1 doesn't match wildcard 'OnePoint - *'
Parameter 3 matches regular expression '^(失败|Fehler|Failed|Error|Échec|Non[ ]riuscito|失敗|失敗|실패)$'
As far as I can tell works fine.
One other respondent recommends using "windows computer" as the "rule target". I think this will have the same problem as the ootb rule and only generate an alert once.
I think potentially a rule that uses "agent job" as the rule target would work if in the criteria, we could add "description" contains "job name". But the gui doen't expose "event description" as a criteria.
Any help would be appreciated.
Thanks,
Paul

SQL Server Agent Job Failing on Job Step

Hi,
Firstly, apologies if this post has been made in the wrong group. Running SQL Server 2012. I'm attempting to add a SQL Server Agent Job which calls a stored procedure that sends a Database Mail message. The SQL Server and SQL Server Agent
both run under the NT AUTHORITY\NETWORK SERVICE account. The Database Mail service has been enabled, and a public profile created. When running the stored procedure manually, I receive no errors - everything runs as expected and I do receive an
email containing the expected information.
I've created the job, job step, job schedule, attached the schedule to the job, and assigned the job to server, all using T-SQL without error. I've also enabled the mail profile on the SQL Server Agent, and I know that part is working because when
the job fails, I get an email notification of the failure.
I've checked the command text in the job step and parsed it within the SQL Job Step Edit window to confirm, it shows as parsing correctly. However, when I manually run the job itself, I get the following:
Execution of job failed. See the history log for details.
I check the history log and it shows:
[474] Unable to refresh Database Mail profile Database Mail Profile. (reason: ) (Not a typo, the history log shows no reason)
[260] Unable to start mail session.
[396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
The command text on the failing job step is as follows:
DECLARE @date [varchar](10)
SET @date = CAST(GETDATE() AS [varchar](10))
EXEC [dbo].[GetExceptions]
@company = 'MyCompany',
@checkDate = @date
With regard to the date value being passed as varchar: This stored procedure is used to check for exceptions against multiple databases on this server (hence the company parameter) via dynamic SQL. I'd much prefer to use proper data typing but this
is the only way I could get it to work.
Does anyone have any suggestions on anything else I could check, or insights into why this is failing? Any help is greatly appreciated!
Best Regards
Brad

I am not sure if this really helps but I would do follow the below steps:
1. make sure sql server agent has database mail enabled(rigt click on server agent--properties--alert system--enable database mail and choose right profile.) and RESTART THE SQL SERVER AGENT.(i know you said it i working, but sometimes, restart the
sql server agent might fix)
2. check agent error log and check if any error messages.
3. run the command text you mentioned in sql server and see if it is working.(i know you said it is working but just to make sure).
4. make sure sql server agent service user has permissions to run database mail in msdb. check this https://msdn.microsoft.com/en-us/library/ms186358.aspx
5. Check the output from select * from msdb.dbo.sysmail_log and if it says anything
6.it does not look like the job log is getting truncated but to make sure, get the job step output to a text file.to do this, edit the job step and on the job step properties click on advanced, enter path to the output file. this will give the complete
output for the step.
Hope it Helps!!

SSIS importing comma delimited with double quote text qualifier - Works in VS - SQL Job ignores text qualifier and fails (truncation)

I've created an SSIS package to import a comma delimited file (csv) with double quotes for a text qualifier ("). Some of the fields contain the delimiter inside the qualified text. An example row is:
15,"Doe, John",IS2,Alabama
In SSIS I've specified the text qualifier as ". The sample output in the connection manager looks great. The package runs perfectly from VS and when manually executed on the SSIS server itself. The problem comes when I schedule the package to run via SQL
job. At this point the package ignores the text qualifier, and in doing so pushes half of a field into the next available column. But instead of having too many columns, it concatenates the last 2 columns ignoring the delimiter. For example (pipes are fields):
15|"Doe| John"|IS2,Alabama
So the failure happens when the last half of a field is too large to fit into the next available field. In the case above _John" is 6 characters where the IS2 field is char(3). This would cause a truncation failure, which is the error I receive from the
job history.
To further test this I created a failure flow in my data flow to capture the records failing to be pulled from the source csv. Out of ~5000 records, ~1200 are failing, and every one of the failures has a comma delimiter inside the quoted text with a 'split'
length greater than the next ordinal field. The ones without the comma were inserted as normal and records where the split fit into the next ordinal column where also imported, with the last field being concatenated w/delimiter. Example records when selected
from table:
25|"Allan Percone Trucking"|GI6|California --Imported as intended
36|"Renolds| J."|UI6,Colorado --Field position offset by 1 to right - Last field overloaded
To further ensure this is the problem, I changed the csv file and flat file connection manager to pipe delimited, and sure enough every record makes it in perfectly from the SQL job execution.
I've tried comma delimited on the following set ups. Each set up failed.
SSIS Server 2008 R2 RTM
DB Server 2008 RTM
DB Compat 80
SSIS Server 2008 R2 RTM
DB Server 2008 R2 RTM
DB Compat 80
SSIS Server 2008 R2 RTM
DB Server 2008 RTM
DB Compat 100
SSIS Server 2008 R2 RTM
DB Server 2008 R2 RTM
DB Compat 100
Since a lot of our data comes in via comma delimited flat files, I really need a fix for this. If not I'll have to rebuild all my files when I import them to use pipe delimiters instaed of commas. I'd like to avoid the extra processing overhead if possible.
Also, is this a known bug? If so can someone point me to the posting of said bug?
Edit: I can't ask the vendor to change the format to pipe delimited because it comes from a federal government site.

Just wanted to share my experience of this for anyone else since I wasted a morning on it today.
I encountered the same problem where I could run the package fine on my machine but when I deployed to a server and ran the package via dtexec, the " delimeter was being replaced with _x0022_ and columns all slurped up together and overflowing columns/truncating
data etc.
Since I didn't want to manually hack the DTS XML and can't install updates, the solution I used was to set an expression on the textdelimiter field of the flat file connection with the value "\"" (a double quote). That way, even if the one stored in XML
gets bodged somewhere along the way, it is overridden with the correct value at run time. The package works fine everywhere now.

SSIS Package compiled successful, in SQL Server Integration Service package executed sucessful, But fail to run in MS SQL Job Scheduler

Hi Everyone,
I having a problem to transfer data from MS SQL 2005 to IBMAS400. Previously my SSIS was running perfectly but there is some changes I need to be done in order for the system to work well. Considers my changes are minimal & just for upgrades (but I did
include DELETE statements to truncate AS400 table before I insert fresh data from MS SQL table to the same AS400 table), so I compile my SSIS package & it run successfully & I passed it into MS SQL Integrated Service as 1 of the packages & manually
executed the package & the result is the same, that mean it was successful again but when I try to run it in a MS SQL Job Scheduler, the job failed with these message shown below as extracted from the job View history.
Date today
Log Job History (MSSQLToAS400)
Step ID 1
Server MSSQLServer
Job Name MSSQLToAS400
Step Name pumptoAS400
Duration 00:00:36
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: MSSQLServer\SYSTEM. ... 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: today time
Error: on today time
Code: 0xC0202009 Source: SSISMSSQLToAS400 Connection manager "SourceToDestinationOLEDB"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80004005. An OLE DB record is available.
Source: "IBMDA400 Session"
Hresult: 0x80004005
Description: "CWBSY0002 - Password for user AS400ADMIN on system AS400SYSTEM is not correct ". End Error
Error: today
Code: 0xC020801C
Source: Data Flow Task OLE DB Destination [5160]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DestinationClearData" failed with error code 0xC0202009. There may be error messages posted before
this with more information on why the AcquireConnection method ca... The package execution fa... The step failed.
So I hope somebody can shed some hints or tips for me to overcome time problem of mine. Thanks for your help in advance. As I had scoured thoroughout MSDN forums & found none solution for my problem yet.
PS: In the SQL Integrated Services when I deployed the package I set the security of the packages to Rely on server...
Hope this will help.

Hi Ironmaidenroxz,
From the message “Executed as user: MSSQLServer\SYSTEM”, we can see that the SQL Server Agent job ran under the Local System account. However, a Local System account doesn’t have the network rights natively, therefore, the job failed to communicate with
the remote IBMAS400 server.
To address this issue, you need to create a proxy account for SQL Server Agent to run the job. When creating the credentials for the proxy account, you can use the Windows domain account under which you executed the package manually.
References:
How to: Create a Credential
How to: Create a Proxy
Regards,
Mike Yin
TechNet Community Support

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

SQL Server agent job failing to back up database

I have set up a SQL server agent job to back up database on regular basis.. For some reason the back up fails.. Could not find any meaningful info in the logs.. Transaction logs are getting created for the same DB but not the database back up..
The below is my environment..
MS SQL Server 2005 - 9.00.1399.06
Windows 2003 server SP2
Any pointers would be helpful.. I checked the event logs and the agent logs and did not see obvious error.
Thanks

I have set up a SQL server agent job to back up database on regular basis.. For some reason the back up fails.. Could not find any meaningful info in the logs.. Transaction logs are getting created for the same DB but not the database back up..
The below is my environment..
MS SQL Server 2005 - 9.00.1399.06
Windows 2003 server SP2
Any pointers would be helpful.. I checked the event logs and the agent logs and did not see obvious error.
Thanks
NO answer can be provided unless you show us the error message. There can be numerous reasons for backup job to fail. See job history for details please post complete information present in job history.
Check errorlog and note what error message is there at time when the backup job failed. You could find something useful. Please learn how to post question in forum just saying I have a problem will not help both of us.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

" The job failed" in copying database SQL SERVER 2012

I'm trying to copy a database. When going through the Copy Database Wizard, I'm getting a Execute SQL Server Agent Job error. The error states " The job failed. Check the event log on the destination server for details". See below:
Performing operation
Add log for package (Success)
Add task for transferring database objects (Success)
Create package (Success)
Start SQL Server Agent Job (Success)
Execute SQL Server Agent Job (Error) Messages
The job failed. Check the event log on the destination server for details. (Copy Database Wizard)
I can't seem to find what causing this problem. Am I using the correct approach? I just need to copy this database. Thank in advance.

Hi mohammad2050,
When using Copy Database Wizard, please make sure that the SQL Server Agent account or Integration Services Proxy account is a member of sysadmin fixed server role, and has access permission on both of source and target file system.
There is a blog about using SQL Server Copy Database Wizard for your reference .
http://reddy25.blogspot.com/2013/12/copy-database-from-one-server-to.html
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Code in before report getting executed but "Job error is: BIP job failed."

Customer is executing a BIP job that fires a pl/sql procedure via before report trigger. Procedure is completing successfully. But the BIP report is not getting generated. ESS process ends in error with the following error:
oracle.as.scheduler.ExecutionErrorException: ESS-07033 Job logic indicated a system error occurred while executing an asynchronous java job for request 604103. Job error is: BIP job failed.
     at oracle.as.scheduler.rp.AsyncFinalizeProcessor.processFinalizeRequest(AsyncFinalizeProcessor.java:131)
     at oracle.as.scheduler.rp.AsyncJavaSysExecWrapper.finalizeExecution(AsyncJavaSysExecWrapper.java:250)
     at oracle.as.scheduler.rp.EndpointProcessor.finalizeExecute(EndpointProcessor.java:1018)
     at oracle.as.scheduler.rp.EndpointProcessor.finalizeExecuteWrapper(EndpointProcessor.java:980)
     at oracle.as.scheduler.adapter.EndpointImpl.finalizeExecute(EndpointImpl.java:561)
     at oracle.as.scheduler.ejb.EssAppEndpointBean.finalizeExecute(EssAppEndpointBean.java:162)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy197.finalizeExecute(Unknown Source)
     at oracle.as.scheduler.ejb.ESSAppEndpoint_t596cy_MDOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.MDOMethodInvoker.invoke(MDOMethodInvoker.java:35)
     at oracle.as.scheduler.ejb.ESSAppEndpoint_t596cy_MDOImpl.finalizeExecute(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.invokeFinalizeExecute(RequestProcessor.java:8133)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.execStage_Finalize(RequestProcessor.java:7331)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.process_execute(RequestProcessor.java:4813)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.dispatchHandler(RequestProcessor.java:2833)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.processExecuteEvent(RequestProcessor.java:696)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.processUpdateEvent(RequestProcessor.java:1345)
     at oracle.as.scheduler.adapter.ra.WorkUnitWorkerBase.processWork(WorkUnitWorkerBase.java:199)
     at oracle.as.scheduler.adapter.ra.WAWorker.run(WAWorke...
Any tips/pointers on possible issues? Could this be a template corruption?

Any reply for the above error please.I do have the same issue.
Please suggest.

Data Collection Jobs fail to run

Hello,
I have installed three servers with SQL Server 2012 Standard Edition, which should be identically installed and configured.
Part of the installation was setting up Data Collection which worked with out problems on two of the servers, but not on the last where 5 of the SQL Server Agent Jobs fails.
The jobs failing are:
collection_set_1_noncached_collect_and_upload
Message:
Executed as user: NT Service\SQLSERVERAGENT. The step did not generate any output. Process Exit Code -1073741515. The step failed.
collection_set_2_collection
Step 1 message:
Executed as user: NT Service\SQLSERVERAGENT. The step did not generate any output. Process Exit Code -1073741515. The step failed.
collection_set_2_upload
Step 2 message:
Executed as user: NT Service\SQLSERVERAGENT. The step did not generate any output. Process Exit Code -1073741515. The step failed.
collection_set_3_collection
Step 1 message:
Executed as user: NT Service\SQLSERVERAGENT. The step did not generate any output. Process Exit Code -1073741515. The step failed.
collection_set_3_upload
Step 2 message:
Executed as user: NT Service\SQLSERVERAGENT. The step did not generate any output. Process Exit Code -1073741515. The step failed.
When I try to execute one of the jobs, I get the following event in the System Log:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Application Popup"
Guid="{47BFA2B7-BD54-4FAC-B70B-29021084CA8F}" />
<EventID>26</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated
SystemTime="2013-06-04T11:23:10.924129800Z" />
<EventRecordID>29716</EventRecordID>
<Correlation
/>
<Execution
ProcessID="396" ThreadID="1336" />
<Channel>System</Channel>
<Computer>myServer</Computer>
<Security
UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="Caption">DCEXEC.EXE - System Error</Data>
<Data Name="Message">The program can't start because SqlTDiagN.dll
is missing from your computer. Try reinstalling the program to fix this
problem.</Data>
</EventData>
</Event>
I have tried removing and reconfiguring the Data Collection two times using the stored procedure msdb.dbo.sp_syscollector_cleanup_collector and removing the underlying database.
Both times with the same result.
Below are the basic information about the setup of the server:
Does any one have any suggestions about what the problem could be and what the cure might be?
Best regards,
Michael Andy Poulsen

I tried running a repair on the SQL Server installation.
This solved the problem.
Only thing is that now I have to figure out the mening of these last lines in the log of the repair:
"The following warnings were encountered while configuring settings on your SQL Server. These resources / settings were missing or invalid so default values were used in recreating the missing resources. Please review to make sure they don’t require
further customization for your applications:
Service SID support has been enabled on the service.
Service SID support has been enabled on the service."
/Michael Andy Poulsen

SSIS job fails on connection to target db - works in debug

the ongoing saga...
I have a web application developed through VS 2012 which has a button on a form that when operated starts a SQL Server agent job on the server that runs an SSIS package. The website and the instance of SQL Server with the agent and SSIS package are
on the same windows 2008 r2 server. When the button is operated no exceptions are raised but the SSIS package did not execute. The SQL Server Agent job owner is sa ...that seemed to resolve some issues as originally I had the owner being another
admin on the same box. Now the job seems to be failing on connect to the target database on an IBM iSeries DB2 server. The job runs fine in debug connecting to the db and doing its task successfully.
The log indicates that the user specified in the connection manager is using an invalid password or is otherwise unable to connect, although it works fine in debug mode and save password is specified.  I use BIDS remote desktoped to the server
when developing and debuging.
Can anyone show me whats wrong now? Thanks much in advance for any help, Roscoe
The log shows as follows...
The job failed. The Job was invoked by User DOMAINNAME\myuserid. The last step to run was step 1 (Step1).,00:00:00,0,0,,,,0
06/12/2014 13:34:50,runWebDevSmall,Error,1,NTSVR59,runWebDevSmall,Step1,,Executed as user: WINDOWSSERVRNAME\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.0.5500.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights
reserved.    Started: 1:34:50 PM Error: 2014-06-12 13:34:50.31     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node "DTS:Password"
with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error:
2014-06-12 13:34:50.84     Code: 0xC0202009     Source: vbTestsmall Connection manager "iSeriesname.DBNAME.iSeriesuserid"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE
DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "IBMDA400 Session" Hresult: 0x80004005 Description: "CWBSY0002 - Password for user iSeriesuser on system iSeriesname is not
correct ". End Error Error: 2014-06-12 13:34:50.86     Code: 0xC00291EC     Source: clear iSeriesname libraryname tablename Execute SQL Task     Description: Failed
to acquire connection "iSeriesname.DBNAME.iSeriesuserid". 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:34:50 PM Finished: 1:34:50 PM Elapsed: 0.703 seconds. The package execution failed. The step failed.,00:00:00,0,0,,,

Hi Arthur, Thanks for the reply,
BIDS would not let me save the package with ProtectionLevel of ServerStorage giving error...
Failed to apply package protection with error 0xC0014061 "The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the destination supports secure storage capability.". This error occurs when saving
to Xml.
(vbTestsmall)
...but it would let me change the ProtectionLevel to EncryptSensitiveWithPassword so I did that and provided the jobstep in the agent with the password and the agent was able to run successfully.
Thanks for all the help...I will follow your blog, Roscoe

Running a SSIS package with SQL Job and Linked Server

I have a SSIS 2008 package. In one of the Script task I am calling a stored procedure which is using Openquery using linked server. I deployed this package with protection level as "EncryptWithPassword" and gave a password to the package.
Created a SQL job and edited its command line to include the password. If I login to SQL Server Mgmt Studio with Windows Authentication and run the job manually it runs fine. But when I schedule it then I get an error that "The Communication link to Linked
server failed".
Please help

Hi Vivek.B,
The issue should occur because the SQL Server Agent Service Account or SQL Agent Proxy account under which the job step runs doesn’t have sufficient permissions on the linked server.
If the job owner is the sysadmin fixed server role, the job can be run under the SQL Server Agent Service Account or a proxy account, then please make sure the SQL Agent Service Account or the proxy account has corresponding login on the linked server. If
the job owner is not a sysadmin fixed server role, the job must run under a proxy account. In this case, make sure the proxy account has a corresponding login on the linked server.
Reference:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/10/13/who-owns-my-job-and-who-runs-it.aspx
Regards,
Mike Yin
TechNet Community Support

SQL Jobs failed

Similar Messages

Maybe you are looking for