VS2015 Community is not showing SQLite in the list of available data sources in one place and showing it in the other.
If I click New Connection button in Server Explorer and click Change, I get the following list of Data Sources:
If I add a new item to my project > choose Entity Model > from existing database > New Connection, I get the following list of Data Sources:
How can I get SQLite in the New Connection data sources list?
Background
The problem started when my existing EDMX failed to load with the infamous error message
The Operation could not be completed: Invalid Pointer
This error can be fixed by deleting ComponentModelCache folder as described in this post. This method has worked for me in the past, but not this time. I finally decided to recreate the EDMX from scratch. Since then I'm facing this issue.
A few things that might give some hint:
I have recently installed VS2017 Community side-by-side with VS2015. VS2017 can open the existing EDMX just fine, but cannot do Update from Database, so I came back to VS2015.
I uninstalled and reinstalled System.Data.SQLite provider several times, thinking that this might be a registration issue. Didn't do any good.
Note that VS2017 support is not there yet on System.Data.SQLite's download page. I'm using the last available version that supports VS2015 (version number 1.0.104.0).
Good news is that the issue is fixed finally; at least for VS2015. Bad news is that I don't know what exactly did the trick. So I'll list down everything that I tried and maybe this could help someone in the future. These steps are not in any particular order.
Uninstall all SQLite packages from NuGet.
Uninstall Entity Framework package too.
Reinstall all these packages.
Remove and reinstall the latest version of SQLite provider (1.0.104.0 as of this writing).
Use VS2015 only. VS2017 is currently not supported by SQLite provider.
Clear ComponentModelCache folder and restart Visual Studio.
I found an easy solution, just install below extension from market place and Sqlite will be available to data source list
SQLite/SQL Server Compact Toolbox
Related
The problem
So I am running into an interesting issue. I have been tasked to change a query for a simple SSIS package in Visual Studio 2015, which is a thing I have done multiple times in the last 6 months.
After changing the package and deploying it (to an installation of SQL server 2016, without errors!) I noticed that the execution of the package (scheduled with SSMS) generates the same result as the pre-updated package, meaning the demanded changes hadn't taken effect. Of course, as test, I have executed the package directly from VS2015 and got the result I wanted.
Ever since I have been running tests and trying to find a solution. The problems seems to lie with the receiving side of the deployment proces.
What I have tried
Deleted the package from the existing project in SSMS and redeployed. Deployment again seemd to succeed but the package didn't show up, so I had to restore an old version of the project.
Deploy the package from multiple different computers with access to VS2015 and the source code. No change...
Deploy the package to a new (empty) SSMS project: package does not appear in the project. This leads me to believe that the old package is kept when I publish the new version to the existing project in SSMS.
Regenating/rebuilding the package in VS2015, frankly this was never necessary and probably doesn't do anything for an SSIS package, but it may help you get an idea of my skill level.
In the past we have had issues with the encryption level blocking the deployment of packages. I have verified these settings and found no issues.
I have verified if any updates have recently been installed to the database server, which does not seem to be the case.
I have (of course) tried to google the issue, which is tricky due to the lack of errors. I have found the following links, that describe the same/a similar issue, but their solutions haven't helped:
https://dba.stackexchange.com/questions/259672/ssis-package-not-being-deployed
Deployed SSIS Package not reflecting changes made to package
What is still left to try
Rebuild project from scratch to see if that version is deployable.
Unfortunately I don't have a lot of experience with this subject and no colleagues or contacts to ask for help.
Thanks in advance.
My workaround
After quite a bit of time attempting to solve the issue I have resorted to working around the problem, by manually importing the .ispac file into the database. While this is not the prettiest of solutions, at least it's a workable one. If anyone has any other idea's I'll gladly see them, but for now the issue isn't nearly as pressing as it was.
From your post. "Deleted the package from the existing project in SSMS and redeployed. Deployment again seemd to succeed but the package didn't show up".
Are you 100% sure you are deploying it to the same project on the same server on the database? Are you refreshing after you deploy?
I am facing the puzzling fact that the information of update sites fail to be updated despite my forcing a reload in Preferences > Install/Updates > Available Software Sites.
I have a local update site (file:/ protocol, on Windows) and an online update site (https://) that I use as staging/test update sites for an open source project that I am maintaining.
I build the update site using an update site project that is stored locally and wiped clean each time I build it. When I have tested the new release in a different Eclipse instance and I have validated my changes, I then upload the entire update site to my server. Then, just to simulate what a user would do, I update the plugin in another Eclipse instance that runs on a different physical machine.
I have (yesterday) built another version, 2.2.0.201702052007 and uploaded it to my server. The previous version was 2.2.0.201702042059.
The problem that I have is that the Eclipse instances (Mars.2 and Neon) on my development machine keep reporting the previous to last version, despite my reloading the update site information. However, the other machine sees the new version without a problem.
This is what I've tried:
Reloading the information of the update site: each time, I get a confirmation message saying "information for [...] has been reloaded from the server" but it turns out that it hasn't been reloaded: I see the older feature version.
Accessing the update site from a different Eclipse instance on a different machine: I see the new version.
Loading the update site's site.xml file from a browser: I see the new version.
Using FileZilla to download the entire update site to a local folder and unzipping content.jar and artifacts.jar so that I can read the XML files embedded in those JAR files: I see no trace of the older version.
Removing the update site, restarting Eclipse and adding the update site again: the problem was still there.
As a last resort, I removed all files of the update site from the server: Eclipse still reported successfully reloading the information from the server.
I shut down the httpd service on the VPS. Eclipse reported success until I restarted it and it then failed. But once the web server was again online, it failed to actually send a request to the web server as it kept saying there was no update site! As a consequence, the online update site now appears empty and restarting Eclipse does not change that.
[EDIT] Even more incomprehensible, the Reload button reports success even when there's no network connection to the update site (network interface disabled).[/EDIT]
There seems to be in the provisioning framework a cache somewhere between the UI and my server that reports an outdated information and feature version in spite of the explicit requests to reload that very information.
Is there any file or folder that I can delete to have the provisioning framework reset itself? If possible, I would altogether disable its cache.
I've found out that Oomph apparently has an action on the update site information retrieval process.
Anyway, I could recover normal operation (for now) and have the information properly reloaded by first deleting the appropriate files in C:\Users\...\.eclipse\org.eclipse.oomph.p2\cache.
By “the appropriate files”, I am referring to the fact that files in that folder are named after the URLs of repositories known to your Eclipse instances.
We are trying to migrate from our on-premises TFS 2010 to Visual Studio Online (VSO). We did it a first time just to test it out. The OpsHub application stopped a couple of times, but we finally succeeded. We did our testing and deleted the project from VSO.
The second time dident go so well. It gives the following error after migrating a lot but not all of our change sets:
com.opshub.eai.config.exception.ConfigServiceException:
OH-CONFIG-0101: Exception while calling service, underlying cause :
could not execute query.
We can press OK and navigate into another view in the application but the same error occurs on every view. We have restarted the application, the service and even the server. We always get the same error. We decided to uninstall the application and reinstall it. That solved the problem, but it appears again after we have migrated about 60% of our source code (a day or so).
So, after 3 re installations we are about to give up. It doesn't crash on the same change set every time.
Does anyone know a way around this? Is there any way we can see the real cause of the problem and fix it?
We are using version V1.3.000B000 (latest version).
Not sure if this is the proper place to post the question, but OpsHub is referring to stack overflow for support.
A project was recently deleted from the Draft and Published databases by mistake. Sever versions are still listed in the Archive database. How can I restore that project to the published database and make it available in PWA?
I tried restoring the project via Administrative Restore. I got a message saying the restore job would be queued. I checked the queue and the job finished successfully - but the project does not appear in Project Center. I'm wondering if Administrative Restore is only meant for restoring specific versions of projects that are still "live".
Thanks for any help and please ask if more information might help.
Have you checked to see if the project is accessible through Project Professional? Also, have you checked the simple things that are easy to forget, such as making sure that "sub projects" is selected in the ribbon, or that when you restored, it wasn't marked as closed, and then being excluded from the views? When I have restored a project previously, sometimes key pieces of Project Details are either missing or incorrect and the project does not appear as expected in the views. Once the project is opened, the details can be reapplied and the project appears in PWA as expected.
You could also attempt to use "ProjTool." It would be worth trying to see if that program recognizes it is as available and publish from there.
I have installed OpsHub and trying to migrate the source code from VSTF2013 to VSO. After selecting the TFS Endpoint and VSO Endpoint, clicking on Next. When trying to load the projects to be migrated I am getting this error, "TF50608: Unable to retrieve information for security object $PROJECT:vstfs:///Classification/TeamProject/faedd6e7-e2bc-4f91-917f-3823c951e71b, it does not exist."
When I select some other TPCs in the same VSTF server, I am able to load the projects in VSTF. Could not understand this error code if this is related to security configuration at TPC level or OpsHub is trying to load some project which is does not exist?
I have done some search on this error code TF50608, looks like this issue can occur if any Team Project is deleted and created with the same name. I am able to connect to TPC and load the projects using TFS Administration Tool (http://tfsadmin.codeplex.com/) but OpsHub fails to load the projects.
Is there any work around to skip this error and continue with the selection of the Team Project?
We have verified it is a defect. It will be resolved in the next build coming out soon.
use VERSION 1.0.1.005, in which this issue is resolved