Unable to execute SSIS package using SSIS task - VisualCron

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.

Welcome Guest! To enable all features please Login or Register.

JohnC
No customer Topic Starter

2010-03-29T18:02:38Z

I am testing VC 5.5.5 on a Windows 2008 server (32-bit) that has the SQL-Server 2008 client tools installed.

I am able to execute SSIS packages from the DOS command prompt and I am able to execute the same packages in VC if I use a "Process / Execute" task to call dtexec.

However, if I try to use the "Database / Execute SSIS package" to execute the same SSIS package, I get an error as follows:

Exception in Task: Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154

I tried searching on the forum here but didn't have much luck. Setting up this SSIS package as a job on SQL-Server and then using VC to execute the job is not an option.

What does this error indicate and how do I troubleshoot / resolve it?

Sponsor

Forum information

Wanna join the discussion?! Login to your Forum forum account or Register a new forum account

Support
Official support

2010-03-29T21:23:44Z

Hi John,

there seems to be an issue with 32/64 bit here. We will get back to you tomorrow after some testing.

Thank you for your patience.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

Support
Official support

2010-04-02T22:50:04Z

Look at attachments how to access output:

Support attached the following image(s):

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

JohnC
No customer Topic Starter

2010-04-02T22:57:23Z

Here is the output from my job.

I am unable to click on the link "Get full output" as it is grayed out.

Support
Official support

2010-04-02T23:00:35Z

Is your file located on a network drive?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

JohnC
No customer Topic Starter

2010-04-02T23:02:40Z

The file is located on a local drive on the server (drive C:).

Edited by user 2010-04-02T23:03:35Z | Reason: Not specified

Support
Official support

2010-04-02T23:03:52Z

Ok, I am not sure how that is setup in your end. Can you move it locally, for simplicity in just testing this?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

Support
Official support

2010-04-02T23:05:07Z

Ok, could you try changing the system account that runs the service to a local or domain user?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

JohnC
No customer Topic Starter

2010-04-02T23:20:05Z

I changed the service account to the same domain account I was using to execute the SSIS package. That appears to have worked and the packages now run, but I am now getitng four notifications when the job starts and four notifications when the job completes.

Edited by user 2010-04-02T23:23:59Z | Reason: Not specified

Support
Official support

2010-04-02T23:25:30Z

#10

Seems like you have checked start and complete Notifications at both Task and Job level.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

JohnC
No customer Topic Starter

2010-04-02T23:31:39Z

#11

No, I only have a signle notification set up if the job fails. I have no task level notifications.

Also, the notifications worked properly when the VisualCron service was set to use a local account instead of a domain account.

Support
Official support

2010-04-02T23:40:14Z

#12

Sorry, I was confused about that. But maybe you have several instances of the VisualCron Tray Client running in the tray (also check in Task manager).

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

JohnC
No customer Topic Starter

2010-04-02T23:42:20Z

#13

I changed the service back to starting using the "Local" account. I then tried executing a few of my jobs that don't execute SSIS packages. The notifications worked correctly and I recieved one notification that the job started and one notification that the job completed.

I then tried running a test job that executes a SSIS package task. I first ran it without using credentials. As expected, the job failed because no credentials were supplied to the package when it kicked off.

I then tried applying two different credentials to the SSIS task and both times the job failed for the same reason ("Exception in Task: Access is denied."). So it seems there is some kind of problem related to passing credentials to SSIS packages when using the "Local" account for the service.

Support
Official support

2010-04-03T00:15:19Z

#14

Try the following:

1. change the account to SYSTEM
2. add a Credential and set the Credential in the SSIS Task. Set it to the same user as you changed the service to.
3. start the service and run the task again.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

Support
Official support

2010-04-05T16:42:59Z

#15

Hi John,

did it work when changing below?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

JohnC
No customer Topic Starter

2010-04-06T18:09:10Z

#16

No, it did not. Are you saying to set the system to start using the "Local System" account? Or are you saying to create a local account named "SYSTEM" and then have the service start using that local account?

Support
Official support

2010-04-06T18:11:31Z

#17

I am talking about "Local System" account which is also known as "SYSTEM" account.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

JohnC
No customer Topic Starter

2010-04-06T18:16:30Z

#18

Using the "Local System" does not help. The SSIS package task still fails to run.

JohnC
No customer Topic Starter

2010-04-06T18:24:48Z

#19

The only time the SSIS package task will work is if I have the VisualCron service start with the same domain users ID / password needed to run the SSIS package. It does not appear that the credentials are being passed properly when starting the service with the Local System account.

Support
Official support

2010-04-06T19:21:44Z

#20

Did you try using the same Credentials in the Credential settings of the SSIS Task when running as SYSTEM?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

JohnC
No customer Topic Starter

2010-04-06T19:55:02Z

#21

How can you specify the "Local System" account as a credential? It asks you for a password to enter and I don't know what the password would be for the local system account.

Support
Official support

2010-04-06T19:56:47Z

#22

No, I mean the service should be running as Local System and the you use the logged in user as Credential.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

JohnC
No customer Topic Starter

2010-04-06T20:05:23Z

#23

(1) I've set the VisualCron service to start using the "Local System" account.
(2) I created a job with an "Execute SSIS package" task.
(a) I set the database version to 2008.
(b) I set the credential to the same domain user that is logged into the server. This user ID is an admin on
the server.
(c) I set the package path to the location of the .dtsx file.

When I try to run the job, the job fails for the following error: Exception in Task: Access is denied.

Support
Official support

2010-04-06T20:16:47Z

#24

And the package is both located locally and you do not try to access any network drive in the package?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

JohnC
No customer Topic Starter

2010-04-06T20:30:27Z

#25

The SSIS package is local to the server where VisualCron is installed. I created a 'test' package that does nothing; it contains no tasks, no connections, nothing at all.

If I try to execute this package using VisualCron, I still get the "Exception in Task: Access is denied" error.

ABOUT VISUALCRON

Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.

Login