Post reply

Integration Services - server name is blank

  • November 27, 2019 at 8:37 am

    #3701445

    We just installed the sql 2017 SE with the SSDT tool, SSMS 18.4.

    SSIS is selected during the installation. SQL 2017 SE is also updated with latest patch.

    We are able to access the database engine using the connect explorer.

    However when we tried to connect to the Server Type; Integration Services, the Server name is blank.

    service2

    After enter the server name and click connect we encounter below error.

    service3

    In our old SQL 2008 R2, there is a local server name and we are able to connect to it without issue.

    Anything that we miss out here. This is a newly installed server.

  • November 27, 2019 at 11:18 am

    #3701487

    Which version did you installed? Was that Client or Server?

    SQL Server Carpenter - Consultant & Trainer
    Author of Learn T-SQL from Scratch

  • November 27, 2019 at 12:56 pm

    #3701503

    try SSMS 16.x if you really want to connect to Integration Services because you did it 20 years ago so. If you don't want to live in the past, connect to the DB Engine and manage via SSISDB / Integration Services Catalogs.

  • November 28, 2019 at 12:18 am

    #3701701

    We are running on SQL Server 2017 SE with SSMS 18.4.

  • November 28, 2019 at 2:23 am

    #3701716

    DinoRS wrote:

    try SSMS 16.x if you really want to connect to Integration Services because you did it 20 years ago so. If you don't want to live in the past, connect to the DB Engine and manage via SSISDB / Integration Services Catalogs.

    It works in SSMS 17.9 on our other system. I will have to downgrade that to that version.

    The reason for that is that we want to migrate the maintenance plan, DTS packages by export and import into the new DB and upgrade the package using the SSMS tools.

    We will this work for this case?

Viewing 5 posts - 1 through 4 (of 4 total)

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