Showing posts with label quotexecute. Show all posts
Showing posts with label quotexecute. Show all posts

Wednesday, March 21, 2012

Executing a batch script from "Execute Process" Task

Hello,

I have an "execute process" task which executes a perl script. When I run the task, it shows a prompt with the message "the publisher can not be verified". It gives the option to continue the task or to cancel.

The problem for me is that I want to schedule this package to run automatically, and I don't want the automated process to show this dialog. I need to override the security setting and have SSIS execute my batch scripts without prompting. Assuming I don't want to rewrite the Perl code into a script task, is there a way to do acomplish this?

Thanks!

Arkadiy

Normally, Digitally Signing whatever is being called into question could resolve this type of error, but I have not seen this error occur in SSIS as of yet (usually see this in IE).

Here's some stuff you can try:

Try testing after lowering the internet security (on the test system) to a lower setting (for example low - or "custom level" and play around with the settings here). Be sure to set this back when you are done testing.

You could look into digitally signing the perl script. I'm not sure if this pertains to that or not:

http://www.cpan.org/authors/id/R/RO/ROODE/perlsign-0.04

"This program invokes GPG to digitally sign Perl source files. The GPG signature becomes embedded into the source file as POD paragraphs. The functionality of the program or module isn't affected. This may be useful to prove authorship of a program, or to prove that changes have or have not been made to a source file."

You could read this to see if it gives you any insight:

http://www.microsoft.com/technet/Security/bestprac/mblcode.mspx

Anyway, if this is not relavent, can you provide more details as to how you are executing the perl script? Like where the perl script is stored, etc.

|||

Thanks,

I found another way of solving this without changing the security settings. The trick is to invoke executable or dll (such as perl.exe) and not a batch script. So in the "execute process" task, the executable became perl.exe and everything else became command line argument. Then it works fine.

Thanks again for your help anyway!

Arkadiy

Sunday, February 19, 2012

Execute Package Task fail with "Access Denied"

Hi all,

I have an error when a package is trying to execute a SubPackage using the "Execute Package Task". I have this problem for all packages that are running sub packages.

The packages are stored in the DTS\Packages folder of the SQL Server installation folder.

The master package is called from an Event Handler on a document library in MOSS 2007.

The account from the Sharepoint Application Pool has Full Control on the DTS\Packages folder.

What am I missing ?

Does it work OK if you run it from BIDS?|||

Yes!

Actually, adding the account of the SPS Process to the Local Admin group on the SSIS server made it work but I don't understand why. This user account already had Read&Execute and Write NTFS permissions on the folder where the SSIS packages are stored and it works for the other packages, only the sub packages returns an "Access Denied" error.

I should have said that I have 2 servers, one SPS server and one SQL/SSIS Server.

I would prefer not to add the SPS User account to the Local Admin group on the SQL/SSIS Server, if anyone has an idea how to avoid this please let me know.