none
Microsoft Project Server Event Service 2010 and Microsoft Project Server Queue Service 2010 services are unable to start and are in disabled status in one of the load balance server.

    Question

  • We are using Sharepoint 2010 with Project Server 2010. The farm architecture is like this. We have two load balancing servers (S1 and S2) where Sharepoint 2010 Central Admin,IIS 7.5, Windows server R2 Standard with 64 bit and Microsoft Sharepoint services. Both servers are mirror image (same). Database is on a server (S3)and Reporting db is on another serve (S4). Ad is on a defferent server (S5). 3 weeks back there is a EMET patch update was done on these two load balacing application (farm) servers (S1 and S2). Due to which one of the Server(S2) got shut down. And in another server (S1) Microsoft Project Server Event Service 2010 and Microsoft Project Server Queue Service 2010 services are not running and Status type is Disabled and Status is blank. In PWA, the queue is strucked. So we restarted S2 and the Queue got cleared. In S2, these services are running without any issues. Services in S1 and S2 are using same AD account and this is a Service account.In S1, we tried to start these services by changing the startup type to Automatic and run. It gave us error "Windows could not start the Microsoft Project Server Event Service 2010 service on Local Computer. Error 1065: The service did not start due to logon failure.'' Same with Microsoft Project Server Queue Service 2010 service. We tried to run by setting manuall, same error. Other services are ruuning fine with same AD account in S1. We check the windows event log, and found below logs. And the services are automatically disabled after few minutes.

    The Microsoft Project Server Events Service 2010 service failed to start due to the following error:

    The service did not start due to a logon failure.


     
    The ProjectEventService14 service was unable to log on as Domain\account name with the currently configured password due to the following error:

    Logon failure: unknown user name or bad password.

    Wednesday, September 04, 2013 3:00 PM

Answers

  • Hi,

    Thanks a lot for your support.

    I stopped and started Project Application Service under Central Admin -->Manage Services on Server for S1. The services started running. Thanks once again.

    Friday, September 13, 2013 12:16 PM

All replies

  • Did you try restarting same services manually on S2?


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Wednesday, September 04, 2013 4:50 PM
  • Hi,

    Thanks for your reply.

    No, we did not try to run these services manually on S2, as they are running without any issues in Automatic mode.

    Thanks & Regards,

    Kiran.

    Thursday, September 05, 2013 8:34 AM
  • Hi,

    Thanks for your reply.

    No, we did not try to run these services manually on S2, as they are running without any issues in Automatic mode.

    Thanks & Regards,

    Kiran.


    Please suggest the next steps to over come this issue.
    Thursday, September 05, 2013 1:58 PM
  • If you do so, you might experience the same issue. Either password has changed or account has been locked in the active direcrolty.

    If project service account is different than web application pool and farm account, you might consider to change the password in AD and update the same in Project services on all app servers.


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Thursday, September 05, 2013 5:19 PM
  • Hi,

    Thanks for your reply.

    Might be same issue if we start manullay in S2, but the service account is not locked as per AD team. We checked the SharePoint Central Admin and found that the password is changed and it is used as farm account also. Is there any way we can find, may I know why these services are disabled after that patching ?  Please suggest the next steps.

    Friday, September 06, 2013 11:04 AM
  • Are you using Automatic password update or someone manually changed the password of this service\farm account in AD?

    To update the farm account you need to execute following SharePoint PowerShell command

    Set-SPManagedAccount -Identity Domain\User -USeExistingPassword

    Once done, reset IIS and verify that all application pools used by this services account are started , if not you need to update the password for each application pool manually and start the application pool. Repeat this step on each server in the farm. You don't have to execute above command on each server though

    Refer following TechNet for more info

    http://technet.microsoft.com/en-us/library/ff724280(v=office.14).aspx#section3


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Friday, September 06, 2013 4:18 PM
  • Hi,

    Thanks for the reply.

    Yes, automatic password update was setup in Central Admin. Before executing the above PowerShell command. I would like to know, will this command uses existing password to reset or update the farm/service account. We had a discussion with our Program team, they suggested to stop and start Project Application Service under Central Admin -->Manage Services on Server. I gone through some sites, even they suggested to do this. My concern is will this hamper productivity. If I stop and start this service in Central Admin, will it create any other problems. This is running in both load balancing servers S1 and S2. But issue is with S1. Will it lead to bad data? Shall I do this during business hours or non-business hours? If the service fail to start from Central Admin, they suggested us to check the windows event logs.And they suggested us to check whether CRL's are expired or not?  How to check this? And they suggested us to check whether timeout is causing perfomance issue? How to check this? And they ask us to check timer job, but it is fine, no issue. They suggested us to disconnect and reconnect S1. How to do this and is there any precautions do we need to take before doing this?

    Please suggest.

    Thanks,

    Kiran.

    Thursday, September 12, 2013 3:17 PM
  • Yes, you can stop and start services form central admin and you need to specifically select the server from Manage Services in the farm page. Make sure to select S1 server. Before doing this if you make sure that there are no pending or processing jobs in the Project Server queue, there wont be any impact.

    I am not sure about CRL's. For timeout issue, error in the event log would be different, like error 1053: service could not start in timely fashion

    Non-business hours would be appropriate , disconnecting and reconnecting the server would be last option.

    Logon failure: unknown user name or bad password

    Above error message is clear indication of password mismatch. If you change the password annually in AD you could use above PowerShell command

    You could also try following two registry settings

    Once the registry editor has been opened navigate to
    HKLM\System\CurrentControlSet\Control

    Create a new DWORD key with the following value:
    ServicesPipeTimeout DWORD 60000 (decimal)

    Note: 60000 = 60 Seconds.

    Next, look for the WaitToKillServiceTimeout key – take note of its current value – and then change the value to 120000
    Note: 120000=120 Seconds.


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you.This can be beneficial to other community members reading the thread.


    Friday, September 13, 2013 4:42 AM
  • Hi,

    Thanks a lot for your support.

    I stopped and started Project Application Service under Central Admin -->Manage Services on Server for S1. The services started running. Thanks once again.

    Friday, September 13, 2013 12:16 PM