I have installed WSS 3.0 and found that the network accounts that i had created were not recognised during the install, so i used my own network account to get things running. I am trying to switch everything to run with the correct accounts. Is there any information anywhere on how to do this (which services etc need what type of account) - i guessed that periodically i would want to change the account passwords...I am getting the following error logged;The Execute method of job definition Microsoft.SharePoint.Administration.SPUpdateWorkerProcessGroup (ID 3f79c474-1a25-40af-bf93-43cc04c73a3c) threw an exception. More information is included below.Failed to connect to an IPC Port: Access is denied.Can anyone shed some light on this for me?regardsThe Mighty Puzzled

I'm getting the same error. It started happening after I added the MOSS service account to the Farm Administrator's group in order to fix a different issue with the users not being able to create their own personal My Sites. Did you ever get an answer on this or figure it out?

This error occurs when the Windows SharePoint Services Timer windows service does not have enough rights. If the account this service runs under has had a password change, you will need to update the password in the service control manager for Windows services. Right-click on this windows service, go to Properties, then click on the Logon tab and re-enter the credentials. The IPC port is the inter-process communication port where the job is trying to handshake with the actual work to be done. The account this service runs under may not have enough permissions to execute this specific job as well.

The error is beacause the account for Windows SharePoint Services Timer have to be local administrator. for change user and password use: stsadm -o updatefarmcredentials -userlogin <domain\username> -password <newpassword> http://support.microsoft.com/kb/934838/en-us Regards Francesco

Hello, Try to give to the windows Sharepoint services Timer service (windows services), the same credential as the account you use to connect to your central administration console. It is a best practice. Regards, Noureddine

OK, I verified all of the following: - The account is a member of the Local Administrator's group. - The username/password for the Windows SharePoint Services Timer is up-to-date and the password is accurate. The service is running successfully with only this one failure. I went in and re-entered it just to be sure. I also reset IIS to make sure the changes took effect. - I can log in as this account to the Central Administration tool and browse to see the Timer Job Status, etc. - The account is a member of the Farm Administrator's Group. - If I go to Central Administration > Operations > Timer Job Status, the only job that is failing is the SharePoint Worker Process Group Update job. There is a Retry in the Status column next to it. All the other jobs have a status of Succeeded. - The specific error in the Event Viewer is: The Execute method of job definition Microsoft.SharePoint.Administration.SPUpdateWorkerProcessGroup (ID c533be13-028d-466e-9e00-d1f86e8364ee) threw an exception. More information is included below. Failed to connect to an IPC Port: Access is denied. - If I go to the Help for this particular Event ID, I see the following: One of two problems occurred. Either a timer job raised an exception or a timer job definition could not be loaded. Determine which assembly was faulty. Determine whether it was a Windows SharePoint Services 3.0 assembly, and then determine its status. The solution seems to recommend either disabling (Deleting?) the job in question or repairing the Windows SharePoint Services installation. I don't like the second option, but I don't want to delete the job since I have no idea what it does. Does anybody know what this particular job does?

Another thing to check is that the AppPool user for your site is running with enough permissions. The SPUpdateWorkerProcessGroup is probably involved in delegating jobs to different worker processes as part of the SharePoint process. This would be similar to the IIS Worker Process Group (WPG). If the App Pool does not have enough permissions for some of your jobs then its possible that the worker process thread is unable to execute also because it does not have enough permissions.

Just to clarify here's the steps: Run the following command from the command line - this will update Central Admin: stsadm -o updatefarmcredentials -userlogin <domain\username> -password <newpassword> Once this completes run: iisreset /noforce Next you'll need to go into the properties in IIS for each of the other web applications and update the username and/or password on the Identity tab. Once you've done this you'll need to stop and start each web ap for the change to take effect. I just tested these steps on my VM and it works like a charm. For more information: http://blogs.msdn.com/joelo/archive/2006/08/22/712945.aspx John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

Hi there, I had the exact same scenario, except I had the "Application Server Administration Service Timer Job" failing in addition to the "SharePoint Worker Process Group Update" jobs. I couldn't run stsadm -o execadmsvcjobs command, it failed with the same IPC port issue you described above. I solved this by starting the Windows SharePoint Services Administration service in the services MMC. That is the service that is involved here I believe, not the Windows SharePoint Services Timer service. I'm not sure why that service wasn't started to begin with. FWIW, the Administration service out-of-the-box was configured to run under Local System account, which seems fine sincethe jobs aren'tfailing now. Hope that helps. Adam Toth

Thank you very much. The last post helped!

hi Francesco,will u tell me cmd for creating a new user account through cmdline

Hi We have struggled with this same problem. At the end we realised that someone deleted the SharePointSSP account out of Active Directory. This account has db_datareader, db_datawriter and ProjectServerRole on the database in SQL, I also made sure the AppPool was running under that account, as well as the two services, Microsoft Office Project Server Events Service and Microsoft Office Project Queue Service Side note: On the http://sspadmin.companyname.com:82/ssp/admin/_layouts/managepwa.aspx page, it doesn't matter what the administrator account is, and I haven't been able to change it?! Hope it helps

hi Francesco, will u tell me cmd for creating a new user account through cmdline You can create a user via the command line using the dsadd command: dsadd userUserDN [-samidSAMName] -pwd {Password|*} http://technet.microsoft.com/en-us/library/cc784390(WS.10).aspx#BKMK_cmd