SSIS and maintenance plans

  • Where I work Service pack 2 was installed on an I64 Windows Server 2003 hardware platform running SQL Server 2005 Enterprise Edition.  The Service Pack 2 distribution(current service pack) was applied 6/15/2007.
     
    There was a database installed as a domain user for an application.  That user took exclusive control of the database.
     
    When SQL Server Service Pack 2(SQLServer2005SP2-KB21896-x64-ENU.exe) was installed, the step for the database failed but the rest were completed.  The former DBA saw the error, had the file permissions changed and reapplied the Service pack and the database portion was successful.  The old DBA then applied the update to Service Pack 2(SQLServer2005-KB934459-x64-ENU.exe)
     
    After connecting to the Server using remote desktop and accessing SSIS the following error appears:
     

    Error message when you connect to an instance of SQL Server 2005 Integration Services by using SQL Server Management Studio on a computer that has a 64-bit processor: "Connect to SSIS Service on machine <computer_name> failed"

     
    Additionally, any new maintenance jobs created cannot be modified
     
    I've researched this and found the following recommended solutions:

    Method 1

    <script type=text/javascript>loadTOCNode(2, 'resolution');</script>To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

    913089 (http://support.microsoft.com/kb/913089/) How to obtain the latest service pack for SQL Server 2005

    Method 2

    <script type=text/javascript>loadTOCNode(2, 'resolution');</script>Install the hotfix packages in the following order:

    SQL Server 2005
    SQL Server 2005 Analysis Services
    SQL Server 2005 Integration Services
    SQL Server 2005 Notification Services
    SQL Server 2005 Reporting Services
    SQL Server 2005 Tools

     
    Obviously Method 1 will not work.  The newer Service Pack was used the first time.  Additionally, the event logs were destroyed so I can't check them to see the order of the hotfixes.  Being new at this how does one get and apply the latest hotfixes in the order described in step 2?

  • The problem was there are 2 different dlls, 1 for 32 bit and the other 64 bit. We had to register the other dll that did not get registered

Viewing 2 posts - 1 through 1 (of 1 total)

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