SQL Server 2014 with instance uninstallation

Hello Team
As i by-mistake perform the installation of SQL Server 2014 Standard edition on one of our server . I removed that instance completely but still i am able to connect that instance and able to access DB's from there instance (Server rebooted after successfully
un-installation of SQL Server).
Can some suggest why it is accessible after complete instance remove from server ?
Thanks Ranveer Katiyar

From Add/remove programs > select 2014 and hit on the uninstall > there is pop up open for add/repair and remove > select remove and there is option for instance > choose instance and select all component for instance which one we selected and
then remove after that i get the below message for successfully installation.
Thanks Ranveer Katiyar
Uninstall is perfect so what is issue now I guess you have multiple instances and you have not uninstalled both ? Is that so.
Can you run below discovery report and post output here
http://blogs.msdn.com/b/petersad/archive/2009/11/13/sql-server-2008-discovery-report.aspx
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 Article
MVP

Similar Messages

What is the recommended static port range for SQL Server 2008 to SQL Server 2014 named instance?

I want to assign a static port to SQL Server 2008 to SQL Server 2014 named instance. Should the port be greater than 49151? The following links give contradicting information:
https://msdn.microsoft.com/en-us/library/ms177440(v=sql.105).aspx
Avoid numbers greater than 49151 which Windows might select for other purposes.
https://technet.microsoft.com/en-us/library/ms345327(v=sql.100).aspx
Port numbers should be assigned from numbers 49152 through 65535
Thanks..

I would still pick a port number below the ephemeral list (dynamic port usage [41952-65535]) as it'll reduce the chances of having a port collision when SQL Server starts up.
Also, I'd stick to lower numbers if possible (<25,000) as some firewalls skew higher port numbers to be more malicious (if heuristics are used).
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

SQL Server 2014 with AGs - Over 6 million DONE tasks in dm_os_tasks

Hello,
We've noticed that our SQL Server deployment has a very high number of tasks in the done state. On our 5 node cluster we have values in the millions on most servers (depending on last restart time), with our highest server returning over 6 million
for the following query:
select count(*)
from sys.dm_os_tasks
where task_state = 'done'
We also track the count daily, and we have never seen the number of tasks decrease. The average growth per day is 50,000. The servers are all running SQL Server 2014 Enterprise Edition CU2 (build 12.0.2370). The servers host between 4 and 8
availability groups each, with 1 to 3 databases per AG.
We're a little concerned that this behaviour is very reminiscent of that noted in the Memory Leak in 2012 KB 2877100), and wondered if anyone else is having a similar experience with 2014 AGs?
We did open a product support case for a separate issue where we mentioned this, but were told that until we could provide a memory dump of a crashing instance we wouldn't be able to investigate if this was actually a leak.
Any advice or discussion that suggests this behaviour is actually 'worked as intended' would be appreciated.
Kind Regards,
Tim

Hi Tim,
This does indeed look quite reminiscent of 2877100 and this behavior does certainly seem abnormal, particularly if you can establish memory consumption growth over time. I'd recommend providing MSFT additional statistics regarding memory usage via DMVs and
perfmon if you haven't already.
Product support is still definitely the recommended route - and you might try escalating or asking for another engineer. I understand why they are asking for this information, but perhaps ask if they can provide less invasive methods for root cause
analysis. If the answer is still "no" - hopefully you have a prod-like environment where you can reproduce this? And if so, then the memory dump is less of a risk in non-prod.
Best Regards, Joe Sack, MVP, SQL MCM | SackHQ.com

Why can't I log into my "Local" sql server (sql server 2014) with my Sql Server Authentication UID ?

I just got a new work station (win7 Pro) which has the following sql server
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
returns
12.0.2254.0 RTM Developer Edition (64-bit)
Select @@version
returns
Microsoft SQL Server 2014 - 12.0.2254.0 (X64)
Jul 25 2014 18:52:51
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
I added/created a new (random) user account to this server [joe123] and made him sa and mapped him to everything, the password never expires, ...
when I try to login to this local server the login fails, but I can log into this server with my windows integrated account (also sa). What do I need to do so that the joe123 account can login to the server
Rich P

Check if both "SQL Server and Windows Authentication mode" is set (not just Windows Authentication mode). Server-->right click and select properties --> Security
Satish Kartan http://www.sqlfood.com/

JDBC Connection String for MS Sql Server 2000 with Instance Name

