SSIS Package logging error - SSIS
-
We are using project deployment model for SSIS. For one of the packages, which writes the log to a UNC path, I get the error when running the package from SSMS remotely. But when I execute the package from the db server(SSIS Catalog), there are no errors.
ERROR: "Exception has been thrown by the target of an invocation"
Please advise of any suggestions.
Many thanks
-
it will be a permission thing most likely related to the service account. If you right click the package in the catalogue and click reports > standard reports > all executions you will see the error and this may help you find the problem.
I experienced the some problem at a previous site. I am having a similar problem now. The package runs but not via job agent. The thing that is different is the caller.
When you fix your problem post the solution.
-
SQL!$@w$0ME (4/22/2016)
We are using project deployment model for SSIS. For one of the packages, which writes the log to a UNC path, I get the error when running the package from SSMS remotely. But when I execute the package from the db server(SSIS Catalog), there are no errors.ERROR: "Exception has been thrown by the target of an invocation"
Please advise of any suggestions.
Many thanks
As you are using project deployment, SSISDB should take care of your logging natively. Or are you doing some additional logging not handled by SSISDB?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
-
Not sure what will be issue the service account permission. When I run from ssis catalog from the server, it's running fine.
What are the required permissions for service account/proxy on integration services (dcomconfig)?
-
The log file is updated on the remote share which includes the number of records updated on that run.
-
OK, understood. But don't forget that tables in SQL Server are pretty good at storing info like that 😀
Do you connect to the SQL instance using Windows Authentication?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
-
Yes Phil, Using Windows authentication. Also as part of the package a report file(excel) is created on the shared folder. All other packages runs fine when executed from remote client/SSMS.
-
SQL!$@w$0ME (4/22/2016)
Yes Phil, Using Windows authentication. Also as part of the package a report file(excel) is created on the shared folder. All other packages runs fine when executed from remote client/SSMS.In SSMS, find the Integration Services Catalogs node in the Object Explorer and drill down to the package which is causing the error.
Right click on it and select
Reports / Standard Reports / All Executions
which will display a list of attempts to run the package. Find a run which failed and drill into that, selecting the All Messages hyperlink.
I am hoping that this will provide more details about the error.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
-
Error Context summary:
CreationNameMicrosoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask, Microsoft.SqlServer.ScriptTask, Version=12.0.0.0, Culture=neutral, PublicKeyToken=34123rfg8080yy89
DebugModeFalse
DefaultActiveItemScriptMain.cs
DelayValidationFalse
DescriptionScript Task
DisableFalse
DisableEventHandlersFalse
EntryPointMain
ExecutionDuration0
ExecutionResult0
ExecutionStatus3
FailPackageOnFailureFalse
FailParentOnFailureFalse
ForcedExecutionValue0
ForceExecutionResult-1
ForceExecutionValueFalse
IsDefaultLocaleIDTrue
ProjectTemplatePathC:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\IS_ST_CS_Template.vstax
ReadOnlyVariablesSystem::TaskName,User::Task_id,System::PackageName,User::UNC_FILE_PATH
ScriptLanguageMicrosoft Visual C# 2012
ScriptLoadedTrue
SuspendRequiredFalse
TransactionOption1
Version0
-
If you look under All Messages, you should see something more like this:
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
-
Please see the error.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply