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 :(
Related
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.
Eariler, We had our solution built with visual studio 2010 and we had .vdproj file for creating the build and it was working fine perfectly.(setup is installed and works as expected).
But recently, we have upgraded our solution to visual 2017. We did the migration successfully but for build or setup .vdproj was not working fine as we were not able to open .vdproj in visual studio 2017. So, I just googled around & found out the following solutions:
Install visual studio installer plugin in 2017
User InstalledShield Limited editions
We have gone with first option. We just installed that plugin. Post this, We are able to open that existed visual studio 2010 .vdproj in visual studio 2017. It got migrated without any error. We had custom actions(primary output) in the project, we just re-added them. *.vdproject gets complied successfully and generates .msi file
But while installing it by command line or explicit(double click the .msi). We get following error:
Error 1001. Error 1001. InstallUtilLib.dll: Unknown error.
DEBUG: Error 2769: Custom Action _71938623_DFF8_4B88_8552_77D8706A0C48.install did not close 1 MSIHANDLEs.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769.
The arguments are: _71938623_DFF8_4B88_8552_77D8706A0C48.install, 1,
CustomAction _71938623_DFF8_4B88_8552_77D8706A0C48.install returned actual error code 1603
(note this may not be 100% accurate if translation happened inside sandbox)
After googling a bit about this, We found couple of suggestion such as adding or removing slash in arguments using command line installation.
But even though we are doing explicit installation(by double clicking the setup file) still we get the above mentioned error.
In case, We remove the custom action from project installation, then msi gets installed successfully. So, we don't know what is the problem with those custom actions.
We tried of debugging custom action by using Debugger.Launch(). But installer doesn't reach that portion. Prior to that we get above mentioned exception.
Don't know what to do.
We are scratching our head. Any suggestion or help would be really appreciated.
Could it be because of .net framework installed. we have installed .NET 4.6.1 too.
I am using VS 2013 and SQL SERVER 2014 and I am trying to use entity framework to connect to the DB from VS 2013. I am getting test connection succeeded when adding the Entity data model but getting the above error.
Error :Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=11.0.0.0'
System cannot find the file specified
I tried so many solution, I re-installed SQLSysClrTypes.msi,
SharedManagementObjects.msi, DB2OLEDBV5_x64.msi and vcredist_x64.exe to resolve this ; but it did n't works.
Could any one please suggest me solution?
Thanks,
Saloni
Just to stamp as the answer, let me rewrite in the answer block from my comments.
Install the right Microsoft.SqlServer.Management.Sdk.Sfc version 11's SharedManagementObjects.msi from http://www.microsoft.com/en-us/download/details.aspx?id=35580, because it seems like the entity is using the previous SQL Server (2012).
Problem: (Sql server 2012) This issue happens when assembly Microsoft.SqlServer.management.sdk.sfc version 11.0.0.0 not found by visual studio.
Solution: just go to http://www.microsoft.com/en-us/download/details.aspx?id=35580 and download:
ENU\x64\SharedManagementObjects.msi for X64 OS or
ENU\x86\SharedManagementObjects.msi for X86 OS,
then install it, and restart visual studio.
I've run into an issue with an SSIS package in Visual Studio 2010 and 2012. When I try to open the package I get the following error:
"Microsoft Visual Studio is unable to load this document
Exception from HRESULT: 0xC0010009"
No other information is provided. I have multiple SSIS packages in the solution and the others open. This package opened until I checked it into TFS and then it broke. Any ideas where I could get more information on the error? Or how to solve it?
Don't know if this is related, but thought I'd throw it out there.
Using SSIS Version 12.0.21005.1 REL, I received the same error and was able to solve it by editing the .dtsx with a good xml editor (hat tip to notepad++).
Basically, ensure it is well formed and all references agree. For example, in a simple ETL package with OLE DB Source, Transformation, and Output steps in a DataFlow, I found 24 references to each column involved. For one column, one reference somehow disagreed with the other 23 (it ended up being misspelled; not sure how that happened). Fixing that solved the error.
Hope that helps.
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...