Hello,

Having been caught out with the issue of R Services being installed in a long filename path which included spaces, I have to ask the questions:

1) Why are long filenames an issue in this day and age?

2) Why, when it is a know issue, does the SQL Installer allow you to install to a long filename path with a space without an error?

We have got round the issue by enabling 8dot3, creating a short name path and editing the launcher.config file.

Rgds

After installing the x64 with all tools excluding the SDK from the SQL Express Edition, I go to Management Studio, log in and get the error when I click under the Instance name- Databases...Have reinstalled many times, removed all directories and registry keys from both HKEYs(regular and Wow6432Node) before rebooting and reinstalling. No VS installed on this computer..put it looks like it installed "MS Visual Studio 2010 Shell (Isolated)-ENU" and "Visual Studio 2010 Prerequisites".....tried working past the error, it just hangs the Studio after it tries to add things...HELP..PLEASE!!!

Object reference not set to an instance of an object. (Microsoft.VisualStudio.Platform.WindowManagement)

----------------------------

Program Location:

I'm trying to do a SQL 2008 cluster installation.
I installed one node and now I'm trying to add a failover cluster node.

in the "add Node Rules" I get following message:

---------------------------
Rule Check Result
---------------------------
Rule "SQL Server Database Services feature state" failed.

The SQL Server Database Services feature failed when it was initially installed. The feature must be removed before the current scenario can proceed.
---------------------------
OK  
---------------------------


Can anyone help me?

I tired to Update SQL Server 2014 Enterprise to SQL Server 2016 Enterprise today. All components succeeded except Client Tools SDK and Client Tools Backwards Compatibility. I then UNINSTALLED the 2 components successfully. I ran Sql Server 2016 setup to ADD the 2 components but a I got the same error.  SEE DETAILS BELOW:

Hi,

I work at a 3 people start up. None of us are IT guys. I know some SQL and would like to use it for some of our reporting needs. We work in one of those shared office spaces but we do have our own shared network. We use a cloud service to share files. When I click on "Network" on Windows Explorer I can see the machines of my other two co-workers (although I have never connected to their machines)

Sql server is installed locally on my machine and I would like to give read-access to the DB to my co-workers so they can view the SSRS reports I created. I tried to create a Login for one of the users but the only location that's available to me is my own machine. Is this even possible in our current set-up or am I completely on the wrong track here? Is it simply a matter of getting their Windows userid and pw and connecting to their machine?

Hi all,

i am facing the below issue and get the below log details.

Hugo Otaola Computer Systems Specialist II SBC - DSS

Database Engine Services continuously fails on install. Firewall and Anitvirus is completely disabled. I have tried the 2016 version aswell as the 2014 version with the same outcome.

Here is the error log:

Namaste All,

Its Monday and we are back with "Interview with Forum Ninja". Today we are publishing interview with SQL Server MVP, expert and forum moderator Tibor Karaszi.

Interview with Microsoft MVP and Forum Moderator Tibor Karaszi.

If you are a forum moderator and want your interview to be done to tell the world about your contributions to MSDN forums and how awesome you are with Microsoft technology please ping me. My ID is in  Wiki Article link present in my signature.

Cheers,

Shashank

Hello,

I need to install SQL Server 2014 business intelligence with SP1 for educational purposes. I have uninstalled the previously installed instance of SQL Server to install a new and clean BI version. To uninstall the previous version I used IObit uninstaller which also deletes all remaining folders and registers.

When I try to boot the setup.exe of the BI version I get an empty error box. I get the same  when trying to install other versions of SQL server.

After doing some research about this error, I found that capsol.exe should be able to resolve the issue. So I tried the command:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\capsol.exe -machine -reset

and

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\capsol.exe -machine -reset

unfortunately, both did not resolve the issue. I tried every other possible solution on the source thread (SQL Server 2008 R2 setup.exe will not run) without success.

Please help me to solve this problem

Kind regards, Wessel

