My development environment
Windows 10 2004 64 bit
Visual Studio 2019 Community Edition Version 16.7.6
SQL Server 2019
EzAPI2016
Working with EzAPI to implement a sample workflow that read a table and write to another temp table in the same database. After create the OLEDB data source providing the corresponding data-flow context, when assign the connection-manager to the connection attribute of the previously crated source object, the error in the title happen.
Thanks in advance for any suggestion.
Have a good day.
Solved:
Found the solution removing the reference to Microsoft.SqlSever.DTSRuntimeWrap.dll (version 13) into the ezapi project, and updating it to version 15, in my environment under c:\windows\Microsoft.net folder.
Related
I'm using the very latest version of Visual Studio Professional 2017 (v15.9.9) with the latest SQL Server Data Tools (v15.1.61903.01040)
I create a new stored procedure in my database project, for example, with the following code:
create proc [dbo].[MyProc] as
select 'Test' as [TestColumn] FOR JSON AUTO
It won't compile with the errors below, and the keyword JSON is highlighted:
SQL46005: Expected XML but encountered JSON instead
SQL80001: Incorrect syntax near 'JSON'
It seems strange that this doesn't compile, when it's perfectly valid SQL (or am I mistaken? Is there something I'm missing? Or is it genuinely not supported?)
This issue seemed to exist for older versions of SSDT before 2016, but was reported as resolved back then, is this perhaps a recent regression? I can't find any other instances of this error or anything like it.
If you have the "Target Platform" on the .sqlproj properties set to SQL 2014 or less or "Microsoft Azure SQL Database" then this will happen, the compatibility level doesn't affect it (or at least setting my project to 2014 compatibility didn't).
This works for me with SQL 2016+ and Azure v12 with SSDT "15.1.61902.21100"
Hope it helps!
ed
I have DevExpress XtraReports v18.1.6 version and PostgreSQL 4 v3.3. Visual studio 2017 v15.3.3 and Windows 7.
Here is scenario: In my project, I have some reports writen in devexpress v17.2. I could not run those reports, because I could not download exactly that version 17.2, I install new 18.1.6. Then in Visual studio main menu "DevExpress" I click on "Project converter to 18.1.." and that action replace my old dlls v17.2 with new 18.1. After that I could run reports (see it in designer).
But problem is with databse connection. I created connection string with "XpoProvider=Postgres".
Every time when I want to get data in report, or rebuild result shema, or manage queries I get error:
Could not load file or assembly 'System.Threading.Tasks.Extensions, Version=4.2.0.0,...
I have that reference, exactly that version. Also I tried with new versions of threading.tasks but unsuccessfully.
My version of Npgsql.dll was 2.2.7, I tried with 3.2.5 (read from some devexpres documentations). Also tried with new 4.0.3.
Did anyone have a similar problem?
we had the same issue when using the DevExpress (18.1) Report Designer with Visual Studio 2017.
I know this might not be an ideal or the best solution but at least it worked for us:
I used ProcMon to determine where it was looking for that specific File, for me it turned out to be C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\hhfnlhs1.kna
I downloaded the NuGet Package for System.Threading.Tasks.Extensions from NuGet (https://www.nuget.org/packages/System.Threading.Tasks.Extensions/)
I unzipped the Package and stored the DLL at that path from step 1
I had to active "loadFromRemoteSources" in my machine-config (see https://learn.microsoft.com/en-us/previous-versions/dotnet/netframework-4.0/dd409252(v=vs.100))
I had to put another DLL from NuGet (https://www.nuget.org/packages/System.Runtime.CompilerServices.Unsafe/4.5.2) into that folder from step 1
That's it - now I can access the DB again.
I got java script error:
SCRIPT5022: Sys.ArgumentOutOfRangeException: Value must be an integer.
Parameter name: y Actual value was 326.739990234375.
When I testing application in IE 10 browser. I did googling and found this solution from Microsoft Support.
I have modified MicrosoftAjax.js and MicrosoftAjax.debug.js files as per above article.
But After modified the javascriptfiles, when I run the application using Visual Studio 2005, I did not get the updated MicrosoftAjax.js and MicrosoftAjax.debug.js files.
So my question is: How can I get the updated versions of these two javascripts files.
Thanks,
Ankur
Instead of hacking JS files try upgrading your project to a newer .NET framework:
http://codecorner.galanter.net/2013/05/01/solution-for-ie10-error-script5022-sys-argumentoutofrangeexception-value-must-be-an-integer/
I am getting the following error using the MongoDB.Web membership provider:
Method not found: 'MongoDB.Driver.SafeModeResult MongoDB.Driver.MongoCollection.Insert(!!0)'.
I have the simplest of implementations:
Visual Studio Express 2012
Empty Website project (VB.NET) with a standard index.aspx added
Nuget packages: MongoDB.Web 1.2, mongocsharpdriver 1.7
MongoDB db version 2.2.3
Windows 7 64-bit
(All Mongo elements downloaded fresh today.)
I copied and pasted the Membership provider web.config details from the FreshLogic site, and modified only the database and collection attributes to reference my desired collection.
I have one line of code in the Page.Load event of my index.aspx:
Membership.CreateUser("fred124243", "Passw0rd$123")
I get the aforementioned error when I run the solution. I can see that my collection gets created, so the solution is communicating with MongoDB.
Any help greatly appreciated!
Answering my own question... I had to download MongoDB.Web source from Git and recompile.
I'm using VS 2012 (Ultimate) together with Entity Framework Power Tools Beta 2 and entity framework 5.0 (using nuget).
I've created a DbContext class. When I right-click on the corresponding file in the solution explorer and select "Entity Framework / View Entity Data Model (Read-only)", I get the error "A constructible type deriving from DbContext could not be found in the selected file." error in VS 2012.
I tried the workaround described at http://blogs.msdn.com/b/adonet/archive/2012/04/09/ef-power-tools-beta-2-available.aspx, but my registry does not contain the key "{BFC24BF4-B994-4757-BCDC-1D5D2768BF29}" in "HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config\BindingPaths\".
After restarting visual studio and following the same steps, a dialog pops up indicating "Exception has been thrown by the target of an invocation".
BTW. I'm able to execute my test application that creates the database from my DbContext and O can insert/delete/etc data in this database.
Any help/hints would be very appreciated.
Kind regards,
Merijn
Uninstalling VSCommands for Visual Studio 2012 should get things working again. Unfortunately, this extension does not play nicely with the EF Power Tools. It loads it's own version of EntityFramework.dll into the main VS process which prevents the DbContext discovery logic from working properly.
As mentioned by Brice, this may be caused by compatibility issue with Visual Studio Extensions.
Latest version of VSCommands fixes this problem. You can get if from Visual Studio Gallery.
Many thanks to Brice and EF Team for their help in diagnosing the problem!
Having seen this error intermittently even without the extensions listed in the other answers, I found deleting the solution's local .suo file worked - although this was very much a when-all-else-fails answer!
I had a similar issue with a different Visual Studio Extension. In my case it was Visual Studio Tools for Git (Version 1.0.0.0).
I just disabled the extension, restarted VS2012 and I was able to use generate the model from a code first EF project.