I try to generate a Code Map for my solution but it blows up saying: Unable to connect to the specified database.
Specifically, it's trying to connect to (LocalDB)\v11.0
Why does it blow up and why does it need to connect to a DB?
Somehow LocalDb was not installed - typically it gets installed with VS 2012. So I installed SQL Server Data Tools for VS2012, which also installed LocalDb
Visual Studio uses a code index database to help store and create the code maps.
Related
I have several SSIS packages created some time ago which read data from one instance of SQL Server and load them to another SQL Server instance, connections have always been OLEDB and has been working fine up until earlier today when I opened one of the packages and all the OLEDB connections are now failing with an error saying 'Unable to create the type with the name 'DTS.ConnectionManagerOleDb.7'.
If I try and create a new OLEDB connection I get the 'object reference not set to an instance of an object' error'.
Have been using Visual Studio Professional 2017 15.9.37 and SSIS 15.0.2000.150, also tried with VS 2019 Community and getting the same error.
I've tried creating a new project and package and get the same error when creating an OLEDB connection manager.
Anyone with any idea what is going on? Was working on one of these packages this morning and it was working fine, since this afternoon it's buggered.
You should do these things:
Keep the Current VS Enterprise (5.7.1)
Uninstall only your SSDT through VS Installer
Current VS Enterprise (5.7.1) with PRIOR SSDT (5.5.2) (You have to install this version to resolve your issue)
enter link description here
'ssisssdt-existing-connection-strings-unable-to-cre'
I have just updated from SQLite 1.0.8x to sqlite 1.0.94.0 to try and use with EF6.
When I try and add a entity data model from an existing database there is no option to select the data source as sqlite as there used to be for the older SQLite. I have installed SQLite from Nuget and from the setup file on the SQLite website for .net4.5/VS2012. I have tried reinstalling and rebooting both VS and my machine and neither worked. I have found many similar problems to this and no answers to this problem. I can add a connection to an SQLite file via server explorer and navigate through the db on the tab in Visual Studio. This now existing connection does not appear when trying to add a new model in EF6, however.
I even found this question on SO that seems to be the same question as mine but has no answers:
SqlLite in Visual Studio 2012 installed by NuGet dosent exist in Data Source for connection
It seems strange to me that this issue would exist with no answers/concern about it. Are people shunning the SQLite/EF6 combo? I had EF5 and SQLite running fine.
I know this is technically a duplicate but I do not know what else I can do.
I don't know if this actually solves your issue, but I had the same problem and tried pretty much every solution out there.
Eventually, after installing the correct packages to support VS2012, I also installed Entity Framework 6 Tools for Visual Studio 2012 & 2013
After doing so (and a restart of VS) the connection showed up in the Entity Data Model Wizard.
Hope it solves your issue as well.
I'm using Visual Studio 2010 Premium and I just wonder if there is a way to see if the database SQL Server 2008 Express is already installed? I read somewhere that if you have the Professional version of Visual Studio it's installed!?
Simple question, but just want to check before I download and install the database. Thanks!
To check if SQL Server is installed, you can check if this registry key
exists: HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Microsoft SQL Server
For the version, I'm not sure since I don't have different versions of
SQL Server installed.
On my computer, the registry path
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Microsoft SQL
Server\80\Tools\Client Setup\Current Version
exists. In this key, you can read the string "CurrentVersion". In my
case it's 8.00.194.
Best Regards,
or for the alternate you can use
Alternate resource for verfying Sql instance
I am trying to create a VS2010 SQL Server 2008 database project for a SQL Server 2008R2 database. When I attempt to import an existing database a window popups up with the following message "The database that you selected is not supported."
Does anyone have any idea why this is happening?
Note: I have managed to create a database project that happily allowed me to create a table in the master database on the same SQL Server 2008 R2 database.
Thanks
Ok so I figured this one out myself. I think this may be related to my uninstalling some software / database driver that had a connection reference in Visual Studio which was not cleaned up.
Basically to fix the problem I closed Visaul Studio and then deleted this file.
C:\Users...\AppData\Roaming\Microsoft\VisualStudio\10.0\ServerExplorer\DefaultView.SEView
Here is a link to the question and answers that helped me out:
http://connect.microsoft.com/VisualStudio/feedback/details/552006/unable-to-create-data-connection-in-server-explorer
Probably your existing database has different version. Try this: How to: Change the Target Database Version
I've both Visual Studio 2010 (Premium) and MS Access 2010 installed. I'm just trying to connect to a .mdb database file from the server explorer and it doesn't work. I get the following message: "Unspecified error". If I try to add a database on the App_Data folder and open it, I get the same error. I've tried with .accdb and .mdb files but both give the same problem.
I have also Visual Studio 2005 installed on the same machine. And it works without any problems.
Anyone has any thoughts about it?
Thank you
Make sure you have the appropriate references in you VS2010 project for Access databases.
Not sure this counts as an answer but, the issue is with Visual Studio 2010. I too need to connect to an Access database (tactical solution, migration not possible) and in VS2010 I get the "unspecified error". It fails if I try an ODBC based connection too. I can connect fine using SSIS, and as it turns out, in VS2008.
My current solution is to create my class library in VS2008 and reference the compiled DLL in my VS2010 project. I haven't got the time to try and fix my VS2010 install at the moment. When I do, I'll upgrade my 2008 project.
An aside: I think most people on here would migrate to a better database if they could, and are only connecting to Access databases because they have no choice.