I just attempted installing SQL 2016 RTM and the install rebooted the server. After the reboot SQL of course is not working at all due to the install not completing; so, it's hosed up.  It appears that msiexec requested a restart due to SSIS (see below).  Has anyone had this issue?  This is a new Win 2012-R2 VM and a new SQL 2016 install.

From the Win App Error Log:

Windows Installer requires a system restart. Product Name: SQL Server 2016 Integration Services. Product Version: 13.0.1601.5. Product Language: 1033. Manufacturer: Microsoft Corporation. Type of System Restart: 1. Reason for Restart: 1.

Hi,

I am new to SQL and I am not sure if this is in the correct thread but here goes anyway.

We have a Virtual Machine which has SQL server running inside it, the VM currently has 16 vCPU assigned to it, and two SQL instances. we are licensed for 16 cores and each instance is left in its default configuration to balance the CPU usage itself, we don't tie any cores to an instance.

The following link states Limited to lesser of 4 Sockets or 16 cores https://technet.microsoft.com/en-us/library/ms143760(v=sql.110).aspx my question is this: If we assigned 20 vCPU to the VM will SQL only use 16 of them? I guess this is easy to see in task manager if we had one instance, but we have two instances which aren't tied to any cores, so is it possible that instance A will use 16 of 20 cores, and instance B will use a different 16 of 20 cores (with some crossover). What we are trying to avoid is breaking any licensing rules, and also learn how SQL technically uses cores? will the SQLServer.exe process of each instance only have its affinity set to 16 of the cores for example?

Would someone be able to explain this to me, we dont have spare resources to perform a test environment using more than 16 cores, so it's tricky for us to find this out ourselves unless we bring the live system down and assign more cores.

the reason behind this is we think the number of vCPU assigned might be having a bit of a performance impact on the server, but without knowing how each instance balances across the cores and whether we will break licensing rules, it is difficult to move forwards.

Many thanks

Steve

Morning All

I am having a issue with my SQLServer install, were after a reboot of the VM the agent fails to start. Once manually starting the agent it runs fine.

Please see below SQLAgent log

2016-09-06 07:20:46 - ? [100] Microsoft SQLServerAgent version 12.0.4213.0 (X64 unicode retail build) : Process ID 2904
2016-09-06 07:20:46 - ? [495] The SQL Server Agent startup service account is DOMAIN\DBA_SQL_AGNT_PD.
2016-09-06 07:21:16 - ! [150] SQL Server does not accept the connection (error: 258). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2016-09-06 07:21:16 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2016-09-06 07:21:17 - ? [000] Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install. [SQLSTATE 01000] (Message 15457)
2016-09-06 07:21:17 - ? [098] SQLServerAgent terminated (normally)

and please see SQLServer log during those times

