When I run SSMS and connect to server, the Authentication dropdown never populates, so I can't select a type of authentication! I've rebooted and reinstalled v18.6 but it still does this. Even entering the server name doesn't change things. Clicking on Options>> just expands the dialog but the dialog is blank. How do I fix this so that it shows authentication options again?
I found the solution. If you go into C:\Users{username}\AppData\Roaming\Microsoft\ and remove the "SQL Server Management Studio" directory and run SSMS, it starts correctly. Apparently some corrupt settings. I believe your settings could be in AppData\Local or AppData\LocalLow depending on your configuration.
I found out when creating SSIS packages that I need to have this SSIS Service installed in order to schedule them from SQL Server Agent. So with that said I've been trying all over to figure out how to get this service installed without wiping my existing instance.
I've been all over online and no one seems to have the same issues that I'm having or their resolutions aren't helping me out. Here's what I do so far and the wall that I'm hitting:
I go to Start/All Programs/Microsoft SQL Server 2008 R2/Configuration Tools/SQL Server Installation Center (64-bit)
When the console opens I click on Installation and then "New installation or add features to an existing installation"
I then get a pop up that says to "brows for SQL server 2008 R2 Installation media so I point it to my Desktop where the file "SQLManagementStudio_x64_ENU.exe" resides and I get an error that says that my desktop "is not a valid installation folder"
Please help me figure this out, I've been racking my brains for days! The only solutions I've found online for this error are to completely uninstall everything and re-install and that's just not an option.
----- edit -----
I have looked at another link within stack overflow that "may" address my problem.
Add SSIS to existing SQL Server instance
It says that I have to get my hands on the "installation media folder" or download it from Microsoft's website. I can't however find anything on their website besides the "SQLManagementStudio_x64_ENU.exe" file that I was referring to later.
----- edit 2 -----
When I try to just use SQLManagementStudio_x64_ENU.exe I get to the point where I select my instance and get this 'instance id required but missing' error. Here's a screenshot
Don't go via Start/All Programs/Microsoft SQL Server 2008 R2/Configuration Tools/SQL Server Installation Center (64-bit).
Go directly to your installation media "SQLManagementStudio_x64_ENU.exe" file, and run it. It will open same panel, that installation center does, but it will not ask for any installation media, and will take you directly to next step.
Hope you go through successfully.
P.S.: You can't update SQL Server 2008R2 installation with SQL 2008 setup files.
When i tried to connect to sql server configuration manager in sql server 2008. It shows error MMC could not create the snap-in.
It was working perfectly till last night. What can be the reason, how can i solve it. I can not post image of error because of low reputation.
I had the same problem and found out that it was an issue with .net framework.
I downloaded this file: "dotNetFx40_Full_x86_x64.exe" from Microsoft website, and used the "repair" option. It worked for me. Hope it helps.
I have a database set up with FILESTREAM enabled on it (if you go to Properties\Advanced on the instance, it shows that FILESTREAM is enabled). I also ran the sp_configure script on it after doing this to enable the access (to make sure it was enabled). But...as soon as I try to alter the database and add the filegroup to it, it says that the feature is disabled.
I have it enabled on other instances on the same computer, and those work fine. It is only this one that is not working. I have not been able to find any good suggestions as to why it is not working.
It is a SQL 2008 R2 instance.
I was unable to script this, (using the link provided by user1977061), as the MSSQLService requires a restart afterwards to apply the change. Even after doing this it didn't work, and instead I had to manually configure FILESTREAM usage via:
SqlServer Configuration Manager
Sql SQL Server Services
SQL Server(MSSQLSERVER) [Properties]
FILESTREAM tab - enable the first 2, and optionally 3rd check box.
Look at the SQLServer properties > Advanced > Running Values value for "Filestream Access Level" to ensure that the FILESTREAM is actually enabled if in doubt.
Was FILESTREAM enabled on the instance level, though?
In Microsoft Sql Server Management Studio, right-click the server and select Properties. Then on the Advanced page, ensure that FILESTREAM Access Level is not set to Disabled (Which I believe is default):
Changing the FILESTREAM settings through SQL Server Management Studio -> Properties -> Advanced had no effect for me, and SQL Server Configuration Manager kept giving me an error when I enabled FILESTREAM there:
There was an unknown error applying the FILESTREAM settings.
Check the parameters are valid. (0x80041008)
Digging around on the internet led me here as well as to this page: https://social.msdn.microsoft.com/forums/sqlserver/en-US/d8060fdd-4583-4bf7-bdcf-4fd053d5d2c0/unknown-error-applying-the-filestream-settings
Fortunately one of the suggestions there was the solution. Connect to the server with SQL Server Management Studio and run this script:
sp_configure 'filestream access level', 2
reconfigure with override
Note: This was for 64-bit SQL Server 2012
For me this worked out:
forget about Microsoft SQL Server Management Studio to solve this bug
find SQLServerManager**.msc in folder C:\Windows\SysWOW64 and open it
enable filestream as in the picture, by clicking on properties
Database import should work then!
I've done this a thousand times and always follow the steps as Mojo outlines above. However I found that on one computer I couldn't get this to work unless I changed SQL Server Service from running as NT Service to running under a local account. I even reinstalled SQL Server, no luck.
I did as follows:
Click start
Type 'compmgmt.msc'
Expand 'Services and Applications'
Sql Server Configuration
Right Click on 'SQL Server (MSSQLSERVER)' and choose 'Properties'
On the Log On tab, change the user to a local account
Maybe one day this will save someone from banging their head on their desk until their eyeballs pop-out.
If you still are having problems with this i suggest you checkout this link!
I had the same problem in which only one instance didn't activate filestream properly. The solution seems to be to use the SQL Server Configuration Manager and enable it from there.
In addition to the other answers: the account that is used by the sql server service must be a member of the Administrators group.
Symptom: the "Configured value" in the server properties does show "enabled", but the "Running value" stays at "disabled".
I got this working by enabling filestream not in SQL Management Studio but in SQL Configuration Manager. See https://learn.microsoft.com/en-us/sql/relational-databases/blob/enable-and-configure-filestream?view=sql-server-2017.
On the Start menu, point to All Programs, point to SQL Server, point to Configuration Tools, and then click SQL Server Configuration Manager.
In the list of services, right-click SQL Server Services, and then click Open.
In the SQL Server Configuration Manager snap-in, locate the instance of SQL Server on which you want to enable FILESTREAM.
Right-click the instance, and then click Properties.
In the SQL Server Properties dialog box, click the FILESTREAM tab.
Select the Enable FILESTREAM for Transact-SQL access check box.
If you want to read and write FILESTREAM data from Windows, click Enable FILESTREAM for file I/O streaming access. Enter the name of the Windows share in the Windows Share Name box.
If remote clients must access the FILESTREAM data that is stored on this share, select Allow remote clients to have streaming access to FILESTREAM data.
Click Apply.
In SQL Server Management Studio, click New Query to display the Query Editor.
In Query Editor, enter the following Transact-SQL code:
SQL
Copy
EXEC sp_configure filestream_access_level, 2
RECONFIGURE
Click Execute.
Restart the SQL Server service.
For me only the combination of SchmitzIT and Mojo suggestions made it work
I also stumbled into this problem and by trial and error i found out that the solution was to change the account under which Sql Server runs so from SS Configuration manager i located the sql server instante, right clicked "Properties" and on the "LOg On" tab i changed Logon as "This account" to "Bulil-in account", where i choose "Local system".
After a service restart all went fine.
I am getting the following error when my DTS package is scheduled:
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER
I am not sure how to get my DTS packages to execute. They run fine when I manually execute them
I am running SQL Server 2005. DTS Packages were created using the Import/Export Wizard.
I changed authentication from SQL Server to Windows Auth and it did the trick. Not sure the technical reason why.
https://imgalib.wordpress.com/2013/01/24/how-to-solve-ssis-error-code-0xc020801c0xc004700c0xc0047017/
Its the issue with excel processing. Required to change default Runtime.
Navigate to “Debugging” option from left panel and from Right panel change Run64BitRuntime value to false. in project properties.
Check the link above for detailed steps.
I think the problem is with the login/password combination in any of the connections in the connection manager of the DTS, or some problem with the access to the server where the db is located.
If your server name is over 31 characters long (including hostname), then it will not fire.
When a package is scheduled, it normally runs under the context and persmissions of the SQL Server Agent.
Does the package make a connection to a drive letter or other mechanism which is not available to the unattended sqlserver agent account?