view log issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
27-01-21 04:43 PM
Please find the details below .
select 'view log', and then this message comes up:
------------------------------
chandra mohan reddy pinnamreddy
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
28-01-21 05:40 AM
"View Log" is a DB resource-intensive activity. Looking at the error, it appears to be an issue with your DB server's performance. Is this your development environment? What is the SQL Server version? Try restarting SQL Server services and check.
Best regards,
------------------------------
Krishna A
Blue Prism
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
29-04-21 09:30 PM
------------------------------
Camilo Andres Duarte Rincon
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
30-04-21 03:49 PM
Hi Chandra / Camilo,
The "View Log" runs a simple select statement against the BPASessionLog_Unicode and BPASessionLog_NonUnicode tables filtering on the session number for which you selected "View Log". The default timeout setting within the Blue Prism Application for this operation is 60 seconds. As by default this action only returns the first 1000 records it would suggest that there is an issue preventing SQL Server from reading the required data within the defined application timeout, 60 seconds is an extremely long time for SQL Server to complete this kind of request. There could be any number of reasons for this;
- CPU Pressure
- Memory Pressure
- Other processes blocking the request
- Large data sets (very large session log table, 10's or millions of records or hundreds of gigabytes in size)
- Large number of records for this particular session
- Heavily fragmented indexes
- Out of date statistics
I would recommend logging a support ticket, Please speak to your DBA team to check the above and provide as much information as possible to assist in resolving the issue as quickly as possible.
Regards
Chris
------------------------------
Chris McGowan
Senior Technical Consultant
Blue Prism
------------------------------
