September 28, 2010 at 10:48 am
hi gurus, i need your help, i am trying to manually start my sql services for one of my instances in sql configuration manager, the other one works ok, and i keep getting this error:
"the request failed or the service did not respond in a timely manner, check the event log"
i checked the eventlog and i get this error:
Message
The description for Event ID '-1073734824' in Source 'Service Control Manager' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'SQL Server (PotentialBuyers)', '%%1053'
does anyone how to fix this? the sql service and agent account is local the same as my other instance in the same server which is working, just in case i tried my account, but same error.
September 28, 2010 at 11:02 am
Look at the windows application log from the server (meaning not from your PC)
September 28, 2010 at 11:10 am
hi, under application log i have no errors for this instance, however if i go to system logs i get this:
The SQL Server (ProfileCenter) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
i have for source service control manager
September 28, 2010 at 11:28 am
Is this a new instance?
September 28, 2010 at 12:12 pm
no is not, it was working before.
September 28, 2010 at 12:16 pm
Check the SQL error log.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 28, 2010 at 12:46 pm
i can't start the instance, i can't see the sql error log for the instance I can't start
September 28, 2010 at 12:49 pm
The error log is in the install directory. Something like C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log
September 28, 2010 at 1:03 pm
DBA-640728 (9/28/2010)
i can't start the instance, i can't see the sql error log for the instance I can't start
It's just a text file. Open it in notepad. Latest one will just be called ERRORLOG (no file extension). Use the explorer search if you don't know which folder it's in.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 28, 2010 at 1:25 pm
If you don't find anything in the ErrorLog, try starting the instance from the command line using sqlservr.exe
This should give you some indication as to why the instance is not starting
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 28, 2010 at 2:00 pm
thanks, i just have lot of failed logins, last one being:
2010-09-22 08:25:00.46 Logon Error: 18456, Severity: 14, State: 8.
2010-09-22 08:25:00.46 Logon Login failed for user 'ProfileUser'. Reason: Password did not match that for the login provided. [CLIENT: 10.78.6.112]
let me try restarting it from the command prompt....
September 28, 2010 at 2:06 pm
Those events are from 6 days ago. I hardly think they're relevant here.
Is that the latest error log file and is it for the correct instance? The server and instance name will be in the startup messages at the beginning. If the SQL server service has attempted to start, there will be an error log that will contain info on why the startup failed.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 28, 2010 at 2:50 pm
yes it is the correct instance and the latest error log i have which is weird because as you say it doesn't have anything for today.
when i try to start the instance from cmd i get this error: d:\programfiles\Microsoft SQL Server\MSSQL10.ProfileCenter\MSSQL\Binn\BatchParser.dll is either not designed to run on windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.
help!
September 28, 2010 at 10:49 pm
You may try the following.
Copy the existing BatchParser.dll to a safe location
Locate an instance running the same build of SQL Server as the one having issues
Copy BatchParser.dll from that instance to this instance to the location mentioned in the error log
Try starting the instance
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 29, 2010 at 8:23 am
I tried that copying the dll from the other instance that is working in the server and still the same error 🙁
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply