Data Package getting "Login failed for user 'Domain\ComputerName$" error

PROBLEM

If you try to use Windows Authentication while creating a new Data Package and getting an error like this with these steps:

Screen_Shot_2019-03-12_at_12.36.41_PM.png

Screen_Shot_2019-03-12_at_12.37.30_PM.png

Screen_Shot_2019-03-12_at_3.19.13_PM.png

Screen_Shot_2019-03-12_at_3.23.13_PM.png

Screen_Shot_2019-03-12_at_12.41.34_PM.png

Screen_Shot_2019-03-12_at_12.41.59_PM.png

PLEASE NOTE: The user indicated in the error message is different between an environment that uses domain and Active Directory and one without. In an environment that uses domain and Active Directory you should see the user as a computer account (a user name with a "$" at the end) as shown in the screenshot above. In an environment without domain and Active Directory the user likely to be shown as ApplicationPoolIdentity which is the default identity for an application pool. 

 

RESOLUTION

This is caused by lack of privilege of the account that runs the Analyzer's application pool, you can find out which account Analyzer application pool is using via IIS:

Screen_Shot_2019-03-12_at_3.26.52_PM.png

To resolve this simply specify a different account for the application pool via Advanced Settings

Screen_Shot_2019-03-12_at_3.39.42_PM.png

NOTE:
This account can be a Managed Service Account that you have created (for environment with AD and domains)
Screen_Shot_2019-03-12_at_3.42.26_PM.png
Or simply the local administrator account like Administrator for environment without AD and domains. 

 

then add the account under the SQL Server Security folder. If you have specified the local Administrator as identity in the previous step then you might be able to skip the following since the local administrator most likely has already been added by the SQL Server Setup program during SQL Server initial installation and configuration. 

Screen_Shot_2019-03-12_at_3.10.10_PM.png

and grant necessary privileges. 

Screen_Shot_2019-03-12_at_3.10.47_PM.png

 

This should resolves the problem. 

 

 

 

 

 

 

 

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.