THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Greg Low (The Bit Bucket: IDisposable)

Ramblings of Greg Low (SQL Server MVP, MCM and Microsoft RD) - SQL Down Under

SQL Server 2016 Polybase Services stuck in Change Pending state

I’ve been using the Polybase services in SQL Server 2016 all throughout the pre-release period without any issue.

When I tried using them in the GA (Generally Availability) release, I could never get the two Polybase services to start. They were always stuck in a “Change Pending” state. Trying to start them in SQL Server Configuration Manager basically made SSCM look like it was hung.

Trying to use the Polybase services to create an external data source returned:

TCP Provider: No connection could be made because the target machine actively refused it.


Fellow MVP John Paul Cook came to the rescue today. He previously had an issue with TCP Chimney support and noted that it looked similar.

True enough, the problem was that TCP wasn’t an enabled protocol on my SQL Server install on my machine. Enabling TCP and restarting made all good.

Thanks John !

Published Wednesday, July 6, 2016 10:39 AM by Greg Low

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



John Payl Cook said:

Make that former MVP and now Microsoft employee.

July 13, 2016 4:35 PM

Greg Low said:

Too true! So used to John being an MVP for so long ! But he still participates in our mailing lists :-)

July 13, 2016 4:51 PM

John Paul Cook said:

I wish I would have spelled my name correctly.

July 13, 2016 11:14 PM

Greg Low said:

We know who you are :-)

July 13, 2016 11:19 PM

Leave a Comment


This Blog



No tags have been created or used yet.


Privacy Statement