Trouble deploying a package to MSDB

Question

Post reply

Trouble deploying a package to MSDB

Welsh Corgi

SSC Guru

Points: 116520
More actions
April 19, 2016 at 12:05 pm

#326575

I'm having trouble with one deploying package to MSDB.
I enter the Server, set the package path and click next and it tries to install the package at the following folder:
c:\Program Files (x86)\Microsoft SQL Server\120\DTS\Packages\Drop_Constraints_629
What am I missing?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

John Rowan SSC Guru Points: 56440 More actions · Answer 1

Are you using the .ispac file for deployment?

John Rowan

======================================================
======================================================
Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 2

John Rowan (4/19/2016)
Are you using the .ispac file for deployment?

I'm using the manifest file.

Thanks.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 3

John Rowan (4/19/2016)
Are you using the .ispac file for deployment?

When I use .ispac I get an error that it failed to encrypt and XML node.

When I click build it does not generate a new .ispac file?

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Phil Parkin SSC Guru Points: 246960 More actions · Answer 4

John Rowan (4/19/2016)
Are you using the .ispac file for deployment?

I'm sure you know this, but ispac files get deployed only to SSISDB (as far as I know).

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 5

I had changed the protectionlevel property to Don't save sensitive but I did not save the package\project.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

John Rowan SSC Guru Points: 56440 More actions · Answer 6

Phil Parkin (4/19/2016)
John Rowan (4/19/2016)
Are you using the .ispac file for deployment?
I'm sure you know this, but ispac files get deployed only to SSISDB (as far as I know).

I think this was a poorly phrased question to determine if he's attempting to use project or package deployment. Probably could have guessed based on the file system reference in the OP.

Welsh,

So I have not used package deployment for quite some time as we only do project deployment where I've been for the last year +. I used to use package deployment (2008) and had no issues w/ deploying to msdb. The deployment manifest used to give the option of file system deployment versus msdb deployment. Does your manifest not prompt for that?

I could try to mock this up in my environment, but you may get other's input before I can get it wrapped up.

John Rowan

======================================================
======================================================
Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 7

I specified SQL Server and the path within MSDB.

I click next and it displays a Windows path.

I added a package just prior to this and it worked fine.

I probably need to use the DTUTIL.

Thanks.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/