Weird question on Job history

hi there:
I've created a job and schedule it to run every 5 mins. This job contains 2 steps. This job has been running for a while and I want to check it out. I saw this log file which is very confusing.
at 9/17/2014 2:10pm, it ran for 3 steps as supposed to be 2 steps. How is that possible?
Also there is no job running history at 2:05pm which is odd. I do know that this job was running very odd( extremely slow)
at 2:05pm...
Anyone saw this before? please feel free to share your experience.
Thanks
Hui
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Really weird. Would it be possible for you to share the job script?
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Similar Messages

Where is "Job History" for e-print?

I am using HP AIO B210e, W7. I have my printer set for e-print. I would like to see list of email jobs I have sent to my printer but do not know where to find "Job History". Please help!
Thank you
Marty
This question was solved.
View Solution.

Job history can be viewed in your ePrint Center account that was set up when first installing printer and enabling web services.
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

Format of Date Field in RAR background job history page

Hi Everyone,
Is it possible to customize the format of the fileds: "last run", "next start" in RAR background job history page?
By default it is in the format yyyy-mm-dd.
I am just wondering my customer's requirement is possible or not?

Hi,
There is no option to set the date format in the Configuration settings. Check the FM /VIRSA/ZCC_GET_STATREC_DATA which has the CALL FUNCTION 'GET_SYSTEM_TIMEZONE'. RAR will read the time from the system.
You may look at formatting the the date format here.
Hope this helps!!
Warm Regards,
Raghu

How can i find the option to delete a recent print job from the "View Job History

1. Photosmart 5510 e-ALL-IN-ONE SERIES
2. Window 7 64 bit
How can i find the option to delete a recent print job from the "View Job History

Hello alfmswongg,
Currently there is no option to delete print jobs from the "View Job History" section of ePrintCenter.
If I have solved your issue, please feel free to provide kudos and make sure you mark this thread as solution provided!
Although I work for HP, my posts and replies are my own opinion and not those of HP.

Execute Process Task showing all the SSIS Config variables in SQL Job History

Hi,
Am using an Execute Process task to execute my child package. And executing the Parent package from a SQL JOB.
I am using the same config file for both Parent and Child packages.
After the Job execution was Successful / Failure, in Job history it is showing all the variables from Config file which are not using in Child package. With the below message.
"The package path referenced an object that cannot be found"
I don't want to catch all the Variables information in Job History. Instead I need only the Success / Failure message.
PFA Screen.
Thanks,
Sailaja

see
http://www.mssqltips.com/sqlservertip/1417/custom-logging-in-sql-server-integration-services-ssis/
https://www.simple-talk.com/sql/ssis/ssis-event-handlers-basics/
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

SQL Server Agent - Job History not being recorded (SQL Server 2005)

I have been trying to get to the bottom of an issue with SQL Server Agent not recording any job history. I am using SQL Server 2005 on a single Windows Server 2008 machine (i.e. no other domain controllers/active directory servers).
The SQL Server Agent service is configured to 'Log On As' NT user account 'sqlagent'. The jobs themselves are executed successfully (all 'Transact-SQL' type steps actually use the 'sa' account) however the there is no actual job history to be found for any
of the jobs -- in the SQL Activity monitor, the 'Last Run Outcome' is always 'Unknown' and the 'Last Run' date is always 'Never' for all jobs; in the SQL Job History Viewer there are no entries for any instances of a job being executed.
The 'sqlagent' NT user account ia a member of the 'Administrators' NT group; the 'Administrators' group appears under Security > Logins on the database server. I have another server that also uses the same setup with a 'sqlagent' NT user account, on that
database server the 'sqlagent' user account appears under Security > Logins and the SQL job history works correctly. I have attempted to add the 'sqlagent' to the Logins on the affected server using the SQL Server Surface Area configuration but this operation
returns an error, detailed below.
Additionally, I have attempted to use the built-in NT system account 'NETWORKSEVICES' to run the SQL Agent Service but this also results in exceptions in the error log and no job history being recorded. The entries in the error logs are very similar to those
from the 'sqlagent' NT user account but instead the user is referred to as 'NT AUTHORITY\ANONYMOUS LOGON' in the error logs, again these are detailed below.
Many thanks in advance for anyone's time and help with this issue!
Arthur
The following errors are raised in SQL Server Agent > Error Logs each time a job is executed:
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[298] SQLServer Error: 18452, Login failed for user ''. The user is not associated with a trusted SQL Server connection. [SQLSTATE 28000]
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
If the SQLAgent service is configured to use the NT system account 'NETWORKSERVICE' then the following errors are returned instead:
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000]
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
I have tried granting the 'sqlagent' NT user account with SysAdmin Server Role privaledges using the SQL Server User Provisioning tool in SQL Server Surface Area Configuration, but this always throws the following, similar error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Error: 18452)
===================================
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476
Server Name: 127.0.0.1,1344
Error Number: 18452
Severity: 14
State: 1
Line Number: 65536
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at sqlprov.SysAdminServerRole.ProvisionInstance(Instance instance, String userName)
at sqlprov.ProvisionTask.Provision(Instance instance, String userName)
at sqlprov.MainForm.ProvisionTasks()

