SSIS: Error when executing a Execute Package Task - sql-server

I have a project where I have 1 master package and several child packages which I call in the master.
However when I launch the master package it goes into error on one "Execute Package Task"
See below for the ouput from the Output-Window:
Information: 0x40016042 at build_NAV_sources: The package is attempting to configure from the parent variable "var_actual_timestamp".
.
.--more variables configuration
.
Information: 0x40016042 at build_NAV_sources: The package is attempting to configure from the parent variable "var_table_prefix".
Error: 0xC00220E0 at Execute Package Read Dim norriq data to sources: The connection is not specified.
Error: 0xC0024107 at Execute Package Read Dim norriq data to sources: There were errors during task validation.
Error: 0xC00220E4 at Execute Package build nav sources: Error 0xC0012050 while preparing to load the package. Package failed validation from the ExecutePackage task. The package cannot run.
.
Task failed: Execute Package build nav sources
SSIS package "F:\Workspaces\KPA\TFS\Norriq\BI\SQL 2012\NAV 2015\SSIS\NAV Datamart\build_NAV_datamart_master.dtsx" finished: Success.
When I check the package where it indicates that the connection is not specified I clearly see that there is an connection specified. In my connection manager I see the connection and when I edit this one and check for connectivity everything works fine.
To make it weirder: When I launch the package (build_NAV_sources) seperatly, it executes without any errors or warnings
Anyone has a clue on whats happening?
Thx

Without changing anything important, I've checked-in my solution in TFS, closed VS, opened the solution again and did a build/rebuild and it worked magically.

Related

Run ssis package in agent job while both are on separate machines

