dbTalk Databases Forums  

SSIS Package runs in VS but not on schedule

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss SSIS Package runs in VS but not on schedule in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Svein Terje Gaup
 
Posts: n/a

Default SSIS Package runs in VS but not on schedule - 12-19-2006 , 03:44 AM






I have a package that transfers data from a table in SQL Server to a
table with identical schema in Oracle. This package runs fine when run
from Visual Studio, but it fails when I set it up with a schedule in
SSMS.

Error message is:
Execution of job 'Eksporter til Formula' failed. See the history log
for details.

Quote:
From the job history these lines show:
12/19/2006 10:25:57,Eksporter til
Formula,Error,0,GK-VIRKSOM02,Eksporter til Formula,(Job outcome),,The
job failed. The Job was invoked by User GKDOMAIN\virksom. The last
step to run was step 1 (Kjør SSIS Pakke for eksport til
ORACLE).,00:00:53,0,0,,,,0
12/19/2006 10:25:57,Eksporter til
Formula,Error,1,GK-VIRKSOM02,Eksporter til Formula,Kjør SSIS Pakke for
eksport til ORACLE,,Executed as user: GKDOMAIN\virksom. The package
execution failed. The step failed.,00:00:53,0,0,,,,0

The job only fails when there are rows in the source tables.

When I run the package in VS I am logged in as the same user that is
shown in the log above.

Can anyone help me? It seems to me that the information from the job
history is useless... it doesnt tell me anything about what actually
happened, and nothing I dont already know. Are there any other places I
could get more details? How can I debug this when it runs fine in my
debug tool (VS)?

Sincerely
Svein Terje Gaup



Reply With Quote
  #2  
Old   
Svein Terje Gaup
 
Posts: n/a

Default Re: SSIS Package runs in VS but not on schedule - 12-19-2006 , 04:38 AM






OK, I found a way to get more information, but its very frustrating
that I cant copy the information to the clipboard. What I did was open
SSMS, then from the View menu, I selected "Registered Servers", then
clicked the icon "Integration Services". Then got the jobs stored on
the SQL Server listed. I then was able to execute the job, and got a
running progress report. Only problem is I have to write very much text
from the error message shown, since its not possible to copy the text
to the clipboard. Or is there a way?

I'd better get started typing the error message if I'm going to be
finished today.

Svein Terje


Svein Terje Gaup skrev:
Quote:
I have a package that transfers data from a table in SQL Server to a
table with identical schema in Oracle. This package runs fine when run
from Visual Studio, but it fails when I set it up with a schedule in
SSMS.

Error message is:
Execution of job 'Eksporter til Formula' failed. See the history log
for details.

From the job history these lines show:
12/19/2006 10:25:57,Eksporter til
Formula,Error,0,GK-VIRKSOM02,Eksporter til Formula,(Job outcome),,The
job failed. The Job was invoked by User GKDOMAIN\virksom. The last
step to run was step 1 (Kjør SSIS Pakke for eksport til
ORACLE).,00:00:53,0,0,,,,0
12/19/2006 10:25:57,Eksporter til
Formula,Error,1,GK-VIRKSOM02,Eksporter til Formula,Kjør SSIS Pakke for
eksport til ORACLE,,Executed as user: GKDOMAIN\virksom. The package
execution failed. The step failed.,00:00:53,0,0,,,,0

The job only fails when there are rows in the source tables.

When I run the package in VS I am logged in as the same user that is
shown in the log above.

Can anyone help me? It seems to me that the information from the job
history is useless... it doesnt tell me anything about what actually
happened, and nothing I dont already know. Are there any other places I
could get more details? How can I debug this when it runs fine in my
debug tool (VS)?

Sincerely
Svein Terje Gaup


Reply With Quote
  #3  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SSIS Package runs in VS but not on schedule - 12-19-2006 , 03:06 PM



Can you try logging withinside your package? Logging info through Jobs
is painful although if you execue it as an Operating System Command it
is a bit better

http://wiki.sqlis.com/default.aspx/S...dPackages.html

--


Regards


Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com



"Svein Terje Gaup" <gaupen (AT) yahoo (DOT) com> wrote


Quote:
OK, I found a way to get more information, but its very frustrating
that I cant copy the information to the clipboard. What I did was open
SSMS, then from the View menu, I selected "Registered Servers", then
clicked the icon "Integration Services". Then got the jobs stored on
the SQL Server listed. I then was able to execute the job, and got a
running progress report. Only problem is I have to write very much text
from the error message shown, since its not possible to copy the text
to the clipboard. Or is there a way?

I'd better get started typing the error message if I'm going to be
finished today.

Svein Terje


Svein Terje Gaup skrev:

I have a package that transfers data from a table in SQL Server to a
table with identical schema in Oracle. This package runs fine when run
from Visual Studio, but it fails when I set it up with a schedule in
SSMS.

Error message is:
Execution of job 'Eksporter til Formula' failed. See the history log
for details.


From the job history these lines show:

12/19/2006 10:25:57,Eksporter til
Formula,Error,0,GK-VIRKSOM02,Eksporter til Formula,(Job outcome),,The
job failed. The Job was invoked by User GKDOMAIN\virksom. The last
step to run was step 1 (Kjør SSIS Pakke for eksport til
ORACLE).,00:00:53,0,0,,,,0
12/19/2006 10:25:57,Eksporter til
Formula,Error,1,GK-VIRKSOM02,Eksporter til Formula,Kjør SSIS Pakke for
eksport til ORACLE,,Executed as user: GKDOMAIN\virksom. The package
execution failed. The step failed.,00:00:53,0,0,,,,0

The job only fails when there are rows in the source tables.

When I run the package in VS I am logged in as the same user that is
shown in the log above.

Can anyone help me? It seems to me that the information from the job
history is useless... it doesnt tell me anything about what actually
happened, and nothing I dont already know. Are there any other places
I
could get more details? How can I debug this when it runs fine in my
debug tool (VS)?

Sincerely
Svein Terje Gaup


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.