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.)
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?
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.
Hi, I want to see my sql executive error log but it grown like anything. How i have to trucate my error log. I cannot stop my server now. i am getting following message. and also suggest me what i have to do not to grow like this means 56.01 mb size. The sql executive error log is 56.01 mb in size and loading it will consume considerble memory and may take several minutes to complete. Now i want to see my executive error log , pls tell me what i have to do.
I just inherited a SQL Server that was set up by a non-DBA. It`s running NT 4.0 and SQL Server 6.50 - 6.50.201 (the vendor hasn`t certified the product on SP4). I am trying to change the SQL Executive Service to use a non-system logon account. The account that I want to use is running SQL Executive on 9 other servers.
I went into Usrmgr and added the account to the administrators group. Made sure that it has rights to: log on as a service, log on as a batch job, increase quotas, act as part of the operating system, replace a process level token.
When I try to change to that id in services, I get the following error:
"cannot set the startup parameters for SQL Executive service. Error 1057 occurred. The account name is invalid or does not exist."
Looking in Technet, I found that if "log on as a service" isn`t set you could get this message but I`ve check/re-checked, had someone else check and it`s set.
We are running sql 6.5 with Serv. pack 4. All of our Prod. database are backedup weekly via scheduled tasks. On occasion the dump of a particular database will cause 1 of 2 things: 1. The db dump seems to work correctly but stops sql executive service. 2. The db dump seems to work correctly but sends an alert email msg to me indicating that it failed. The msg in the email is "NO Message".
Has anyone experienced either of these 2 problems or have any solutions?
I must introduce myself... Kris Allain. I am a VERY new DBA. Basically I as sort of pushed into the position even though I have no previous DBA experience. I come more from a Net Admin background although I've only graduated with a degree in MIS 2.5 years ago.
With that said, I ran into a problem last week in which took down a mission critical application for 4 hours. We have an app that his highly transactional and I'm using the Full Recovery method for this DB with weekly full backups, daily differential backups, and hourly log backups. Someone (could have been me) disabled the log backup job and a couple of days later the log grew until there was no more disk space (35+ gb). Well, it took me 4 hours to back up and shrink the log and get the system up and running again.
I told my boss what had happened and now he wants to know who did it. I told him it could've possibly been me, but I highly doubt it because it appears to have been disabled between 7-8pm on my "work from home" day, which I specifically remeber packing it up and playing xbox at 4:30pm.
Could someone help me figure out what happened and if there it is possible to track these changes in the future?
Has anyone ever seen TCP/IP become a disabled protocol without manual intervention from a user?
My websites just stopped talking to my MSSQL db and when I went into sql client config utility on the web boxes, tcp/ip was disabled. Any clues? Can't find anything to support this in the event or web logs.
While in the design window of a table, I click the properties button and click the Relationships tab. Here everything is grayed out, and I can't drag and drop to create relationships in my Diagram either. Its like things are locked up right now. Can any of you give me some direction? thanks
My production database has a maintenance plan that rebuilds all indexes and it's scheduled to run every day at 5 AM.
I disabled some nonclustered indexes that were not used by any execution plan I found, and run a Profiler session to catch any negative impact in performance.
But I found that the indexes were re-enabled the next day by the Rebuild Index task from the maintenance plan.
Is there a way to keep those index disabled? I don't want to drop them as I could have to re-enable some of them by users' request.
hi, all my toolbars except for the standard toolbar in SSRS are disabled. I cannot use anything. For example, I selected the formatting toolbar and it appears on the bottom of the standard toolbar, but I cannot select anything because it's all greyed out. Any suggestions. Thanks.
Environment: Visual Studio V8.0.50727.42 (RTM.050727-4200) Installed Products: Visual Studio Team Explorer V8.0.50727.127
The Variables are not available to the IDE. I cannot 1) Open the Variables Window (View > Other Windows > Variables), 2) Add or Edit Variables (SSIS > Variables).
I am preparing to re-install Visual Studio. Has anyone else seen this behavior? Is it a "feature" of some sort?
I having problem of using SQL Server management studio to create a database. Database have alot of colume, if i want to make column 1 to disabled, may i know how to set it?
The report functionality is working fine with the provided parameters,but the problem is one of the parameter Asofday is getting disabled until then servername and drive are provided and a click on the other remaining three parameters.
i have default for this asofday for today, and i feel that because of default parameter only it is getting disabled. i removed the default and is working fine wihtout getting disabled.
As this Asofday is of thirdplace in parameters list, i moved it to firstplace,it works fine here also.
What is happening when i supplied default and moved to third place?
If any one of you experienced any issue like this.pls share .
Hi, I'm using SQL Server 7.0. I'd like to know if there is anywhere in the information schema or system tables where I can tell that a constraint has been flagged as 'enable constraint for INSERT AND UPDATE' or not.
I have several alerts set up and a job setup to notify via email if alerts occur. There are times when I might be doing maintenace on a box that may generate alerts but I don't want to get emailed or paged for these "dummy" alerts. I thought first of setting the enabled column of sysalerts to 0 - that doesn't work. I still get notified. Then I thought I'd set the enabled column in sysjobs for my notification job to 0 while I'm doing the work. But as soon as I re-enable the job I get an alert. It seems that as soon as the job is re-enabled it checks the NT application log and sees that an alert was fired and somehow knows that there was no notification sent so sends one. If I purge the NT application log before re-enabling the job is solves the problem. But that is a very in-ellegant solution and I don't want to loose all the info stored in the event log any way. Does anyone know how SQL SErver aggent keeps track of this stuff? (ie. that an alert was fired but it's response job is disabled and to check once a job is re-enabled to see if any alerts occured while it was disabled?) I did a Profiler trace while re-enabling the job but didn't see anything pertinant in there.
Just curious to hear if anyone else has experiences this or knows a reason why it maybe should be this way...
I have some jobs that are disabled accourding to the Job Activity Monitor view in Mgmt Studio. However, if I open the schedules details, this view says Enabled. Can a schedule be enabled for a job, even if the job in itself is disabled maybe? But, I can't see any enable/disable flag in the sysjobschedules table, only in sysjobs.
Hi, I have been scheduling jobs from past couple months on production but it does not execute on the scheduled time.
I checked the schedule enabled tab, it was enabled when i scheduled the job, but was disabled at a later date when i checked to see why the job did not run.......
Can some one please guide me if there is any process in SQL which disables the jobs automatically.
I want to find out how the jobs when scheduled and enabled gets disabled on its own.
Is there something that would cause a SQL Login to get disabled automatically? The login was used successfully yesterday but today we were getting an error:
Login failed for user '<sql login>'. Reason: The account is disabled. [CLIENT: ipaddress]
Perhaps someone accidentally disabled this but that sounds unlikely.
I didn't see anything in the log about the account getting disabled.
my SB configuration involves 3 servers. Server A sends a message to Server B. there's a stored proc on Server B that is being activated (using Activation), does some processing and sends the message to server C. on C there's another SP that is activated and it's supposed to insert a record into a table.
My problem is that on Server C, the record doesn't get inserted when activation is set to ON.
when activation is off on C and I run the proc manually, everything works fine, but when activation is on, the record doesn't get inserted. after this happened I tried to fire the proc manually and I got the following error :
Msg 9617, Level 16, State 1, Procedure spMSG_ReceiveMessagesOnSubscriber, Line 52
The service queue "TargetQueue" is currently disabled.
I am using the following code for activation on server C :