I am trying to run ssis package through agent jobs. The packages and the sql server are on different machines.
When the agent job tries to run ssis package step the job fails with following error:
Executed as user: Domain\username. Microsoft (R) SQL
Server Execute Package Utility Version 13.0.5026.0 for 64-bit
Copyright (C) 2016 Microsoft. All rights reserved. Started:
1:42:42 AM Error: 2020-01-23 01:42:42.49 Code: 0xC0011007
Source: {07BB41B6-D0DF-4349-B9AE-498397D214D7} Description:
Unable to load the package as XML because of package does not have a
valid XML format. A specific XML parser error will be posted. End
Error Error: 2020-01-23 01:42:42.49 Code: 0xC0011002 Source:
{07BB41B6-D0DF-4349-B9AE-498397D214D7} Description: Failed to
open package file
"D:\ssis_packages\package.dtsx"
due to error 0x80070003 "The system cannot find the path specified.".
This occurs when loading a package and the file cannot be opened or
loaded correctly into the XML document. This can be the result of
specifying an incorrect file name when calling LoadPackage or the
specified XML file has an incorrect format. End Error Could not load
package
"D:\ssis_packages\package.dtsx"
because of error 0xC0011002. Description: Failed to open package file
"D:\ssis_packages\CoreLogic\CoreLogicSSIS\Real_Estate_Monthly.dtsx"
due to error 0x80070003 "The system cannot find the path specified.".
This occurs when loading a package and the file cannot be opened or
loaded correctly into the XML document. This can be the result of
specifying an incorrect file name when calling LoadPackage or the
specified XML file has an incorrect format. Source:
{07BB41B6-D0DF-4349-B9AE-498397D214D7} Started: 1:42:42 AM
Finished: 1:42:42 AM Elapsed: 0.047 seconds. The package could not
be found. The step failed.
I need some suggestion as what is the best way to run ssis package when sql server and packages are on different machines.
There can be below defined reasons and solutions.
1. The error says it cannot find the package. Just double-check if this is the correct path for your package:
D:\ssis_packages\CoreLogic\CoreLogicSSIS\Real_Estate_Monthly.dtsx
2. It looks like a local path, so if indeed your package is on the D: Drive of another server make sure to add the server name in front of the path:
//server-name/ d$/
ssis_packages\CoreLogic\CoreLogicSSIS\Real_Estate_Monthly.dtsx
3. Grant the account running your SQL Agent job (I am guessing it's the SQL Agent account, but you should double-check that) access rights to the folder where your SSIS package is stored.
4. If the above did not solve the issue, also check if the SSIS package and your SSIS installation on the server where you are running it are the same. Running a 32bit SSIS package on a 64-bit system/SSIS will result in a similar error message.

Executing SSIS package gives System.IO.IOException

I am trying to execute the package and every time I see the following error. Especially when I execute the data flow task.
Error :
System.IO.IOException: The process cannot access the file
'C:\PPE_OVERRIDES.ispac' because it is being used by another process.
Full Output:
------ Build started: Project: PPE_OVERRIDES, Configuration: Development ------
Build started: SQL Server Integration Services project: Incremental ...
Starting project consistency check ...
Project consistency check completed. The project is consistent.
Error : System.IO.IOException: The process cannot access the file
'C:\PPE_OVERRIDES.ispac' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalDelete(String path, Boolean checkHost)
at System.IO.File.Delete(String path)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.IncrementalBuildThroughObj(IOutputWindow outputWindow)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.BuildIncremental(IOutputWindow outputWindow)
Build complete -- 1 errors, 0 warnings
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========
How can I fix it. My ispac file is in bin folder. I want to make sure the SsISDB catalog and Visual Studio are not fighting over this location
Based on the following article:
Fix SSIS Error while execution: System.IO.IOException: The process cannot access the file ‘PATH\Project.ispac’ because it is being used by another process.
Possible Solution:
Need to kill the Windows processes (SSIS Debug Host, and SSIS Debug Host (32 bit)) related to SSIS Debug and restart Visaul Studio to address the problem.
Similar Issue links
The process cannot access the file 'ssisproject.ispac' because it is being used by another process.
SSIS: The process cannot access the file ‘*.ispac’ because it is being used by another process
SIS: The process cannot access the file ‘*.ispac’ because it is being used by another process
Every time you start up an instance of SQL Server Manager, you have to go kill the SSIS Debug Host processes. However, I don't think they showed up until I tried to re-execute a package. I might try executing an empty, dummy package, fix the crash, then try again with the real package.

SSIS package failed when executed through agent

While searching for the solution, I have followed this link.
I have executed the package successfully with EXEC [SSISDB].[catalog].[create_execution]. Instead of either true or false for #use32bitruntime this command is executing well.
But if a server agent job is created with the same package, showing the below error.
The AcquireConnection method
call to the connection manager ODBCManger failed with
error code 0xC0014009. There may be error messages
posted before this with more information on why the
AcquireConnection method call failed.
How to solve this . . .

Could not load package "\File System\ because of error 0x80070002. Description: Unable to find the specified file. Source: MsDtsSrvr

We are building a new environment having SQL server 2014 and migrating our SSIS job to the new environment.
We have a SSIS job named as ABCD (assume)
The job is deployed as file system deployment:
C:\Program Files\Microsoft SQL Server\90\DTS\Packages\ABCD\ABCD.dtsx
While executing, It gives an error as
Could not load package "\File System\ABCD\ABCD because of error 0x80070002. Description: Unable to find the specified file. Source: MsDtsSrvr
Please suggest how to solve this issue, Also as the environment is controlled I am unable to try changes

R Missing Package error when uploading to shinyapps.io

My Shiny program works fine locally on my PC (Windows 8, RStudio 0.99.489) but not when I upload it to shinyapps.io . I've tried 2 ways of packaging the data for upload - saveRDS on each object and save.image on the entire environment. Either way, when I upload it to shiny.io I get:
Preparing to deploy application...DONE
Uploading bundle for application: 77966...DONE
Deploying bundle: 350891 for application: 77966 ...
Waiting for task: 132618597
building: Parsing manifest
building: Building image: 344796
building: Installing packages
################################ Begin Task Log ################################
[2016-01-16T22:19:45.818533554+0000] Installing R package: magrittr (1.5)
Error in library(stylo) : there is no package called �stylo�
Execution halted
################################# End Task Log #################################
Error: Unhandled Exception: Child Task 132618599 failed: Error building image: Build exited with non-zero status: 1
Execution halted
It seems that Shiny isn't aware of the Stylo package. I tried to install it in my code, but that didn't help.
1. Does Shiny have all R packages?
2. If not, is there a list of which packages are available?
Thanks very much.
Are you including the stylo package at the top of your server.R file via library("stylo")? If you are doing that and it's giving you the error, try using require("stylo") instead.
From the docs, the rsconnect package is supposed to automatically detect what packages are necessary for your app. Probably worth a read (if you haven't already) just to be sure you're following everything correctly in order for rsconnect to do its job.
I solved the problem by doing a clean build of my environment -- imported data tables and functions from RDS files only, and carefully avoided references to unnecessary packages. I recreated the one function I needed from Stylo locally, so that I could be certain I wouldn't require it.

Resources