Hi All,
I am having problems connecting to a MS Sql Server 2000 database using MSSqlServer4
driver when the database server has an Instance Name. If the database server has
no instance name then I am able to connect using the connection string
connection=jdbc:weblogic:mssqlserver4:hansa:1433
But when I have the MS Sql Server DB with an instance name such as "TestInstance",
then I am unable to connect with any of the connection strings given below
connection=jdbc:weblogic:mssqlserver4:hansa\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa\\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:1433:TestInstance
Can anybody help me in resolving this issue. Appreciate your help.
Thanks in advance.
Vikram

Vikram wrote:
Hi All,
I am having problems connecting to a MS Sql Server 2000 database using MSSqlServer4
driver when the database server has an Instance Name. If the database server has
no instance name then I am able to connect using the connection string
connection=jdbc:weblogic:mssqlserver4:hansa:1433
But when I have the MS Sql Server DB with an instance name such as "TestInstance",
then I am unable to connect with any of the connection strings given below
connection=jdbc:weblogic:mssqlserver4:hansa\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa\\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:1433:TestInstance
Can anybody help me in resolving this issue. Appreciate your help.Hi. No type-4 jdbc driver is going to be able to use a name for a DBMS instance.
Let's assume you have two DBMS instances running on the machine hansa. One
of them may be listening for tcp connections on port 1433, but the other must not.
The other most be listening on some other port number you have chosen.
Therefore, to choose which DBMS instance you want to connect to, use the
working URL you have, and switch the port number as desired.
Joe Weinstein
>
>
Thanks in advance.
Vikram

Backup Database From SQL Server 2014 with expired trial period.

Hi,
Looking for some advice. I created a database on a SQL Server 2014 Trial Version i downloaded from the Microsoft website. Our company bought a license for SQL Server 2012 instead of 2014, how can i migrate my database to 2012 without the ability to connect
to my 2014 Server or Management studio (Because the trial period has expired)?
Thank You.

Hi,
Alternatively, you can stop SQL Services and then locate the mdf & ldf file copy these files to new location.
Now you try to attach above files in new server.
Sorry little correction
I dint pay attention to 2014 to 2012, in this case you need to attach these files on SQL Server 2014 then generate script and execute these script on 2012.
Please refer following article on how to attach database.
Attach a Database
Also refer following post with similar issue.
MS SQL 2008 Evaluation expired...need to get database backup
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
Praveen Dsa | MCITP - Database Administrator 2008 |
My Blog | My Page

Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

Hello everyone.
We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
MCP

Hi. Yes...
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="SQLISServer" />
<EventID Qualifiers="0">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" />
<EventRecordID>469950</EventRecordID>
<Channel>Application</Channel>
<Computer>abtru1a11.oneabbott.com</Computer>
<Security />
</System>
- <EventData>
<Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data>
</EventData>
</Event>
MCP

SQL Server 2014 SSRS Login Prompt won't go away

