Hi, I get the NT AUTHORITY\SYSTEM login access error in SQL Server. However I observe that it is causing from Sharepoint where OfficeServerApplicationPool is in NetworkService. I want to change it to a valid domain account - but when I change and restart IIS, it reverts back to networkservice...Not sure how. Appreciate any thoughts in this. Regards, kart

I don't have any options in Service Accounts for OfficeServerApplicationPool. Service accounts options:I have only one web application Pool: Windows Sharepoint Services Web Application.I have two Application Pools: one for the site admin and one for the web application. any idea?Sara

Hi Sara,I have exactly the same issue, did you manage to solve this problem?

With exactly the same problem, there is no need to post both a reply to an existing thread and two completely new posts with the same title. Either post to an existing thread or post ONE new thread not both. I have deleted the duplicates. (Moderator)WSS FAQ sites: WSS 2.0: http://wssv2faq.mindsharp.com WSS 3.0 and MOSS 2007: http://wssv3faq.mindsharp.com Total list of WSS 3.0 and MOSS 2007 Books (including foreign language titles) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx

Check that please:http://weblogs.asp.net/erobillard/archive/2007/07/06/how-to-change-service-accounts-and-their-passwords-in-moss-and-wss-3-0.aspxJuan Pablo. http://surpoint.blogspot.com/

Alpesh, Thank you for responding. OfficeServerApplicationPool is not one of the application pools that appears in the list of application pools when the "Windows SharePoint Services Web Application" web service is selected (the only option) -- as noted previously by Sara_111 and Damian_K, after which Mike Walsh responded, "With exactly the same problem, there is no need to post both a reply to an existing thread and two completely new posts with the same title."

KjellSJ is right. If you want or need to change the identity of the OfficeServerApplicationPool so Office Server Web Services runs under a domain account, you'll need a new app pool. Changing the identity of OfficeServerApplicationPool is not possible: SPTimerV3 (the Windows SharePoint Services Timer) will simply change it back to NetworkService! We're running negotiate (Kerberos) throughout our medium farm (1 app and 2 WFEs). We ran into all sorts of problems with Excel Services and Search using the OfficeServerApplicationPool as NetworkService. To solve this, we: Copied OfficeServerApplicationPool and changed the copy's identity to the server farm account (a domain account) on each server Registered SPNs for the HTTP protocol for each of the servers in the farm under the server farm account (this had been done previously, anyway) (i.e.: "setspn -a HTTP/[server] MYDOMAIN\farmaccount" and "setspn -a HTTP/[server].domain.x MYDOMAIN\farmaccount" where [server] equalled "sp_wfe1", "sp_wfe2", and "sp_app"). Changed the app pool used by "Office Server Web Services" web site to the new app pool copy (did not change the app pool used by the shared services application found within this site) None of the methods listed in the article referenced by Juan Pablo (jpussacq) will change the identity of the OfficeServerApplicationPool.