Unable To Start SqlServerAgent Service In A Sql 2005 Cluster
Jul 4, 2007
hi all
i'm using a domain accout to setup a sql 2005 cluster in a win2003 cluster.when the installation ended,the SqlServerAgent service can't be started.the event in event viewer
is "SQLServerAgent could not be started (reason: Unable to connect to server "(local)"; LServerAgent
cannot start). " (event id 103 ,source sqlserveragent).I try to use local system and network service account to start it,but it's all the same.
And i found i can connect to the sql cluster vitrual ip 10.73.2.224,but can't connect to the node A.So i enable all the network protocols for the instance MSSQLSERVER,and also enable every ip in the TCP/IP protocol,then restart the sqlserver service,but it still doesn't work.
I restarted the MSSQLSERVER service and SQLSERVERAGENT will not restart. I get the following error.
Could not start the SQLSERVERAGENT service on Local Computer. The service did not return an error. This could be an internal Windows erroror an internal service error. If the problem persists, contact you system administrator.
I am intsalling SQL 2005 in an activepassive cluster. The OS is Windows 2003 with SP1. Everything installs OK but the sql server service cannot start afterwards. There are many access errors in the Security Event log - see example below - and numerous "SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. " errors in both the SQL and Application event logs. I have tried installing SQL in both mixed mode and under Windows Authentication and get the same errors. I can install SQL 2005 outside of the cluster on both nodes. Other items of note: This was a SQL 2000 cluster. I uninstalled SQL 2K, the virtual name was changed (IP remained the same) and the DNS entry was updated to reflect the new name. Early in the installation process - 3 or 4 days ago - I got a few errors about the Server Principal Name had to be updated but when I do a setspn -l the both nodes are listed and the entries look fine, though there are no entries for the sql service (MSSQLSvc). Not sure if there should be entries for the virtual name, but there aren't any for either the old or new name. Does the new virtual name need to be added to AD? Here is the security error - Event ID is 560 and it looks like there's a problem with Remote Access and is generated when trying to access either node: Category: Object Access Type: Failure Audit Event_ID: 560 User: NT AuthorityNetwork Service Object Open: Object Server: SC Manager Object Type: SERVICE OBJECT Object Name: RemoteAccess Handle ID: - Operation ID: {0,134558507} Process ID: 1516 Image File Name: C:WINDOWSsystem32services.exe Primary User Name: CM-OHCO-DS006B$ Primary Domain: SWNA Primary Logon ID: (0x0,0x3E7) Client User Name: NETWORK SERVICE Client Domain: NT AUTHORITY Client Logon ID: (0x0,0x3E4) Accesses: Query status of service
One other informational message that may be of use - looks like there's a problem with dll's for remote access, though this isn't pertaining to SQL: The description for Event ID ( 0 ) in Source ( srmservice ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: srmservice error: 0, Started the agent (srmagent.exe)..
I am trying to start ms sql server 2005 express as a network user from originally starting as local system. I cannot start the service.
I have given this network user administrator access to sql express from the sql server surface area configuration "Add New Administrator". I have went into the local users/groups and added this network user to the 3 security groups
The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x8009030d. Check certificates to make sure they are valid.
I receive five errors in the event logs/application
EventID: 26014
Unable to load user specified certificate. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online.
EventID: 17182
TDSSNIClient initialization failed with error 0x80092004, status code 0x80
EventID: 17182 TDSSNIClient initialization failed with error 0x80092004, status code 0x1
EventID: 17826
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately prceding this one in the error log.
EventID: 17120
SQL Server could not spawn the FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I don't recall assigning any sql specific certificates. The reason I'm trying to run this as a network user is because an application on a remote windows server requires it.
After starting the service back running as local system as it was before, I went into the SQL Server Management Studio Express and edited the properties for this new network user I wish to run the service as. I gave him full access including checking all grants in securables.
I now see a bit of a difference in the event logs with these errors.
EventID: 17058
initerrlog: Could not open the log file 'c:Program FilesMicrosoft SQL ServerMSSQL1MSSQLLOGERRORLOG.' Operating system error =5(Access is denied).
I saw a notification when changing the sql server service's logon that the new network user has been granted the log on locally right.
The second and last new error is
EventID: 17053
UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.
I have installed sqlserver 2005 using the standard msdn universal installation discs on my laptop running vista business.
The mssqlserver service will not start automatically as the setup configures it and I cannot start the service manually because I get the 'Access Denied' error message
I am logged on the the computer with adminstration privileges
I have installed MS analysis service(OLAP) on my lap top
my user is in the Administrative group , other than that I tried creating a user with 'OLAP ADMINISTRATOR' privilate and tried to start the ms analysis service
I am getting the error , unable to start the service on server(), you are not a member of OLAP Administrators group
I tried to install the service pack 3 from Microsoft
Could you pleae guide me to start this serivice Thanks,
When i started the service, i am getting the following message Starting up database 'master'. Error: 9003, Severity: 20, State: 1. Cannot recover the master database. Exiting.
i tried starting using -f -m paramters,but could not succeed i don't have any backups for master database is there any way i can restore it from .mdf, .ldf files..
I am having Windows 2012R2 Std with SQL2012SP2. Trying to add SQL cluster node2 but unable to locate the instance name when I click on drop down button.Understand that SQL Server Agent is required but it is not listed as cluster resource. Therefore, I perform the followingFrom Windows Power Shell with Administrator rights
1. Import-Module FailoverClusters 2. Add-ClusterResourceType "SQL Server Agent" c:windowssystem32SQAGTRES.DLL
Error: Add-ClusterResourceType : Unable to locate the cluster service executable on node1.The network name cannot be found.No problem to ping all cluster related names as well as fail-over to and from next available node.
I have Vista x64 and I had been fighting SQL Server for a few days and yesterday I decided for reinstallation. Unfortunately now I am not able to instal the server back!
Each time I got the following error (it refers to SQL Server service):
Code Snippet <Func Name='LaunchFunction'> Function=Do_sqlShutDownRANUInstance <Func Name='GetCAContext'> <EndFunc Name='GetCAContext' Return='T' GetLastError='203'> Doing Action: Do_sqlShutDownRANUInstance PerfTime Start: Do_sqlShutDownRANUInstance : Tue Sep 04 23:32:16 2007 <Func Name='Do_sqlShutDownRANUInstance'> Service SQLEXPRESS with parameters '' is being started at Tue Sep 04 23:32:16 2007 Unable to start service (3) Error Code: 0x80070003 (3) Windows Error Text: System nie może odnaleźć określonej ścieżki. Source File Name: sqlsetuplibservice.cpp Compiler Timestamp: Wed Jun 14 16:29:04 2006 Function Name: sqls::Service::Start Source Line Number: 316
Setting status of unmanaged components and removing unmanaged resources
Error Code: 3 MSI (s) (F4:E4) [23:32:24:490]: I/O on thread 3716 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 788 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 2948 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 4392 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 5048 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:495]: I/O on thread 4464 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:495]: I/O on thread 4992 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:495]: I/O on thread 4768 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:497]: I/O on thread 3004 could not be cancelled. Error: 1168 MSI (s) (F4!4C) [23:32:24:497]: Product: Microsoft SQL Server 2005 -- Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (3) System nie może odnaleźć określonej ścieżki. . Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (3) System nie może odnaleźć określonej ścieżki. . <Failure Type='Fatal' Error='3'> <EndFunc Name='LaunchFunction' Return='3' GetLastError='203'> MSI (s) (F4:80) [23:32:24:507]: User policy value 'DisableRollback' is 0 MSI (s) (F4:80) [23:32:24:507]: Machine policy value 'DisableRollback' is 0 Action ended 23:32:24: InstallFinalize. Return value 3. MSI (s) (F4:80) [23:32:24:512]: Executing op: Header(Signature=1397708873,Version=400,Timestamp=925154312,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1) MSI (s) (F4:80) [23:32:24:512]: Executing op: DialogInfo(Type=0,Argument=1033) MSI (s) (F4:80) [23:32:24:513]: Executing op: DialogInfo(Type=1,Argument=Microsoft SQL Server 2005) MSI (s) (F4:80) [23:32:24:514]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1]) MSI (s) (F4:80) [23:32:24:516]: Executing op: ActionStart(Name=Do_sqlShutDownRANUInstance.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Running action to shutdown instance(Run As Normal User),) MSI (s) (F4:80) [23:32:24:517]: Executing op: ProductInfo(ProductKey={C3F5DBA5-ABFC-443E-AA60-928223AADF53},ProductName=Microsoft SQL Server 2005,PackageName=sqlrun_sql.msi,Language=1033,Version=151129058,Assignment=1,ObsoleteArg=0,ProductIcon=ARPIcon.ico,PackageMediaPath=Setup,PackageCode={08AD0897-0300-4F7D-A3CC-A0CCEDD42E0D},,,InstanceType=1,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3) MSI (s) (F4:80) [23:32:24:518]: Executing op: ActionStart(Name=ProcessComponents,Description=Updating component registration,) MSI (s) (F4:80) [23:32:24:519]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWAREMicrosoftWindowsCurrentVersionSharedDLLs,,BinaryType=0,) MSI (s) (F4:80) [23:32:24:520]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWAREMicrosoftWindowsCurrentVersionSharedDLLs,,BinaryType=0,) MSI (s) (F4:80) [23:32:24:520]: Executing op: ComponentUnregister(ComponentId={68C6D258-77E0-11D5-8528-00C04F68155C},ProductKey={C3F5DBA5-ABFC-443E-AA60-928223AADF53},BinaryType=0,) MSI (s) (F4:80) [23:32:24:520]: Executing op: ComponentUnregister(ComponentId={68C6D257-77E0-11D5-8528-00C04F68155C},ProductKey={C3F5DBA5-ABFC-443E-AA60-928223AADF53},BinaryType=0,)
We're running sql 7.0 sp1 and both the sqlserver service and sqlserveragent service are running under local system account. For some reason, the sqlserveragent service started failed with "error 2140" - windows nt internal error From event viewer, it saids it has some connection problem.
The sqlserver service has no problem. All knowledge base material related to 6.5 resolution. Would rebuilding the registry entry help ? I tested and rebuilding the registry did not regrant any registry permission, should it ?
I have a maintenance plan on SQL2000, that is backing up the database.
It is under Management/SQL Server Agent. When I try to start the job, I got an error, saying: Error 22022 SQLServerAgent is not currently running so it cannot be notified of this action.
But, when I try to start the SQL Server Agent (in Services), it stops directly with the following information: The SQLAgent$Sharepoint service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
When I try to start it from the SQL Server Service Manager: no reaction at all!
I have successfully installed SQL 2005 on W2K3 Cluster. The problem is that SQL Server Agent won't start. Below are the lines from SQLAGENT.OUT:
2007-03-15 09:40:02 - ! [298] SQLServer Error: 2, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001] 2007-03-15 09:40:02 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2007-03-15 09:40:02 - ! [298] SQLServer Error: 2, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001] 2007-03-15 09:40:02 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start 2007-03-15 09:40:07 - ! [298] SQLServer Error: 2, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001] 2007-03-15 09:40:07 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2007-03-15 09:40:07 - ! [298] SQLServer Error: 2, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001] 2007-03-15 09:40:07 - ! [382] Logon to server '(local)' failed (DisableAgentXPs) 2007-03-15 09:40:08 - ? [098] SQLServerAgent terminated (normally)
I have tried starting Agent with Domain Admin account. No luck. SQL Server is started.
We just set up VPN on our system and changed the passwords. For some reason I cannot start the SQL Server Agent now. I get this msg: "An error 1069 - (The service did not start due to a logon failure) occurred while performing this service operation on the SQLServerAgent service.
Any ideas why is that happening and what should I do about that?
I need to start the SQLServerAgent because I have a need to install a backup procedure that will run regularly. but I need to also make the Agent service be set up to autostart with the PC. If I go into ControlPanel...Services I can do this manually, but how to do it programmatically? Is there a command line command like net start that can do the trick, or can I direct SQL Server to do it through a TSQL procedure?
I am trying to install MS Sql Server 2000 on my machine. The OS on my machine is Windows XP SP2. During the installation i keep getting an error message, "Setup failed to configure the server. Refer to the server error logs and C:WINDOWSsqlstp.log for more information." I have copied an extract from the sqlstp.log file below:
10:05:28 Process Exit Code: (-1) 10:05:31 Setup failed to configure the server. Refer to the server error logs and C:WINDOWSsqlstp.log for more information. 10:05:31 Action CleanUpInstall: 10:05:31 C:WINDOWSTEMPSqlSetupBinscm.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT 10:05:31 Process Exit Code: (1060) The specified service does not exist as an installed service.
Since Copy Databas Wizard failed to copy anything from remote SS20005 (both are with SP2 3054) in any combination, I changed SQLServerAgent(myinstance_name) to run under Network from Local System with the help of SQL Server Configuration Manager
For this change it was restarted, failed to start again and continues to be stopped giving "SQLServerAgent could not be started (reason: Unable to connect to server '<mymachine_name><myinstance_name>'; SQLServerAgent cannot start)."
I changed SQL Server Agent (myinstance_name) back to Local Service, then to Local System and still can't start it.
So, my questions: 1) What has happened and how can I start SQLServerAgent?
2) Why cannot I start it under Network Service? since it apparently should access remote resources for CDW to copy from remote SS2005
This is on MS Windows XP SP2
PS After few trials I amnaged to restart it again under Local System but still cannot change to any different one
Ran the SP2 locally on a Windows Server 2003 SP1 box that had SQL Server 2005 SP1 install on it. Problem was I ran out of C: drive and it failed in the middle of upgrading the server.
I'm unable to start the SQL Server at all now. Is there any way to back this out? Don't think I can reapply any patches since the service is dead.
Eventlog now shows: One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
The log shows it's unable to start SQL (blames it on permisions but it's because SQL can no longer start)
Product : Database Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29538 Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmssqlsystemresource1.mdf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
I'm guessing its reinstall time but not sure how the attached databases will like that idea.
- Operating System Minimum Level Requirement (Success) Messages * Operating System Minimum Level Requirement
* Check Passed
- Operating System Service Pack Level Requirement. (Success) Messages * Operating System Service Pack Level Requirement.
* Check Passed
- SQL Server Edition Operating System Compatibility (Warning) Messages * SQL Server Edition Operating System Compatibility
* Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.
* The current system does not meet the minimum hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.
* Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
- Internet Explorer Requirement (Success) Messages * Internet Explorer Requirement
* Check Passed
- COM Plus Catalog Requirement (Success) Messages * COM Plus Catalog Requirement
* Check Passed
- ASP.Net Version Registration Requirement (Success) Messages * ASP.Net Version Registration Requirement
* Check Passed
- Minimum MDAC Version Requirement (Success) Messages * Minimum MDAC Version Requirement
* Check Passed
furthermore i get error 26 when trying to create new sql server database. and while doing the SQL server surface area configuration i got this message.:
SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC) ------------------------------ Program Location: at Microsoft.SqlSac.MainPanel.FormFeatures..ctor(String machineName, Form callingForm)
HOpefully somebody out there will help me...or is this problem only appearing in sql server 2005 and would it be a better decision to install SQL server 2000...or if someone can help me rectify this problem i'll be really thankful.
This may be more of an IT question, but I hope someone here will have the answer.
I am trying to change the "Log on as" for SQLSERVERAGENT NT Service through Windows Registry. I am able to find HKLMSYSTEMCurrentControlSetServicesSQLSERVERAGENTObjectName and change it but I dont know how to specify a password to go with it. If I simply change it to .Administrator (from Local System) it errors out.
Ideally I would like to script this so I can change the logon without having to go though the Services Control Panel or SQL Management Studio.
Hi can someone help me please? I browsed through the SP2 install feedback below, but it doesn't quite seem to fit what happened to my install. My .MDF and .LDF files for the system databases are in C:Program FilesMicrosoft SQL ServerMSQL.1MSQLData (I presume this is the correct location.)
I am the local administrator on this box.
I uploaded the .CAB file with all the logs onto www.sendspace.com if it gives you something to go on.
The only other thing of note is that it said there were two machines on the network and that I needed to change my machine name in the control panel when I installed. This doesn't seem right, as far as I understand the computer name is unique.
The SQL Server runs under the local system account, if that is of any use.
I attempted uninstalling and reinstalling the SQL native client MSI package in the hope it would be a simple fix similar to that chap further down the page, but that didn't help at all either.
.CAB file of installation logfiles is here: http://www.sendspace.com/file/7ihoet
kind regards Jason
ERRORLOG starting SQL Server post failed SP2 install
2007-06-12 19:55:21.94 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-06-12 19:55:21.96 Server (c) 2005 Microsoft Corporation. 2007-06-12 19:55:21.96 Server All rights reserved. 2007-06-12 19:55:21.97 Server Server process ID is 5468. 2007-06-12 19:55:21.97 Server Authentication mode is MIXED. 2007-06-12 19:55:21.97 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2007-06-12 19:55:21.97 Server This instance of SQL Server last reported using a process ID of 5756 at 12/06/2007 19:36:35 (local) 12/06/2007 18:36:35 (UTC). This is an informational message only; no user action is required. 2007-06-12 19:55:21.97 Server Registry startup parameters: 2007-06-12 19:55:21.99 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2007-06-12 19:55:21.99 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2007-06-12 19:55:21.99 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2007-06-12 19:55:22.00 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2007-06-12 19:55:22.00 Server Detected 4 CPUs. This is an informational message; no user action is required. 2007-06-12 19:55:22.17 Server Address Windowing Extensions is enabled. This is an informational message only; no user action is required. 2007-06-12 19:55:22.33 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 2007-06-12 19:55:22.57 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-06-12 19:55:23.60 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-06-12 19:55:23.63 Server Database mirroring has been enabled on this instance of SQL Server. 2007-06-12 19:55:23.72 spid5s Starting up database 'master'. 2007-06-12 19:55:24.07 spid5s SQL Trace ID 1 was started by login "sa". 2007-06-12 19:55:24.11 spid5s Starting up database 'mssqlsystemresource'. 2007-06-12 19:55:24.13 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required. 2007-06-12 19:55:24.29 spid5s Server name is 'GBLOND088SQ8MSQL_CREDS_DEV1'. This is an informational message only. No user action is required. 2007-06-12 19:55:24.29 spid9s Starting up database 'model'. 2007-06-12 19:55:24.30 Server Error: 17182, Severity: 16, State: 1. 2007-06-12 19:55:24.30 Server TDSSNIClient initialization failed with error 0x34, status code 0x1e. 2007-06-12 19:55:24.30 Server Error: 17182, Severity: 16, State: 1. 2007-06-12 19:55:24.30 Server TDSSNIClient initialization failed with error 0x34, status code 0x1. 2007-06-12 19:55:24.30 Server Error: 17826, Severity: 18, State: 3. 2007-06-12 19:55:24.30 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-06-12 19:55:24.30 Server Error: 17120, Severity: 16, State: 1. 2007-06-12 19:55:24.30 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 downloading SQL Express 2005 but it will not install properly, stating that it is already installed. I cannot get the SQLExpress Service to start. I keep getting the message (The request failed or the service did not respond in a timely fashion). Can anyone help or point me in the right direction?
We have a N+1 SQL 2005 x65 SP2 + 3159 cluster which was running fine until the service account which runs Windows cluster and the SQL services was removed as a login from SQL. This was a new setup so the only SQL accounts are (SA) as SA, Windows Domain GROUP's which one group is configured as SA and the cluster account is added to this group. I cannot start SQL service on the cluster now. I've tried logging into one node as the service account which is member of a AD group which has SA rights to SQL as well as my personal account. If anyone knows a way ot fix this without reinstalling I'd appreciate your help.
A few service stop/start/restart questions on SQL Server 2005 SP2, whichI'll call SQLS.It looks as if there are *potentially* 6 ways to start/stop SQLSServices like the engine itself, integration services, reportingservice, Agent..-SQLS Configuration Manager-SQLS Surface Area Configuration (for Services and Connections)-Mgmt Studio Local (on server)-Mgmt Studio Remote (on client)-Windows Control Panel->Admin Tools->Services-Command Prompt (ala net start MSSQLSERVER)By policy, I am /not/ Administrator on the server. But I am SysAdminrole in SQLS. I have had various levels of success starting/stoppingservices in the ways listed above. In some I get Access denied, and inothers I get no msg and it simply doesn't work.Is there some special non-Admin OS group I need to be in to start/stopservices? Is this handled differently in the different interfaceslisted above?It seems like my best success for starting/stopping the engine and Agentis in /local/ Mgmt Studio, but /not/ remote Mgmt Studio - the optionsare greyed out on a remote client. Is this by design? Is it a SQLSbug?I'm sure I'm not the only SQLS DBA who does not have Admin rights on hisserver who wants to start/stop services. Generally speaking, how isthis intended to work?Any help appreciated.Allen JantzenA freshly minted DQLS DBA
System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed. at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout) at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
i get the above error when attepting to install reporting services
I am not able to start the sql server 2005 database engine services...
Sql server 2005 server is installed in one machine(SERVER) and we have 10 client machine connecting to the server
When i try to start the service from the Service.msc in the SERVER i am getting the following error
===================================
Cannot connect to KEYSKILL.
===================================
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
2006-03-26 20:33:09.42 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-03-26 20:33:09.42 Server (c) 2005 Microsoft Corporation.
2006-03-26 20:33:09.42 Server All rights reserved.
2006-03-26 20:33:09.42 Server Server process ID is 2068.
2006-03-26 20:33:09.42 Server Logging SQL Server messages in file 'd:SQL Server 2005MSSQL.1MSSQLLOGERRORLOG'.
2006-03-26 20:33:09.42 Server This instance of SQL Server last reported using a process ID of 1624 at 3/26/2006 8:32:45 PM (local) 3/26/2006 12:32:45 PM (UTC). This is an informational message only; no user action is required.
2006-03-26 20:33:09.42 Server Registry startup parameters:
2006-03-26 20:33:09.42 Server -d d:SQL Server 2005MSSQL.1MSSQLDATAmaster.mdf
2006-03-26 20:33:09.43 Server -e d:SQL Server 2005MSSQL.1MSSQLLOGERRORLOG
2006-03-26 20:33:09.43 Server -l d:SQL Server 2005MSSQL.1MSSQLDATAmastlog.ldf
2006-03-26 20:33:09.43 Server Command Line Startup Parameters:
2006-03-26 20:33:09.43 Server -m SqlSetup
2006-03-26 20:33:09.43 Server SqlSetup
2006-03-26 20:33:09.43 Server -Q
2006-03-26 20:33:09.43 Server -q SQL_Latin1_General_CP1_CI_AS
2006-03-26 20:33:09.43 Server -T 4022
2006-03-26 20:33:09.43 Server -T 3659
2006-03-26 20:33:09.43 Server -T 3610
2006-03-26 20:33:09.43 Server -T 4010
2006-03-26 20:33:09.43 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-03-26 20:33:09.43 Server Detected 1 CPUs. This is an informational message; no user action is required.
2006-03-26 20:33:09.51 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2006-03-26 20:33:09.53 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-03-26 20:33:09.53 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2006-03-26 20:33:09.53 spid5s Starting up database 'master'.
2006-03-26 20:33:09.60 spid5s SQL Trace ID 1 was started by login "sa".
2006-03-26 20:33:09.64 spid5s Starting up database 'mssqlsystemresource'.
2006-03-26 20:33:09.78 spid7s Starting up database 'model'.
2006-03-26 20:33:09.84 spid5s Server name is 'XYZ-FNB5RZRU9ZP'. This is an informational message only. No user action is required.
2006-03-26 20:33:09.84 spid5s Starting up database 'msdb'.
2006-03-26 20:33:09.98 Server A self-generated certificate was successfully loaded for encryption.
2006-03-26 20:33:09.99 Server Server local connection provider is ready to accept connection on [ \.pipeSQLLocalMSSQLSERVER ].
2006-03-26 20:33:09.99 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2006-03-26 20:33:09.99 Server Error: 17826, Severity: 18, State: 3.
2006-03-26 20:33:09.99 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.
2006-03-26 20:33:09.99 Server Error: 17120, Severity: 16, State: 1.
2006-03-26 20:33:09.99 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.
