|
|
|
date: Mon, 30 Jun 2008 02:25:04 -0700,
group: microsoft.public.sqlserver.dts
back
RE: How to solve the SSIS deployment issue :(
Daniel:
So set me get this straight:
You try to connect to an instance of SSIS using SQL Server Management Studio
and you get a Connection Timeout?
Or
You connect to the SSIS instance OK, but when you try to import the package,
you get a timeout?
If the first case, then it sounds like SSIS is not even running. Open the
SQL Configuration Manager on that machine and start it. If the second, not
sure what to tell you.
--
Todd C
"Daniel" wrote:
> Hi Todd,
>
> i have connection timeout issue to continue ur suggested steps..dunno which
> access role need to add in order to continue..:(
>
> danie;/
>
> "Todd C" wrote:
>
> > If your package does not need any special configurations and will work just
> > as it is in any environment, then there is no need to go through the whole
> > "Deployment Process" that is available in BIDS.
> >
> > Try this:
> > Open SSMS and connect to the SSIS server instance. Expand the nodes and
> > righ-click on MSDB and select Import Package. Get your package from the file
> > system.
> >
> > There's really not all that much to deploying packages that way.
> >
> > HTH
> > --
> > Todd C
> >
> > [If this response was helpful, please indicate by clicking the appropriate
> > answer at the bottom]
> >
> >
> > "Daniel" wrote:
> >
> > > Hi todd,
> > >
> > > The SSIS package does not uses any package configuration setting and just
> > > directly compile into Deployment package.
> > >
> > > After that, the compilation package will just copy and paste on the target
> > > server and install.
> > >
> > > Any steps i have miss?
> > >
> > > Please advice.
> > > thank you in advance
> > >
> > > Daniel.
> > >
> > > "Todd C" wrote:
> > >
> > > > Daniel:
> > > > You are going to need to give us a little more to go on than just an error
> > > > message.
> > > > --
> > > > Todd C
> > > >
> > > > "Daniel" wrote:
> > > >
> > > > > Hi experts,
> > > > >
> > > > > I have no idea why development of SSIS is easy but is hard when comes to
> > > > > deployment with the wizard and copy the installation "deployment" folder on
> > > > > the destination server..
> > > > >
> > > > > The error message is "The AcquireConnection method call failed with error
> > > > > code 0xC0202009. "
> > > > >
> > > > > Please provide steps to resolve the issue :). Really have no idea on this.
> > > > >
> > > > > thank you in advance.
> > > > > Daniel.
date: Mon, 30 Jun 2008 09:00:01 -0700
author: Todd C
RE: How to solve the SSIS deployment issue :(
hi todd,
the problem solve. i am still facing the same erro issue when executed the
imported package.
normally the task in pakcage is to read information from oracle data source
and pas te on sql server data source.
really have no idea on the issue. Is it because of the default connection
string? do u have any example of correct connectionstring?
thank you in advance
"Todd C" wrote:
> Daniel:
> So set me get this straight:
>
> You try to connect to an instance of SSIS using SQL Server Management Studio
> and you get a Connection Timeout?
> Or
> You connect to the SSIS instance OK, but when you try to import the package,
> you get a timeout?
>
> If the first case, then it sounds like SSIS is not even running. Open the
> SQL Configuration Manager on that machine and start it. If the second, not
> sure what to tell you.
> --
> Todd C
>
>
>
> "Daniel" wrote:
>
> > Hi Todd,
> >
> > i have connection timeout issue to continue ur suggested steps..dunno which
> > access role need to add in order to continue..:(
> >
> > danie;/
> >
> > "Todd C" wrote:
> >
> > > If your package does not need any special configurations and will work just
> > > as it is in any environment, then there is no need to go through the whole
> > > "Deployment Process" that is available in BIDS.
> > >
> > > Try this:
> > > Open SSMS and connect to the SSIS server instance. Expand the nodes and
> > > righ-click on MSDB and select Import Package. Get your package from the file
> > > system.
> > >
> > > There's really not all that much to deploying packages that way.
> > >
> > > HTH
> > > --
> > > Todd C
> > >
> > > [If this response was helpful, please indicate by clicking the appropriate
> > > answer at the bottom]
> > >
> > >
> > > "Daniel" wrote:
> > >
> > > > Hi todd,
> > > >
> > > > The SSIS package does not uses any package configuration setting and just
> > > > directly compile into Deployment package.
> > > >
> > > > After that, the compilation package will just copy and paste on the target
> > > > server and install.
> > > >
> > > > Any steps i have miss?
> > > >
> > > > Please advice.
> > > > thank you in advance
> > > >
> > > > Daniel.
> > > >
> > > > "Todd C" wrote:
> > > >
> > > > > Daniel:
> > > > > You are going to need to give us a little more to go on than just an error
> > > > > message.
> > > > > --
> > > > > Todd C
> > > > >
> > > > > "Daniel" wrote:
> > > > >
> > > > > > Hi experts,
> > > > > >
> > > > > > I have no idea why development of SSIS is easy but is hard when comes to
> > > > > > deployment with the wizard and copy the installation "deployment" folder on
> > > > > > the destination server..
> > > > > >
> > > > > > The error message is "The AcquireConnection method call failed with error
> > > > > > code 0xC0202009. "
> > > > > >
> > > > > > Please provide steps to resolve the issue :). Really have no idea on this.
> > > > > >
> > > > > > thank you in advance.
> > > > > > Daniel.
date: Mon, 30 Jun 2008 09:23:01 -0700
author: Daniel
RE: How to solve the SSIS deployment issue :(
Daniel:
So, you got connected to SSIS, imported the package, but now it won't run?
Don't worry, you are not alone. I had the same problems just starting out as
well.
You mention Oracle as a source. My guess is that you have a password
associated with the Oracle Connection Manager, yes? When you save the
package, it does not save the password with it.
When you go to run the package from SSIS (or when you schedule it from
within SQL Agent), click on the Connections tab and put a check next to the
Oracle connection. Then in the Connection String property, manually add a
"Password=abc123xyz;" clause right after the "User=Daniel;"
Let us know how that works out.
--
Todd C
[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]
"Daniel" wrote:
> hi todd,
>
> the problem solve. i am still facing the same erro issue when executed the
> imported package.
>
> normally the task in pakcage is to read information from oracle data source
> and pas te on sql server data source.
>
> really have no idea on the issue. Is it because of the default connection
> string? do u have any example of correct connectionstring?
>
> thank you in advance
> "Todd C" wrote:
>
> > Daniel:
> > So set me get this straight:
> >
> > You try to connect to an instance of SSIS using SQL Server Management Studio
> > and you get a Connection Timeout?
> > Or
> > You connect to the SSIS instance OK, but when you try to import the package,
> > you get a timeout?
> >
> > If the first case, then it sounds like SSIS is not even running. Open the
> > SQL Configuration Manager on that machine and start it. If the second, not
> > sure what to tell you.
> > --
> > Todd C
> >
> >
> >
> > "Daniel" wrote:
> >
> > > Hi Todd,
> > >
> > > i have connection timeout issue to continue ur suggested steps..dunno which
> > > access role need to add in order to continue..:(
> > >
> > > danie;/
> > >
> > > "Todd C" wrote:
> > >
> > > > If your package does not need any special configurations and will work just
> > > > as it is in any environment, then there is no need to go through the whole
> > > > "Deployment Process" that is available in BIDS.
> > > >
> > > > Try this:
> > > > Open SSMS and connect to the SSIS server instance. Expand the nodes and
> > > > righ-click on MSDB and select Import Package. Get your package from the file
> > > > system.
> > > >
> > > > There's really not all that much to deploying packages that way.
> > > >
> > > > HTH
> > > > --
> > > > Todd C
> > > >
> > > > [If this response was helpful, please indicate by clicking the appropriate
> > > > answer at the bottom]
> > > >
> > > >
> > > > "Daniel" wrote:
> > > >
> > > > > Hi todd,
> > > > >
> > > > > The SSIS package does not uses any package configuration setting and just
> > > > > directly compile into Deployment package.
> > > > >
> > > > > After that, the compilation package will just copy and paste on the target
> > > > > server and install.
> > > > >
> > > > > Any steps i have miss?
> > > > >
> > > > > Please advice.
> > > > > thank you in advance
> > > > >
> > > > > Daniel.
> > > > >
> > > > > "Todd C" wrote:
> > > > >
> > > > > > Daniel:
> > > > > > You are going to need to give us a little more to go on than just an error
> > > > > > message.
> > > > > > --
> > > > > > Todd C
> > > > > >
> > > > > > "Daniel" wrote:
> > > > > >
> > > > > > > Hi experts,
> > > > > > >
> > > > > > > I have no idea why development of SSIS is easy but is hard when comes to
> > > > > > > deployment with the wizard and copy the installation "deployment" folder on
> > > > > > > the destination server..
> > > > > > >
> > > > > > > The error message is "The AcquireConnection method call failed with error
> > > > > > > code 0xC0202009. "
> > > > > > >
> > > > > > > Please provide steps to resolve the issue :). Really have no idea on this.
> > > > > > >
> > > > > > > thank you in advance.
> > > > > > > Daniel.
date: Mon, 30 Jun 2008 09:33:02 -0700
author: Todd C
RE: How to solve the SSIS deployment issue :(
Hey Todd,
Is working but correction need to make for User ID instead of User :).
Here is another clarification link:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=1148720&SiteID=1
I may continue test the remaining package.
thanks for ur time and help :).
You're great !.
Daniel.
"Todd C" wrote:
> Daniel:
> So, you got connected to SSIS, imported the package, but now it won't run?
>
> Don't worry, you are not alone. I had the same problems just starting out as
> well.
>
> You mention Oracle as a source. My guess is that you have a password
> associated with the Oracle Connection Manager, yes? When you save the
> package, it does not save the password with it.
>
> When you go to run the package from SSIS (or when you schedule it from
> within SQL Agent), click on the Connections tab and put a check next to the
> Oracle connection. Then in the Connection String property, manually add a
> "Password=abc123xyz;" clause right after the "User=Daniel;"
>
> Let us know how that works out.
> --
> Todd C
>
> [If this response was helpful, please indicate by clicking the appropriate
> answer at the bottom]
>
>
> "Daniel" wrote:
>
> > hi todd,
> >
> > the problem solve. i am still facing the same erro issue when executed the
> > imported package.
> >
> > normally the task in pakcage is to read information from oracle data source
> > and pas te on sql server data source.
> >
> > really have no idea on the issue. Is it because of the default connection
> > string? do u have any example of correct connectionstring?
> >
> > thank you in advance
> > "Todd C" wrote:
> >
> > > Daniel:
> > > So set me get this straight:
> > >
> > > You try to connect to an instance of SSIS using SQL Server Management Studio
> > > and you get a Connection Timeout?
> > > Or
> > > You connect to the SSIS instance OK, but when you try to import the package,
> > > you get a timeout?
> > >
> > > If the first case, then it sounds like SSIS is not even running. Open the
> > > SQL Configuration Manager on that machine and start it. If the second, not
> > > sure what to tell you.
> > > --
> > > Todd C
> > >
> > >
> > >
> > > "Daniel" wrote:
> > >
> > > > Hi Todd,
> > > >
> > > > i have connection timeout issue to continue ur suggested steps..dunno which
> > > > access role need to add in order to continue..:(
> > > >
> > > > danie;/
> > > >
> > > > "Todd C" wrote:
> > > >
> > > > > If your package does not need any special configurations and will work just
> > > > > as it is in any environment, then there is no need to go through the whole
> > > > > "Deployment Process" that is available in BIDS.
> > > > >
> > > > > Try this:
> > > > > Open SSMS and connect to the SSIS server instance. Expand the nodes and
> > > > > righ-click on MSDB and select Import Package. Get your package from the file
> > > > > system.
> > > > >
> > > > > There's really not all that much to deploying packages that way.
> > > > >
> > > > > HTH
> > > > > --
> > > > > Todd C
> > > > >
> > > > > [If this response was helpful, please indicate by clicking the appropriate
> > > > > answer at the bottom]
> > > > >
> > > > >
> > > > > "Daniel" wrote:
> > > > >
> > > > > > Hi todd,
> > > > > >
> > > > > > The SSIS package does not uses any package configuration setting and just
> > > > > > directly compile into Deployment package.
> > > > > >
> > > > > > After that, the compilation package will just copy and paste on the target
> > > > > > server and install.
> > > > > >
> > > > > > Any steps i have miss?
> > > > > >
> > > > > > Please advice.
> > > > > > thank you in advance
> > > > > >
> > > > > > Daniel.
> > > > > >
> > > > > > "Todd C" wrote:
> > > > > >
> > > > > > > Daniel:
> > > > > > > You are going to need to give us a little more to go on than just an error
> > > > > > > message.
> > > > > > > --
> > > > > > > Todd C
> > > > > > >
> > > > > > > "Daniel" wrote:
> > > > > > >
> > > > > > > > Hi experts,
> > > > > > > >
> > > > > > > > I have no idea why development of SSIS is easy but is hard when comes to
> > > > > > > > deployment with the wizard and copy the installation "deployment" folder on
> > > > > > > > the destination server..
> > > > > > > >
> > > > > > > > The error message is "The AcquireConnection method call failed with error
> > > > > > > > code 0xC0202009. "
> > > > > > > >
> > > > > > > > Please provide steps to resolve the issue :). Really have no idea on this.
> > > > > > > >
> > > > > > > > thank you in advance.
> > > > > > > > Daniel.
date: Mon, 30 Jun 2008 09:59:00 -0700
author: Daniel
RE: How to solve the SSIS deployment issue :(
Hi Todd,
Although we are able to update manually on the connectionstring. but it will
not save. After i reopen the package on msdb, the password is lost again.
Any idea to maintain it?
daniel
"Todd C" wrote:
> Daniel:
> So, you got connected to SSIS, imported the package, but now it won't run?
>
> Don't worry, you are not alone. I had the same problems just starting out as
> well.
>
> You mention Oracle as a source. My guess is that you have a password
> associated with the Oracle Connection Manager, yes? When you save the
> package, it does not save the password with it.
>
> When you go to run the package from SSIS (or when you schedule it from
> within SQL Agent), click on the Connections tab and put a check next to the
> Oracle connection. Then in the Connection String property, manually add a
> "Password=abc123xyz;" clause right after the "User=Daniel;"
>
> Let us know how that works out.
> --
> Todd C
>
> [If this response was helpful, please indicate by clicking the appropriate
> answer at the bottom]
>
>
> "Daniel" wrote:
>
> > hi todd,
> >
> > the problem solve. i am still facing the same erro issue when executed the
> > imported package.
> >
> > normally the task in pakcage is to read information from oracle data source
> > and pas te on sql server data source.
> >
> > really have no idea on the issue. Is it because of the default connection
> > string? do u have any example of correct connectionstring?
> >
> > thank you in advance
> > "Todd C" wrote:
> >
> > > Daniel:
> > > So set me get this straight:
> > >
> > > You try to connect to an instance of SSIS using SQL Server Management Studio
> > > and you get a Connection Timeout?
> > > Or
> > > You connect to the SSIS instance OK, but when you try to import the package,
> > > you get a timeout?
> > >
> > > If the first case, then it sounds like SSIS is not even running. Open the
> > > SQL Configuration Manager on that machine and start it. If the second, not
> > > sure what to tell you.
> > > --
> > > Todd C
> > >
> > >
> > >
> > > "Daniel" wrote:
> > >
> > > > Hi Todd,
> > > >
> > > > i have connection timeout issue to continue ur suggested steps..dunno which
> > > > access role need to add in order to continue..:(
> > > >
> > > > danie;/
> > > >
> > > > "Todd C" wrote:
> > > >
> > > > > If your package does not need any special configurations and will work just
> > > > > as it is in any environment, then there is no need to go through the whole
> > > > > "Deployment Process" that is available in BIDS.
> > > > >
> > > > > Try this:
> > > > > Open SSMS and connect to the SSIS server instance. Expand the nodes and
> > > > > righ-click on MSDB and select Import Package. Get your package from the file
> > > > > system.
> > > > >
> > > > > There's really not all that much to deploying packages that way.
> > > > >
> > > > > HTH
> > > > > --
> > > > > Todd C
> > > > >
> > > > > [If this response was helpful, please indicate by clicking the appropriate
> > > > > answer at the bottom]
> > > > >
> > > > >
> > > > > "Daniel" wrote:
> > > > >
> > > > > > Hi todd,
> > > > > >
> > > > > > The SSIS package does not uses any package configuration setting and just
> > > > > > directly compile into Deployment package.
> > > > > >
> > > > > > After that, the compilation package will just copy and paste on the target
> > > > > > server and install.
> > > > > >
> > > > > > Any steps i have miss?
> > > > > >
> > > > > > Please advice.
> > > > > > thank you in advance
> > > > > >
> > > > > > Daniel.
> > > > > >
> > > > > > "Todd C" wrote:
> > > > > >
> > > > > > > Daniel:
> > > > > > > You are going to need to give us a little more to go on than just an error
> > > > > > > message.
> > > > > > > --
> > > > > > > Todd C
> > > > > > >
> > > > > > > "Daniel" wrote:
> > > > > > >
> > > > > > > > Hi experts,
> > > > > > > >
> > > > > > > > I have no idea why development of SSIS is easy but is hard when comes to
> > > > > > > > deployment with the wizard and copy the installation "deployment" folder on
> > > > > > > > the destination server..
> > > > > > > >
> > > > > > > > The error message is "The AcquireConnection method call failed with error
> > > > > > > > code 0xC0202009. "
> > > > > > > >
> > > > > > > > Please provide steps to resolve the issue :). Really have no idea on this.
> > > > > > > >
> > > > > > > > thank you in advance.
> > > > > > > > Daniel.
date: Mon, 30 Jun 2008 10:02:00 -0700
author: Daniel
RE: How to solve the SSIS deployment issue :(
Daniel:
You are very welcome. I also posted another blog concerning Passwords that
you may be interested in:
http://toddchitt.wordpress.com/2008/06/30/ssis_pw/
I, too, have had packages run OK from SSIS server instance (right-click and
select "Execute Package"), but they fail when they are scheduled to run from
within SQL Server Agent.
The most I can tell you about this is to make sure that the Service Account
that runs SQL Agent has all the permissions it needs on all the resources
(things like integrated security on Database loginsn, file permissions on the
folders, etc).
Good Luck.
--
Todd C
[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]
"Daniel" wrote:
> Hi Todd,
>
> Now i m able to execute from the integration service server. But i m facing
> another issue in executing the job in SQL Agent. The history log only show
> the steps was invoke from who and fail. It does not show detail of why fail.
>
> I tried changing the command line if i have encryption on the package - also
> fail.
>
> Any ideas on this?
>
> Daniel.
>
> "Daniel" wrote:
>
> > Bravo! I will definitely read thru the blog and give it a try. Thanks for ur
> > passion in sharing ur knowledge.
> >
> > Daniel.
> >
> > "Todd C" wrote:
> >
> > > In the design environment (BIDS) you can assign various values to a package
> > > property called "ProtectionLevel". The defaul is "Save Sensetive With User
> > > Key". One of the options there is "Save Sensetive With Password" but that
> > > requires that you re-supply the password every time you save the package, and
> > > that you know the password when you deploy or run it. (I know, just what you
> > > needed, MORE PASSWORDS!).
> > >
> > > You could work long and hard to design all your packages to save the
> > > Connection String passwords INSIDE the package, but what if it changes? You
> > > must then edit and re-deploy all your packages.
> > >
> > > Enter SSIS's new functionality: Configurations
> > >
> > > I *just* finished this blog and it might help you out:
> > >
> > > http://toddchitt.wordpress.com/2008/06/27/ssis_configs/
> > >
> > > HTH
> > > ------
> > > Todd C
date: Tue, 1 Jul 2008 05:47:00 -0700
author: Todd C
RE: How to solve the SSIS deployment issue :(
Hi Todd,
thanks for the info.
Finally i do observe the gap and let me share out the experience :).
i have lock all my package with password. So, in order to run the SSIS
package at Job Agent, we need to ensure the CommandLine tab has to switch to
edit the command line manually. <the setting will capture on system although
next round u view again and is not selected at the manual radio button>
After with the just one manual radio selection, the package run successfully
on the job agent.
daniel.
"Todd C" wrote:
> Daniel:
> You are very welcome. I also posted another blog concerning Passwords that
> you may be interested in:
>
> http://toddchitt.wordpress.com/2008/06/30/ssis_pw/
>
> I, too, have had packages run OK from SSIS server instance (right-click and
> select "Execute Package"), but they fail when they are scheduled to run from
> within SQL Server Agent.
>
> The most I can tell you about this is to make sure that the Service Account
> that runs SQL Agent has all the permissions it needs on all the resources
> (things like integrated security on Database loginsn, file permissions on the
> folders, etc).
>
> Good Luck.
> --
> Todd C
>
> [If this response was helpful, please indicate by clicking the appropriate
> answer at the bottom]
>
>
> "Daniel" wrote:
>
> > Hi Todd,
> >
> > Now i m able to execute from the integration service server. But i m facing
> > another issue in executing the job in SQL Agent. The history log only show
> > the steps was invoke from who and fail. It does not show detail of why fail.
> >
> > I tried changing the command line if i have encryption on the package - also
> > fail.
> >
> > Any ideas on this?
> >
> > Daniel.
> >
> > "Daniel" wrote:
> >
> > > Bravo! I will definitely read thru the blog and give it a try. Thanks for ur
> > > passion in sharing ur knowledge.
> > >
> > > Daniel.
> > >
> > > "Todd C" wrote:
> > >
> > > > In the design environment (BIDS) you can assign various values to a package
> > > > property called "ProtectionLevel". The defaul is "Save Sensetive With User
> > > > Key". One of the options there is "Save Sensetive With Password" but that
> > > > requires that you re-supply the password every time you save the package, and
> > > > that you know the password when you deploy or run it. (I know, just what you
> > > > needed, MORE PASSWORDS!).
> > > >
> > > > You could work long and hard to design all your packages to save the
> > > > Connection String passwords INSIDE the package, but what if it changes? You
> > > > must then edit and re-deploy all your packages.
> > > >
> > > > Enter SSIS's new functionality: Configurations
> > > >
> > > > I *just* finished this blog and it might help you out:
> > > >
> > > > http://toddchitt.wordpress.com/2008/06/27/ssis_configs/
> > > >
> > > > HTH
> > > > ------
> > > > Todd C
date: Thu, 10 Jul 2008 08:43:01 -0700
author: Daniel
|
|
