SQL Server Agent Running; Jobs Failing

Jul 9, 2007

Hi. I was wondering if anyone has ever had a problem where nothing seems to be wrong with the server, and SQL Server Agent is up and running, but jobs fail. We had a job run at midnight, and it was the last successful run. Every job failed after that, with an error stating "Unable to retrieve steps for job..." There doesn't seem to be any reason for the problem. The jobs were kicked off manually and they all ran.

The only other error messages we could find were in the Application Event Viewer on the server. But the first error happened days ago and said this: "The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Unable to open shim database version registry key - v2.0.50727.00000."

Since then, every few seconds this error occurred: "Windows cannot load extensible counter DLL MSSQLServerOLAPService, the first DWORD in data section is the Windows error code."

We turned off the performance monitor counters and that error stopped. But we still have no idea if that was the cause of the problem.

This isn't the first time we've had an issue with jobs failing because the steps couldn't be 'found', while SQL Server Agent was up and running.

Has anyone else had this problem?

Thanks!

View 1 Replies


ADVERTISEMENT

SQL Server 2008 :: How To Find All Agent Jobs That Are Currently Running By Query

May 29, 2013

When I give job Id in filter of this query this will give job status of "Success" but actually my job is currently in executing stage. I want to get all jobs that are currently in executing status.

Use msdb
go
select distinct j.Name as "Job Name", --j.job_id,
case j.enabled
when 1 then 'Enable'
when 0 then 'Disable'

[Code] ....

View 4 Replies View Related

SQL Agent Failing When Running SSIS Package

Mar 9, 2006

I deployed my SSIS package to SQL Server 2005.

I have done the following:

1) Gave the sql agent account permissions to the msdb database and other databases

2) Checked the paths for "Data Sources" under properties of my agent in the SSIS properties

3) Set the authentification to Windows and used the sql agent account (a domain account that I setup) to run the agent. I also tried my login. So it's not a permission issue, because I do not get permission errors...it's past this.

What works:

1) Other SQL Agent packages...they are not running an SSIS package, just SQL

2) Running the SSiS package by right-clicking on it in Management Sudio. No errors found in the execution and the package does it's intended function

3) Package runs fine with absolutely no errors in VS 2005

What doesn't work:

1) My agent that points to my SSIS package. All this agent does is run that package. When I run the agent, I get a minimal error message in the job history logs stating the following error message:

03/09/2006 12:49:58,Run EN Process,Error,0,BG-22SQL,Run EN Process,(Job outcome),,The job failed. The Job was invoked by User domainmy_account. The last step to run was step 1 (Run EN SSIS Package).,00:00:02,0,0,,,,0


03/09/2006 12:49:58,Run EN Process,Error,1,BG-22SQL,Run EN Process,Run EN SSIS Package,,Executed as user: domainsqlagent_account. The package execution failed. The step failed.,00:00:01,0,0,,,,0

View 4 Replies View Related

Long Running Agent Jobs

Jan 4, 2008

I’m trying to write a script that will detect long running agent jobs.

Having looked at this article:
http://www.databasejournal.com/features/mssql/article.php/3500276

It appears that agent job job id’s don’t necessarily get stored in the programname of the sysprocesses table. This is true if the agent executes an os command. It also appears that job steps do not get stored in the sysjobhistory until the step is complete so that cannot be used accurately.

Does anyone know of an effective way to find if there are long running jobs other than these methods?

View 1 Replies View Related

SQL Agent Jobs Running On Witness?

Jan 30, 2008



Hi,

I'm trying to configure mirroring with High Availability, Automatic Failover.

I know that all the jobs and maintenance plans need to be copied to the mirror server, and enabled if a mirror database takes over the principal role.

I wonder if it is a good solution to have all agent jobs on the Witness server (no jobs on principal and mirror). And all the jobs select the server where they should run (depending on current role).

One of the advantages of this approach would be that the jobs have to be created only once on the witness.

Will this solution work? What are the downsides of it?

Thanks,

Anna Sibirtseva.

View 5 Replies View Related

Long Running Agent Jobs

Jan 4, 2008

I€™m trying to write a script that will detect long running agent jobs.

Having looked at this article:
http://www.databasejournal.com/features/mssql/article.php/3500276

It appears that agent job job id€™s don€™t necessarily get stored in the programname of the sysprocesses table. This is true if the agent executes an os command. It also appears that job steps do not get stored in the sysjobhistory until the step is complete so that cannot be used accurately.

Does anyone know of an effective way to find if there are long running jobs other than these methods?

View 17 Replies View Related

Transact SQL :: Agent Jobs - Running More Than 3 Hours Based On Job Name?

Sep 24, 2015

I need a sql script for Jobs is running more-than 3 hours in a current server, based on a particular jobs.

View 2 Replies View Related

SQL SERVER JOBS FAILING

Jun 27, 2000

I have created DTS packages to export data to text files....these packages are
running...the jobs that are created to run these packages are failing ...
both the SQL SERVER and the SQL SERVER AGENT are running administrator accounts ...if the job step is run on the command line it works..so basically
some permission that invokes the the command shell is missing...jobs that run just T-SQL steps work fine too....what am i missing out?

View 1 Replies View Related

Execute Sql Server Agent Job Task - Job Immediately Returns Success... However Agent Job Is Still Running???

Nov 30, 2006

when I run a package from a command window using dtexec, the job immediately says success.
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 3:37:41 PM
Finished: 3:37:43 PM
Elapsed: 2.719 seconds



However the Job is still in th agent and the status is executing. The implications of this are not good. Is this how the sql server agent job task is supposed to work by design.



Thanks,

Larry

View 1 Replies View Related

Jobs In SQL Server Agent

Apr 9, 2001

Hi All,
I am not able to see any of the jobs in the enterprise manager that are scheduled on one of our production servers. Have any body seen this type of behaviour of SQL server.. The jobs are there in the SQL as I can query sysjobs table to see there entry.. The jobs are being executed properly when they are supposed to..
Thanks
Ajay

View 2 Replies View Related

Jobs In SQL Server Agent..

Apr 4, 2007

Hello all,
we just moved our databases over from a SQL 2000 server onto a new SQL 2005 server. We had no problem migrating them over, but was wondering if there was a way to migrate the jobs over as well. We have about 20 of them and would prefer not to hav to create them all again on the new server.

Thanks in advance,
Phoenix

View 1 Replies View Related

DB Engine :: Server Agent Job Failing After Moving A Database

Aug 10, 2015

On Saturday we moved a few databases from SQL Server 2005 to a SQL Server 2012 cluster; and as expected some jobs have been failing because of this. The Job in Question executes two stored procedures and then an SSIS package; however when I ran the Job it failed with the error

Msg 7411, Level 16, State 1, Line 1
Server 'servername' is not configured for RPC

I therefore configured the Server for RPC with the following script: -

exec sp_serveroption @server='servername', @optname='rpc', @optvalue='true'
GO
But the job failed again.  So I therefore reran the script with the reconfigure option: -
exec sp_serveroption @server='OCELOT7CLUST', @optname='rpc', @optvalue='true'
GO
reconfigure with override
go

But again the job failed.  I then closed SSMS and reopened it and attempt to run the job again and once again it failed.This is not an issue with the Linked Server as the linked Server is connecting as sa.

View 6 Replies View Related

Document SQL Server Agent Jobs

Feb 27, 2008

Hello,
I need to document all SQL Server Agent Jobs with full description of dependencies - database, table, stored procedure, etc.
Is there are a tool that I can download for that particular use???

Thank you so much

View 11 Replies View Related

SQL Server Agent Jobs And Scheduling

Sep 19, 2007

I created an agent job, and it runs fine, but I want more control over the scheduling. I need to schedule jobs to run Sunday through
Thursday at 8:00pm, skipping Friday.

