I am learning asp.net / C# at my job. I was practicing using VS community edition. Now I have installed 2017 professional edition and SQL Server 2012 (after removing CE version). When I try to run a project in VS, I get this error message: Could not load file or assembly 'System.Data.SqlServerCe, Version=4.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. Googling this error tells me that it is trying to access components from SQL CE 4.0. How can I ensure that SQL CE is completely removed from my machine? Are there any other ways to address this problem?
Try removing the reference of the 'System.Data.SqlServerCe' from your project as I understand that you don't need it anymore.
You can do this by right clicking in references of project and unchecked it or by deleting from web.config
You need to remove the reference to SQL CE. By the text of the error message, the refence would be System.Data.SqlServerCe. Here's more on how to add or remove references to a project
Hope it helps.
Related
I am using SSIS with Visual Studio 2019 for creating and deploying packages on SQL Server 2019. Initially when my package was running on SSDT I deployed it on SSMS Integration server but there was no output.
So, I Checked in Visual Studio 2019: Project -> Project Properties -> Configuration Properties -> General -> Target Version, which was set to SQL Server 2022, So I changed it to SQL Server 2019.
When I tried to run the package again in Visual Studio 2019 I got this error:
Failed to load the package "Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.Sql2019.IDTSApplication160'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{037FE238-12C5-4313-AE13-9E116E90ACEA}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).".
I tried registering the C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn\DTS.dll using regsvr32 which shows success, but I am still getting the same error.
I also tried registering Microsoft.SqlServer.DTSRuntimeWrap.dll using gacutil.exe, still no luck.
Can someone tell me why am I getting this error and how to solve this.
Thank you in advance.
here is the workaround.
Here is the workaround: Solution Explorer -> right click project ->properties->debugging->Run64bitRuntime->set to false.
taken from https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects#:~:text=SSIS%20Execute%20Package,set%20to%20false.
I had the same problem with my VS 2019 after update to SSIS Projects 4.0. If possible, uninstall this version and install the latest general availability (GA) version 3.16, which can be downloaded here:
https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects
https://ssis.gallerycdn.vsassets.io/extensions/ssis/sqlserverintegrationservicesprojects/3.16/1645603822968/Microsoft.DataTools.IntegrationServices.exe
It solved the problem, you can run in 64bit runtime after downgrade.
I have only updated SSIS extension 3.16 to 4.0. I got same error. You should change configuration properties from right click project ->properties->debugging->Run64bitRuntime->set to false.
After that when i want to initiate VS, i got this warning '../Visual Studio 2019.lnk side by side configuration is incorrect'. I resolved the problem through repairing of SQL Server Integration Services Projects on Control Panel-->Programs and Properties.
I had the same problem start after updating Microsoft Data Tools Integration Services VS extension because of prompt by VS. The upgrade was to v4.0 which is not yet generally available.
https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects
On that page it states that "Version 3.16 is the latest general availability (GA) version, which does not support target server version SqlServer2022." There you will find a link to v3.16.
Uninstall v4.0 which, given how recently it was released, is probably still in your downloads folder, otherwise use Extension Manager. Then download and install 3.16. Be warned, both the uninstall and retro install were extremely slow.
Without a reboot, I opened the project and the package that failed with v.4.0, ran first time without problem.
Hope this helps somebody.
I like to deploy SQLServer CE privately on my VSPackage application.
I already tried the following information:
Using Entity Framework with an SQL Compact Private Installation
as well as this one:
How to deploy SQL Server Compact Edition 4.0?
But I still get the following exception message:
The specified store provider cannot be found in the configuration, or is not valid
I guess the above methods do not work for me because my VSPackage will appear as a DLL, while the above methods work for an .EXE application.
Any suggestion how can I do it?
Thanks
Most likely, Visual Studio cannot find and load one of SQL Server Compact Edition assemblies. By default, Visual Studio don’t look dependent assembles in a VSPackage folder if VSPackage code have not explicit reference to such assembles. I described several ways to solve this problem here. Hope it help you.
I have been following along with David Gassner's ASP.NET tutorial on Lynda.com and had things going pretty well up until he walked me through adding an SQL server in the Server Explorer in Visual Studio 2012. When following his steps, I receive the following error:
Unable to add data connection.
Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
I have found numerous websites that suggest installing 3 additional programs/add-ons, such as this site.
I have installed all 3 recommended (Native Client, CLR Types, and Management Objects) and restarted the program and my computer, but still nothing seems to work. Any ideas on how I can add the database?
Additional detail: When I test the connection before choosing OK, the test is successful. I am quite new to SQL/Database stuff so please explain as simply as you can, or link to a resource that will help me fix this.
#mattcoker solved his own problem with the following solution
Problem has been solved by switching to Visual Studio 2010, works without a hitch. Thanks for the speedy responses.
I cannot figure out how to remedy this error when I select the SQL server object explorer.
Could not load file or assembly
'Microsoft.Data.Tools.Schema.Utilities.Sql.11 Version=11.1.0.0
Culture=neutral, PublicKeyToken=**** or one of its dependencies. The system cannot find the file specified.
I have asked on the microsoft forums but I figured people who actually work with this daily may have a better response. I am a new user with VS so my knowledge is limited. I have updated VS and I have SQL server 2012 installed on this machine.
Thank you in advance for helping me make sense of this error.
Getting the same with VS 2013, maybe the same root problem:
Could not load file or assembly
'Microsoft.Data.Tools.Schema.Utilities.Sql.12 Version=12.0.0
I was able to resolve this by getting the most recent version of Microsoft SQL Server Data Tools. This is under the tools menu:
Tools >> Extensions and Updates >> Updates
oI am building a WPF application in .net 4.0.
I have a local DB .sdf file. I am using EF to connect to the DB.
When building the application I get Error 175: The specified store provider cannot be found in configuration
I tried droping and recreating both the model and the sdf file.
I tried everything detailed in this link and the blog post it was taken from.
I cannot get this error to go away. The application runs on my machine (The error is in the edmx file, so it still runs), but when I publish it and run the installer on another computer, I get the same error in a messagebox.
My local machine is Windows 2008 R2 64bit with VS2010 installed. The machine I'm installing on is Windows 7 32bit.
Edit: Also tried this and got the same result.
I donwloaded SQL Server CE again and did a repair install, then reopned VS2010, did a build and the error went away.
I uninstalled and reinstalled and it didn't help, so I don't really know why this did, but there you go.