Hi Rama,
Thanks for your reply. I have run the query you specified and can see only one entry with "NTLM" in the auth_scheme column, all of the rest have "SQL". It figures that the entry with "NTLM" is relating to the one NT user account that can successfully log
in to the service (as mentioned in my reply to Nag above, this is the NT user account that installed the service on the machine). I have also executed the same query on the other machine that I mentioned in my original post and this contains two "NTLM" entries,
I'd assume that these relate to the NT user that installed the software and the correctly working "sqlagent" NT user account that is correctly logging the job history on that machine.
I think the problem is very much to do with granting access to new NT user accounts, as per the KB article that you have quoted above. In this case, it is not relating to scenarios 1 or 2 as these relate to SQL Server logins and this issue is about a Windows
Authentication login. As I mentioned to Nag above, I am unable to grant any NT user accounts with access to the service however the NT accounts are all defined locally on the same machine as the SQL server is installed (i.e. there is no domain controller,
active directory controller, etc) so I don't understand how the Windows login cannot be verified.
Any further advice on the issue would be greatly appreciated, please let me know if there is any more information I can provide to help diagnose the problem.
Many thanks!
Arthur

SSIS Package "running" in Job History?

My first post to Technet fora: Hello to everyone!
Last March our DW-system was migrated from SQL Server 2005 to SQL Server 2008 R2. Several SQL Server Agent jobs using SSIS packages were also migrated. The packages were converted from 2005 to 2008 with Visual Studio conversion tools.
After the migration several (but not all) of these jobs show a peculiar behavior in 'View Job History'.
As you can see the job history consists of two rows. But the lower one - from Execute Package Utility - has the green 'arrow head', as if it were still running.
In the Selected Row Details Pane, however, everythig seems to be ok:
Message
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.2500.0 for 64-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 8:00:02
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 8:00:02
Finished: 8:00:03
Elapsed: 1.482 seconds
Is this something to be concerned about? The job seems to work just fine (a simple sql query, results to flat file).

Welcome to the fora :)
Strange, everything indicates the job finished, except for that little icon.
I would ignore it and classify it as a visual glitch, but I understand it can be annoying.
MCTS, MCITP - Please mark posts as answered where appropriate.

CCMS job monitoring -- RZ20 job history node get duplicated record

Hi,
I configured CCMS/Solution Manager auto monitoring job failure. When a job failed on my satellite system, it created a alert and send notification to my CEN, which is my solution manager. Then solution manager send e-mail to a distribution group.
This is working fine until last week. Now when a job failed, in job history node of RZ20 of my satellite system, the alerts are created mutiple times even the job actually only failed once. For some reasons, the history node of the alerts are updated every 5 minutes with the same job failure. More interestingly, after one hour, it did not create alerts any more. However, as the result I get many e-mails with the same job failure in this once hour, which I expect only one e-mail.
Do you guys encounter the same problem? I am wondering something has been unintentionaly turned on so it's updating every 5 minutes. I want to turn it off. I looked at SM37 try to find if some batch jobs are doing this but did not find anything running on every 5 minutes.
Any helpful answers will definitely be appreciated and reward point.
Yujun Ran

Hi Suhas,
Once we had the same issue. But once we updated the current ccmsagent in both Solution manger and the satellite system the issue got resolved.
Regards,
Rafikul Hussain

Cups Job History shows Name 'Unknown' User 'Withheld'

We have previously used the cups interface to review our print job history and indenify problems with jobs that went missing at the press.
This worked great in previously versions of OS X, but in Lion every job we send, regardless of what printer we send it to, is coming up Name 'Unknown' User 'Withheld' as shown in the attached screeshot.
Does anyone have and suggestions for a fix? I failed to find an answer via google. /___sbsstatic___/migration-images/165/16507372-1.jpg

This was an intentional change to improve privacy, and the privacy settings can be changed in the cupsd.conf file:
http://www.cups.org/documentation.php/ref-cupsd-conf.html#JobPrivateValues
Hope this helps.

Want to change the SQL Server Agent Job History Text Files Location

We have SQL Server 2014 installed on a couple servers, but they were not consistent on directory paths during the installs. I am trying to get the servers to all match.
On one server, SQL Server the Agent Log and Job History files were being written to [H:\Data Root Directory\MSSQL12.MSSQLSERVER\MSSQL\Log].
I want to change that to [H:\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log] to match the other server.
I have ALREADY gone into SSMS - [SQL Server Agent] - [Properties] and changed the "Error Log " "Fle Name" to [H:\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\SQLAGENT.OUT]. And that is working great.
In [SQL Server Configuration Manager] - [SQL Server (MSSQLSERVER)] - [Properties] - Startup Parameters entries have been changed to the new path (-d, -e, and -l), and under [Advanced] both Data Path and Dump Directory are pointing to the new path.
In [SQL Server Configuration Manager] - [SQL Server Agent (MSSQLSERVER)] - [Properties] - [Advanced] Dump Directory is pointing to the new path.
However, the job's History text files are still being written to the old path.
There is no setting in the Jobs or the Maintenance Plans that controls the history file location.
I have searched the registry and changed three settings from the old path to the new path. The registry does NOT contain any more references to the old path.
I rebooted the server, but when the jobs run their history text files are still be written to the old path.
Does anybody have any ideas?? Thanks

I checked the [Job] - [Step] - [Advanced ] - "Output File", and the field is blank.
I then reviewed all the tabs and left menu items in the Job...I cannot find any where the references the old path.
I then went to the Maintenance Plan and checked every thing there. Still cannot find what is referencing this old path.
SQL Server is also still writing xel files to this old path...if that offers any clues.
The text file being generated is the recap of the Job run. Starts with this:
Microsoft(R) Server Maintenance Utility (Unicode) Version 12.0.2430
Report was generated on "xxxxxxxxxxxxxxx".
Maintenance Plan: SQL_Backups_Log
Duration: 00:00:03
Status: Succeeded.
Details:
Thanks for the ideas....

Need help on TRacking Jobs history of an ETL package

Hello there, Kindly Elaborate me the way to track Job history of my ETL package.
For Sample I am running that package on my local Server.
i need a SQL Server tAble, Which Gives me following information
-Name of the package
-TYpe of job.: Etl or TSql
-Is_SuccessRun
-LAst run time
-ErrorRun
-Last Execution time Taken by the ETL.
Kindly Guide me on this,
Thanks in advance

Hi Aditya,
We cannot integrate the package execution information into the job history.
This sysssislog table is created in the msdb database when we install SQL Server Integration Services. If you configure logging to log to a different SQL Server database, a sysssislog table with this format is created in the specified database. So, whether
the sysssislog table in the MSDB database or in a specified database depends on how you create the connection manager for the SSIS log provider for SQL Server, and either one is okay.
For more information about implementing SQL Server logging, please see:
http://www.bidn.com/blogs/ShawnHarrison/ssis/2436/basics-of-ssis-logging-part-1-enabling-and-using-sql-server-provider
http://www.msbiguide.com/2013/10/logging-in-ssis-sql-server-log-provider/
In addition, you can implement custom logging using event handlers:
http://consultingblogs.emc.com/jamiethomson/archive/2005/06/11/SSIS_3A00_-Custom-Logging-Using-Event-Handlers.aspx
Regards,
Mike Yin
TechNet Community Support

Missing steps in Job History

Hi,
I am having this strange issue where in the job some steps are missing. There are 20 steps out of which in the job history the first 4 steps are not showing up. The packages being called in these 4 steps are running successfully.
Also, in job history, I can see only the history for current run. All the previous entries are missing.
Any information would be very helpful.
Thanks
Jatin

By default is set to 100, you change it by going to
Object Explorer -> SQL Server Agent –> Right click -> Properties -> History - > check Maximum
job history per job
-Prashanth

Job history retention

Hi,
I have job history setting like this:
I would like to see keep backup history for long time (this job setup last year). But I can only see job history earliest at 04/17 this year.
Does anyone have idea what happen to this job history? What process can purge it? Any suggestion will be appreciated.

Have you checked anything runing to clear the history ?
USE msdb ;
GO
EXEC dbo.sp_purge_jobhistory
@job_name = N'NightlyBackups' ;
GO=======================
By Default this is set to 100. We have to modifying this to be 1000 or as per the requirment. USE [msdb]
GO
EXEC msdb.dbo.sp_set_sqlagent_properties @jobhistory_max_rows_per_job=1000
GOJob Execution progress :===========================
SELECT j.name, COUNT(*) Executions
FROM msdb.dbo.sysjobs j
INNER JOIN msdb.dbo.sysjobhistory h
ON j.job_id = h.job_id
GROUP BY j.name
ORDER BY Executions DESC
Follow this link for more details and configuration:=====================================================SQL Server Instance
SQL Server Agent
Right click on SQL Server Agent
Select the 'Properties' option
Select the 'History' page
http://www.mssqltips.com/sqlservertip/1269/missing-sql-server-agent-history/
Raju Rasagounder Sr MSSQL DBA

Job History in Succession Planning

Hi,
Has anyone used Oracle Succession Planning in R12.1.1 ?
I have setup the module as per the implementation guide.
I am not able to see the Job History of the employee in the Job History box.
Has anyone seen this work? Is there any additional configuration required ?
Any comments on this will he highly appreciated.
Regards,
-Debojyoty

In 10.2.0.5 Grid Control, in order to speed up the response time for the page, 'All' behavior was changed to show only all Jobs executed in the past 24 hours. So when the job activity page loads, you see job history from only the last 24 hrs.
To view complete history, you can switch to advanced search and change search filters to view
complete history. This has been fixed in 11.1 by adding help text on the page.

Two weird questions about BP maintenance......SOS!!!

Two weird questions about BP maintenance......SOS!!!
The procedure is like this:
These informtion will be import to SAP:
BP information
Address Information of this bp.
Communication information of this BP
1. check if the bp exist, if yes, update the BP.Then go to 3.if no go to 2
2. Create a bp with the Address information and communication information
3. Check if the Address information has been existed,if yes go to 4.else go to 5
4.Update the address information with the communication information.
5.Create a new address for this BP.
And the problem I got is like this:
1. After I changed the BP information, such as the surname,lastname etc.Use this BAPI
"BAPI_BUPA_CENTRAL_CHANGE",I commited it.Then I call the BAPI "BAPI_BUPA_ADDRESS_CHANGE" to change the Address of this BP,however
When I call the BAPI_BUPA_ADDRESS_CHANGE,it always told me the BP is locked by myself.............
I am sure I do not open the BP in the other window.And I commit it after I call the BP Change BAPI.
2. When I change the communication information ,it always told me BAPIADTEL you want to update does not exist in this system.....I am sure it does.
Who can help me??
Thanks very much

Hi,
1) Problem with the lock. To commit the changes after the BAPI_BUPA_CENTRAL_CHANGE API, instead of using commit work to commit, Use BAPI_TRANSACTION_COMMIT. This should solve the problem. This wil help in clearng the buffers of BP.
2) in the BUPA_ADDRESS_CHANGE, for telephone there are two parameters to be filled IT_ADTEL, IT_ADTEL_X
IT_ADTEL : Should be filled with the telephone details etc (Consnumber should not be filled for inserts. This should be filled only for updates).
Corresponding IT_ADTEL_X structure has to be filled with update flag as 'I', 'U' or 'D' based on the task.
Hope this helps. Let me know if some more info is needed.
Regards,
Sudheer.

Weird question on Job history

Similar Messages

Maybe you are looking for