2016-09-06 07:20:40.87 Server      SQL Server detected 2 sockets with 2 cores per socket and 2 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2016-09-06 07:20:40.87 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-09-06 07:20:40.87 Server      Detected 4095 MB of RAM. This is an informational message; no user action is required.
2016-09-06 07:20:40.87 Server      Using locked pages in the memory manager.
2016-09-06 07:20:41.21 Server      Default collation: Latin1_General_CI_AS (us_english 1033)
2016-09-06 07:20:44.27 Server      This instance of SQL Server last reported using a process ID of 1744 at 06/09/2016 07:18:54 (local) 06/09/2016 06:18:54 (UTC). This is an informational message only; no user action is required.
2016-09-06 07:20:44.27 Server      The maximum number of dedicated administrator connections for this instance is '1'
2016-09-06 07:20:44.28 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-09-06 07:20:44.28 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.
2016-09-06 07:20:44.35 spid7s      Starting up database 'master'.
2016-09-06 07:20:44.74 Server      CLR version v4.0.30319 loaded.
2016-09-06 07:20:44.88 spid7s      Resource governor reconfiguration succeeded.
2016-09-06 07:20:44.89 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-09-06 07:20:44.91 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-09-06 07:20:45.13 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2016-09-06 07:20:45.31 spid7s      Error: 25602, Severity: 17, State: 22.
2016-09-06 07:20:45.31 spid7s      The target, "5B2DA06D-898A-43C8-9309-39BBBE93EBBD.package0.event_file", encountered a configuration error during initialization. Object cannot be added to the event session. The operating system returned error 3: 'The system cannot find the path specified.
' while creating the file 'D:\DBAdmin\Extended Events\Waits\Waits_0_131176164452790000.xel'.
2016-09-06 07:20:45.34 spid7s      Error: 25710, Severity: 16, State: 1.
2016-09-06 07:20:45.34 spid7s      Event session "Waits" failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems.
2016-09-06 07:20:45.34 spid7s      Error: 25709, Severity: 16, State: 1.
2016-09-06 07:20:45.34 spid7s      One or more event sessions failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems.
2016-09-06 07:20:45.37 spid7s      SQL Trace ID 1 was started by login "sa".
2016-09-06 07:20:45.48 spid7s      Server name is 'MYSERVER'. This is an informational message only. No user action is required.
2016-09-06 07:20:45.79 spid15s     A self-generated certificate was successfully loaded for encryption.
2016-09-06 07:20:45.80 spid15s     Server is listening on [ 'any' <ipv6> 1433].
2016-09-06 07:20:45.80 spid15s     Server is listening on [ 'any' <ipv4> 1433].
2016-09-06 07:20:45.80 spid15s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2016-09-06 07:20:45.80 spid15s     Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2016-09-06 07:20:45.81 Server      Server is listening on [ ::1 <ipv6> 1434].
2016-09-06 07:20:45.81 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2016-09-06 07:20:45.81 Server      Dedicated admin connection support was established for listening locally on port 1434.
2016-09-06 07:20:45.83 spid15s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-09-06 07:20:45.84 Server      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.
2016-09-06 07:20:45.90 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MYSERVER.domain.com ] for the SQL Server service.
2016-09-06 07:20:45.90 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MYSERVER.domain.com:1433 ] for the SQL Server service.
2016-09-06 07:21:03.49 Logon       Error: 18456, Severity: 14, State: 38.
2016-09-06 07:21:03.49 Logon       Login failed for user 'DOMAIN\DBA_SQL_INST_PD'. Reason: Failed to open the explicitly specified database 'ReportServer'. [CLIENT: <local machine>]
2016-09-06 07:21:05.72 Logon       Error: 18456, Severity: 14, State: 38.
2016-09-06 07:21:05.72 Logon       Login failed for user 'DOMAIN\DBA_SQL_INST_PD'. Reason: Failed to open the explicitly specified database 'ReportServer'. [CLIENT: <local machine>]
2016-09-06 07:21:08.74 spid16s     A new instance of the full-text filter daemon host process has been successfully started.
2016-09-06 07:21:08.97 spid17s     Starting up database 'msdb'.
2016-09-06 07:21:08.97 spid11s     Starting up database 'mssqlsystemresource'.
2016-09-06 07:21:08.97 spid20s     Starting up database 'distribution'.
2016-09-06 07:21:08.97 spid21s     Starting up database 'DB_ADMIN'.
2016-09-06 07:21:08.97 spid22s     Starting up database 'ADMIN'.
2016-09-06 07:21:08.97 spid23s     Starting up database 'ADMIN6'.
2016-09-06 07:21:08.97 spid24s     Starting up database 'TTL_DB_MASTER'.
2016-09-06 07:21:08.97 spid27s     Starting up database 'ADMIN5'.
2016-09-06 07:21:08.97 spid28s     Starting up database 'ReportServer'.
2016-09-06 07:21:08.97 spid29s     Starting up database 'ReportServerTempDB'.
2016-09-06 07:21:08.99 spid11s     The resource database build version is 12.00.4100. This is an informational message only. No user action is required.
2016-09-06 07:21:09.00 spid26s     Starting up database 'TTL_DB_ANALYSIS'.
2016-09-06 07:21:09.00 spid25s     Starting up database 'TTL_DB_ADMIN'.
2016-09-06 07:21:09.19 spid11s     Starting up database 'model'.
2016-09-06 07:21:09.69 spid11s     Clearing tempdb database.
2016-09-06 07:21:10.43 Server      Software Usage Metrics is enabled.
2016-09-06 07:21:11.93 spid11s     Starting up database 'tempdb'.
2016-09-06 07:21:15.37 spid34s     Server is listening on [ 'any' <ipv6> 4024].
2016-09-06 07:21:15.37 spid34s     Server is listening on [ 'any' <ipv4> 4024].
2016-09-06 07:21:15.38 spid34s     The Service Broker endpoint is now listening for connections.
2016-09-06 07:21:15.41 spid34s     The Database Mirroring endpoint is in disabled or stopped state.
2016-09-06 07:21:15.60 spid34s     Service Broker manager has started.
2016-09-06 07:21:15.98 spid7s      Recovery is complete. This is an informational message only. No user action is required.
2016-09-06 07:21:16.02 spid7s      Launched startup procedure 'sp_MSrepl_startup'.
2016-09-06 07:21:16.10 spid28s     The activated proc '[MAIN].[PROCESS_SERVER_CONFIGURATION_EVENT]' running on queue 'DB_ADMIN.AUDIT.SERVER_CONFIGURATION_EVENT_NOTIFICATION_QUEUE' output the following:  'Invalid object name 'SERVER_CONFIGURATION_EVENT_NOTIFICATION_QUEUE'.'

