I am trying to add a SQL Server Data Source to a Web Test in VS2017:
I click Install packages and get this:
Missing option value: installpath
How do I overcome this problem?
Edit 1:
Using Process Monitor I have identified the command VS2017 runs:
"C:\program files (x86)\microsoft visual studio\installer\vs_installer.exe" modify --focusedUi --installPath "" --activityId 6bb6d93d-8c2a-4462-9304-4ef2b29d27d1 --add Microsoft.VisualStudio.Component.SQL.DataSources --includeRecommended
The installPath is empty so I specified it as:
"C:\Program Files x86\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\"
When I specify the installPath I get this error:
System.ArgumentException: The directory path 'C:\Program Files x86\Microsoft Visual Studio\2017\Enterprise\Common7\IDE" --activityId 6bb6d93d-8c2a-4462-9304-4ef2b29d27d1 --add Microsoft.VisualStudio.Component.SQL.DataSources --includeRecommended' is invalid.
Parameter name: installationPath
I guessed since its trying to install a Package it must be:
"C:\Program Files x86\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\PACKAGES"
That results in this error:
Unsupported option includeRecommended /finalizeinstall
What is the correct command?
Edit 2:
Confirming I already have the DataSources for SQ Server support installed:
Edit 3:
Ok, this is my fault.
I run Visual Studio using a shortcut that uses a junction to avoid the brackets in the path C:\Program Files (x86) in order to connect to an Oracle 9.2 database.
Running Visual Studio (not from the shortcut) I see the dialog and can connect to the Database.
However, when I click OK, no data source is added to the WebTest.
This is just a typical day using VS2017. I swear this product has not been properly tested.
So I ran a Process Monitor trace when I clicked the OK button in the Data Connection Dialog and I found one Access Denied:
Event Class: Registry
Operation: RegCreateKey
Result: ACCESS DENIED
Path: \REGISTRY\A\{A8BB3990-53C7-4BD7-A7E3-CFA0DD6BD4EC}\Software\Microsoft\VisualStudio\15.0_8708a912\Data Connection Dialog
TID: 11800
Duration: 0.0000764
Desired Access: Read/Write
I opened Visual Studios own Registry Hive (using these steps) and it turns out the Data Connection Dialog key didn't even exist. I created the Key, closed the registry, re-opened VS2017 and added a DataSource successfully:
Related
I am trying to install SQL2019 Server.
comming This Error. cant Installation
TITLE: Microsoft SQL Server 2019 Setup
The following error has occurred:
PerfLib 2.0 counter removal failed with exit code 2. Command line:
C:\WINDOWS\system32\unlodctr.exe /m:hkengperfctr.xml from directory
C:\Program Files\Microsoft SQL Server\150\Shared.
• There is incomplete uninstallation of SQL server and we are not able to install in SQL server in your PC due to below errors.
• Database Engine services Failed
• PerfLib 2.0 counter removal failed with exit code 2.
• The MOF compiler could not connect with the WMI server.
• Below is troubleshooter link and search window
https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d
• Here, you have to download the troubleshooter in your PC
• After download, you have to run the file and you will get below window & click Next
• Choose based on issue, its related to Installation or Uninstallation
• Choose one by one all relevant SQL Server content and uninstall, it will repeat each time for one item. Once you have done with all SQL server content, then only uninstall successful. Now you have good to install and without any issue.
I am hoping that I can get some assistance with an error that I'm getting when trying to install the SQLServer2005_DTS.msi on Windows 10.
The error that I'm getting is:
'Module C:\Program Files\Microsoft SQL Server\80\Tools\Binn\dtsui.dll failed to register. HRESULT -2147024714. 'Contact your support personnel.'
I got the msi from
"Feature Pack for Microsoft SQL Server 2005 - February 2007" at https://www.microsoft.com/en-us/download/details.aspx?id=24793
It seems that the msi tries to to register the 4 dll's below but fails:
dtsui.dll
ctasksui.dll
cdwtskui.dll
sqlns.dll
I have also tried to manually register the dll's without any luck as follows:
Open a command prompt as admin
Change the directory to the Binn folder where the dll is located from the command prompt type cd C:\Program Files\Microsoft SQL Server\80\Tools\Binn
Register the dll, from the command prompt type: regsvr32 dtsui.dll
All I get is a return to the command prompt where I was expecting a dialog box.
SQL Server 2005 and some components are not compatible with Windows 10
https://technet.microsoft.com/en-us/library/ms143506(v=sql.90).aspx
What you can do it deploys a VM to use.
Its compatibility problem.Because its support till windows Vista.
Try to install in compatibility mode from properties option from run as administrator,
I am getting this error when trying to launch SQL Server Management Studio 2014.
Package VsDebugPresentationPackage did not load correctly.
And in error log:
SetSite failed for package [VsDebugPresentationPackage, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]
Any ideas?
If you run the SSMS with /Log you would be able to find an xml file named "ActivityLog.xml" here:
"C:\Users\\AppData\Roaming\Microsoft\AppEnv\10.0"
Going through that file you will find a line which is saying config files is not having the root element. If so, simply remove any sub folder of "C:\Users\\AppData\Local\Microsoft_Corporation". Then run SSMS with admin privilege and bingo...
This little solution took 1 day of my sprint...
I'm attempting to build a .sqlproj on a TFS Build Server. I've followed the instructions here:
http://sqlproj.com/index.php/2012/03/headless-msbuild-support-for-ssdt-sqlproj-projects/
which I was directed to from here:
How to build .sqlproj projects on a build server?
But I still cannot build. The error is:
C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets
(441): The "SqlModelResolutionTask" task could not be instantiated
from "C:\Program Files
(x86)\Common7\IDE\Extensions\Microsoft\SQLDB\Dac\120\Microsoft.Data.Tools.Schema.Tasks.Sql.11.dll".
System.TypeInitializationException: The type initializer for
'Microsoft.Data.Tools.Schema.Tasks.Sql.DataTask' threw an exception.
---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Data.Tools.Schema.Sql, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The
system cannot find the file specified. at
Microsoft.Data.Tools.Schema.Sql.Extensibility.ToolingShim.ConfigureExtensions()
--- End of inner exception stack trace --- at Microsoft.Data.Tools.Schema.Tasks.Sql.DataTask..ctor()
The SqlTasks.targets file, used by the SQL project, references this:
C:\Program Files (x86)\Common7\IDE\Extensions\Microsoft\SQLDB\Dac\120\Microsoft.Data.Tools.Schema.Tasks.Sql.11.dll
which in turn references the invalid version mentioned above.
However, the files installed by the process in the link above don't install this version. They do install version 10.3.0.0, which is referenced by
C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin\Microsoft.Data.Tools.Schema.Tasks.Sql.12.dll
but this file is not the one used by the .targets file.
I don't know what the numbers at the end of this dll mean, but it seems odd to me that the one ending 12.dll references an earlier version of the one ending 11.dll.
I'm using Visual Studio 2013 and SQL Server 2012 - neither of which are installed on the build server, which I believe is the recommended situation. I don't know what the IDE folder is, or why the .targets file is using it.
I've spent about two days now trying to get this to build, but I'm out of ideas. Anyone know what's going on?
If you are running VS2013 SSDT is built into VS as long as you select it on the install screen. Install VS2013 with SSDT onto your build server. create a build definition and under Process > Build > Advanced Add the following to the MSBuild arguments to build the sql proj
/t:Build
if you have a publish profile and want to test publishing to SQL then add the publish switch and provide the link to the profile file
/t:Publish /p:SqlPublishProfilePath=MyDB.publish.xml.
this will publish the db to the server specified in the publish file.
the publish profile file can be created by opening the project in Visual Studio, right click on the project and select publish. Select save once you are happy with the publish options and then check in the file to source control so the build can find it, (project Root).
I was having this issue building a SQL Server project on an Azure DevOps CI/CD pipeline. None of the pre-built build tasks would work for me. And it is not possible to install a VS instance on the build server, I guess.
I solved this by avoiding to add a SQL Server project to the solution.
I achieved this by using an MSBuild SDK, capable of producing a SQL Server Data-Tier Application package (.dacpac) from the set of SQL scripts. By adding this second project to the solution, I managed to continue taking advantage of linking the project to a live database through SQL Server Object Explorer on Visual Studio. I gave a more detailed explanation in this answer.
I am receiving the following error when trying to execute an SSIS package using Visual Studio 2012:
Error 39 Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: The
package failed to load due to error 0xC0011008 "Error loading from
XML. No further detailed error information can be specified for this
problem because no Events object was passed where detailed error
information can be stored.". This occurs when CPackage::LoadFromXML
fails. ---> System.Runtime.InteropServices.COMException: The package
failed to load due to error 0xC0011008 "Error loading from XML. No
further detailed error information can be specified for this problem
because no Events object was passed where detailed error information
can be stored.". This occurs when CPackage::LoadFromXML fails.
at
Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPackagePersist100.LoadPackageFromXML(Object
vSource, Boolean vbSourceIsLocation, IDTSEvents100 pEvents) at
Microsoft.SqlServer.Dts.Runtime.Package.LoadFromXML(String packageXml,
IDTSEvents events) --- End of inner exception stack trace ---
at Microsoft.SqlServer.Dts.Runtime.Package.LoadFromXML(String
packageXml, IDTSEvents events) at
Microsoft.SqlServer.Dts.Runtime.Project.LoadPackage(IProjectStorage
storage, Package package, String streamName, IDTSEvents events) at
Microsoft.SqlServer.Dts.Runtime.PackageItem.Load(IDTSEvents events)
at Microsoft.SqlServer.Dts.Runtime.PackageItem.get_Package() at
Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.IncrementalBuildThroughObj(IOutputWindow
outputWindow) at
Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.BuildIncremental(IOutputWindow
outputWindow)
0 0
The package is stored in TFS and I can open the package/solution without any errors. I just get the error when i try to excecute the package or any step in the package.
I created a new package on my machine (64 bit) and it worked fine. I'm just having trouble running the package when opening from TFS.
thanks
Scott
I resolved a very similar situation by changing the SQL Server sdk version that my solution was pointing.
I had SQL Server Express 2008 installed, and was using VS 2012 with BI Tools 2012. So, my solution was referencing the assembly Microsoft.SqlServer.ManagedDTS.dll version 10. For my case, the correct was the version 12.
I had this problem when trying to open an SSIS package which used a component which I did not have installed. In my case, it was the "Azure Feature Pack".
I had similar errors on a Win64, VS2013, SQL2012 system. The SSIS package did not load correctly.
Identify: I created a local copy of the whole package, and narrowed the problem with reduction to a single sub-package.
Reason: different date format.
Solution: I had to change the Windows date format to UK (source of the package), and since then everything is fine.
You have to copy the reference libraries to the Program Files directly as well.
I saw that in the (x86) path, the files were there, but not in the 64-bit folder of Program Files. I'm using Visual Studio 2010.
1 - C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Connections
2 - C:\Program Files\Microsoft SQL Server\110\DTS\Connections
The referenced DLL was found in location 1, but not in 2.
I closed Visual Studio, copied the DLL over to path 2, and opened VS again. The package just worked like normal.
I resolved a very similar situation by changing the TargetServerVersion in the project general configuration properties. I use Visual Studio 2015. By default SQL Server vNext was selected, whereas I have SQL Server 2012 installed.