I am migrating some scheduled tasks from one Server 2008 R2 64 bit to another. One task is failing on the new server with the error
"Reason for failure: System.Exception: Cannot create ActiveX component.
at Microsoft.VisualBasic.Interaction.CreateObject(String ProgId, String ServerName)".
That task fails ONLY when run from the task scheduler, and not when run from the command line. I have added the folder C:\Windows\SysWOW64\config\systemprofile\Desktop, and the user running the task is a local administrator.
Excel is installed on the server - the program is manipulating a spreadsheet.
Any suggestions will be much appreciated, thank you!
Dan
Related
I have configured a machine with windows server 2016 and pentaho CE 7.0
I have already developed several Jobs and Transformations with their respective .BAT.
My problem occurs when I run the Jobs from the Windows Task Scheduler, which indicates the following error in the log:
Error opening new file 2020/07/08 13:43:36 - Microsoft Excel Writer.0
ERROR (version 7.0.0.0-25, build 1 from 2016-11-05 15.35.36 by buildguy) : java.io.IOException: Error creating output file! Parent
directory [file:///W:/Prueba] does not exist.
I already confirmed that the route exists and the most frustrating thing is that if I run the .BAT with a double click I get to the route.
Check for permissions ! it seems probably your script dont have correct permission to write in that folder.
I have an SSIS job that contains a script task.
There is also a connection to another server within the package that can only be executed accessed by a specific user and the agent cannot be given read rights to the other server.
So the solution to this is have the SQL job be run as the required user.
The problem with this is this user does not have full control over the folder/file where the script task will be temporarily located while the code runs so I get a failure on the script task but if I run it in visual studio or with the normal agent account the script task executes successfully.
I have tried giving the user access to all major drives on the server but this has not solved the problem
Is the script doing something on the folder?
Or does it just need permission to execute script?
I would anyway advise you to implement error handling in script:
https://learn.microsoft.com/en-us/sql/integration-services/extending-packages-scripting/task/logging-in-the-script-task?view=sql-server-2017
Make sure it works in visual studio, so that when you get that error you are sure that the error is caused by permissions/environment.
You could also take a look at this article:
article
I am using SQL Server 2014 and I have created an SSIS package in SSMS using the Import Data Wizard.
The package imports a table from the database of a linked server and creates a copy on the main database. The SSMS wizard executed all the steps correctly and during one of the steps, I saved the settings as an SSIS package in the File System.
I then created a SQL Server Agent job to execute the package on a daily basis. The job failed to execute with the following error message:
(Import Data into PickUp Table).,00:00:01,0,0,,,,0
06/20/2018 17:18:00,PickUp Table,Error,2,XXXX\XXXXXX,PickUp Table,Import Data into PickUp Table,,Executed as user: XXXXXX\sql_bisvcs. Microsoft (R) SQL Server Execute Package Utility Version 12.0.5000.0 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.
Started: 5:18:01 PM
Error: 2018-06-20 17:18:01.16
Code: 0xC0010018
Source: PickUp
Description: Error loading value "
End
Error
Could not load package "C:\Users\Administrator\Documents\Visual Studio 2013\projects\PickUp\PickUp.dtsx" because of error 0xC0010014. Description: 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.
Source: PickUp
Started: 5:18:01 PM Finished: 5:18:01 PM Elapsed: 0.157 seconds.
The package could not be loaded. The step failed.
I tried to open the package in SSDT, but it failed giving me the same error messages as mentioned above.
What might be causing this error?
You can have a look at the value of Run64BitRuntime debug parameter and try different value True or False.
Depending of your environment, some DLL of third party software can be in conflict.
Also, if your SQL Server instance is on an other server than the computer on wich you want to run the job, you may not be able to execute the package with features you have not installed on this machine.
SSDT, Connector to each remote database / file etc..
Have a look at your SSDT version, if the package is generated via SSMS, it can have a version wich is not recognize by your local machine.
I have a 2008 SSIS package that have a lot of steps, one of the steps is a script task that runs a stored procedure. It is not an option for now to change it from a script task, as it would require a lot of extra developing. The procedure runs fine in the production environment, but I need to be able to test it from VS.
The reason for the failure I have found is that the connection to the target database is not working, it is giving error "Login failed for user 'user'".
The SSIS package is built on a SSIS framework, and it has a "Initialize Connections" task as an Event in the "Initialize" part of the package. I do not know much about what this does. I want to just run the Data Flow (With "Execute task" option inside the Data Flow).
In the ProtectionLevel for the package I have tried both DontSaveSensitive and EncryptSensitiveWithPassword without any luck. I manually insert the password in the Connection Manager.
I read some about the need to use a connection manager/XML file, but I'm unsure of how this can be done. (Not done much SSIS before).
Please explain how this debugging in VS should be done.
I created an SSIS package, which runs fine in Sql Server Business Intelligence. The problem is when I try to schedule a job to run, I tested it and it says the exe does not exist in the directory and it lists the path to the directory where the exe is located. The exe is obviously there, and the exe runs fine, it just doesn't like the package when I try to schedule a job.
The error that I can see in the job activity monitor is
Description: File/Process "FileName.exe" does not exist in the directory "DirectoryName" End Error
Anybody know how to fix this?
An SSIS package is not an EXE. The name is typically something like 'MyPackageName.dtsx'. The package is interpreted & executed by the DTS utility running in conjunction with a SQL Server instance.
We use SQL Agent to run SSIS packages as a standard part of our application, so that itself shouldn't be a problem. How do you have your SQL Agent job defined?