How can I use the agent job interface and customize the schedule this way? Will I have to resort to a Windows Service and control the
scheduling that way?

View 3 Replies View Related

Log Information For SQL Server Agent Jobs.

Dec 12, 2007



Hi Guys,


I am not sure if this is the right place to put a question on SQL Server Agent.

I have scheduled some SSIS Jobs using the SQL Server Agent, and wanted to know how can I view detailed log information on how the Job ran (particularly Failure Information).

The information in the Log File Viewer to see the job execution log doesnt seem to help much - as it only says weather the Job Failed or Succeeded.

I need to see the reason and/or the step in a job where it failed!

Can someone help me out with some insight into this....


Thanks
Pramod

View 6 Replies View Related

Is There Any Way Of Restoring Sql Server Agent Jobs

Mar 3, 2008



I have a few jobs in sql server 2005 agent that got corrupted that Iwould like to restore.
Do they get backed up and how can I restore them?

View 4 Replies View Related

SQL Server Agent Jobs And A Frequency &< 1 Minute

Jan 22, 2004

Just wondering if anyone knew if it was possible to create a SQL Server agent job that ran once every 30 seconds. I can't enter a value below 1 minute when editing the job schedule in Enterprise Manager.

Alternatively, I can create duplicate stored procedures and set one to run on the minute and one on the half minute. Thought there might be a better alternative to this though and I'll always have to be remembering to makes changes to both sprocs.

Thanks!

View 3 Replies View Related

Sql Server Agent Stops Executing Jobs

Oct 29, 2007

Hello everyone. I'm having a problem with the sql server agent occasionally not executing its scheduled jobs, and unless the sql server agent is restarted they will not execute according to their schedule. I've read many posts on people having problems with running a package manually and then not being able to run it in a job, although that is not my problem since these are jobs that have all run successfully historically, and only until the agent is restarted do they start working again. It is the strangest thing.....we have many different jobs on this server and all of them will just mysteriously stop being executed. Two other things of note, the agent and server processes both run on AD accounts, and we receive this error:



SQL Server Scheduled Job 'X' - Status: Failed - Invoked on: 2007-10-27 02:00:00 - Message: The job failed. Unable to determine if the owner (ADadacct) of job 'X' has server access (reason: Unable to connect to server - check SQL Server and SQL Server Agent errorlogs).



Any help would be greatly appreciated.


View 14 Replies View Related

SQL Server Agent Scheduled Jobs Question

Apr 30, 2007

Hi,

I have couple of questions about the scheduler:

I'd like my packages to run only on weekdays and disable a package if one of the first two packages fail. is it possible to do it?



Thanks

Gulden

View 1 Replies View Related

SSIS Package Vs SQL Server Agent Jobs

Mar 12, 2007

Hello All,
My database application has certain stored procedures which are scheduled to run at certain predefined interval (say once everyday). Now to implement this logic I have two options with me, first being to use the EXECUTE SQL TASK of the SSIS package and schedule it using the windows scheduler and the other is to use the SQL Server Agent Jobs and schedule it there itself. Now the current implementation is using the SSIS packages and I even know that the second approach of using the SQL Server Agents Job is better.
The only thing I want to know is whether it makes sense to invest time in converting my SSIS packages (20 in all) to SQL Server Agent jobs or not. Can somebody briefly explain or give some pointers regarding the performance benefits of Agent Jobs over the SSIS packages.

Thanks in Advance
Mitesh

View 5 Replies View Related

SQL Server,SQL Server Agent,SQL Analysis Resources Failing In SQL 2005 Cluster

Aug 17, 2007

