Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Not able to restart the MSSQL Server Services Expand / Collapse
Author
Message
Posted Friday, June 4, 2010 1:43 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, June 16, 2014 9:46 PM
Points: 284, Visits: 263

Refer the MS artilce on
"
The SQL Server service cannot start when you change a startup parameter for a clustered instance of SQL Server 2000 or of SQL Server 2005 to a value that is not valid "


Sivaprasad S - [ SIVA ]http://sivasql.blogspot.com/
Post #932630
Posted Sunday, January 29, 2012 10:24 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, September 14, 2012 12:22 AM
Points: 1, Visits: 17
Thanks :)
Post #1243404
Posted Thursday, June 7, 2012 6:12 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, July 25, 2012 6:25 AM
Points: 1, Visits: 5
I had exactly this problem (with Errors on EventIDs 17120, 17182, 17826 & 17190), and could never find a solution, other than tediously re-installing SQL Server. I'd tried disabling VIA, using different Port numbers and just about all the other suggestions I found online, none of which helped at all.

It happened again today and I just couldn't face the re-install for some reason, but as I had to have it fixed I did one last trawl through google and finally found a solution. It was roughly as described in the following blog post:
http://www.sqlserverblogforum.com/tag/could-not-spawn-fruncm-thread/

Although at the final stage he has entered LOCAL SERVICE as the log on, that wouldn't work for me, but selecting Local System account and ticking "Allow service to interact with desktop" did. Whatever the reason, it seems accessing the Services through Control Panel gives slightly different behaviour than accessing it through the SQL Server Configuration Manager. No idea why, but it worked for me so thought I'd share in case it helped anyone else avoid a re-install
Post #1312418
Posted Wednesday, September 19, 2012 4:37 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, October 31, 2013 4:24 AM
Points: 1, Visits: 27
If you have tried to disable Name Pipe, Via or TCP/IP then by just enabling it i solved my problem
Post #1361250
Posted Wednesday, March 12, 2014 12:11 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, March 12, 2014 12:09 PM
Points: 1, Visits: 0
niall1981 (6/7/2012)
I had exactly this problem (with Errors on EventIDs 17120, 17182, 17826 & 17190), and could never find a solution, other than tediously re-installing SQL Server. I'd tried disabling VIA, using different Port numbers and just about all the other suggestions I found online, none of which helped at all.

It happened again today and I just couldn't face the re-install for some reason, but as I had to have it fixed I did one last trawl through google and finally found a solution. It was roughly as described in the following blog post:
http://www.sqlserverblogforum.com/tag/could-not-spawn-fruncm-thread/

Although at the final stage he has entered LOCAL SERVICE as the log on, that wouldn't work for me, but selecting Local System account and ticking "Allow service to interact with desktop" did. Whatever the reason, it seems accessing the Services through Control Panel gives slightly different behaviour than accessing it through the SQL Server Configuration Manager. No idea why, but it worked for me so thought I'd share in case it helped anyone else avoid a re-install


I just wanted to add that this solution just worked for me. I'm not sure why it happened in the first place. I rebooted the server after the most recent round of MS Patches and encountered this error.

Thanks!
Post #1550373
Posted Tuesday, May 27, 2014 3:28 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 6:37 AM
Points: 1, Visits: 14
is the above IP address standard or does it have any meaning?
Post #1574718
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse