Missing green arrow on the sql server icon in object Explorer

I am using SQL Server 2008 R2 on windows 2008 server. i am able to get connected to management studio but the status light with white circle.
the status lights in my Enterprise manager are no longer working. I am connected to the databases.
I can't use right-click the instance icon to select "start", "stop", "pause", "resume" or "restart" because they are all grayed out. But all the rest operations are available.
Where should I look more into then?
Thanks for your inputs in advance!iffi

Start > Programs > Microsoft SQL Server 2008 R2 > Management Studio > Right Click > "Run as Administrator"
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter

Similar Messages

How to SQL Server icons in start menu (Win Server 2012 R2)

Hi Folk's,
I have an installation of SQL Server 2012 Developer Edition on Windows Server 2012 R2. The installation was successful with the exception I have no SQL icons in the start menu - so I can't run the SQL Server Management Studio without going and looking
for the executable.
Does anyone know how I can re-generate the icons. I have tried doing a repair but this did not work.
Regards
Andy

I deleted the virtual machine and did a clean install and got the same issue. SQL Server 2012 SP1 Developer Edition does not install the icons in the start menu on Windows 2012 R2 (it works fine on Windows Server 2012).
In the Search menu if I type in SQL it just comes up with the SQL Server Installation center.
I have checked via the installer and via the discovery report mentioned above and all features are recorded as being installed.
However, I note that the Management Studio executable is missing (and likely so are some of the others).
Hi AndyW2007,
According to your description, we need to verify if you have install SQL Server 2012 Developer Edition successfully, you can check the setup log in the following folder.
-- C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\LOG\Summary.txt.
--C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\<YYYYMMDD_HHMM>\Detail.txt
If installing well, but the icons does not show in the start menu, I recommend you can create the lnk from the following installing location.
C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe
If you have any feedback on our support, please click here.
Thanks,
Sofiya Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Missing BI Data Tools in SQL Server 2014

Hi All!
I just doing the first steps in SSIS 2014 (RTM) after I played around a lot with SSIS 2014 (CTP2).
In case of CTP2 there was a separate download in MSDN called "SQL Server Data Tools for SQL Server 2014 CTP2" which contained VS2012 + the projects for SSIS, SSRS etc...
I'm missing these tools for SQL 2014 RTM. What do I do wrong? Could it be, that they are still unreleased?
Thanks in advance for your help.
Regards,
Patrick

Hi Patrick,
It's true that the SQL Server Data Tools (SSDT) is not shipped with SQL Server 2014 RTM DVD, and we need to download and install it from:
Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013
http://www.microsoft.com/en-us/download/details.aspx?id=42313
Regards,
Mike Yin
TechNet Community Support

What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?

What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?
Are these the same as software product keys, or just some pieces of paper the company needs to have on hand?
In which case, when we install SQL Server 2014, (and when looked for videos) - there is only 1 product key value to be put in, is there some other screen in the setup to input the License bought ( in our case will be Core licenses).
So in addition to the Core Licenses do will a Product key be needed? Would product key from an msdn work, as it is the licenses that we will buy to indicate that we bought to run the software on server X?
Thanks for any indications.

1. What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?
Are these the same as software product keys, or just some pieces of paper the company needs to have on hand?
2. In which case, when we install SQL Server 2014, (and when looked for videos) - there is only 1 product key value to be put in, is there some other screen in the setup to input the License bought ( in our case will be Core licenses).
3. So in addition to the Core Licenses do will a Product key be needed? Would product key from an msdn work, as it is the licenses that we will buy to indicate that we bought to run the software on server X?
Thanks for any indications.
I will answer your question point wise
1. Keeping license key is good idea it helps you during audit and you have proof that you are using a valid Microsoft License. Plus in scenario of disaster where whole box gets damanged you might need to install SQL Server again in that case during
reinstallation on setup page where you need to enter key you might need need it. If you are missing your paper then you are in trouble.
2. Only on product key page license key is required and it is not required anywhere else during installation. Unless you enter valid product key installation will not proceed further.
3 License makes you a valid owner of Microsoft product with restrictions on how much hardware resource you can use how much max connections you can make etc. Key lets you install it on Windows machine making sure that you are using valid Microsoft product.
This was just a general idea please speak to your licensing specialist for more details. This is technical forum and we generally ask user to speak to licensing expert for such queries.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

I am trying to have access tables of the Sql Server through the Oracle

I am trying to have access tables of the Sql Server through the Oracle and this being occurred the error:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message: [Generic Connectivity using ODBC][H006] The init parameter <HS_FDS_CONNECT_INFO> is not set.
Please set it in init <orasid>.ora file.
ORA-02063: preceding 2 lines from HSMSQL
I created the ODBC with name HSMSQL.
I made all the configurations in the archives
tnsnames.ora:
HSMSQL=
(DESCRIPTION=
(ADDRESS= (PROTOCOL = tcp)(HOST = wsus)(PORT = 1521))
(CONNECT_DATA =
(SID = HSMSQL)
(HS = OK)
listener.ora:
(SID_DESC = (SID_NAME=HSMSQL)
(ORACLE_HOME= C:\oracle\ora92)
(PROGRAM =hsodbc)
initHS_SID.ora:
HS_FDS_CONNECT_INFO = HSMSQL
HS_FDS_TRACE_LEVEL = OFF
-- Create database link
create database link HSMSQL.US.ORACLE.COM
connect to TESTE identified by TESTE2
using 'HSMSQL';
But when I execute query the error occurs:
Select * from TabTeste@HSMSQL
ORA-28500: connection from ORACLE to a non-Oracle system returned this message: [Generic Connectivity using ODBC][H006] The init parameter <HS_FDS_CONNECT_INFO> is not set.
Please set it in init <orasid>.ora file.
ORA-02063: preceding 2 lines from HSMSQL
Please they help me, thanks, Paulo.

Hi,
It seems that your configuration is Ok. By the way, the workaround for this error is:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Transparent gateway for ODBC][H001] The environment variable <HS_FDS_CONNECT_INFO> is not set.
* Set HS_FDS_CONNECT_INFO in the hs{sid}init.ora file to the data source name.
Example: HS_FDS_CONNECT_INFO = <ODBC DataSource Name>
* Make sure the hs{sid}init.ora file exists in the ORACLE_HOME/hs/admin directory and has the same name as the SID in the LISTENER.ORA.
Example: If SID=hsodbc in the listener.ora file, then the hs{sid}init.ora file would be named ORACLE_HOME/hs/admin/inithsodbc.ora
For more information see if this [url http://forums.oracle.com/forums/thread.jspa?forumID=61&threadID=576975]thread can help you.
Cheers

What are the SQL server versions those are compatible with XI 3.0.

Hi All,
Please suggest,
what are the SQL server versions those are compatible with XI 3.0.
or with which SQL server versions XI 3.0 will interact using JDBC Adapter.

Check in the [Product Availability Matrix |https://websmp201.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200314690900000192]in market place for more information on this
Thanks
SaNv...

The report I published on the SQL server report server is not showing in the application we use to retrieve reports.

The report I published on the SQL server report server is not showing in the application we use to retrieve reports. My cell phone number is {removed}
Thanks.

Hello Roger Tenn,
Thank you for posting in the TechNet Forum.
As this issue is related to SQL server report server, to receive better report, it is recommended to ask in the SQL server forum.
https://social.technet.microsoft.com/Forums/en-US/home?category=sqlserver
The professionals here will be glad to help you.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

Configure Synchronization Connections An error has occurred while accessing the SQL Server database

Hi,
i am getting following error message
Central Administration --> Synchronization Connections
An error has occurred while accessing the SQL Server database or the SharePoint Server Search service.
If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.
Central Administration --> Manage Profile Service: User Profile Service Application --> Manage User Properties
Error
An unexpected error has occurred.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 3bce5a11-f2dc-4788
Please tell how to fix it.
iffi

Event ID 5555 -> i have change the Timer jobs recycling time AM to PM
for User profile page not display number of count in the page first check services , connection ,
IISRESET /NOFORCE / timer services restart
Deepesh Yevle MCTS

DPM failing SQL backups due to error: "the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F85)

I ran across this error starting on 6/4/2011 and have been unable to find the root of the problem. In our environment, we have a DPM 2010 server dedicated to backing up all our SQL envrionment (about 45 SQL Servers total). All of the SQL
environment is backing up fine except for a SQL Cluster Application. This particular SQL Instances is part of a 6 node failover cluster with 6 SQL Instances distributed amongst them. The other 5 SQL instances in the cluster are backing
up fine; only one instance is failing. The DPM Alerts section shows this error when attempting to do a SQL backup of one of the databases on this SQL instance:
Affected area: KEN-PROD-VDB001\POSREPL1\master
Occurred since: 6/11/2011 11:00:56 PM
Description: Recovery point creation jobs for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com have been failing. The number of failed recovery point creation jobs =
4.
If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
The DPM job failed for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com because the SQL Server instance refused a connection to the protection agent. (ID 30172 Details:
Internal error code: 0x80990F85)
More information
Recommended action: This can happen if the SQL Server process is overloaded, or running short of memory. Please ensure that you are able to successfully run transactions against the SQL database in question and then retry the failed job.
Create a recovery point...
Resolution: To dismiss the alert, click below
Inactivate alert
I have checked the cluster node this particular SQL instance is running on using Perfmon and the machine is nowhere near capacity on CPU, memory, network, or Disk I/O.  I have failed this SQL Application to another node in the cluster and
receive the same error (this other node has another clustered SQL application on it that is actively running as well as backing up fine). The only thing that I am aware of that has changed is that we installed SP2 for SQL 2008 about 2 weeks prior
to when the failures started to occur. However, we updated all six clustered SQL Instances at the same time and only this one is having this issue so I don't believe that caused the problem. We are running SQL 2008 SP2 (version 10.0.4000.0)
on all clustered instances along with DPM 2010 (version 3.0.7696.0) on this particular DPM server that has the issue.
One last thing, I have also noticed errors in the event log pertaining to the same SQL backups that are failing (but the time stamps are not concurrent with each backup attempt):
Log Name:      Application
Source:        MSDPM
Date:          6/13/2011 1:09:12 AM
Event ID:      4223
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KEN-PROD-BS002.aarons.aaronrents.com
Description:
The description for Event ID 4223 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.
Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSDPM" />
    <EventID Qualifiers="0">4223</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-06-13T05:09:12.000000000Z" />
    <EventRecordID>68785</EventRecordID>
    <Channel>Application</Channel>
    <Computer>KEN-PROD-BS002.aarons.aaronrents.com</Computer>
    <Security />
</System>
<EventData>
    <Data>DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.
Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
</Data>
    <Binary>3C00440070006D005700720069007400650072004500760065006E0074003E003C005F005F00530079007300740065006D003E003C00490044003E00330030003C002F00490044003E003C005300650071003E0031003800330033003C002F005300650071003E003C00540069006D00650043007200650061007400650064003E0036002F00310033002F003200300031003100200035003A00300039003A0031003200200041004D003C002F00540069006D00650043007200650061007400650064003E003C0053006F0075007200630065003E0066003A005C00640070006D00760033005F00720074006D005C0070007200690076006100740065005C00700072006F0064007500630074005C0074006100700065006200610063006B00750070005C006400700073007700720069007400650072005C00760073007300660075006E006300740069006F006E0061006C006900740079002E006300700070003C002F0053006F0075007200630065003E003C004C0069006E0065003E003800310035003C002F004C0069006E0065003E003C004800610073004500720072006F0072003E0054007200750065003C002F004800610073004500720072006F0072003E003C002F005F005F00530079007300740065006D003E003C00440065007400610069006C006500640043006F00640065003E002D0032003100340037003200310032003300300030003C002F00440065007400610069006C006500640043006F00640065003E003C002F00440070006D005700720069007400650072004500760065006E0074003E00</Binary>
</EventData>
</Event>
Any help would be greatly appreciated!

Don't know if this helps or not, but I also noticed another peculiar issue that is derived from this problem. If I go to "Modify protection group", then expand the cluster, then expand all six nodes in the cluster, five of them show "All SQL Servers"
and allow me to expand the SQL Instance and show all databases; the one that is having a problem backing up, when I expand the node, doesn't even show that SQL exists on the node, when in fact, it does.
I would also like to add that the databases on this node that will not backup are running fine. They run hundreds of transactions daily so we know SQL itself is OK. Even though it is a busy SQL Server, there is plenty of available resources as
the SQL buffer and memory counters show the node is not under durress.

Welcome to the SQL Server Disaster Recovery and Availability Forum

(Edited 8/14/2009 to correct links - Paul)
Hello everyone and welcome to the SQL Server Disaster Recovery and Availability forum. The goal of this Forum is to offer a gathering place for SQL Server users to discuss:
Using backup and restore
Using DBCC, including interpreting output from CHECKDB and related commands
Diagnosing and recovering from hardware issues
Planning/executing a disaster recovery and/or high-availability strategy, including choosing technologies to use
The forum will have Microsoft experts in all these areas and so we should be able to answer any question. Hopefully everyone on the forum will contribute not only questions, but opinions and answers as well. I’m looking forward to seeing this becoming a vibrant forum.
This post has information to help you understand what questions to post here, and where to post questions about other technologies as well as some tips to help you find answers to your questions more quickly and how to ask a good question. See you in the group!
Paul Randal
Lead Program Manager, SQL Storage Engine and SQL Express
Be a good citizen of the Forum
When an answer resolves your problem, please mark the thread as Answered. This makes it easier for others to find the solution to this problem when they search for it later. If you find a post particularly helpful, click the link indicating that it was helpful
What to post in this forum
It seems obvious, but this forum is for discussion and questions around disaster recovery and availability using SQL Server. When you want to discuss something that is specific to those areas, this is the place to be. There are several other forums related to specific technologies you may be interested in, so if your question falls into one of these areas where there is a better batch of experts to answer your question, we’ll just move your post to that Forum so those experts can answer. Any alerts you set up will move with the post, so you’ll still get notification. Here are a few of the other forums that you might find interesting:
SQL Server Setup & Upgrade – This is where to ask all your setup and upgrade related questions. (http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/threads)
Database Mirroring – This is the best place to ask Database Mirroring how-to questions. (http://social.msdn.microsoft.com/Forums/en-US/sqldatabasemirroring/threads)
SQL Server Replication – If you’ve already decided to use Replication, check out this forum. (http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/threads)
SQL Server Database Engine – Great forum for general information about engine issues such as performance, FTS, etc. (http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/threads)
How to find your answer faster
There is a wealth of information already available to help you answer your questions. Finding an answer via a few quick searches is much quicker than posting a question and waiting for an answer. Here are some great places to start your research:
SQL Server 2005 Books Onlinne
Search it online at http://msdn2.microsoft.com
Download the full version of the BOL from here
Microsoft Support Knowledge Base:
Search it online at http://support.microsoft.com
Search the SQL Storage Engine PM Team Blog:
The blog is located at https://blogs.msdn.com/sqlserverstorageengine/default.aspx
Search other SQL Forums and Web Sites:
MSN Search: http://www.bing.com/
Or use your favorite search engine
How to ask a good question
Make sure to give all the pertinent information that people will need to answer your question. Questions like “I got an IO error, any ideas?” or “What’s the best technology for me to use?” will likely go unanswered, or at best just result in a request for more information. Here are some ideas of what to include:
For the “I got an IO error, any ideas?” scenario:
The exact error message. (The SQL Errorlog and Windows Event Logs can be a rich source of information. See the section on error logs below.)
What were you doing when you got the error message?
When did this start happening?
Any troubleshooting you’ve already done. (e.g. “I’ve already checked all the firmware and it’s up-to-date” or "I've run SQLIOStress and everything looks OK" or "I ran DBCC CHECKDB and the output is <blah>")
Any unusual occurrences before the error occurred (e.g. someone tripped the power switch, a disk in a RAID5 array died)
If relevant, the output from ‘DBCC CHECKDB (yourdbname) WITH ALL_ERRORMSGS, NO_INFOMSGS’
The SQL Server version and service pack level
For the “What’s the best technology for me to use?” scenario:
What exactly are you trying to do? Enable local hardware redundancy? Geo-clustering? Instance-level failover? Minimize downtime during recovery from IO errors with a single-system?
What are the SLAs (Service Level Agreements) you must meet? (e.g. an uptime percentage requirement, a minimum data-loss in the event of a disaster requirement, a maximum downtime in the event of a disaster requirement)
What hardware restrictions do you have? (e.g. “I’m limited to a single system” or “I have several worldwide mirror sites but the size of the pipe between them is limited to X Mbps”)
What kind of workload does you application have? (or is it a mixture of applications consolidated on a single server, each with different SLAs) How much transaction log volume is generated?
What kind of regular maintenance does your workload demand that you perform (e.g. “the update pattern of my main table is such that fragmentation increases in the clustered index, slowing down the most common queries so there’s a need to perform some fragmentation removal regularly”)
Finding the Logs
You will often find more information about an error by looking in the Error and Event logs. There are two sets of logs that are interesting:
SQL Error Log: default location: C:\Program Files\Microsoft SQL Server\MSSQL.#\MSSQL\LOG (Note: The # changes depending on the ID number for the installed Instance. This is 1 for the first installation of SQL Server, but if you have mulitple instances, you will need to determine the ID number you’re working with. See the BOL for more information about Instance ID numbers.)
Windows Event Log: Go to the Event Viewer in the Administrative Tools section of the Start Menu. The System event log will show details of IO subsystem problems. The Application event log will show details of SQL Server problems.

hi,I have a question on sql database high availability. I have tried using database mirroring, where I am using sql standard edition, in this database mirroring of synchronous mode is the only option available, and it is giving problem, like sql time out errors on my applicatons since i had put in the database mirroring, as asynchronous is only available on enterprise version, is there any suggestions on this. thanks ---vijay

SCVMM 2008 R2 - "The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS)."

I know this question has been asked before, but never for R2, that I can tell, and the posted fixes aren't working. I have just installed SCVMM 2008 R2 on a Windows Server 2008 R2 server, using a remote SQL 2008 SP1 database. When I attempt to connect to SCVMM, I get the following error:
"The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS).
Ensure that the SQL Server service is running under a domain account or a computer account that has permission to access AD DS. For more information, see "Some applications and APIs require access to authorization information on account objects" in the Microsoft Knowledge Base at http://go.microsoft.com/fwlink/?LinkId=121054.
ID: 2607"
What I've seen online is that this is usually becuase the domain account SCVMM is running as does not have the proper permissions on the SQL database. Here's what I've confirmed:
1) My SCVMM service account is a local admin on the SCVMM server
2) My SCVMM service account is a dbowner on the SCVMM database in SQL
3) My SQL service account is a dbowner on the SCVMM database in SQL
4) My SQL service account is a domain user (even made it a domain admin, just in case, and it still "doesn't have access to AD DS," which is obviously untrue)
5) Neither service account is locked out
Has anyone run in to this? It says in Technet that remote SQL 2008 is supported, as long as the SQL management studio is installed to the SCVMM server, and I installed and patched before I began the SCVMM installation. I just don't know what else to try - I have no errors in event logs, no issues during the installation itself...
Andrew Topp

That answer was very unhelpful fr33m4n. The individual mentions that they've received the error that points to the KB article. I currently receive the same error -- there seems to be no resolution. I've run the Microsoft VBS script to add TAUG to the WAAG
as suggested by 331951, and that made absolutely no difference.
1) My SCVMM service account is a local admin on the SCVMM server
2) My SCVMM service account is a dbowner on the SCVMM database in SQL
3) My SQL service account is a dbowner on the SCVMM database in SQL
4) My SQL service account is a domain user (even made it a domain admin, just in case, and it still
"doesn't have access to AD DS," which is obviously untrue)
The user is also a member of WAAG, the machines have delegated authority to each other. Is there any other solution?

Can't Start the SQL Server & SQL Server Agent Services

Hello i had to make Help Please.
2014-10-31 12:18:55.66 Server Feb 10 2012 19:39:15
Copyright (c) Microsoft Standard Edition (64-bit) 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server -d C:\Program Files\Microsoft -e C:\Program Files\Microsoft -l C:\Program Files\Microsoft 2014-10-31 12:18:55.69 Server -s "MSSQLSERVER"
2014-10-31 12:18:56.21 Server 2014-10-31 12:18:56.21 Server 2014-10-31 12:18:56.21 Server 2014-10-31 12:18:56.21 Server 2014-10-31 12:18:58.04 Server 2014-10-31 12:18:58.05 Server 2014-10-31 12:18:58.07 Server 2014-10-31 12:18:58.08 Server 2014-10-31 12:18:58.15 spid5s 2014-10-31 12:18:58.71 Server 2014-10-31 12:18:59.22 spid5s 2014-10-31 12:18:59.24 spid5s 2014-10-31 12:18:59.81 spid5s 2014-10-31 12:18:59.98 spid5s 2014-10-31 12:19:00.76 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 Server 2014-10-31 12:19:00.80 Server 2014-10-31 12:19:00.80 Server 2014-10-31 12:19:00.81 Server 2014-10-31 12:19:00.81 spid13s 2014-10-31 12:19:00.81 Server 2014-10-31 12:19:00.81 Server 2014-10-31 12:19:00.86 Server 2014-10-31 12:19:22.49 spid15s 2014-10-31 12:19:22.68 spid17s 2014-10-31 12:19:22.69 spid9s 2014-10-31 12:19:22.69 spid18s 2014-10-31 12:19:22.69 spid19s 2014-10-31 12:19:22.71 spid9s 2014-10-31 12:19:22.90 spid9s 2014-10-31 12:19:23.36 spid9s 2014-10-31 12:19:23.46 spid9s 2014-10-31 12:19:23.67 spid20s 2014-10-31 12:19:23.67 spid20s 2014-10-31 12:19:23.73 spid20s 2014-10-31 12:19:24.67 spid5s 2014-11-01 00:00:08.70 spid28s 2014-11-02 00:00:23.48 spid29s 2014-11-03 00:00:53.66 spid29s 2014-11-04 00:00:08.08 spid19s 2014-11-04 18:03:23.74 spid53 2014-11-04 18:03:23.79 spid53 2014-11-04 18:03:24.72 spid54 2014-11-04 18:03:24.78 spid54 2014-11-04 18:03:27.74 spid53 2014-11-04 18:28:12.10 spid52 2014-11-04 18:28:12.13 spid52 2014-11-05 00:00:26.82 spid18s a copy of my setup for a coworker in a different country to work with i can't make this two services to start. A timed out error shows and maybe the logs say something but i can't understand it.
Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Corporation
on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
(c) Microsoft Corporation.
All rights reserved.
Server process ID is 2540.
System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
Authentication mode is MIXED.
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
Registry startup parameters:
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
Command Line Startup Parameters:
SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
Detected 3071 MB of RAM. This is an informational message; no user action is required.
Using conventional memory in the memory manager.
This instance of SQL Server last reported using a process ID of 2532 at 31/10/2014 12:18:20 p.m. (local) 31/10/2014 06:18:20 p.m. (UTC). This is an informational message only; no user action is required.
Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
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.
Software Usage Metrics is disabled.
Starting up database 'master'.
CLR version v4.0.30319 loaded.
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
SQL Server Audit has started the audits. This is an informational message. No user action is required.
SQL Trace ID 1 was started by login "sa".
Server name is 'WIN-3FNEFF25D4V'. This is an informational message only. No user action is required.
A self-generated certificate was successfully loaded for encryption.
Server is listening on [ 'any' <ipv6> 1435].
Server is listening on [ 'any' <ipv4> 1435].
Server is listening on [ 'any' <ipv6> 1433].
Server is listening on [ 'any' <ipv4> 1433].
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
Server is listening on [ ::1 <ipv6> 1434].
Server is listening on [ 127.0.0.1 <ipv4> 1434].
Dedicated admin connection support was established for listening locally on port 1434.
SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
SQL Server is now ready for client connections. This is an informational message; no user action is required.
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WIN-3FNEFF25D4V ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WIN-3FNEFF25D4V:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
A new instance of the full-text filter daemon host process has been successfully started.
Starting up database 'msdb'.
Starting up database 'mssqlsystemresource'.
Starting up database 'CMOVILBD'.
Starting up database 'ArgusTec'.
The resource database build version is 11.00.2100. This is an informational message only. No user action is required.
Starting up database 'model'.
Clearing tempdb database.
Starting up database 'tempdb'.
The Service Broker endpoint is in disabled or stopped state.
The Database Mirroring endpoint is in disabled or stopped state.
Service Broker manager has started.
Recovery is complete. This is an informational message only. No user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
Using 'xpstar.dll' version '2011.110.2100' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
Starting up database 'Argus'.
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Using 'xplog70.dll' version '2011.110.2100' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.

Sorry i feel so stupid. Here it is. I can clearly see the errors now
2014-11-05 10:49:47.43 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
2014-11-05 10:49:47.43 Server (c) 2005 Microsoft Corporation.
2014-11-05 10:49:47.43 Server All rights reserved.
2014-11-05 10:49:47.43 Server Server process ID is 4596.
2014-11-05 10:49:47.43 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2014-11-05 10:49:47.43 Server Authentication mode is MIXED.
2014-11-05 10:49:47.43 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2014-11-05 10:49:47.43 Server This instance of SQL Server last reported using a process ID of 5720 at 05/11/2014 10:28:35 a.m. (local) 05/11/2014 04:28:35 p.m. (UTC). This is an informational message only; no user action is required.
2014-11-05 10:49:47.43 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2014-11-05 10:49:47.44 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-11-05 10:49:47.44 Server Detected 2 CPUs. This is an informational message; no user action is required.
2014-11-05 10:49:47.46 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.
2014-11-05 10:49:47.49 Server Node configuration: node 0: CPU mask: 0x0000000000000003 Active CPU mask: 0x0000000000000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014-11-05 10:49:47.50 spid7s Starting up database 'master'.
2014-11-05 10:49:47.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2014-11-05 10:49:47.60 spid7s SQL Trace ID 1 was started by login "sa".
2014-11-05 10:49:47.60 spid7s Starting up database 'mssqlsystemresource'.
2014-11-05 10:49:47.61 spid7s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2014-11-05 10:49:47.67 spid7s Server name is 'WIN-3FNEFF25D4V\SQLEXPRESS'. This is an informational message only. No user action is required.
2014-11-05 10:49:47.67 spid10s Starting up database 'model'.
2014-11-05 10:49:47.68 spid7s Informational: No full-text supported languages found.
2014-11-05 10:49:47.68 spid7s Starting up database 'msdb'.
2014-11-05 10:49:47.76 spid10s Clearing tempdb database.
2014-11-05 10:49:47.83 Server A self-generated certificate was successfully loaded for encryption.
2014-11-05 10:49:47.83 Server Error: 26023, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server Server TCP provider failed to listen on [ 'any' <ipv6> 1433]. Tcp port is already in use.
2014-11-05 10:49:47.83 Server Error: 17182, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa. Reason: Unable to initialize the TCP/IP listener.
2014-11-05 10:49:47.83 Server Error: 17182, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors.
2014-11-05 10:49:47.83 Server Error: 17826, Severity: 18, State: 3.
2014-11-05 10:49:47.83 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.
2014-11-05 10:49:47.83 Server Error: 17120, Severity: 16, State: 1.
2014-11-05 10:49:47.83 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.

Using the SQL Server Agent for the first time

I have set up several jobs to run automatically throughout the day. Each job just does one thing: executes an SSIS package.
The packages themselves run perfect when I test them in Visual Studio 2005, but when the SQL Server Agent tries to run the job I am getting failed jobs.
Is there any tutorials or walkthroughs that can teach my about using the SQL Server Agent? If I wanted extensive help troubleshooting my SQL Server Agent problems which part of the message boards would I post that too?
Thanks for the info!

Anyone?
I really need some resources for SQL Server Agent 2005.
Refer these links,
http://technet.microsoft.com/en-us/library/ms141701(v=sql.90).aspx
http://stackoverflow.com/questions/10489392/permissions-issue-running-ssis-package-from-sql-job
Regards, RSingh

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

I cannot start the "SQL Server Reporting Services (SCE)" service

Attempts to run any of the Windows Computer Reports fail with an error:
Date: 10/29/2008 10:19:30 AM
Application: System Center Essentials
Application Version: 6.0.1251.0
Severity: Error
Message: Cannot initialize report.
Microsoft.Reporting.WinForms.ReportServerException: The Report Server Windows service 'ReportServer$SCE' is not running. The service must be running to use Report Server. (rsReportServerServiceUnavailable)
   at Microsoft.Reporting.WinForms.ServerReport.GetExecutionInfo()
   at Microsoft.Reporting.WinForms.ServerReport.GetParameters()
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.ReportParameterBlock.Initialize(ServerReport serverReport)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.SetReportJob(Object sender, ConsoleJobEventArgs args)
My attempts to start the "SQL Server Reporting Services (SCE)" service fail with an error:
Could not start the SQL Server Reporting Service (SCE) service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.
The application log in the event viewer has hundreds of instances of Event ID 107:
Event Type: Error
Event Source: Report Server (SCE)
Event Category: Management
Event ID: 107
Date:  10/29/2008
Time:  10:36:25 AM
User:  N/A
Computer: DC
Description:
Report Server (SCE) cannot connect to the report server database. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Please help.

Thanks for the link to the Reporting Services forum. I found the fix in this thread:
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3644545&SiteID=1
I had to create a registry key and reboot:
1.
Click Start, click Run, type regedit, and then click OK.
2.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3.
In the right pane, locate the ServicesPipeTimeout entry.
Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
a.
On the Edit menu, point to New, and then click DWORD Value.
b.
Type ServicesPipeTimeout, and then press ENTER.
4.
Right-click ServicesPipeTimeout, and then click Modify.
5.
Click Decimal, type 60000, and then click OK.
This value represents the time in milliseconds before a service times out.
6.
Restart the computer.
After the reboot, the service was running. Thanks for your help with this.

Missing green arrow on the sql server icon in object Explorer

Similar Messages

Maybe you are looking for