February 28, 2017 at 10:16 am
Hello,
I have an issue where I'm unable to connect to SSIS 2016 SP1 with Integration Services version #13
Below is the following error that I'm receiving:
The SSIS service is running like it should and I've already added my credentials within the DCOM Config file, even though this error is different.
I'm wondering if anyone has experienced the same issue as I. I've come up empty with my research.
Any information would be much appreciated.
Thank you
February 28, 2017 at 10:26 am
check the content of C:\Program Files\Microsoft SQL Server\130\DTS\Binn\MsDtsSrvr.ini.xml and confirm server name is correct:
<?xml version="1.0" encoding="utf-8"?>
<DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown>
<TopLevelFolders>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB</Name>
<ServerName>.</ServerName>
</Folder>
<Folder xsi:type="FileSystemFolder">
<Name>File System</Name>
<StorePath>..\Packages</StorePath>
</Folder>
</TopLevelFolders>
</DtsServiceConfiguration>
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
February 28, 2017 at 11:25 am
Hi Henrico,
I forgot to mention within the original post that I've already made the necessary changes to the MsDtsSrvr.ini.xml file and restarted the service, but still receive the same error.
February 28, 2017 at 11:40 am
PFlorenzano-641896 - Tuesday, February 28, 2017 11:25 AMHi Henrico,I forgot to mention within the original post that I've already made the necessary changes to the MsDtsSrvr.ini.xml file and restarted the service, but still receive the same error.
Have you verified the connection properties and the service configurations i.e. port etc.? Any firewalls in the way?
😎
February 28, 2017 at 12:45 pm
Eirikur Eiriksson - Tuesday, February 28, 2017 11:40 AMPFlorenzano-641896 - Tuesday, February 28, 2017 11:25 AMHi Henrico,I forgot to mention within the original post that I've already made the necessary changes to the MsDtsSrvr.ini.xml file and restarted the service, but still receive the same error.
Have you verified the connection properties and the service configurations i.e. port etc.? Any firewalls in the way?
😎
Yes we have our firewall enabled and the MsDtsSrvr.exe application has been added to the exceptions list.
February 28, 2017 at 12:52 pm
PFlorenzano-641896 - Tuesday, February 28, 2017 12:45 PMEirikur Eiriksson - Tuesday, February 28, 2017 11:40 AMPFlorenzano-641896 - Tuesday, February 28, 2017 11:25 AMHi Henrico,I forgot to mention within the original post that I've already made the necessary changes to the MsDtsSrvr.ini.xml file and restarted the service, but still receive the same error.
Have you verified the connection properties and the service configurations i.e. port etc.? Any firewalls in the way?
😎Yes we have our firewall enabled and the MsDtsSrvr.exe application has been added to the exceptions list.
have you tried to telnet to the port?
😎
February 28, 2017 at 1:22 pm
I did and the port is open
February 28, 2017 at 1:31 pm
Do you get the same response when trying to connect from a different server/workstations SSMS?
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
February 28, 2017 at 1:37 pm
PFlorenzano-641896 - Tuesday, February 28, 2017 1:22 PMI did and the port is open
Then this is an authentication issue!
😎
February 28, 2017 at 1:49 pm
Henrico Bekker - Tuesday, February 28, 2017 1:31 PMDo you get the same response when trying to connect from a different server/workstations SSMS?
Yes I tried three different workstations and all three come up with the same message within SSMS. The SSIS service is up and running on the server, and myself and another co-worker have verified the port is open.
February 28, 2017 at 9:57 pm
This was removed by the editor as SPAM
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply