For some reason , the report server is trying to login as <domainname>\<machine name> - its supposed to be <domain>\<user name> or ASPNET or Network Service Authority - I have no clue why it is pickin gup machine name. Any ideas and how to fix
SQL Server Reporting Services
For some reason , the report server is trying to login as <domainname>\<machine name> - its supposed to be <domain>\<user name> or ASPNET or Network Service Authority - I have no clue why it is pickin gup machine name. Any ideas and how to fix
We have service credentials as web identity sign-on. And we are using IIS 5.1 so app pool does not mean the same as what you were talking about and there is no IIS_WPG that I know of with 5.1. We cannot go to IIS 6.0 as that would make us install software that would be incompatible with the rest of our system. Sorry the IIS version would have been helpful if I would have given that earlier.
What we think is the case at this time, is that the profile of the user is screwed up and is somehow thinking the username is actually the machine name at this time. We're looking into it from that angle but would appreciate any other suggestions.
You mentioned it might be running as Network Service. A process running as Network Service, Local Service or Local System on one machine will log on using the machine account - i.e. [domain name]\[machine name] when connecting to another machine. This is a perfectly reasonable setup, which can be made to work by granting the machine account permissions in your database(s), though it may also involve setting the AD option 'Trust for Delegation' onn the account.
I don't think the problem is anything to do with user profile problems