Exceptions Management

Exceptions Management

Here you can view your Exceptions

Error Log ID	Date Time	User ID	User Email	Org ID	Org Name	Entity ID	Entity Name	Stored Procedure	Machine	Unique Check	Cause	Status
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved
567	2018-06-30 09:42:00	478	testingorg10@emails.receipt-bot.com	378	testingorg10	622	testingorg10	Class: global_asax, Method: , Machine: RebotTest-01	RebotTest-01	New	Server cannot set status after HTTP headers have been sent.	Resolved

Exceptions Details

Here you can view your Exceptions Details

Occurrence History

Date	User Id	Org Id	Entity Id
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622
2018-06-30 09:42:00	478	378	622

Exception Details

Resolution History

Date	User	Action	Comment	Status
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved
30-06-2018	Azfar Bukhari	Developed	The issue appeared because null data was not handled	Resolved
29-08-2018	Kamran Umar	Developed	The issue appeared because null data was not handled	Unresolved

User

Date

Action

Status

Comment

Staff Member invitation accepted by Zainab Ali

Staff Member invitation accepted by Muhamamd Shahzaib

Staff Member invitation accepted by Muhamamd Shahzaib

Changes to the Advisor Menu

Changes to the Advisor Menu

Staff Member invitation accepted by Fahed Azeem

Staff Member invitation accepted by Fahed Azeem

Changes to the Advisor Menu

Changes to the Advisor Menu

Staff Member invitation accepted by Fahed Azeem

Exceptions Management

Exceptions Details