Skip to main content

Performance: Remedy Login issue

Last Updated:
2013-12-18 00:00:00
Event:
2013-12-17 00:00:00
Status:
Closed
Brief Description:
Remedy Login issue
User Impact:
N/A
Workaround:
There is no workaround for this issue
Current Status:
N/A
Services Affected:
Full Description:
The issue with Remedy was resolved December 17 as of 6:08 pm. Users who were trying to log in to Remedy were getting the native Remedy login page and couldn’t log in.



Timeline of Changes

Description Current Status Date Time
The issue has been resolved, but the vendor has not yet provided a statement about the cause. The alert will be updated once that is available. The issue has been resolved, but the vendor has not yet provided a statement about the cause. The alert will be updated once that is available. 2013-12-18 00:00:00
The vendor have been contacted and his working on solving the issue. The vendor have been contacted and his working on solving the issue. 2013-12-17 00:00:00
In the process of fixing the issue, BMC servers had to be rebooted hence logging out everyone which means that this issue now impacting all Remedy users. \n\nSorry for the inconvenience this is causing!\n\nThe Remedy service team.\n\n In the process of fixing the issue, BMC servers had to be rebooted hence logging out everyone which means that this issue now impacting all Remedy users. \n\nSorry for the inconvenience this is causing!\n\nThe Remedy service team.\n\n 2013-12-17 00:00:00
The vendor is still working on resolving the issue by restoring the configuration to the most recent working state. This effort will take another 30-45 minutes and it is not a guaranteed success. \n\nAgain, we are very sorry for the inconvenience this is causing.\n\nThe Remedy support team.\n The vendor is still working on resolving the issue by restoring the configuration to the most recent working state. This effort will take another 30-45 minutes and it is not a guaranteed success. \n\nAgain, we are very sorry for the inconvenience this is causing.\n\nThe Remedy support team.\n 2013-12-17 00:00:00
The issue has been resolved. A statement about the cause should be posted by the morning of December 18. The issue has been resolved. A statement about the cause should be posted by the morning of December 18. 2013-12-17 00:00:00