Log onto ServicePulse - vmnsbdev1app01:81/#/ (make sure the configurations are as follows):

Go to Failed Messages and group by Message Type.


Replay each of these message types strictly in this order - if you replayed a message type in the wrong order, e.g. ChangeEmailAddress before AddEmailAddress, the message will fail again and appear back in Service Pulse (the message will show the number of failed attempts). Wait until each message type has been replayed before going on to next step.

If a message type does not exist, simply move onto the next one in the list that does.

As you’re going through the list, keep an eye out for any failed messages that re-appear, as this will require developer resource to investigate. If messages relating to email addresses / telephone numbers fail after they’ve been replayed, you can skip these and investigate when all messages have been replayed.

1. CreateClient

2. AddPerson

3. AddAddress

4. ChangeAddress

5. AddEmailAddress

6. ChangeEmailAddress

7. RemoveEmailAddress

8. AddTelephoneNumber

9. ChangeTelephoneNumber (if his exists)

10. RemoveTelephoneNumber

11. ChangePersonName

12. CreateClientNote

13. CreateClientAlert

14. RemoveClientNote

15. RemoveClientAlert

16. ClientHasChosenASolution

17. ResetClientPlanType

18. ResetClientPlanStatus

19. Change Manage Mail

20. ChangeClientPartnerAwareness

21. CreditorCommunicationRequested

22. ResetDebtReasons

23. ChangeEmailStatus

24. ChangeClientMaritalStatus

25. UpdatePaymentOption


Once the messages have been replayed, check that the clients can now be searched for in Portal.

2. When users log onto Portal the internal authorization server either redirects to VMSRVPRO1APP01 or VMSRVPRO1APP02 depending on which one the load balancer selects. If VMSRVPRO1APP01 is selected this will prevent users from connecting to Portal because it cannot access any of the API services as its unresponsive due to high load.