Hi!
I am trying to deploy a package to SQL. However, when I open Integration services I can not expand MSDB folder. Error is; SQL Server specified in SSIS service configuration is not present or available.... Login time expired .....(MsDTSSrvr)
I have found post here that says MsDtsSrvr.ini.xml file needs to be changed from
<Name>MSDB</Name>
<ServerName>.</ServerName>
to
<Name>MSDB</Name>
<ServerName>MyServerName</ServerName>
I tried MyServerName - does not work. I also tried value from connecting to Database Engine ( MyServerName\SQL2K5LOCAL) - does not help either.
What am I doing wrong?
Also, I need some documentation on deploying packgaes using File System.
I have saved Copy of the Package as File System location.
When I doubleclick the .dtsx file, Connection Manager holds my local SQL info. Goal is to deploy this to Development and other environments. Can this be handled some other way so I do not have to modify this file on every environment?
Also, this Execute Utility Package says at the top to use this utility to run SSIS on local computer.
So far, help on MSoft sites did not really help me a lot.
this is what I am using:
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: IDE Standard
SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00
Ljiljana wrote:
Also, I need some documentation on deploying packgaes using File System.
I have saved Copy of the Package as File System location.
When I doubleclick the .dtsx file, Connection Manager holds my local SQL info. Goal is to deploy this to Development and other environments. Can this be handled some other way so I do not have to modify this file on every environment?
You can use package configurations, which allow you to store connection strings and other information outside of the package in a file, database, or environment variable. Right-click on the background of the package when it is open in BIDS, and you'll see the configurations option on the menu.
Also, this Execute Utility Package says at the top to use this utility to run SSIS on local computer.
You can use SQL Server Agent to schedule the job to run on the server.
Sorry, I can't help with the MSDB issue.
|||Thanks John!
I am aware of the Config wizard.
I have found article by Jamie T. (www.sqlis.com/26.aspx) where he explains how to use direct configuration.
However, I am doing something wrong as I was not able to deploy this to another PC.
I went to my coworker PC and in Integration Services -File System imported my package.
When I say Run it still has data from my local PC. It will work if I modify connection string in Execute Package Utility in Integration Services to point to his PC but then I wonder where is disconnecti between this package and Environment.dtsConfig file. I thought if I change <ConfiguredValue> to his PC name in this .dtsConfig file it will pick it up from there.
I had folder c:\PackageConfiguration\Environment.dtsConfig on his local PC
|||I have fond resolution to the issue
please look at the question asked on this forum "File System and MSDB folders gone"
sql