I'm running SQL Server 6.5 and have schedules a number of tasks to run overnight. This has generally been successful; even when the tasks have failed, it's been because of a lack of data in a feeder database system.
My problem is that when I try to run the tasks manually, I get a message saying that they can't be run because SQL Executive is not running on the server. Now, this ain't true. The little gizmos show green in the server manager, and if I right click on SQL Executive, 'Start' is disabled and 'Stop' is enabled.
Am I missing something here? Does anyone have any clues or suggestions?
1) SQL Executive stops running jobs 2) The only way I can get it to START running jobs is to reboot the server 3) When SQL Server and executive come back up, a number of the tasks have been DISABLED! (I have seen this happen over and over on my SQL 6.5 SP4 instances.)
If you have seen this situation, have you found a way to prevent it? (ie: procedure or bug fix, etc.)
If I have 2 scheduled tasks set for the same time (perhaps accidentally), will the SQL Executive start 1 and queue the other one until the first is complete and then run the 2nd task? Or will they both be started simultaneously?
I have been running the following production job successfully for a long time. It now fails, and the Task History Last Error Message displays 'No Message'. The log file ( C:MSSQLLOGMaint_TombV50.txt) shows it ran successfully, with a Return Code 0.
To all, If I have a scheduled tasks that is owned by 'sa', how can I assign permissions to allow another user, even the database dbo, to register the SQL server and view the scheduled tasks?
Hi, I am using Windows 2000 and created around 15 scheduled tasks. My scheduled tasks supposed to run every morning. I have to set password to first scheduled tasks every morning; otherwise none of the scheduled tasks works. As soon as i put password in the scheduled tasks, other tasks work fine.
1) Is there a way to call a second task 'upon completion' of the first one. Or would I need to place the code of the second task in one task? (This is v6.5) I guess the main purpose is to avoid conflict & see if one fails, the other may succeed, etc. I generally like to keep diff tasks separate, but one is dependent upon the completion of the other.
2) I want to restore a db, upon completion of the backup of another db. They are on separate servers, but i know i can use remote sp's.
Any advice, help, code, scripts, etc, would be appreciated. Thank you.
Apologies if this has already been covered, but I can't find any information.
What is the easiest way to move a batch of scheduled tasks from one server/network to another? Can you script them up somehow and then reapply the script to the new location?
I'm going crazy with EM's Sheduled Tasks. I've setup couple of backups and weekly maintenance plans from EM. After couple of days I viewed sheduled tasks from EM toolbar and found that all the tasks have not executed as I have scheduled. the task history does not show any history at all. Clicking refresh does not do any good either. However if i right click on the database and choose restore i see all the backups that i have scheduled. Is this a bug?
We are running SQL 6.5 sp5a. There have been a number of instances recently where some scheduled tasks don't complete. I can't even cancel them. The only way to stop them is to stop and start the Executive service.
Anyone come across this before and know what the problem is?
Is anyone aware of a way of adding scheduled tasks to MSDE?
Obviously in SQL Server you'd use the Enterprise Manager to do that, but I don't believe it is possible to get Enterprise Manager seperately from SQL Server.
What are peoples opinions on using SSIS as a "central repository" and replacement for all scheduled tasks. Example, we have a bunch of servers which we have installed services which we have written. Currently we have scheduled tasks on each machine to stop and start the services. One of my collegues is using SSIS to run a system which runs tasks on multiple machines by remotely running programs on other machines via scheduled tasks and then collects the data and puts it into a database.
He's now pitching the idea that we remove the scheduled tasks on each machine and start and stop our services via SSIS so that it's centralized. In addition, we can also check for holidays in our database before starting services. Since it doesn't seem like SSIS was meant for this type of use, I'm weary of using the tool to do something it wasn't intended for.
Any opinions? I'm also worried that the learnnig curve for everyone is going to be too high.
I googled this an I got wonderful resul... no, no I didnt. Could someone please provide a link or a step by step guide on how to schedule the running of SP's that will then send the results to an email address.
I recently changed the SA password on my SQL Server 6.5 installation and discovered that this had caused the Scheduled CmdExec Tasks (defined in SQL Executive) to fail with:
"Process Exit Code 1. Microsoft (R) SQLMaint Utility, Version 6.50.240 Copyright (C) Microsoft Corporation, 1995 - 1996 [Microsoft SQL-DMO] Error 4002: [SQL Server] Login failed"
Changing the password back to the original resolves the problem, but is a less than satisfactory solution.
Any advice on how I can change the SA password and allow CmdExec tasks to continue running would be gratefully appreciated.
I have a strange problem with a scheduled task failing with the following:
"Unable to send completion notification email to operator with email name '' for task 2780, 'Scheduled Update'"
This job is the same across several servers and the job runs on the other servers. This is a bit frustrating... I cannot seem to find the difference that is causing the problem.
The funny thing is that I am not using SQLMail or anything to notify anyone regardless if the job succeeds or fails.
I have some "phantom" tasks running, specifically, DB dumps to a NULL Pipe device and they are not scheduled!!! These do not show up in the SYSTASKS table, where can I look to possibly find these un-scheduled dumps? Thank you....
I schedule dbcc checkdb command in the SQL schedule task program at 3:00am. It ran successfully but since it ran as a schedule task, I don't know where to find the results. Can anyone help?
Would please any expert here give me any guidance about what Data Mining tasks can be automated and scheduled via Integration Services Packages? Also, If we automated the tasks, can we also automatically save the results of the tasks somewhere? Like if we automate assessing the accuracy of a mining model, then we wanna know the mining model accuracy later, therefore, we need to save all these results from the automated actions. Is it possible to realize this?
Thanks a lot in advance for any guidance and help for this.
Hi all! Does anyone of you know what port number SQL Executive is using? Is it separate from the SQL Server's 1433? I have a user who is behind a firewall. He can connect to sql server but he can not run a task manually. If the task is scheduled it is successful but if he run manually , sql server display "The SQL Executive service is not currently running on <servername>. This prevents task .... from being run." Eventhough the service is running and other jobs are successfully.
Would it be possible the port for SQL Server is open to that user but not the sql executive.
i have both SQL Server 6.5 and 7.0 installed...for some reason i cannot start SQLExecutive while operating on 7.0...when i try to start the service it says 'Yu need SQL version 6.5 or later to start SQL Executive' has ayone come across such an error?
Having issue starting this service on SQL7 SP2. Returns "specific error 109" Any tips on resolution--no help on MS site search. what are ramifications of NOT starting this service if it is a single Server and the SQL application we use does not seem to be affected other than problem loading SP3 and is this related?
When trying to run SQL Executive from the SQL Enterprise manager it run in a dos window ( all scheduled tasks runs fine). PS: the machine in question had sql 6.5 installed , removed and then and then re-installed again. this is when the problem started.
I have registered a Sql server on my local machine.
I can adddelete jobs to the Task Scheduler, view job histories etc on that server however, when I try to execute a job on that server using the Task Scheduler, I get the following error message:
"The sqlexecutive servive is currently not running on server <server name>. This prevents the task from running".
I have checked the SqlExecutive service on the server and it is running. I have jobs that get executed each night via the Task Scheduler
Does anyone have any idea of what the problem could be ?
I have SQL Server 6.5 on Windows NT 4.0. Every night i was doing my backups with SqlExecutive. Some days ago I had to restart my server. First I stopped SQL Sevrver,then DTS service and when I tried to stop SQL Executive it begun to show me the stopping status. I waited for 20 min. and status didn't changed. In the Control panel, Services SQL Executive status is stopped. When I'm trying to start it from control panel the system tells me that this service is already running. And now I can't stop it or start it from service manager. What could be wrong ? Is it SQL Server problem or NT problem.
I registered a remote server on my machine that has SQL 6.5 Client installed. Using the SQL Enterprise manager I am trying to run the scheduled jobs in the remote site, and I get the following error message
"The SQLExecutive Service is not currently running on Server 'Server Name'. This prevents task 'task name' from being run"
I have verified that SQL executive is running in the remote server and I was able to run the same jobs on the same server from another machine. Can you please suggest me as what is wrong with my machine. I have tried to re-install SQL client on my machibe.
I would appreciate if anyone can reply this ASAP as I am stuck.
Hi all Can someone tell me what are these Logs mean. If you right click on SQL executive in EM and select Error Log you'll get a list of errors,warnings...etc.
In my Case I get these Errors that are occuring every few seconds. 11/05/98 09:03:10 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:12 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:18 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:28 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:35 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:40 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:46 AM DBLIB ERROR HANDLER: LOGIN INCORRECT
And Warnings:
11/05/98 09:03:10 AM DBLIB Message HANDLER: LOGIN FAILED - User: sa Reason: Not Associated with a trusted SQL Server Connection. 11/05/98 09:03:12 AM DBLIB Message HANDLER: LOGIN FAILED - User: sa Reason: Not Associated with a trusted SQL Server Connection. 11/05/98 09:03:16 AM DBLIB Message HANDLER: LOGIN FAILED - User: sa Reason: Not Associated with a trusted SQL Server Connection. 11/05/98 09:03:22 AM DBLIB Message HANDLER: LOGIN FAILED - User: sa Reason: Not Associated with a trusted SQL Server Connection. 11/05/98 09:03:28 AM DBLIB Message HANDLER: LOGIN FAILED - User: sa Reason: Not Associated with a trusted SQL Server Connection.
I have no clue which security i use on the server and on my workstation. How can one find out which security is being used.
I presently have Error Logging turned on for the SQL Executive, but I no longer want it. When I open up the "Configure SQL Executive" window under the Server menu, the "Error Log File" field is dimmed and there is no option to turn it off.