Hi.
I have installed an SQL 2005 Failover Cluster on a Two Node Active Passive Windows 2003 Cluster.If i am trying to failover from the Active node to the passive Node,The Sql Server,Sql Server Agent and SQL Analysis resources fail,However if i reset the passowrd in the services tab of the above three services on the pasive node,the resources come online.
Below is the brief of my setup
1.I have two Active directory domain controllers running Windows 2003 R2 Standard edition with SP2.
2.i have installed a Windows 2003 Two Node Active Passive Cluster as NODE1 and NODE2.
3.The Domain account used to install WIndows 2003 A/P Cluster is Clusteradmin.This account is the member of Administartors on the Domain as well as the Local Admin on NODE1 and NODE2.
4.SQL 2005 with SP2 is installed on both the Nodes as SQL 2005 Failover Cluster.The account used to install SQL 2005 is sqadmin.This account is the member of Administartors on the domain and the member of Local Admins on NODE1 and NODE2.
5.SLQ 2005 has four domain groups for 4 SQL Services.The Services are SQL Server,SQL Server Agent,SLQ Anaylisis Server and Full text Search.
6.Each of these servcie has a seperate service account created for them.All these service accounts areb the members of domain admin and the member of Local Admin on NODE1 and NODE2.
7.Each of these servcies is running under these servcie accounts in the Servcies tab in NODE1 and NODE2.
8.If i fail the resources from NODE1 to NODE2 ,The SQL Server,SQL Server Agent and SQL Anaylisis resources are failing.on going to the service tab of NODE 2 I reset the password for these services,the services come online.
10.The Cluster resources and MSDTC Resources are Failing over successfully.They are coming online successfully.
11,I have a problem with the SQL Server Resources,even if i failback to NODE1 from NODE2,the same resources are failing again.

Plz Advice.
Regards
Khalid

View 1 Replies View Related

SQL SERVER 2005 REPLICATION (MERGE AGENT FAILING : PUSH SUBSCRIPTION)

Mar 27, 2006

ERROR MESSAGE:

"Message: Incorrect syntax near 'NoteID'."

Here is a snipet from the output file:

2006-03-27 13:01:49.820 Skipping file 'NotesHistory_21.sch' because it has already been delivered for a previous article or by a previously interrupted snapshot.
2006-03-27 13:01:49.867 OLE DB Subscriber 'LUZERNV4-PDOSQL4': SET ANSI_NULLS ON

2006-03-27 13:01:49.898 OLE DB Distributor 'LARGOS00-SDI': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:49.945 OLE DB Subscriber 'LUZERNV4-PDOSQL4': SET QUOTED_IDENTIFIER ON

2006-03-27 13:01:50.008 [17%] OLE DB Subscriber 'LUZERNV4-PDOSQL4': CREATE TABLE [dbo].[MSmerge_conflict_EFILE_MERGE_NotesHistory](
[NoteID] [int] NOT NULL,
[CaseRefNum] [int] NOT NULL,
[KeyField] [varchar](500) NOT NULL,
[KeyValue] [varchar](500) NOT NULL,
[Note] [varchar](800) NULL,
[NoteField] [varchar](100) NULL,
[ScanDocID] [int] NULL,
[PDF_ID] [int] NULL,
[RescanCode] [int] NULL,
[RescanNote] [varchar](100) NULL,
[AuditID] [bigint] NOT NULL,
[rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL
)


ꜽśã¹? êœ?Å›B 27 13:01î–”Å›è›ªç —êœ?Å›é”?Ä€Percent Complete: 17
2006-03-27 13:01:50.086 OLE DB Subscriber 'LUZERNV4-PDOSQL4': SET ANSI_NULLS ON


2006-03-27 13:01:50.117 Preparing table 'NotesHistory' for merge replication
2006-03-27 13:01:50.164 OLE DB Subscriber 'LUZERNV4-PDOSQL4': SET QUOTED_IDENTIFIER ON


2006-03-27 13:01:50.195 OLE DB Distributor 'LARGOS00-SDI': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:50.258 OLE DB Subscriber 'LUZERNV4-PDOSQL4': if object_id('MSmerge_conflicts_info') is not NULL
alter table [MSmerge_conflict_EFILE_MERGE_NotesHistory] add origin_datasource_id uniqueidentifier NULL

2006-03-27 13:01:50.351 OLE DB Subscriber 'LUZERNV4-PDOSQL4': if object_id('MSmerge_conflicts_info') is not NULL
create nonclustered index [ncMSmerge_conflict_EFILE_MERGE_NotesHistory] on [MSmerge_conflict_EFILE_MERGE_NotesHistory] ([rowguid], origin_datasource_id)

2006-03-27 13:01:50.383 OLE DB Subscriber 'LUZERNV4-PDOSQL4': exec sp_MSsetconflicttable @article = N'NotesHistory', @conflict_table = N'MSmerge_conflict_EFILE_MERGE_NotesHistory'

2006-03-27 13:01:50.430 OLE DB Subscriber 'LUZERNV4-PDOSQL4': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:50.476 [17%] The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.Percent Complete: 17
2006-03-27 13:01:50.50é”?Ä€
2006-03-27 13:01:50.539 Applied script 'NotesHistory_21.cft'
2006-03-27 13:01:50.586 OLE DB Subscriber 'LUZERNV4-PDOSQL4': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:50.617 OLE DB Distributor 'LARGOS00-SDI': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:50.711 Percent Complete: 17
2006-03-27 13:01:50.742 {call sp_MSsetconflicttable (N'NotesHistory', N'MSmerge_conflict_EFILE_MERGE_NotesHistory', N'LARGOS00-SDI', N'EFILE', N'EFILE_MERGE')}
2006-03-27 13:01:50.773 OLE DB Distributor 'LARGOS00-SDI': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:50.867 Percent Complete: 0
2006-03-27 13:01:50.898 Category:COMMAND
Source: Failed Command
Number: 0
Message: {call sp_MSsetconflicttable (N'NotesHistory', N'MSmerge_conflict_EFILE_MERGE_NotesHistory', N'LARGOS00-SDI', N'EFILE', N'EFILE_MERGE')}
2006-03-27 13:01:50.961 Percent Complete: 0
2006-03-27 13:01:50.992 Category:SQLSERVER
Source: LUZERNV4-PDOSQL4
Number: 102
Message: Incorrect syntax near 'NoteID'.
2006-03-27 13:01:51.039 Percent Complete: 0
2006-03-27 13:01:51.070 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
2006-03-27 13:01:51.133 Disconnecting from OLE DB Subscriber 'LUZERNV4-PDOSQL4'
2006-03-27 13:01:51.180 Disconnecting from OLE DB Subscriber 'LUZERNV4-PDOSQL4'
2006-03-27 13:01:51.226 Disconnecting from OLE DB Subscriber 'LUZERNV4-PDOSQL4'
2006-03-27 13:01:51.258 Disconnecting from OLE DB Subscriber 'LUZERNV4-PDOSQL4'
2006-03-27 13:01:51.305 Disconnecting from OLE DB Publisher 'LARGOS00-SDI'
2006-03-27 13:01:51.336 Disconnecting from OLE DB Publisher 'LARGOS00-SDI'
2006-03-27 13:01:51.383 Disconnecting from OLE DB Publisher 'LARGOS00-SDI'
2006-03-27 13:01:51.414 Disconnecting from OLE DB Publisher 'LARGOS00-SDI'
2006-03-27 13:01:51.445 Disconnecting from OLE DB Distributor 'LARGOS00-SDI'
2006-03-27 13:01:51.492 Disconnecting from OLE DB Distributor 'LARGOS00-SDI'
2006-03-27 13:01:51.523 The merge process will restart after waiting 60 second(s)...

View 1 Replies View Related

Jobs Running On The Server

Mar 30, 2008

hi every 1,
i am having a real tough time to figure this one out .

i need to find out what jobs are schedule in the server that sends data out to ever .
we are doing the migration from 2000 to 2005 and need to know which jobs send data to the another server .
i looked at the sysjobs_view , it tells the origination server and all the jobs that are running on it, but that's pretty much it.
on the sql agent , i see all the jobs but dint know which jobs are sending data out side the server .
some jobs are regular backup
maintenance jobs
how will I figure out which once are gong out .
hope you people can help . any help will be so much appreciated.
bobby

View 3 Replies View Related

How To Schedule A Database Backup In SQL Server Agent Jobs?

Jan 7, 2008

I want to schedule a database backup using SQL Server Agent Jobs how can i do this?

View 1 Replies View Related

Some Jobs Failing In SQL

Dec 20, 2007

I was hoping if someone can help me shed some light on the following error messages -

Some of the billing jobs in SQL are failing, here is the message from application log - This is happening on the production server.

"SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan 'DB Maintenance Plan3'' (0x8BCD2C33DF5EC447BC7F1228E2C455E4) - Status: Failed - Invoked on: 2007-12-20 06:00:01 - Message: The job failed. The Job was invoked by Schedule 54 (Schedule 1). The last step to run was step 1 (Step 1)."

Has anyone seen this message before, whats a way to fix this issue.

Nishi

View 2 Replies View Related

SQL 2012 :: Ability To View Server Level Logins And Agent Jobs?

Sep 16, 2014

In one of my environments, I need to grant the ability to view all the logins and agent jobs to an account, but I don't want to give him "sysadmin" or "securityadmin".

View 2 Replies View Related

Executing SSIS Package Using Jobs In SQL Server Agent Infinite Loop

Jan 4, 2008

I'm trying to execute my package using schedule in SQL Server Agent, I've already tested my package by run it manually in Integration services and it works. The table created, the data from my flat file also inserted into the table correctly and the result return with success.

The question is why when I execute my package using SQL Server Agent, the SQL Server Agent keep executing my package like infinite loop until I stop the job. after I stop the job there is no error generated by sql server. Could you figured why this happen?? I've already tried to upgrade into SP2 and set the package protection level and still not get good result from it. thank you.

View 11 Replies View Related

Failing Backup Jobs

Dec 14, 2005

I have a DB Maintenance plan created that performs optimizations, integrity checks, and a database backup. The optimizations and integrity checks work fine, but the backup job fails. The backup job is to write the .bak file to a network share.
When I change the owner of the job to "sqluser", the job fails at step 0 withe the following error:
The job failed. Unable to determine if the owner (rsnsqluser) of job DB Backup Job for DB Maintenance Plan 'Online Database Server Maintenance Plan' has server access (reason: Could not obtain information about Windows NT group/user 'rsnsqluser'. [SQLSTATE 42000] (Error 8198)).
Checked with the system admin for this server and sqluser has priviledges to do everything, including write to the network share.

So, now I change the owner of the same maintenance job from sqluser to "sa". I now get this error:
Executed as user: RSNsqluser. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.

Checked the settings for MSSQLSERVER and SQLSERVERAGENT in Control Panel. Everything seems to be in order according to the other threads I have read.

For grins, I tried to ensure the sqluser password on the SQL Server Agent was correct. When I try to enter the new password I get this:
sql server agent startup account could not be verified
I click yes (it asks if I want to continue anyway).
Is the password not being registered properly in the agent?

One other thing, the sqluser user is listed under Security|Logins as connecting with Windows Authentication. We have several other servers that are set up the same and work fine. What am I missing? I'm pulling my hair out! :eek:

View 6 Replies View Related

All Maintenance Jobs On New Servers Failing

Sep 2, 2002

Hi all,

I've just set up 2 new SQL 7.0 servers, and my new maintenance jobs - backups, optimisations, consistency check jobs etc - are all mysteriously failing. I've created them both with the Maintenance Wizard, and again by hand. I've attempted manual and scheduled runs. All to no avail. Nor do they populate the sysmainthistory table, although they're configured to do so. The mystery is that we have successfully installed some user DTS processes, and THEIR jobs work. In order to resolve the problem, I've:

(1) ensured the Agent service is running;

(2) ensured adequate space on the drive etc;

(3) verified that sqlmaint.exe exists in Mssqlinn;

(4) unchecked the 'attempt to repair minor errors' box (I read this was a known cause of the problem);

I've got some clues to go on, but nothing conclusive;

'sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.'

Executed as user: NT AUTHORITYSYSTEM. sqlmaint.exe
failed. [SQLSTATE 42000] (Error 22029). The step
failed.

Additionally, both servers hold databases that I imported from another server-INCLUDING the msdb, and BOTH have the same problems and same error messages. This cannot be a coincidence.


Anyone have any ideas?


Thanks in advance,


JB.

View 1 Replies View Related

Failing Scheduled Jobs - Help - Urgent

Jul 27, 2001

When I change the SA password on my server the current Scheduled SQL Jobs no longer work. If I run DTS packages by themselves and not from the Scheduled job window they work fine. I am using the sa as the Owner of the jobs and my SQL Agents services use a Domain Account. If I rebuild the jobs after the sa password is change they work fine. However, I don't want to rebuild 100 jobs every time I change my SA password.How can I fix or get around this problem without rebuilding my jobs?

View 5 Replies View Related

DTS Sched Jobs Started Failing

May 2, 2002

I just had 2 DTS job fail, that had been running fine for weeks. Any ideas why these would fail when nothing about the jobs has changed ? Other jobs with the same owner ran OK.

Here's the message from DTS #1 Job History:

DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSDataPumpTask_1 DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error string: Error opening datafile: The referenced account is currently locked out and may not be logged on to. Error source: Microsoft Data Transformation Services Flat File Rowset Provider Help file: DTSFFile.hlp Help context: 0 Error Detail Records: Error: 1909 (775); Provider Error: 1909 (775) Error string: Error opening datafile: The referenced account is currently locked out and may not be logged on to. Error source: Microsoft Data Transformation Services Flat File Rowset Provider Help file: DTSFFile.hlp Help context: 0 DTSRun OnFinish: DTSStep_DTSDataPumpTask_1 DTSRun: Package execution complete. Process Exit Code 1. The step failed.

And here's the message from DTS #2 job history:

... DTSRun: Executing... DTSRun OnStart: Delete from Table [TI].[dbo].[Sheet1$] Step DTSRun OnFinish: Delete from Table [TI].[dbo].[Sheet1$] Step DTSRun OnStart: Copy Data from Sheet1$ to [TI].[dbo].[Sheet1$] Step DTSRun OnProgress: Copy Data from Sheet1$ to [TI].[dbo].[Sheet1$] Step; 117 Rows have been transformed or copied.; PercentComplete = 0; ProgressCount = 117 DTSRun OnFinish: Copy Data from Sheet1$ to [TI].[dbo].[Sheet1$] Step DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_2 DTSRun OnError: DTSStep_DTSExecuteSQLTask_2, Error = -2147467259 (80004005) Error string: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 18452 (... Process Exit Code 1. The step failed.

View 2 Replies View Related

Moving Sql Server Agent Server Jobs

May 6, 2008

I am actually the MOM administrator and only know enough SQL 2005 to keep mom working....sometimes I noticed on my dev mom box that SQL server agent has a lot of jobs configured to run against the mom onepoint database. The production box does not have these jobs. What would be the simplest way to export these jobs so that i can import them on the production box. Any help would be appreciated.

View 1 Replies View Related

SQL Server AGENT - Job Is Not Running??

Jan 10, 2006

It is SQL server 7. Scheduled jobs were running fine until the hard drive crasked. Replace the hard drive and restored the dabases. However, all the scheduled jobs cannot run. I created new jobs using database maintenance plan and it still doesn't work. the same error occurs when viewing the Job history.

sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.


However, if I create a job by right click on the database and select backup database. This job runs fine.

What should I do to make jobs created by the database maintenance plan running again?

Thank you for your help.

View 9 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved