November 9, 2021 at 3:59 pm
Hey y'all. I've just inherited a SQL2019 server that uses PolyBase to hit some other SQL Servers. I'm new to Polybase and could really use some help.
The original server works fine: [Server-Prod]. But, I used our VM software to clone the server to make a development VM instance with a different name: [Server-Dev]. I did do the server instance Drop/Add server to get the right name on [Server-Dev]. Almost everything seems to work on [Server-Dev] except the external tables.
When I try to query any of the External Tables, I get the error below. Some searching and I found some troubleshooting tip about the l_certSignPolyBaseAuthorize needing the SysAdmin role, which it does. Any pointers in the right direction would help greatly.
Msg 110064, Level 16, State 1, Line 1
110064;Windows authentication failed. Possible network configuration issue. Please contact your system administrator.
November 10, 2021 at 4:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
November 15, 2021 at 5:33 pm
My first thought would be firewall or permissions.
Permissions could be a problem if the SQL Server Service account (or Agent service account or the Polybase service account... not 100% certain on this one) doesn't have permission to the external data source.
Firewall could be a problem if the new VM cannot see the external system that holds the external tables.
Depending on the external systems, it may not hurt to look at the logs on them to see if anything looks out of place (such as authentication errors).
My last thought is that the external systems have restrictions in place with regards to which machines can access them and your new VM isn't in the allow list.
But, I have not used external tables or polybase before; the above are just some general "authentication failed" things to look at with new systems and a little bit of googling on my end to learn a little bit about external tables.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply