Local machine login failure on new install - why is local machine trying to login?

  • Hi,

    I've built myself a test install of SQL Server 2017 (Developer, RTM-CU1) including the agent, SSAS, SSIS (and Scale out), PolyBase and Analysis Services and I have added Power BI ReportServer.

    Everything appears to be working normally but I am continually getting login failures from the domain machine account but I cannot figure out what is attempting to make that login - looking for help trying to pin it down please!

    Error message is :
    Error 18456, Severity 14, State 5
    Login failed for user "mydomain\machinename$". Reason could not find a login matching the name provided [Client Local machine]

    Yes there is no account added for the domain\machine name - what I am struggling to figure out is what is attempting to use the account and hence why I need to add it - all I have on the box is a base Windows build (along with all my domains' stuff like AV so I'm not ruling out something local to us but this does appear specific to this machine) and the SQL parts. 

    The default trace shows audit login failed for the machine name$, our domain from this host but usefully the application name is only ".net sqlclient data provider" attempting to make a non dac connection but not other detail that might point in the right direction.

    We aren't see the problem on any other version of SQL so looks like something 2017 related and hoping someone else has already seen this.

    Thanks

    Update : I've been turning services off to figure out which is the problem - down to 6 possibilities....

  • Turns out that SSISScaleOutMaster is the problem - I hadn't gotten around to creating the SSIS catalog, all sorted now!

  • This was removed by the editor as SPAM

Viewing 3 posts - 1 through 2 (of 2 total)

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