Hi.
I'm very tired and irritated by now. Around two weeks of dances with bells-n-whistles... Pretty easy task, and so much time wasted - would love to get some payment from Microsoft for this.
So, very simple case. Developer machine. Installed from scratch:
Windows server 2016 - Hostname
SQL Server 2016 - Hostname\DEV (SQL, AS, SSIS)
SSDT 17.1
SSMS 17.1
I'm running SSMS under admin privileges, and trying to connect SSIS Services on Hostname (not SQL Server)
I've already got many, many different errors (we still can't develop normaly in Visual Studio 2015.3), always do much googling to find a workaround for them... but this... I just can't stand that stupidity any more.
And create and tune jobs and steps on SSIS packages inside them.
But not from SSMS 17.1! Why?!
I'm very tired and irritated by now. Around two weeks of dances with bells-n-whistles... Pretty easy task, and so much time wasted - would love to get some payment from Microsoft for this.
So, very simple case. Developer machine. Installed from scratch:
Windows server 2016 - Hostname
SQL Server 2016 - Hostname\DEV (SQL, AS, SSIS)
SSDT 17.1
SSMS 17.1
I'm running SSMS under admin privileges, and trying to connect SSIS Services on Hostname (not SQL Server)
I've already got many, many different errors (we still can't develop normaly in Visual Studio 2015.3), always do much googling to find a workaround for them... but this... I just can't stand that stupidity any more.
TITLE: SSIS Execution Properties
------------------------------
Connecting to the Integration Services service on the computer "HostName" failed with the following error: "The specified service does not exist as an installed service.".
This error can occur when you try to connect to a SQL Server 2005 Integration Services service from the current version of the SQL Server tools. Instead, add folders to the service configuration file to let the local Integration Services service manage packages
on the SQL Server 2005 instance.
WTF?! That 2005? There is no mention about 2005 ANYWHERE on this machine!
Let me show you the pictures!
All versions is up-to-date. Microsoft, what do you want from administrators?
Btw, I can normally connect to the remote SSIS Hostname from other machine with SSMS 16.5 installed.And create and tune jobs and steps on SSIS packages inside them.
But not from SSMS 17.1! Why?!