Hi,
I'm attempting to set up SQL Server Reporting Services on one of my environments. The architecture is:
Database Server: SQL Server 2014 hosting my databases as well as the ReportServer / ReportServerTempDB databases
SSRS Server: SQL Server 2014 with just SSRS installed, hosting the web front end
I created a new SSRS database using the SSRS configuration manager.
When I log into the website on the local machine (http : // localhost/reports),
I'm prompted for my credentials once and once I authenticate (domain\username), everything works as expected. However, when I attempt to access the server remotely (either http or https : // reportserver.domain.com/reports)
I'm prompted for my credentials at least 12 times. If I keep re-entering them, the SQL Server Reporting Services Home folder/website will eventually re-appear, but if I try to navigate, I'm once again prompted for my credentials.
I did some research and verified that my AuthenticationTypes in the rsreportserver.config file was set to only RSWindowsNTLM.
Additional environment info: both servers are hosted on AWS, and we are using an ELB to access the SSRS webserver. I'm using IE11 to attempt web access.
Thanks!

Hi Rob,
I am not sure why you are using the -A while setting up the SPN, Use -S to set the SPN and make sure you delete the old one(setspn -D HTTP/<server> domain\user )
Use the following command line to set the SPN
SETSPN –S HTTP/hostname.abc.com:<portnumber> DOMAIN\ServiceAccount
Note: The config file for reporting services also needs to be updated to allow Windows
authentication. Do the following:
1. Locate the installation directory of the reporting server instance.
2. Open the ‘rsreportserver.config’ with a text editor such as Notepad.
3. Find the following XML parameters
<Authentication>
<AuthenticationTypes>
<RSWindowsNTLM/>
</AuthenticationTypes>
4. Change the value
‘RSWindowsNTLM’ to ‘RSWindowsNegotiate
Hope This Helps
Thanks
Bhanu

SQL Server 2014 Management Studio - "The operation could not be completed"

Hi there!
I've recently installed SQL Server 2014 Express Edition to my Windows 8.1 x64 computer. It was working fine for one month or so. Now, when I try to open Management Studio I get the error "The operation could not be completed". A few seconds into
the splash screen. Then the application shuts down.
I don't have any errors or warnings on Event Viewer. Not even any information lines related to SSMS when opening. I've tried to use ProcMon but I can't see any events related to SSMS.exe that could give this result. I've already installed Cumulative Update
2 for SQL Server 2014 with no luck. Also, I've repaired SQL Server installation and even reinstalled this instance with the same outcome.
I know this topic has already been written before but it was related to Windows Server. The response marked as Answer was not applicable to my case. As I said, I'm using Win 8.1 x64.
I'm out of options for now. Can you please give any help?
Thank you so much.

Hello,
Before reinstalling Windows, please try the .NET Framework Repair Tool.
http://www.microsoft.com/en-us/download/details.aspx?id=30135
If the above did not help, you may want to try the automatic repair option.
http://www.bleepingcomputer.com/tutorials/http-wwwbleepingcomputercom-tutorials-automatically-repair-windows-8-with-automatic-repair-/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

MS SQL Server 2014 Report Services Link error

I have installed SQL Server 2014 with Report builder 3 for 2014 report builder is perfect working, but report services is not working when click on this link "http://microsoft:80/ReportServer" then message is alerted " Reporting
Services error" The permissions granted to user 'Microsoft\MCSD'
are insufficient for performing this operation. (rsAccessDenied)and when click on this link "http://microsoft:80/Reports" then message is alerted:
"User 'Microsoft\MCSD' does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed."
i am using MCSD account as administrator so how resolve this problem?

Hi Visio,
I think this issue can be caused by BUILTIN\Administrators might be deleted by someone else. Local Administrators group is equal to BUILTIN\Administrators group on Report Manager. By default, BUILTIN\Administrators user is granted with Content Manger Role.
When someone delete the BUILTIN\Administrators group in the Folder Settings, Local Administrators group cannot access report manager and report server any more.
To fix this issue, please use an account which has access to report server to assign some sufficient permissions to the account “Microsoft\MCSD”.
Another possible is the operating systems limit the overuse of elevated permissions by removing administrator permissions when accessing applications. To fix this issue, please open the Report Manager in Internet Explorer with Run as administrator option.
References:
http://technet.microsoft.com/en-us/library/aa337491(v=sql.105).aspx
http://social.technet.microsoft.com/Forums/exchange/en-US/f095f769-2081-4173-ac16-b806941f0811/uireportmanager01219c08072014161821-e-error?forum=sqlreportingservices
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

High PREEMPTIVE_SP_SERVER_DIAGNOSTICS wait time in sql server 2014 server

I am seeing high waittimes for PREEMPTIVE_SP_SERVER_DIAGNOSTICS and the server is runninf with high cpu.
What could have triggered this high waittime, how can this be fixed,
WaitType Wait_S
Resource_S Signal_S
WaitCount Percentage
AvgWait_S AvgRes_S
AvgSig_S
PREEMPTIVE_SP_SERVER_DIAGNOSTICS 1655043.72
1655043.72 0.00
4 39.75
413760.9305 413760.9305
0.0000
PREEMPTIVE_OS_PIPEOPS 935157.21
935157.21 0.00
343445 22.46
2.7229 2.7229
0.0000
CXPACKET 259912.58
250608.73 9303.85
25115286 6.24
0.0103 0.0100
0.0004
PAGEIOLATCH_SH 206350.14
205563.18 786.96
37649420 4.96
0.0055 0.0055
0.0000
SOS_SCHEDULER_YIELD 139263.91
2430.27 136833.63
293382681 3.35
0.0005 0.0000
0.0005

Hello,
I remember I read a user complaining about high waits on PREEMPTIVE_SP_SERVER_DIAGNOSTICS when he installed CU5 for SQL
Server 2012 SP1, but in your scenario you have a SQL Server 2014 with CU1 (build 2342). I am treating this as a bug and that is the reason I would like you to consider applying CU5, the latest cumulative update, to see if that solves the issue.
http://support.microsoft.com/kb/3011055/en-us
This is the first time I read about this happening on SQL Server 2014 though.
I would like to suggest you to create a Connect item too, to see if the SQL Server team can suggest you another way to
treat this issue.
https://connect.microsoft.com/sqlServer/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SSDT-BI for SQL Server 2014, Command line(silent unattendant automatic) installation script/steps

Hi,
I have downloaded SSDT-BI software and looking for commandline steps,config file for this.
http://www.microsoft.com/en-us/download/details.aspx?id=42313
Any one have Command line installations steps for SSDT-BI automatic(command line) installation for SQL Server 2014 with giving the files location,where to install.....etc, i mean config.xml.
I found below but not sure it will work or not. If any one have working correct command line script, please reply on this forum.
Looking for config.xml file, i searched online and did not find any where with clear config.xml file details.
--Found below from link and not sure it will work or not
http://blogs.technet.com/b/ilikesql_by_dandyman/archive/2013/03/10/how-to-automate-the-installation-of-sql-server-ssdt-office-2013-and-visual-studio-2012.aspx
setup.exe /ACTION=INSTALL /FEATURES=SSDTBI_VS2012 /Q /IACCEPTSQLSERVERLICENSETERMS /norestart
thanks in advance.

Hi SQLDBA321,
The SSDT-BI is automatically installed under xxx:\Program Files\Microsoft SQL Server\. Now matter in GUI or command line, we can't change the path. Because SSDT is a feature of SQL Server, not a feature of Visual Studio. It just use the Visual
Studio Shell. So SSDT will only be installed with SQL Server.
Reference:
Install SQL Server Data Tools - Business Intelligence for Visual Studio 2013
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

How to restore a database backup taken from a SQL Server 2012 instance to SQL Server 2014

I am trying to restore a database backup taken from a SQL Server 2012 instance to my new SQL Server 2014 instance. When I add the .bak through the Mgmt studio UI, it does not seem to find a backup set in the file so I cannot proceed (does not give
me any errors though either. I tried restoring through TSQL command but only got a database restore terminating abnormally error with no other details. How can I restore this database to SQL 2014?

Hello,
Please examine SQL Server Error Log and share with us any error you can find. The following article may locate the log:
http://msdn.microsoft.com/en-us/library/ms187109.aspx
Regards,
Alberto Morillo
SQLCoffee.com

Exploring AlwaysOn Failover Cluster Instances in SQL Server 2014 Tecnet Labs

I like the Labs and have found them very usful. I have a problem with: Exploring AlwaysOn Failover Cluster Instances in SQL Server 2014. The lab starts but hangs on opening SQLONE and the Manual never loads. I have tried coming out and starting again but
get returned to the same failing session. I thought I would mention it here as the is no way to feedback a response as the appraisal only happens once the lab is completed, i.e. no apparent link on the lab site. The session ends when the HOL is reported
as not responding.

Hi,
I'd try this first:
https://vlabs.holsystems.com/vlabs/SystemRequirements.aspx
If that's no help, try the 'Help and Support' link on this page:
https://vlabs.holsystems.com/vlabs/technet?eng=VLabs&auth=none&src=vlabs&altadd=true&labid=12693#
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

Uninstallation SQL server 2014

I installed sql server 2014, but after six months this version has expired and logically it should be a registred and not a trial version.
I decided to uninstall and reinstall, but some services could not be installed as the engine of the database, the analysis services, reporting services etc.
I tried to install sql server 2012 and I had the same problems.
thank you for your understanding.

Hi Dfi-Elec,
Agree with Shanky.
Please make sure that the existing SQL Server instance is removed completely on the machine before reinstalling SQL Server. You can perform the following steps to manually uninstall SQL Server 2014.
1. Uninstall all SQL Server 2014 components from the control panel.
2. Backup the registry.
3. Delete the following keys in regedit:
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
6. Rename all the SQL Server folders in the computer.
7. Reboot the machine.
8. Reinstall SQL Server.
Thanks,
Lydia Zhang

SQL Server 2014 with instance uninstallation

Similar Messages

Maybe you are looking for