dbTalk Databases Forums  

SSIS Woes - Jobs

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


Discuss SSIS Woes - Jobs in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #31  
Old   
cappjr@gmail.com
 
Posts: n/a

Default Re: SSIS Woes - Jobs - 04-21-2008 , 11:55 AM






On Apr 21, 11:39*am, jhofm... (AT) googlemail (DOT) com wrote:
Quote:
Hi Jeremy,

From the error message, it looks as if the SSIS components haven't
installed correctly on the server. *I would try re-installing SSIS.

Do you have BIDS installed on the server? *You could try running it
through BIDS on the server using remote desktop.

Good luck!
J
Thanks for the reply. BDIS is installed and I am able to successfully
run it via BDIS. But, the package needs to be executed weekly on
Sundays. Though, I believe I found a work-around.

First off, SSIS was NOT installed on that machine. Which really
confused me because how am I able to create and run SSIS packages
using BDIS if it is not installed? Anyway, it turns out that they
didn't want extra components running on this machine. So, I'm using
another machine on the network that does have SSIS installed on it.

I created an SSIS package using the Import/Export wizard from
Management Studio. The package ran fine and subsequently created the
SSIS package. When I tried to scheduled the SSIS package as a job, I
was getting errors.

Next, I tried running DTEXEC and got an error. This was the default 64-
bit DTEXEC. I "cd" to the 32-bit DTEXEC and ran the .dtsx package
using the 32-bit DTEXEC and it worked. So, I set up a .bat file and
set up a scheduled task to run the .bat file on Sundays.

Not how I wanted it to work, but it works nonetheless.

Thanks for everyone's help.

Jeremy


Reply With Quote
  #32  
Old   
cappjr@gmail.com
 
Posts: n/a

Default Re: SSIS Woes - Jobs - 04-21-2008 , 11:55 AM






On Apr 21, 11:39*am, jhofm... (AT) googlemail (DOT) com wrote:
Quote:
Hi Jeremy,

From the error message, it looks as if the SSIS components haven't
installed correctly on the server. *I would try re-installing SSIS.

Do you have BIDS installed on the server? *You could try running it
through BIDS on the server using remote desktop.

Good luck!
J
Thanks for the reply. BDIS is installed and I am able to successfully
run it via BDIS. But, the package needs to be executed weekly on
Sundays. Though, I believe I found a work-around.

First off, SSIS was NOT installed on that machine. Which really
confused me because how am I able to create and run SSIS packages
using BDIS if it is not installed? Anyway, it turns out that they
didn't want extra components running on this machine. So, I'm using
another machine on the network that does have SSIS installed on it.

I created an SSIS package using the Import/Export wizard from
Management Studio. The package ran fine and subsequently created the
SSIS package. When I tried to scheduled the SSIS package as a job, I
was getting errors.

Next, I tried running DTEXEC and got an error. This was the default 64-
bit DTEXEC. I "cd" to the 32-bit DTEXEC and ran the .dtsx package
using the 32-bit DTEXEC and it worked. So, I set up a .bat file and
set up a scheduled task to run the .bat file on Sundays.

Not how I wanted it to work, but it works nonetheless.

Thanks for everyone's help.

Jeremy


Reply With Quote
  #33  
Old   
cappjr@gmail.com
 
Posts: n/a

Default Re: SSIS Woes - Jobs - 04-21-2008 , 11:55 AM



On Apr 21, 11:39*am, jhofm... (AT) googlemail (DOT) com wrote:
Quote:
Hi Jeremy,

From the error message, it looks as if the SSIS components haven't
installed correctly on the server. *I would try re-installing SSIS.

Do you have BIDS installed on the server? *You could try running it
through BIDS on the server using remote desktop.

Good luck!
J
Thanks for the reply. BDIS is installed and I am able to successfully
run it via BDIS. But, the package needs to be executed weekly on
Sundays. Though, I believe I found a work-around.

First off, SSIS was NOT installed on that machine. Which really
confused me because how am I able to create and run SSIS packages
using BDIS if it is not installed? Anyway, it turns out that they
didn't want extra components running on this machine. So, I'm using
another machine on the network that does have SSIS installed on it.

I created an SSIS package using the Import/Export wizard from
Management Studio. The package ran fine and subsequently created the
SSIS package. When I tried to scheduled the SSIS package as a job, I
was getting errors.

Next, I tried running DTEXEC and got an error. This was the default 64-
bit DTEXEC. I "cd" to the 32-bit DTEXEC and ran the .dtsx package
using the 32-bit DTEXEC and it worked. So, I set up a .bat file and
set up a scheduled task to run the .bat file on Sundays.

Not how I wanted it to work, but it works nonetheless.

Thanks for everyone's help.

Jeremy


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.