Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Problem accessing a SSIS Package

Problem accessing a SSIS Package

Scheduled Pinned Locked Moved Database
helpsql-serversysadmincsharpc++
4 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    mysorian
    wrote on last edited by
    #1

    My evaluation copy ran-out and I uninstalled the previous and installed another evaluation edition. The installation was successful. I created a SSIS package importing a table from Oracle 10G XE to the SQL 2005 on my machine. I saved the package on the server. The SSIS service is running but when I try to refresh the node, I get this message. The help link leads to no where(Hello, Microsoft!): -------------------------------------- TITLE: Microsoft SQL Server Management Studio ------------------------------ Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) For help, click: http://go.microsoft.com/fwlink? ProdName=Microsoft+SQL+Server&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: Login timeout expired An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. TCP Provider: No connection could be made because the target machine actively refused it. (Microsoft SQL Native Client) ------------------------------ Login timeout expired An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. TCP Provider: No connection could be made because the target machine actively refused it. (Microsoft SQL Native Client) ------------------------------ My efforts so far: :-DI have verified the items in the Surface area screen, everythign looks good. SSIS service has started. :-DBoth the Network Server TCP/IP dynmaic port and the SQL Client TCP/IP dynamic port are the same. :-DI have no problem logging in to any of the services. :mad:But I get this message. :mad:I tried to create a package from Visual Studio, but that also did not succeed. :rolleyes:In my previous set up, I created perhaps 1/ 2 dozen different packages. I am puzzzled. I appreciate if some one could throw some light.

    M D 2 Replies Last reply
    0
    • M mysorian

      My evaluation copy ran-out and I uninstalled the previous and installed another evaluation edition. The installation was successful. I created a SSIS package importing a table from Oracle 10G XE to the SQL 2005 on my machine. I saved the package on the server. The SSIS service is running but when I try to refresh the node, I get this message. The help link leads to no where(Hello, Microsoft!): -------------------------------------- TITLE: Microsoft SQL Server Management Studio ------------------------------ Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) For help, click: http://go.microsoft.com/fwlink? ProdName=Microsoft+SQL+Server&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: Login timeout expired An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. TCP Provider: No connection could be made because the target machine actively refused it. (Microsoft SQL Native Client) ------------------------------ Login timeout expired An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. TCP Provider: No connection could be made because the target machine actively refused it. (Microsoft SQL Native Client) ------------------------------ My efforts so far: :-DI have verified the items in the Surface area screen, everythign looks good. SSIS service has started. :-DBoth the Network Server TCP/IP dynmaic port and the SQL Client TCP/IP dynamic port are the same. :-DI have no problem logging in to any of the services. :mad:But I get this message. :mad:I tried to create a package from Visual Studio, but that also did not succeed. :rolleyes:In my previous set up, I created perhaps 1/ 2 dozen different packages. I am puzzzled. I appreciate if some one could throw some light.

      M Offline
      M Offline
      mysorian
      wrote on last edited by
      #2

      One of my statements is wrong. I could create a package in Visual Studio, but I could not access this in SSIS.

      1 Reply Last reply
      0
      • M mysorian

        My evaluation copy ran-out and I uninstalled the previous and installed another evaluation edition. The installation was successful. I created a SSIS package importing a table from Oracle 10G XE to the SQL 2005 on my machine. I saved the package on the server. The SSIS service is running but when I try to refresh the node, I get this message. The help link leads to no where(Hello, Microsoft!): -------------------------------------- TITLE: Microsoft SQL Server Management Studio ------------------------------ Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) For help, click: http://go.microsoft.com/fwlink? ProdName=Microsoft+SQL+Server&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: Login timeout expired An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. TCP Provider: No connection could be made because the target machine actively refused it. (Microsoft SQL Native Client) ------------------------------ Login timeout expired An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. TCP Provider: No connection could be made because the target machine actively refused it. (Microsoft SQL Native Client) ------------------------------ My efforts so far: :-DI have verified the items in the Surface area screen, everythign looks good. SSIS service has started. :-DBoth the Network Server TCP/IP dynmaic port and the SQL Client TCP/IP dynamic port are the same. :-DI have no problem logging in to any of the services. :mad:But I get this message. :mad:I tried to create a package from Visual Studio, but that also did not succeed. :rolleyes:In my previous set up, I created perhaps 1/ 2 dozen different packages. I am puzzzled. I appreciate if some one could throw some light.

        D Offline
        D Offline
        Dave Kreskowiak
        wrote on last edited by
        #3

        mysorian wrote:

        My evaluation copy ran-out and I uninstalled the previous and installed another evaluation edition

        Do you want to read that again and guess what a probably cause of the problem is? Do you think it's entirely possible that the new installation knows that you already had an evaluation edition installed and it expired? Dave Kreskowiak Microsoft MVP - Visual Basic

        M 1 Reply Last reply
        0
        • D Dave Kreskowiak

          mysorian wrote:

          My evaluation copy ran-out and I uninstalled the previous and installed another evaluation edition

          Do you want to read that again and guess what a probably cause of the problem is? Do you think it's entirely possible that the new installation knows that you already had an evaluation edition installed and it expired? Dave Kreskowiak Microsoft MVP - Visual Basic

          M Offline
          M Offline
          mysorian
          wrote on last edited by
          #4

          The evaluation edition was completely removed as any new install flags any remnants that needs removing. I was instructed during new install to move my 'Data' to another location which I did. The packages although saved to 'Sql Server' had created 'dtsx' files as well. However, from VS 2005 I can create a package, but cannot see, or access it in the SQL 2005 Management Studio. I wish error messages could have been more friendly [see my comments in the article on SQLCMD]. I am technical writer and I routinely, meticulously document what I do. Here are my recent articles. Thnaks for your fast response. Moving Data from SQL Server 2000 to SQL Server 2005 Querying Databases in SQL Server 2005 SQL2000 Data Transfer is a snap with SQL 2005 On using the SQLCMD in SQL 2005 Server Generating and Hosting a SQL Server Reporting Services Report Using SQL Server 2005 Business Intelligence Development Studio These and other articles may be found at:http://www.angelfire.com/vt2/hodentek/[^]

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups