We Keep Coding

LoadPackage fails from .NET with Integration Services class cannot be found

I know this has been asked many times before but I haven't found a solution to my specific problem.
My setup is a newly installed Windows 10 Enterprise fully updated with SQL Server 2017 incl Integration Service and Analysis Service. I've installed latest SSDT as well. I've also installed client tools SDK from the SQL Server 2017 installation.
Visual Studio 2017 is installed as well.
My ASP.NET application 'should be' running SSIS packages, but it fails when loading the package using LoadPackage(packageName, null).
The error is "an integration services class cannot be found etc etc.....".
Just to repeat - Integration Service 2017 and Client Tools SDK are installed.
My application has been working on previous SQL Server versions - the most recent version is with SQL Server 2014, but I've upgraded my application from SQL Server 2008 to 2008R2 to 2012 to 2014 and I've never met problems before.
What is different from other posts I can find is that I do not deploy the SSIS package to a separate web server (well, I do and that doesn't work either but a first step is to solve it on my dev machine).
I have created an empty SSIS package in VS2017 to ensure it is not the content of the package that causes the error.
The SSIS package is developed on the same machine, and I can run the package with both 32 and 64 bit versions of DTExec.exe successfully.
I have updated any references in my ASP.NET application to ManagedDTS.dll version 14.0.
I've updated my ASP.NET application to .NET 4.7 as part of this update to SQL Server 2017.
As I can easily search and find many posts about similar problems with lots of solution suggestions, I hope someone will reply to this with solution suggestions rather than links to 'copies' of my question, as chances are I've already read those and tried all suggested solutions.
Thanks in advance...
UPDATE:
First of all, creating a new project and loading a package works - so I figured that I might be facing a problem with the code after updating from .NET 3.5 to 4.7.
I started commenting code and found that if I don't do impersonation before calling LoadPackage, it actually works.
Based on some other issues I've had recently with the July updates from Microsoft, I have removed one of the updates and I now get a different error - with the impersonation code enabled.
The current error is one I've seen many other people have so I'll dig into that - it is: "The package failed to load due to error 0x80131534 \"(null)\". This occurs when CPackage::LoadFromXML fails.\r\n".
I don't really understand if this should be caused by a mismatch between versions, but I'll update as I find out more.
If anyone has good suggestions, I'd be happy to hear them :)

As a quick WORKAROUND, you can set sql job calling the ssis package and run the job using the sp_start_job stored procedure from the asp.net app.
If the running job needs to be monitored, status can be checked using:
select * FROM msdb.dbo.sysjobactivity

This submission failed with error code(s) 2003,1201

We have created a Windows Store app and are running into error code(s) 2003 and 1201 while trying to submit the app to the store. Apparently these errors are not documented in the documentation and there is pretty much absolutely nothing that we can find about these online. Hoping somebody have a knowledge about their resolution and is willing to share it here.

I recommend you to contact the Dev Center support, as they will know what is the cause of this error and will assist you with fixing it. I suspect the problem is some kind of backend issue on their side. You can choose either to create a e-mail based incident on chat with the support live.
You can also post the problem on the dedicated forums (same link as above), to see whether someone else has seen it as well.

It looks like error 1201 is a long-standing issue (bug) with the store.
From the link above, it looks like some people have been able to overcome this issue by upgrading (or just changing) UWP .NET CORE to a different version, or changing or updating their version of Visual Studio.
It looks like you have also posted on this link, and are using UWP Platform 6.2.0. I believe this version is currently considered to be a "Preview" version.
If I was you, I would try rolling back to a previous version (via NuGet Package Manager in Visual Studio). I would suggest you try 6.1.4 (latest stable. as of 5/20/2018), or even earlier 6.0.8

In case it is helpful to others, I am sharing my solution that worked on 2021-11-12.
I encountered error 1201:
I deleted the submission and resubmitted exactly the same package and it worked. It appeared to be a Microsoft Store glitch.

How to add Oracle provider in VS2017 for Entity Framework?

I want to connect to a database(Oracle 12c) for generating ADO.NET model, Code First From Database. I have installed ODAC for VS but there is still no option for connecting Oracle DB at the Entity Data Model Wizard:
At Server Explorer there is a Oracle provider but it is stated as deprecated:
I've also tried to install the following 4 Nuget packages but still no Oracle provider at Entity Data Model Wizard:
I'm suspecting VS2017(Community) is not looking at where I installed ODAC for the list of providers it use but I can't figure where it store this configuration.
Is there anything I'm missing? Or is there other ways to use EF for Oracle? E.g. Fallback to VS2015, create entity models manually (how do I do that?), etc.
Please help me I don't want to write plain SQL in code ever again! Thanks.

I have the same error. I solve this problem by add Oracle database from Visual 2015. And then Open project by Visual 2017. It done. I has been read a lot of topic about this. They say now, Oracle not yet Support for connecting Oracle DB at the Entity Data Model Wizard you can see at here:
https://community.oracle.com/thread/4024914

There is something extra:
Nuget package manager suggests Oracle.ManagedDataAccess.EntityFramework 18.3.0
This won't work with the latest ODP.
Nuget Package versions should match ODP versions:
ODP 12.2.0.1.1
Nuget Oracle.ManagedDataAccess.EntityFramework 12.2.1100
If not the Entity Data Model Wizard will crash without leaving any trace in the
C:\Users\YOURUSER\AppData\Roaming\Microsoft\VisualStudio

I solved this by installing Oracle Developer Tools for Visual Studio 2017

I hade the sam problem, but found the solution here:
Do not use the .NET driver. Use the ODP.NET driver (managed or unmanaged).
http://www.oracle.com/technetwork/topics/dotnet/whatsnew/vs2012welcome-1835382.html
Create a new connection from Server Explorer in Visual Studio and use these images as guides: change the datasource, making sure to choose the flavor of ODP.NET that your .NET application will use (Managed or Unmanaged) - and then connect to oracle. In the Oracle connection dialog, if you have a connection alias choose a "Connection Type" of "TNS" and then choose the alias from the "Data Source Name" drop down list. If you do not have a connection alias, you can choose a Connection Type of "EZ Connect" and then provide the host, port, and service name for the database you wish to connect to.
Best Regards, Par

I was facing same problem. first ensure that you installed odac for visual studio 2017
just go this link and follow:
https://www.oracle.com/technetwork/topics/dotnet/downloads/odacmsidownloadvs2017-3806459.html
uninstall previous odac version.
Hopefully, if you install from the link, you will get all things.

connecting C# with Oracle database

I have C# and Oracle 10g installed on my workstation.And also created a C# program,so my problem is i cant connent my C# application with Oracle database.it is really freaking me out.when adding Reference i cant find "Oracle.DataAccess.dll".thnx in advance.#Amu

Have you installed ODAC (oracle client) components on you workstation?
If you would use Oracle.Data namespace You need them. You can download from here
Please chek database version and bitness, because it is an important factor.
If you dont want to install Oracle client, you could try to use System.Data.OracleClient namespace, that's bundled with framework. In this case take in account that's deprecated and will be removed on next version of framework (link)

How to upgrade SQLCE from 3.1 to 3.5

In the previous project, I've already developed an application with Ms Visual Studio 2005 and use SQLCE 3.1. Now, I have to add some feature there. Today I want to use SQLCE 2008(3.5). my sdf file still didnt work.
How do I upgrade it?
my error:
{"The database file has been created by an earlier version of SQL
Server Compact. Please upgrade using SqlCeEngine.Upgrade() method."}
I already tried and get some source in here and here, but it still doesn't work.
What should I do?
Must I downgrade my VS and DB or have another way to do it?
#joshua
of course i already try it, but the error message still like before i put it there. the output still detail:
unhandeled exception has occured in your application. if you click
continue. the application will ignore this error and attempt to
continue". if you click quit, the application will close immidiately
the databe file has been created by an earlier version of SQL server
compact. please upgrade using SqlCeEngine.Upgrader() method it still
display.
what should i do now?

I hate to ask it like this, but did you try calling the SqlCeEngine.Upgrade() method like the error message stated. That method is supposed to upgrade the SDF file from SQLCE 3.1 to SQLCE 3.5.
It should work like this:
SqlCeEngine engine = new SqlCeEngine("Data Source=data.sdf");
engine.Upgrade();