Hello everybody
I setup Sql agent for autostart with sql server and autorestart if stoped
but after rebooting NT or after stoping SQL server it never starts ,I have to start it manualy
Where to look for problem ?
I need to restart (becouse of the Database Mail :( ) SQL Server Agent on a live server which acts as a distributor for a lot of replications. I know that it shouldn't cause any problem, but I want to confirm that it want couse a subscriptions to be reinitiated.
Thanks in advance for quick reply
I've installed an SSL certificate via IIS. I stopped sql server and agent but cannot restart them. I'm getting the following message in the error log:
2007-10-31 21:24:53.63 Server Error: 17182, Severity: 16, State: 1.
2007-10-31 21:24:53.63 Server TDSSNIClient initialization failed with error 0x2, status code 0x38.
2007-10-31 21:24:53.63 Server Error: 17182, Severity: 16, State: 1.
2007-10-31 21:24:53.63 Server TDSSNIClient initialization failed with error 0x2, status code 0x1.
2007-10-31 21:24:53.63 spid9s Starting up database 'model'.
2007-10-31 21:24:53.63 Server Error: 17826, Severity: 18, State: 3.
2007-10-31 21:24:53.63 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2007-10-31 21:24:53.63 Server Error: 17120, Severity: 16, State: 1.
2007-10-31 21:24:53.63 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I've tried removing the SSL certificate but with no success.
Help! I'm starting to think that the only solution is to uninstall sql server 2005 and reinstall.
I have a problem where developers will stop the SQLServer service during the day and then they will not remember to restart the SQLAgent. It does not seem to restart when you stop the Server service and restart the services with out a reboot. Is there a setting somewhere in Enterprise Manager where I can tell the Agent service to restart with the Service service?
View 4 Replies View Relatedhello
i have a question regarding sql agent. Is it ok to restart the agent any time (i need to restart it for enabling the email alert option in sql agent properties..otherwise it doesnt work)? Does restarting sql agent affect replication jobs and other scheduled jobs? Are there any issues restarting agent on production?
Any help appreciated
Thanks
Whenever I restart the Sql Server Agent, it causes SQL Server to restart also - is this correct ? I thought the dependency was the other way around i.e. restarting SQL Server would cause the agent to restart ? Any insights gratefully accepted.
View 5 Replies View RelatedMorning,
I set up SQL Agent to start up on a domain account with Administrator rights, and the
auto-restart option is on. However, the agent does not restart automatically when restarting
SQL Server. No problems restarting manually. The Event Viewer logs the following:
"SQLServerAgent security context does not have server-autorestart privileges."
Any ideas on how to diagnose this?
Thanks,
Sergio
I'm trying to figure out a way to automatically restart the SQL Agent service when an AG fails over to a secondary node. I've created a job on each AG node that runs every 15 seconds and detects when a fail over has happened. It then issues a SQL Agent stop command and then a SQL Agent start command. The problem is that once the stop command happens the start command never fires because the SQL Agent is now stopped.
View 3 Replies View RelatedHi, I have setup a replication between two servers. And sometimes due to network connection problem, I get error message like :
The subscription to publication 'pub_1' is invalid.
After 10 retries, if connection cannot be made successfully, the Merge Agent will stop running.
How can I start the Merger Agent automatically after it has been stopped?
Create a table with an Identity column, insert data / restart the server / insert more data / restart the server/ insert some more data.
My data looks like this :
Identity column
1
2
3
1002
1003
1004
1005
2002
2004
It looks like the indentity value gain +~1000 after most server restart (sometimes identity stay the same). This can be very dangerous for some datatype! The only thing google told me was this : URL...but microsoft did not comment on it yet!
I want to schedule a sql job to run at specific time for restarting the sql services(MSSQLServer and SQLServerAgent) and also want to send notification to all the users 5 minutes before restarting them. Please let me know. Thanks in advance.
View 4 Replies View RelatedWe have an ASP application installed on one powerful Win 2003 andthe SQL Server on another Win 2003.We have two copies of the application (identical, one for productionand one for test purposes) that are operational. The 2nd applicationis connected to the same SQL Server but a test copy of the productiondatabase.Today, running the application, a place where it shows a list of records,the ASP application was timing out after 30 seconds for a lot of users.I backed up the production db and restored it over the test db and testedthe ASP application; within 10-15 seconds the ASP page loaded the listof the records, so i didn't get any timeout. So i started to think thatmaybethe test db when it was being restored, SQL Server would do some kind ofdata cleanup and defragment the new db.But, then i checked the Task Manager, SQL Server was almost using 1.2GBof memory and the server had only 100megs available.As soon as i restarted the SQL Server, the ASP page did no longer timeouton the production database.So now i am trying to figure out why the SQL Server restart fixed myproblem?Unfortunately i did not check if there were a lot of connections in theProcess infounder the Current Activity in SQL EM.Do you think there were a lot of sessions that weren't killed by theapplication?And that was causing the timeout? But why only for the Production db and notalsofor the test db?I mean, i am puzzled as to why before restarting the SQL Server, running theASPapplication connected to the TEST database did not time out!As always, I appreciate any feedback, comments.Thank you
View 1 Replies View Relatedwhen 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
how can I configure the SQL server to automatically restart selected services on a regular basis?
View 1 Replies View RelatedHas anyone ever experienced the SQL Server unexpectedly rebooting?
Yesterday my SQL Server 7 installation rebooted itself and the error log seemed fine as did the restart. The only evidence I can find was a message in the event viewer's application log stating the the MSSQLServer service terminated unexpectedly. Any ideas are appreciated.
Thanks,
- D
I've a SQL server that intermittently restarts itself mostly during. Its a SQL Server 6.5 SP4 running NT 4.0 SP6. It really has no rhyme or reason to it happening. The are no indications in either the SQL or the Nt events logs.
Has anyone heard of this?
Thanks inadvance
Hi,
I have a linked server set up to a proprietarty temporal DB through an OLEDB provider. From time to time and for various reasons the OLEDB provider crashes with "Error 7302 Could not create an instance of OLE DB Provider 'IhOLEDBProvider.iHistorian.1'. OLE DB Trace [Non Interface Error: CoCreate of DSO for IhOLEDBProvider.iHistorian.1 returned 0x80070008"
Up till now, to re-initilize the connection we have just restarted the SQL Server service. However, some automated processes are now feeding data into this server and more users and have started coming online so restarting for this issue has become a big deal.
Getting the OLEDB provider sorted out isn't an option at present so my question is:
Is there a way to re-initalise a failed linked server other that restarting the SQL Service?
Thanks,
Eamon.
Hi,
I have SQL server running on windows Adv Server 2000. Since last couple days whole computer restart every one hours. Only thing I remember doing was to shrink database db size is 200+GB.
How can I fix this problem.
Any help will be highly appreciated?
Thanks.
Samir
Hi,
I've got a table with a column that contains the status of available licenses to the user, i.e. they are either in use or are available. If the server goes down, then when it is restarted I need to make sure all the rows in this column describe each license as being available.
So the question is how can I ensure data in a table is, if you like, initialized, each time the server is restarted? Is there a system defined stored proc or trigger than is executed when a server is restarted?
Thanks.
Hi...
i hv a database (sql server 2000) where i got locking on many tables and my application was down.
I restarted the sql server and the application was fine but after five minutes the same locking issue started happening. I did a index rebuild the next time on all indexes and everything was fine.But i cannot relate how locking occured and why it was not after index rebuild.Can anyone shed some light on this or anyone had similar experience... cos i cannot figure out a way on this.
Thanks in advance
We just moved source server to newer, bigger box ... Windows 2003 and Active Directory ... Snapshot agent worked but distribution failed ... Same login as on older machine, login is sysadm, used DCOMCNFG to allow ability to launch process ... What are we missing?
View 4 Replies View Relatedhello,
View 1 Replies View RelatedI acciently change the locale id of my sql server using sp_configure. After i stop the server it now can not be re-started. Any help is appreciated.
View 1 Replies View RelatedI have an old application to maintain that uses CDatabase to connect to SQL Server. If SQL Server is stopped and restarted, such as in a cluster failover (i.e. move group), then the CDatabase connection needs to reconnect. It seems that it's not capable of doing this on it's own so I need to check the state some how. Various methods, such as IsOpen, seem to be useless as far as determining if I have a "good" connection.
Any thoughts?
@@servername sometimes returns NULL depending on how you have been messing around with replication and various other settings.
The simple solution offered to fix this is to delete the entries in the system tables and sp_addserver 'servername','local' and then restart the SQL service.
This is fine but what do you do in the situation where the SQL server is a 24/7 production box ? Does anyone know of a method / hack to fix this without stopping the service ?
Thanks
s
We were trying to restore our production server db backup in test server over LAN (due to space shortage on test server) . Test server hanged and did not respond for abt more than 15 hours (backup file 40 GB ) . The we restarted the server (resetting the power button) . Now it's showing the status 'Restoring' . According to me it's not doing anything (as seen in task manager workload ) . So how can I go ahead with checking the db .
Due to 'restoring' status I get following error
------------------------------------
Msg 927, Level 14, State 2, Line 1
Database 'envdb' cannot be opened. It is in the middle of a restore.
----------------------------------
Hi All.
Our inhouse app used to run on a SQL2000, but we've recently moved it to 2005.
The move was done by way of backup and restore (it was on a whole new server).
After the move, an odd problem showed up: once in a while, the server seems incapable of finding/using its indexes: everything starts working slowly, until I run a maintenance plan that rebuilds its indexes etc.
In the database/server all relevant options seem to be ok (auto update statictiscs etc.), and my conclusion that it doesn't use its indexes comes from the fact that:
* it gives the results from certain select statements in a totally different order (although the set of rows is the same),
* performance is (all of a sudden) very slow (seconds turning to minutes!!)
This happens:
* at least after a reboot of the server
* sometimes just in the middle of the day
The only way I've found to solve the matter, is by running the maintenance plan to rebuild the indexes, but sometimes this only seems to work the second time.
Does anybody share this experience, or know what to do about it?
Thanks,
Nick.
I am unable to login to the sql server as I would like to reboot the server, please let me know how I can do the following remotely in such a scenario:
1. Reboot the sql server
2. Restart the mssqlserver and sqlserveragent services
Thanks.
Hi
We have been having a problem with on of our servers, applications connecting to it are experiencing poor performance, even though the server is only running at a peak of 50%.
The odd thing is that after a sql service restart we couldnt connect at all on the SQL port. We were only able to re-connect after rebooting the actuall box. Is there anything that can be done about this? Its strting to look like a network related problem instead of SQL
We changed the database maintainence plan, after changes do we have to restart the server in order to effect the new changes.
View 2 Replies View RelatedI have got the error “a network related or instance specific error occurred sql server 2012 “.I have enabled tcp/ip, restarted the services. The sql server service is getting stopped even after the manual restart. I have checked in event viewer and I noticed a error. Here is the error...The log scan number (43:456:1) passed to log scan in database ‘model’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication.
View 1 Replies View RelatedIs there a way to find the max number of sessions that were on a sql server since its last restart? I know how to get how many total connections there were since last restart, and the current number of sessions, but not the max number of sessions that were running since last restart. Also, opinion on the optinum number of allowable sessions, or a good way to figure out the balance?
View 0 Replies View RelatedI have a service that depends on SQL Server service. Basically we make sure that our service only starts after SQL server service started. Unfortunately this dependency does not ensure that database is available.
Basically I observed in Application log that SQL server reports that it started to listen on a port. And then I see that recovery process started. As I understand SQL server is not available while database is in the recovery state.
Note: I might have not used a correct terminology to describe SQL server recovery process as I don't have access to Application log with the exact message at the moment. I can verify the message if necessary.
Because SQL server service is started our service starts and attempts to connect to the database. Service fails to connect to database, because of the restoration process. Once restoration is done service connects successfully.
I observed that restoration process starts every time machine is rebooted. It only takes a few minutes to run, but it is enough to generate a number of error messages in event log about failed SQL connections.
My first question is: Is it normal for database to enter into recovery state every time machine is rebooted?
My second question is: If it is a normal operation, is there any way to detect that SQL server is truly available, so our code does not have to try retry establishing connection many times