Re: SSIS package fails to execute from scheduler

Tech-Archive recommends: Fix windows errors by optimizing your registry



Because you are not executing the package as you. The execution context is
somebody else and chances are they do not have access to that path

--


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com


"Panos Stavroulis." <PanosStavroulis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:41010350-D9F8-4945-84F6-FCF95E0295C1@xxxxxxxxxxxxxxxx
Hi Alan,

Now that might be a Windows question not SQL server. I've tried the
logging
within the package and after I've changed the drive names to something
more
appropriate now I get

Message: The script threw an exception: Access to the path
'\\cqsm.com\cqsnet\shareddata\CreditFund\Data\Mark-It\CDS\AllComposite' is
denied.

Why I don't have access when executing from SQL. I do have access to see
files in the folders from the file system. Thanks.

Panos.

"Allan Mitchell" wrote:

No I am talking about inside the package itself.

It would seem that the package fires from the scheduler so we are
actually
executing. The best way to see what is happening inside is to turn on
logging in the package itself.

Make sure you turn it on for each executable and all events. Whilst this
will be verbose it will allow you to see everything. You can always turn
it
down afterwards.

--


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com


"Panos Stavroulis." <PanosStavroulis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:61301D15-708A-49D8-9F82-EA4002840FA6@xxxxxxxxxxxxxxxx
Hi,

I've tried the logging, are you talking about the tap page on the step?
I've
tried both text and sql but now it fails with a different error
message.
What's the configuration string, don't know what to enter there.
Thanks.

Panos.

"Allan Mitchell" wrote:

Enable logging in your package. My guess from the info available so
far
is
that you have a login failure.

--


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com


"Panos Stavroulis." <PanosStavroulis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:8E8C8A79-6661-42B5-A7D3-B3C82B46059D@xxxxxxxxxxxxxxxx
Hi,

This is the first time I've am scheduling an SQL Server 2005
package.
The
package contains few vb.net scripts and other sql scripts. The
package
works
fine when I execute from Visual studio. So I tried to schedule from
sql
server agent. But it just fails on me, no specific error message no
more
info
in the package history.

I've created another very simple package to test if that works and
that
works fine. So must be something wrong with this particular package.
Does
anybody have any ideas what's wrong? What else can I do to debug it?
Thanks.

Panos.








.



Relevant Pages

  • Re: Access while running DTS package using stored procedure
    ... The permissions when executing xp_cmdshell can be different depending on who ... which the SQL Server service is running. ... > I wrote a DTS Package that can take the data from a .txt file residing ... > Declare @RunDTS as varchar ...
    (microsoft.public.sqlserver.dts)
  • QUESTION: shared libraries
    ... how would I create a package easy-to-install for a new user? ... we could use a script to install the package. ... I have seen some scripts executing from a ... Gouvernement du Canada / Government of Canada ...
    (comp.os.linux.development.apps)
  • QUESTION: shared libraries
    ... how would I create a package easy-to-install for a new user? ... we could use a script to install the package. ... takes root privileges to do so. ... I have seen some scripts executing from a ...
    (alt.os.linux.redhat)
  • QUESTION: shared libraries
    ... how would I create a package easy-to-install for a new user? ... we could use a script to install the package. ... takes root privileges to do so. ... I have seen some scripts executing from a ...
    (comp.os.linux.development.system)
  • RE: DTSRun Call from Unix
    ... "There are two main methods of executing a DTS package from within T-SQL, ... either using the DTSRUN utility to perform the execution, ... fully documented in SQL Server Books Online. ...
    (microsoft.public.sqlserver.dts)