i understand i could prorably just set the SQLAGENT service to a delayed start to get around this, but im keen to understand what is causing the holdup to prevent the agent connecting in the first place.

Thanks in advance

I want to change SQL Server from starting automatically to starting manually. 

In the Config Manager, when I open the properties window and select the Start Mode, the combo box does not display when clicked, and so it does allow me to change it from Automatic.

It appears to be a bug.

I'm running Windows 10.

I'm about to set up a new SQL failover cluster and plan to put the tempdb files on shared storage.

The following page states this will be supported: https://msdn.microsoft.com/en-us/library/mt683723.aspx

But this page states it won't: https://msdn.microsoft.com/en-us/library/ms143506.aspx#StorageTypes

Which is correct?  Thanks

This page implies Windows 2012 is not supported for a SQL 2016 cluster.

https://msdn.microsoft.com/en-us/library/ms189910.aspx?f=255&MSPPError=-2147217396

Is this correct?

Hi,

I am trying to install the SQL 2012 tools onto a Server 2012 management server.

I get the error in the install log file:

SQM key not found

Setup closed with exit code: 0x84C40013

When running setup from a PS prompt:

Unhandled Exception: System.Security.SecurityException: That assembly does not allow partially trusted callers. at Microsoft.SqlServer.Chainer.Setup.Main()

I have not been able to find anything that is clear to me on a way forward to resolve as I am not a .Net Developer!

I've been trying to repair my SQL SERVER 2012 installation, I've had it for years  and all of a sudden the Management Studio application will not open and suggests that i reinstall. But when i try to either REPAIR or REINSTALL, i get the error message below:

I have read a few forums online that recommend moving the Config.ini file and editting it, but the Config file i find does not have any refernce to Installshare directory. What do i need to do to get this pointing to the right location.

Hello,

I have SQL 2012 installed 2 years ago. The server contains one DataBase for the app that should be removed from production next week.

The server was properly configured, always patched.

I just got a new request for the app that requires SQL. In current situation the app that uses SQL was installed on separate server .

New APP could be installed and I want to install on existing SQL 2012 machine.

Here is my plan

1. I want to remove existing DB in right way. Please suggest how.

2. I need to RENAME the server.

3. I need to install New App on the server

I would like to know if 3 points are OK and if there are any potential issues for the future.

If there is a minimum chance for a problematic behavior I will start with new server installation.

If possible provide more details on steps if my plan is valid.

Thanks.

--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis