I have Visual Studio 2019 installed with Data Tools. I'm able to execute dtsx package from Visual Studio and execute (Both from run button and right click the file from solution explorer and click execute).
However, I want to simplify how its run, my SSIS package is using a project connection, actually, I'm using more than 1 OLEDB & FTP connection and I want to run it using command prompt, since its project connection, I got error no connection on the cmd.
Can someone help me with this matter, so I can run the package using cmd.
Thanks
Related
When I run the SSIS package via SSMS (right click on package and execute) on the client machine, then I get permission errors at the step where it tries to read an excel file on a shared path. I have full permissions on the shared path.
However, when I run the SSIS package via SSMS (right click on package and execute) on the SQL Server machine, then it runs OK.
What could be possible issues?
Probably something with authentication method in your SSIS package connection. If you created the package in server machine and have it as Window Authentication then you can only run it on SQL server machine.
I am trying to automate SSIS package deployment with only SSDT on my source computer. When I start the ISDeploymentWizard from SSDT for VS 2013 I can successfully deploy packages to a VM that I am running, but when I try to launch from the command line it fails with the following error:
To launch the Integration Services Deployment wizard, one of the Integration Services,
Management Tools - Basic or SQL Server Data Tools has to be installed by the
%SQL_PRODUCT_SHORT_NAME% Standard, Enterprise, Developer, or Evaluation Edition. To install
a component, run SQL Server Setup and select the component name.
I have SQL Server Data Tools for Visual Studio 2013 installed so I do not understand why I am receiving this error. The VM that I am running is a Windows Server 2012 R2 and has SQL 2014 installed on it. When I run the wizard from the command line on the VM it appears to work properly.
Has anyone run into the same issue? Any ideas on how to solve it?
Thanks!
edit 1: To get the package to deploy via SSDT I must launch SSDT using the "runas" command and run as the user on the VM.
Can you try running the command prompt as 'Run as Administrator'?
I solved the issue by updating my SSDT through Visual Studio 2015 extensions and updates panel.
I am having trouble implementing the execution of a SSIS package via the command line utility dtexec. I am implementing this process on a SQL 2012 server
(64 bit) with Integration Services and Business Intelligence Development Studio (VS).
The package is taking in some log files, manipulating them a little and then exporting them to excel. (I have forced 32 bit execution enabled
It runs fine on the server when ran in visual studio or manually by clicking on the package.dtsx file and executing manually.
When I run via dtexec and command line, I get an ACE.OLEDB.12 is not registered error.
screen capture of error
This doesn't make sense to me because I know that I have the driver installed, and it runs manually on the same server with the same package settings.
I have been searching with little success for the past two days, Any help would be appreciated!
The error occurs because the command line calls the 64-bit DTExec utility which makes the package run in 64-bit runtime mode, however, only 32-bit Microsoft ACE 12.0 OLE DB drivers are installed. In BIDS, the package runs in 32-bit runtime mode (the Run64BitRuntime property of the IS project should be set to False), therefore, the package can execute successfully. To address this issue, you can specify the 32-bit DTExec.exe utility in the command line like:
"C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\DTExec.exe" /f yourPackagePath
I'm working on a Data Mart loading package in SSIS 2012. When attempting to execute the package in Visual Studio I get this error:
"The AcquireConnection method call to the connection manager Data
Warehouse.ssusr failed with error code 0xC0014009".
When I test the connectivity of the Connection Manager Data Warehouse.ssusr I see that it passes.
When I execute the package outside of Visual Studio using the Execute Package Utility, the package runs.
I don't understand what's going on.
The package also refuses to run using the SQL Server Job Schedule, if that has anything to do with anything.
Making some assumptions here, but I'm going to assume that this is a 32 vs 64 bit issue. To verify, try these two commands from a command prompt (Windows Key, R, cmd.exe or Start, Run, cmd.exe)
"C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\dtexec.exe" /file C:\myPackage.dtsx
"C:\Program Files\Microsoft SQL Server\110\DTS\Binn\dtexec.exe" /file C:\myPackage.dtsx
The first will run your package in 32 bit mode whilst the second runs it in 64 bit mode. This is going to matter as your drivers and any DSNs you've created are going to only be visible in the 32/64 bit world.
Fixing SSDT
Once you've identified which one you need, probably 32 bit version, you'd need to ensure your project is using the appropriate run-time. Right click on your project and select Properties and then navigate to the Debugging tab under the Configuration Properties.
After inverting the Run64BitRuntime value, I assume your package will work from within SSDT.
Fixing SQL Agent
You will need to edit the existing SQL Agent job to change the bittedness of the job step. This will be under the Configuration tab and then under the Advanced tab. Check/Uncheck the 32-bit runtime.
Lies and deception
Observant folks may see that the dtexec offers a /X86 option. Don't believe it. The only way to get the correct bit-ness is to explicitly call the correct dtexec.exe The documentation even says as much but nobody reads documentation.
This option is only used by SQL Server Agent. This option is ignored
if you run the dtexec utility at the command prompt.
I recently had some problems with my VS 2008, and was recommended to reinstall. To make sure that the reinstall would solve my problems, i manually uninstalled everything that could have to do with VS and SQL Server (I had the 2008 Express edition installed).
Now when I reinstall SQL Server and Visual Studio, the Server Explorer in VS is dead. When I click the menu option "View\Server Explorer", I get an error message in the Output window reading:
The Visual Studio Explorers and Designers Package ({8D8529D3-625D-4496-8354-3DAD630ECC1B}) did not load because of previous errors. For assistance, contact the package vendor. To attempt to load this package again, type 'devenv /resetskippkgs' at the command prompt.
I run the suggested command, but when I try again I get the exact same error message.
How do I solve this? As I work with the Entity Framework, it is crucial that VS can connect to my database... Any help is very much appreciated!
After looking back and forth over the internet, coming across a lot of different answers, i finally managed to get this working. This was my solution:
Close all open instances of Visual Studio.
Open the Command Prompt in an Administrator context by navigating to Start\All Programs\Accessories, right-clicking Command Prompt and choosing Run as Administrator.
Navigate to the install path of VS2008 - in my case (default on Vista x64) it was **C:\Program Files (x86)\Microsoft Visual Studio 2008 9.0\Common7\IDE**
Run the command devenv /setup. It takes a little while, but be patient.
Start Visual Studio.
After following these steps, the setup is reset to default, so you'll have to reconfigure all startup options, fonts for the text editors etc. This could possibly be helped by running devenv /resetskippkgs instead, however it did not on my machine.
I've had this issue with Visual Studio 2008 as well. Running the devenv commandline statements did not help me though. I basically had to live with it until Visual Studio 2008 Service Pack 1 came out. Since installing Service Pack 1, I haven't had any problems with the Server Explorer.
Run "devenv /setup" as described above. Now, start Visual Studio without opening any solution or project file. If Server Explorer opens at this point, delete all Data Connections and Servers from there. Now, exit and restart Visual Studio. Then, open the solution or project file and the error be gone. This worked for me.