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. But in background sql server is working perfect.
*Note: Before doing this, make sure that your user has Administrative righs to run MMC, unless it's not Administrator, below procedure won't work.
Win button + R, then type mmc and press enter.
Choose File->Add/Remove Snap-in.
Click Add to Console Root
and find the "SQL Server Configuration Manager"
You will be able to use it from there or replace existing console by saving it to bin folder of you SQL server's installation.
Note: This is the only option that really worked for me...
This guy here had the same problem: MMC could not create the snap-in. SQL Server configuration manager error
I said there that 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.
Try to run SQL Server Installation and Repair your SQL Server. It works for me.
Sql Managment Studio stop working, sending me this message:
Package ‘Microsoft SQL Management Studio Package’ failed to load
I follow the solution from this page
http://blog.dotsmart.net/2012/01/04/solution-for-package-microsoft-sql-management-studio-package-failed-to-load/
I delete it HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\100 key, just like the page says. Now, ssms.exe it's not starting!!! Not even an error message. The article says that, after restart the machine, the registry will be recreated, but I don't have the registry! What am I missing? Now I don't have error message nor Sql Managment Studio!
I don't know how to help you get back the sql server but for those that haven't deleted "HKEY_CURRENT_USER\Software\Microsoft\Microsoft Sql Server\100\Tools" yet, just rename it to "HKEY_CURRENT_USER\Software\Microsoft\Microsoft Sql Server". You don't have to delete the whole thing. That should work but it doesn't fix it for some. If that is the case, check your .net permission setting s. You might have changed MY_COMPUTER_ZONE code group from full trust to everything. Change it back to full trust. Note that .net permission settings cannot be changed in version 4 and later versions.
Cannot start LocalDB instance, I have installed and re-installed over and over.
Keep getting this error :
Start of LocalDB instance "v11.0" failed because of the following error:
Error occurred during LocalDB instance startup: SQL Server process failed to start.
Anyone any advice ? ?
Microsoft SQL Server 2012, i have ensured the FULL installation options, stopped all services SQL related and tried restarting .
sqllocaldb info
gives me :
Projects
v11.0
when i try
sqllocaldb start v11.0
I get the above error.
When all else fails and you don't care about data loss, delete and recreate your LocalDB\v11.0 database! At the command prompt
sqllocaldb delete v11.0
sqllocaldb create v11.0
(Sqllocaldb is in your PATH right? It was for me.)
I was getting a similar error, but when running
sqllocaldb start
The local db started successfully. Also when checking the event log I saw an error along the lines of
Windows API call WaitForMultipleObjects returned error code: 575
What fixed it for me:
In IIS, configure the app pool to run under an account with permissions to the DB on the server (advanced options of the app pool)
In the advanced option of the app pool, set Load User Profile to true
Reference: http://blogs.msdn.com/b/sqlexpress/archive/2011/12/09/using-localdb-with-full-iis-part-1-user-profile.aspx
It worths looking at LocalDB log files too, it is more detailed than event log:
%LocalAppData%\Microsoft\Microsoft SQL Server Local DB\Instances\ProjectsV12\error.log
Besides recreating the instance I had to delete the content of this folder:
%LocalAppData%\Microsoft\VisualStudio\SSDT\
This is where I have the mdf and ldf files.
My solution:
Go to: %LocalAppData%\Microsoft\Microsoft SQL Server Local DB\ and allow total control of the folder "Instances" to everyone group.
I know this is not OK but it solved my problem and i don't really care about the data of that folder as this is a developing and testing computer.
Same problem here. Here's how I fixed it using bits of the other solutions posted here.
I had dozens of these errors in the application event log:
Windows API call WaitForMultipleObjects returned error code: 575. Windows system error message is: {Application Error}
The application was unable to start correctly (0x%lx). Click OK to close the application.
Reported at line: 3730.
I realized that I had SQL Server Management Studio installed on my development machine, but no other SQL components. I installed the database engine, shared components, and localdb from SQL Express
https://www.microsoft.com/en-us/cloud-platform/sql-server-editions-express
After installing, I still get the same error in event log :(
Found this article:
Cannot start LocalDB
Run the following in cmd to get the localdb instance name:
C:> sqllocaldb info
In my install, I had:
MSSQLLocalDB
ProjectsV13
I ran the following to delete the instances:
sqllocaldb delete MSSQLLocalDB
sqllocaldb delete ProjectsV13
I ran into issues trying to delete/create these (sqllocaldb delete MSSQLLocalDB). I ended up deleting all of the folders and files under '%LocalAppData%\Microsoft\Microsoft SQL Server Local DB\Instances*' (You need to stop SQL Server and kill all sqlserver processes)
Then running 'sqllocaldb create' created and started the default instance and all files.
Had this issue suddenly too but saw nothing weird in logs. Was able to get it running by running the following in an administrator command prompt:
sqllocaldb start
I had this issue. I was trying to use Windows Authentication through an application, but the IIS App Pool credentials were wrong. I was using my Windows user name (ie: NETWORK\name) as my identity, but I changed it to the built-in "LocalSystem" and it worked.
You should check the Event Log for additional information.
Product Name
SQL Server
Product Version
11.0
Product Build Number
Event ID
266
Event Source
SQL Server Local Database Runtime 11.0
Component
Local Database Runtime API
Message Text
Error occurred during Local Database instance startup: SQL Server
process failed to start.
Explanation
A SQL Server process is started but SQL Server startup failed.
User Action
See the event log for details.
Source: http://msdn.microsoft.com/en-us/library/hh256140.aspx
What worked for me was the local IIS application pool I was using was the ApplicationPoolIdentity and that did not have permission to login to MSSQLLocalDB. As soon as a I changed the app pool identity to my windows login account - I was able to connect ok.
Had this issue on Windows 10 when our application was run with compatibility for Windows 8 enabled. Turning off the compatibility setting fixed it.
Before you try something drastic:
After waiting for about 5 minutes it "healed" itself.
(May be this is what this log message is pointing at: "The RANU instance is terminating in response to its internal time out")
I can not yet comment posts here but I really want to give a hint for the in my case extremely helpful post https://stackoverflow.com/a/30298863/8015089 above:
If your LocalDB instance is run by the Windows SYSTEM user (as in my case) the path to error.log is this (MS SQL Server 2012 Express LocalDB on Win11): C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\<InstanceName> (enter this path subfolder by subfolder to avoid access problems!)
I have an application that uses SQL Server Express. How to make setup that will install the application on client's computer?
I searched a lot on google but nothing found helpful.
Also tried this link http://www.codeproject.com/KB/database/Deploy_your_database.aspx
but got stuck on step 3. Please help.
Thanks
Try this article :
http://msdn.microsoft.com/en-us/library/bb264562(v=sql.90).aspx#emsqlexcustapp_topic3