January 9, 2007 at 1:02 pm
Close the command window to stop the sql...
Check the startup parameters in configuration manager...
Disable VIA protocol if it is enabled...
Start the sql from configuration manager and see what you get..
MohammedU
Microsoft SQL Server MVP
January 9, 2007 at 1:20 pm
VIA is disabled and TCP/IP ,shared memory and named pipes are enabled but still it does not start the service "say service cannot be started on local computer"
November 11, 2007 at 6:14 pm
Go to the local users and groups to check if the domain account is in the sqserver2005 group.we find the the domain account in the group sqlserver2005mssqluser is miss.
November 12, 2007 at 2:57 am
I had this problem when installed SQL 2005 SP2 - it defaults back to C:\Program Files\etc for the system db files, so if you've moved master,etc it will fail when starting up. Just make sure your startup parameters match where the actual files are.
February 12, 2008 at 6:48 am
This happened to me when i installed reporting services, and then re-ran SQL 2005 SP1 install. I had to add the domain account to the local admin group, but it never needed to be there before, why would this change?
May 15, 2008 at 3:02 am
This document worked a treat thanks for the poster.
August 19, 2009 at 9:09 pm
Thanks mate, I spent two days to figure it out, and the log on user was not in the sql group..
it worked for me.
thanks again
September 14, 2009 at 1:49 am
hi,
can you elaborate your resolution ... im facing the same error 'Error 32 occurred while opening file 'c:\program' to obtainconfiguration information at startup.
but no where in the command we are specifing C:\program ... we are specifing C:\program files....
September 14, 2009 at 1:50 am
hi,
im not able to open configuration manager too.. please any help!!!
March 29, 2010 at 10:01 am
Hi All,
I faced a similar issue with the error logs pointing to
Error: 26023, Severity: 16, State: 1.
2010-03-29 21:07:23.01 Server Server TCP provider failed to listen on [ 'any' <ipv4> 1301]. Tcp port is already in use.
2010-03-29 21:07:23.03 Server Error: 17182, Severity: 16, State: 1.
2010-03-29 21:07:23.03 Server TDSSNIClient initialization failed with error 0x271d, status code 0xa. Reason: Unable to initialize the TCP/IP listener. An attempt was made to access a socket in a way forbidden by its access permissions.
2010-03-29 21:07:23.04 Server Error: 17182, Severity: 16, State: 1.
2010-03-29 21:07:23.04 Server TDSSNIClient initialization failed with error 0x271d, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. An attempt was made to access a socket in a way forbidden by its access permissions.
2010-03-29 21:07:23.04 Server Error: 17826, Severity: 18, State: 3.
2010-03-29 21:07:23.04 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.
2010-03-29 21:07:23.04 Server Error: 17120, Severity: 16, State: 1.
2010-03-29 21:07:23.04 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.
checked in SQL Server Configuration manager and found that both shared memory nand TCP/IP is enabled. When I disabled TCP/IP, I was able to resolve the issue and could connect to the instance.
Can anyone provide me the reason for this?
Viewing 10 posts - 16 through 24 (of 24 total)
You must be logged in to reply to this topic. Login to reply