I am trying to migrate a DTS package from server 2000 to 2005. I is there a
How-to for this.

I am also getting a

Client unable to establish connection
Encryption not supported on SQL Server. (Microsoft SQL Native Client)

when I try to expand the MSDB folder in Stored Packages.

Any help is Appreciated

Thank you
--
Jerry

This article may help:

DTS -Transfer DTS Packages to SQL Server 2005 SSIS
http://searchsqlserver.techtarget.co...216481,00.html


--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


"Jerry C" <jerryed (AT) nospam (DOT) nospam> wrote

Some more links here-

Upgrading DTS
(http://wiki.sqlis.com/default.aspx/S...radingDTS.html)


--
Darren
http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com |
http://www.konesans.com

"Arnie Rowland" <arnie (AT) 1568 (DOT) com> wrote

Hi Jerry,
My understanding of your issue is that:
You wanted find some how-to articles on DTS upgrading to SSIS.
Also, you encoutered the error:
Encryption not supported on SQL Server. (Microsoft SQL Native Client)
when you tried to expand the MSDB folder in Stored Packages.
If I have misunderstood, please let me know.

For your first question, I recommend that you refer to this article for
best practice:
SQL Server 2005 Integration Services, Part 1: Lessons from Project REAL
http://msdn.microsoft.com/library/de...us/dnsql90/htm
l/SQL05InSrREAL.asp

For your second question, to be honest, I couldn't understand clearly.
Could you please describe your operation more detailed and mail me
(changliw (AT) microsoft (DOT) com) a screenshot for further research?

If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.

Sincerely,
Charles Wang
Microsoft Online Community Support

================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Thank you for your replys. I now have a DTS package file in the sql server
2005 it is in both places Legecy DTS packages and stored packages. but it
will not run. How do I edit it with the business intelegence package. I have
emailed some screen shots.

Thank you,
--
Jerry


"Charles Wang[MSFT]" wrote:

Charles,
I have tried to email some screen shots but they are 23 meg and too big for
email. is there a ftp site I can send the file to.

The other problem I am having is this message when I try to execute the
package in stored packages.

Error: Failed to acquire connection "LJ Machine". Connection may not be
configured correctly or you may not have the right permissions on this
connection.

How do I configure the connection and set permissions on it.

Thank you



Thank you
--
Jerry


"Jerry C" wrote:

Hi Jerry,
I just send a email to you on how you can upload the file to me.

Also, I would like to know if you use the Migration Wizard option of the
Data Transformation Service under the Legacy folder in SQL Server
Management Studio to migrate your DTS package.
Please refer to this article to check your operation:
SQL Server 2005 Integration Services Backward Compatibility
http://msdn2.microsoft.com/en-us/library/ms143706.aspx

To let me reproduce your issue, it is better that If you could describe
more detailed on what your DTS package was like and how you migrated your
DTS package.

Sincerely yours,
Charles Wang
Microsoft Online Community Support

Charles,

I have downloaded some screen shots of the connection problem.
I hope I have not confused the issues. I have two problems.

1. On the customers machine I have migrated a DTS package from a SQL server
2000 and it seemed to migrate ok. The problem when I try to run it from
Server Management Studio I get the "Failed to accquire connection" error. I
have uploaded the screen shots to you. Since this is the customer's machine I
would like to work on this problem now.

2. On my server I am getting the Encription problem. I would like to work on
this one later.

Thank you

--
Jerry


"Charles Wang[MSFT]" wrote:

Hi Jerry,
Thanks for your response.

Your uploading file actually help me better understand your issue.
Firstly, let me answer your Encryption issue when you expand your MSDB
folder.
================================================== ======================
I reproduced your issue at my computer and resolved this issue by following:
1. Click Start->Program Files-> Administrative tools->Component Services,
expand Componet
services, expand My Computer, expand DCOM Config, look for MsDtsServer and
go to Properties,
go to Security, edit the Launch application, add the Windows User that you
used to connect to your SQL Server,
and give the user all the 4 rights eg: local launch, remote launch, Local
Activation, Remote activation.
Then in the same MsDtsServer Properties, go to Security again, this time
edit the Access Permissions Properties,
add the same faulty user here as well, and give the follwoing rights: Local
access and Remote access.

2. Open the file:
C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml
then correct the ServerName node in MsDtsSrvr.ini.xml, change the "." into
your SQL Server instance like:
Before:
<ServerName>.</ServerName>
After:
<ServerName>YOUR_SQLSERVER_INSTANCE_NAME</ServerName>

Complete XML:
<?xml version="1.0" encoding="utf-8"?>
<DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown>
<TopLevelFolders>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB</Name>
<ServerName>YOUR_SQLSERVER_INSTANCE_NAME</ServerName>
</Folder>
<Folder xsi:type="FileSystemFolder">
<Name>File System</Name>
<StorePath>..\Packages</StorePath>
</Folder>
</TopLevelFolders>
</DtsServiceConfiguration>

3. Open services.msc and restart your SQL Server Integration Service.
4. Log on your Integration Service from SQL Server Management Studio, then
you can expand the MSDB folder without the error.
================================================== ==========================
=====================

For your editing connection string question, this issue should be caused by
missing the sa password.
================================================== ==========================
=====================
In SQL Server 2005, SSIS packages can be edited in SQL Server Business
Intelligence Development Studio (SSBIDS). Please refer to the following
steps:
1. Open the SSBIDS from your SQL Server 2005 program group in start menu;
2. Click File, select New, click Project..., select Business Intelligence
Projects, select Integration Service Project, input the Name and Location,
then click OK.
3. In the Solution Explorer, right click the SSIS packages folder, select
Migrate DTS 2000 packages or Add Existing package (since you have migrated
the DTS package), then follow the wizard to add the package into this
project.
4. Once the package is included, a transfor data task will be displayed on
the Control Flow panel, double click the task, then you can see the package
details under the Data Flow Panel, select the connection in the Connection
Managers below and you can edit the connection string in the Properties
window.
================================================== ==========================
====================

For more information on SSBIDS, you can refer to SQL Server 2005 Books
Online. Search for Integration Service.

Hope this helpful.

If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.

Sincerely,
Charles Wang
Microsoft Online Community Support

Hi Jerry,

I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.

Have a great day!

Charles Wang
Microsoft Online Community Support