IDE : VS Studio 2017
DB : Oracle SQL
I keep on having this kind of error
Things I do resolving this but nothing helps me w/ my issue :
I already add the latest version (140.1000.523) of Microsoft.ReportingServices.ReportViewerControl.WebForms
I also tried to find the TargetServerVersion but seems only applicable to those who use Report Server Project and I'm not using it (The right-click properties then change TargetServerVersion to "SQL Server 2008 or later"
I also change my ...reporting/2016/01/reportdefinition into ...reporting/2008/01/reportdefinition at xmlns and this not recommended since I keep on adjusting it in back-end whenever I change something in report.
Related
I've installed the extension Microsoft RDLC Report Designer in Visual Studio 2017 in order to modify my .rdlc files that were created with an older RDL scheme 2008.
The problem is that the designer is changing the scheme to version 2016 and when I try to run my report I'm getting the next error:
The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas. Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition' which cannot be upgraded.
As a first solution, I had to change manually the report adapting the changes to the old format(2008) but it's pretty annoying doing it all time.
Could you recommend me another kind of solution?
Thanks!
This is pretty anoying. I've discovered another workaround, this way i dont need to update the xml to the old format everytime, give it a try:
https://stackoverflow.com/a/61072633/9026516
Just installed ODAC for Visual Studio 2017 version 19.3 from here: https://www.oracle.com/database/technologies/dotnet-odacmsi-vs2017-downloads.html to replace ODT for Visual Studio 2017 NuGet Package. Then I noticed my Oracle NuGet packages were gone in my VS solution, and I had to re-add them. But this time I used Oracle.ManagedDataAccess 19.3 (previously had used 12.2.1100), and Oracle.ManagedDataAccess.EntityFramework 19.3 (previously used 12.2.1100).
Now my EDMX gets an error when I try to open it: "Error 168: The provider did not return a ProviderManifest instance. The type initializer for 'OracleInternal.Common.ProviderConfig' threw an exception."
I found an interesting answer by Mitaka here: Entity Framework: The provider did not return a providermanifest instance, so I opened my EDMX with XML Text Editor and found my ProviderManifestToken="12.1". So just for grins, I tried "19.3" and "19.1" but neither worked.
Anybody know the magic value? I'm just hoping that is how to solve the error. Thanks.
Got it. "18.0"
It actually updated itself after I got a bunch of other kinks worked out including "There is a duplicate 'oracle.manageddataaccess.client' section defined." Turns out the definition for Oracle.ManagedDataAccess was in my WebAPI web.config and also the machine config. Had to update THIS specific machine.config:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config - do a search on "managed" and comment out in 3 places.
Then it let me create a connection in Visual Studio 2017 Server Explorer and open the EDMX. Finally the EDMX update wizard is no longer aborting on the Data Connection screen. Back in business.
I create an SSIS package with VS 2013 SSDT-bi, I try to create a job in SQL Server 2012:
I add my package under Integration Services Catalogs, when I want to validate it says :
Package error : Pacakge migration from version 8 to version 6 failed with error 0xC001700A
The version number in the package is not valid. the version number cannot be greater than current version number
And when I try to create a new job it says :
The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
I Googled and I found that VS 2013 SSDT-bi starts working with SQL Server 2014.
I want to know if there is a workaround for my issue or I have to download VS2012 and re-create my package ?
I did succeed in tricking it to work (changing the project/package XML). However, i would never recommend that, since it's gonna stop working at some point and give you further headaches.
Download VS 2012 SSDT (you'll probably need VS2012 shell as well), open packages there and redeploy.
EDIT: spelling :(
Just installed WebMatrix and upgraded Visual Studio 2012 to Version 4.5.50709 SP1Rel. Now when I open my webapplication I get a bunch of errors of this type:
'IIf' is not declared. It may be inaccessible due to its protection level.
'IsNothing' is not declared. It may be inaccessible due to its protection level.
'IsNumeric' is not declared. It may be inaccessible due to its protection level.
I get so many errors that I even get this:
Error 104 Maximum number of errors has been exceeded.
It turned out that during WebMatrix installation or Visual Studio upgrade MySql Connector version 6.5.4.0 was also installed.
Somehow MySql Connector v. 5.1.5, which my project were referring was uninstalled in the process.
Reinstalling MySql connector 5.1.5 solved the issue. Changing the reference to the new MySql connector would probably also solve the issue.
I just ran into the same problem in VS 2012 when attempting to copy over an old version of a program I received from another colleague.
As muleskinner says, it is not a reference issue to Microsoft.VisualBasic...
When you try to add that as a reference it will tell you that it is already automatically referenced by the build system.
It turns out that even though Microsoft.VisualBasic is automatically referenced, the project didn't actually have the namespace imported.
You can add it by going to the properties of your project -> References -> And then make sure that Microsoft.VisualBasic is checked in the list of namespaces at the bottom.
At least that worked for me and cleared up all my errors. Wasn't relishing trying to change all my IIf statements into the more traditional format...
I have a solution with a SQL CLR project in VS2008. The solution / project was converted to VS2010 and now the deploy no longer works.
I get the following type of erros:
Beginning deployment of assembly MyProjectDatabaseCode.dll to server DEVPN-004 : MyProject
The following error might appear if you deploy a SQL CLR project that was built for a version of the .NET Framework that is incompatible with the target instance of SQL Server: "Deploy error SQL01268: CREATE ASSEMBLY for assembly failed because assembly failed verification". To resolve this issue, open the properties for the project, and change the .NET Framework version.
C:\inetpub\wwwroot\VS2010_MyProjectSolution\DatabaseCode\bin\Release\MyProjectDatabaseCode.dll : Deploy error : Plan verification encountered errors; deployment cannot continue.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\TeamData\Microsoft.Data.Schema.SqlClr.targets(96,5): Deploy error TSD00561: This deployment may encounter errors during execution because changes to [dbo].[Column1] are blocked by [dbo].[Table1].[Column1]'s dependency in the target database.
I verified and the project is targeted against .NET 3.5. We have predeployscript.sql and postdeployscript.sql files that are supposed to be run. It appears like they are not being run by VS2010. What could be causing the issue?
We ended up contacting Microsoft and they reproduced our issue as a known bug. They offered a workaround by retargeting the assembly to .NET 2.0, but that didn't work in our scenario either.
It seems that the only way forward until the fix is to create a brand new SQL CLR project in 2010 and add all the files to it by hand.
I'd recommend using Reflector to take a look at your assembly in the build output directory. If you see 2 references to mscorlib, then what has happened is that a phantom reference to the 4.0 framework has been added to the project. If you see this problem, you may be able to get rid of the 4.0 reference by hand editing your project file. Open the project in an XML editor, and look for the following line:
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="2.0">
Change ToolsVersion="2.0" to ToolsVersion="4.0"
This helped me with a similar upgrade problem, but your mileage may vary. If you don't see the phantom mscorlib reference, you probably have another issue.
I've seem this problem consistently when I renamed some objects or somehow the target database got out of sync, that is, some objects were not dropped and Deploy was trying to recreate them.
I managed to fix it by running a cleanup script (drop objects/assemblies) from MS Server Management Studio and verifying that no old objects remained in the Database.
It's a try/error experience but you can try first to deploy to another server/database and if it succeeds, chances are you have some garbage in the target database, that's how I came to the conclusion for I was able to deploy to another database.