I just imported data from one database to another, I specified to save the
SSIS package on the database server (not on the file system).
Now I cannot find the package anywhere. There isn't a "Local Package" tree
like in 2000 Enterprise Manager. I can't even find a shortcut for starting
SSIS in my Start menu, and the SSIS Tutorial only shows how to create a new
project in VS, not how to open an existing package.
Hello,
You could click "Connect" button in Server management studio and click to
select "Integration services", and then type the instance information you
want.
Hope this is helpful.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Dumb question about SSIS
>thread-index: AcXx8eErD985vRkIQ9eWYJ2xuQK32Q==
>X-WBNR-Posting-Host: 84.56.32.28
>From: "=?Utf-8?B?SmFtZXM=?=" <aa1948@.nospam.nospam>
>Subject: Dumb question about SSIS
>Date: Fri, 25 Nov 2005 10:56:02 -0800
>Lines: 7
>Message-ID: <E17165D6-8E0C-40F9-982B-9A4530B8CF5A@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:412281
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I just imported data from one database to another, I specified to save the
>SSIS package on the database server (not on the file system).
>Now I cannot find the package anywhere. There isn't a "Local Package" tree
>like in 2000 Enterprise Manager. I can't even find a shortcut for starting
>SSIS in my Start menu, and the SSIS Tutorial only shows how to create a
new
>project in VS, not how to open an existing package.
>
|||Thanks Peter, exactly what I was looking for.
But now I still cannot see my package, as I'm getting following error
message when clicking on MSDB under "Stored Packages" in the Object Explorer
tree. Any idea why?
Client unable to establish connection
Encryption not supported on SQL Server. (Microsoft SQL Native Client)
at
Microsoft.SqlServer.Dts.Runtime.Wrapper.Applicatio nClass.GetDtsServerPackageInfos(String bstrPackageFolder, String bstrServerName)
at
Microsoft.SqlServer.Dts.Runtime.Application.GetDts ServerPackageInfos(String
sPackageFolder, String sServerName)
"Peter Yang [MSFT]" wrote:
> Hello,
> You could click "Connect" button in Server management studio and click to
> select "Integration services", and then type the instance information you
> want.
> Hope this is helpful.
>
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> new
>
|||Hello,
To understand the issue better, will you confirm the default instance is
SQL server 2005 instance? SSIS does not support named instance anyway.
Also, from the error message, it seems that client force encryption but
server does not have certificate installed. Please check the following
settings:
Run SQL Server 2005 Network Configuration, right click SQL native client
network conigurations->Properties, and configure "force protocol
encryption" to NO.
Right click the protocol under server network configuration and also
configure "force protocol encryption" to NO.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Dumb question about SSIS
>thread-index: AcX0F5fDrM411FMOTvOM/FE4ub5KUA==
>X-WBNR-Posting-Host: 84.147.181.254
>From: "=?Utf-8?B?SmFtZXM=?=" <aa1948@.nospam.nospam>
>References: <E17165D6-8E0C-40F9-982B-9A4530B8CF5A@.microsoft.com>
<hsnnFv88FHA.4000@.TK2MSFTNGXA02.phx.gbl>
>Subject: RE: Dumb question about SSIS
>Date: Mon, 28 Nov 2005 04:31:02 -0800
>Lines: 76
>Message-ID: <36EAC47F-E63C-4DA8-9F75-ED51B80E761B@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:412425
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Thanks Peter, exactly what I was looking for.
>But now I still cannot see my package, as I'm getting following error
>message when clicking on MSDB under "Stored Packages" in the Object
Explorer
>tree. Any idea why?
>Client unable to establish connection
>Encryption not supported on SQL Server. (Microsoft SQL Native Client)
> at
>Microsoft.SqlServer.Dts.Runtime.Wrapper.Applicati onClass.GetDtsServerPackag
eInfos(String bstrPackageFolder, String bstrServerName)
> at
>Microsoft.SqlServer.Dts.Runtime.Application.GetDt sServerPackageInfos(String
[vbcol=seagreen]
>sPackageFolder, String sServerName)
>"Peter Yang [MSFT]" wrote:
to[vbcol=seagreen]
you[vbcol=seagreen]
rights.[vbcol=seagreen]
the[vbcol=seagreen]
tree[vbcol=seagreen]
starting
>
|||Both encryption settings were set to No.
Also, SQL Server 2005 is a named instance. The default instance is SQL
Server 2000.
In the "Connect to Server" dialog of management studio, I connect to
Integration Service, and as server name, the name of the machine. Does that
mean that I'm attempting to connect to the default instance? That would be
SQL 2000.
Does that mean that you cannot use SSIS on a machine where there is default
instance of SQL 2000?
"Peter Yang [MSFT]" wrote:
> Hello,
> To understand the issue better, will you confirm the default instance is
> SQL server 2005 instance? SSIS does not support named instance anyway.
> Also, from the error message, it seems that client force encryption but
> server does not have certificate installed. Please check the following
> settings:
> Run SQL Server 2005 Network Configuration, right click SQL native client
> network conigurations->Properties, and configure "force protocol
> encryption" to NO.
> Right click the protocol under server network configuration and also
> configure "force protocol encryption" to NO.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> <hsnnFv88FHA.4000@.TK2MSFTNGXA02.phx.gbl>
> Explorer
> eInfos(String bstrPackageFolder, String bstrServerName)
> to
> you
> rights.
> the
> tree
> starting
>
|||Hello,
You could still store SSIS package in filesystem other than msdb under this
situation. Since SSIS will try to access msde of default instance, you
could not store the package in msdb because it is a 2000 database.
Also, you may try the following method to change the instance SSIS
connects. However, it is not officially documented and may have issues when
running package from there
1. Edit the Configuration file MsDtsSrvr.ini.xml in the following path:
C:\Program Files\Microsoft SQL Server\90\DTS\Binn
2. Change the string <ServerName>.</ServerName>?as following:
<ServerName>MachineName\InstanceName</ServerName>
3. Save the file and Re-Start SSIS Service
Please let me know if you have further concerns or questions on this.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Dumb question about SSIS
>thread-index: AcX02Vvn5mIYncaZQVq2jfNzlN2UsA==
>X-WBNR-Posting-Host: 84.147.129.198
>From: "=?Utf-8?B?SmFtZXM=?=" <aa1948@.nospam.nospam>
>References: <E17165D6-8E0C-40F9-982B-9A4530B8CF5A@.microsoft.com>
<hsnnFv88FHA.4000@.TK2MSFTNGXA02.phx.gbl>
<36EAC47F-E63C-4DA8-9F75-ED51B80E761B@.microsoft.com>
<yI1K45L9FHA.4000@.TK2MSFTNGXA02.phx.gbl>
>Subject: RE: Dumb question about SSIS
>Date: Tue, 29 Nov 2005 03:38:03 -0800
>Lines: 159
>Message-ID: <43861D30-F658-4906-B197-CE2D9DE8D97C@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:412564
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Both encryption settings were set to No.
>Also, SQL Server 2005 is a named instance. The default instance is SQL
>Server 2000.
>In the "Connect to Server" dialog of management studio, I connect to
>Integration Service, and as server name, the name of the machine. Does
that
>mean that I'm attempting to connect to the default instance? That would be
>SQL 2000.
>Does that mean that you cannot use SSIS on a machine where there is
default[vbcol=seagreen]
>instance of SQL 2000?
>
>"Peter Yang [MSFT]" wrote:
rights.[vbcol=seagreen]
>Microsoft.SqlServer.Dts.Runtime.Wrapper.Applicati onClass.GetDtsServerPackag
>Microsoft.SqlServer.Dts.Runtime.Application.GetDt sServerPackageInfos(String
click[vbcol=seagreen]
so[vbcol=seagreen]
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl[vbcol=seagreen]
save[vbcol=seagreen]
Package"[vbcol=seagreen]
create a
>
|||This sounds like a solution. Many thanks.
"Peter Yang [MSFT]" wrote:
> Hello,
> You could still store SSIS package in filesystem other than msdb under this
> situation. Since SSIS will try to access msde of default instance, you
> could not store the package in msdb because it is a 2000 database.
> Also, you may try the following method to change the instance SSIS
> connects. However, it is not officially documented and may have issues when
> running package from there
> 1. Edit the Configuration file MsDtsSrvr.ini.xml in the following path:
> C:\Program Files\Microsoft SQL Server\90\DTS\Binn
> 2. Change the string <ServerName>.</ServerName>?as following:
> <ServerName>MachineName\InstanceName</ServerName>
> 3. Save the file and Re-Start SSIS Service
> Please let me know if you have further concerns or questions on this.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> <hsnnFv88FHA.4000@.TK2MSFTNGXA02.phx.gbl>
> <36EAC47F-E63C-4DA8-9F75-ED51B80E761B@.microsoft.com>
> <yI1K45L9FHA.4000@.TK2MSFTNGXA02.phx.gbl>
> that
> default
> rights.
> click
> so
> TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
> save
> Package"
> create a
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment