I have VS2005 Team suit installed and also VS2005 Team edition for DB Proff. Now I took down a solution with three db projects in it but they din't load. I tried reload but it failed as well with error that SQL SERVER WAS NOT FOUND OR NOT ACCESSIBLE....ERROR 26.
I went in tools - options - dbtools - design time validation db and checked the server instance name and connect to it thru sql server 2005 mgmt studio and got in ok.
what could be the issue for unloaded db projects in VS ?
does it use windows authentication when connecting from VS?
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'
My instance of TFS 2010 has developed this problem.
When I try and connect to a Team Project in VS 2010 I get this error:
TF31001: Cannot connect to Team Foundation Server at 'PROJECT COLLECTION'. The server returned the following error: Value cannot be null. Parameter name: serviceDefinition
I have ran the Team Foundation Server 2010 Best Practices Analyzer and it found no problems. I can load the Admin Console fine, everything seems to be in working order, there are no other errors that I have seen and there is nothing in the Event Log that would suggest there has been an issue and there have been no drastic changes to service accounts or SQL Server.
Has anyone seen this error before? If so what did you do to fix it?
Delete the cache from below location, then try to connect again.
c:\users\[username]\Appdata\Local\Microsoft\Team Foundation\3.0\Cache
I have a project that uses EF 5 (code first) in Visual Studio 2012. When I build the database it works, but it isn't showing up in the SQL Explorer for some reason. I checked the connection object at runtime and I can see that the name of the local database is not listed in the SQL explorer. What's odd is that this project doesn't have this problem on another machine. The project is under source control
Check to see if you have a running copy of Sql Server running.
I experienced the same thing; creating a project and then EntityFramework objects, and then running the project. VS 2012 created the database in my 2008 R2 db which was running at the time, but I hadn't opened it in VS, so didn't see the new db. It wasn't until I specifically opened that db in VS that it appeared.
I'm pretty new to Visual Studio so this might be an easy issue :)
I have created a Visual C# SQL CLR Database project where I have created a Trigger. This trigger is supposed to access an IIS on another machine in the network. In order to do this I found that I needed System.DirectoryServices but when I added this VS complained that I needed an assembly. Then I found that I should run the CREATE ASSEMBLY in the MS SQL SERVER. Did that successfully and successfully added my database as a data connection (Server Explorer -> Data Connections). In the Assemblies subfolder I can see the System.DirectoryServices but cannot reference it from the add reference... (when right-clicking references in the solution explorer). When trying to add a reference I have two tabs: Projects (empty) and SQL Server which gives the following error:
The connection to the database failed for the following reason: There
is no available SQL server connection.
No server references can be added at this time, but you may continue
to develop the project.
When I try to add a server connection to either localhost or the machine name of my computer it seems to do nothing (no error but also no server is added in the server explorer).
In Solution Explorer, right click on the Project and select 'Properties'. Select 'Database' tab on the right hand side, then browse to your database or insert a connection string.
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.