[OLE-3714] Alert: "A server error has occurred." Created: 20/Feb/13 Updated: 19/Aug/13
Resolved:
19/Aug/13
Status:
Project:
Component/s:
Fix Version/s:
Closed
OLE
Select & Acquire
OLE 1.0
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Bug/Defect
Jain Waldrip (Inactive)
Cannot Reproduce
None
Not Specified
Notes:
Between 10:00 and 10:05 this morning I received an alert with the text "A
server error has occurred." It was during Selenium testing, so I didn't
discover the error exactly when it occurred, due to Selenium's alert
suppression, but if it helps for searching the output logs, I was working on a
Requisition, Doc # 3666, Req # 1013. It was while trying to click on the
"Vendor" tab. The page may still have been reloading from hiding one of the
accounting lines on the requisition - for some reason, "AndWait" hasn't been
functioning entirely normally in Selenium during the course of KFS 5.0
testing - so it could be that the error encountered was due to the page still
refreshing when the script tried to click an element, but normally this results
in either no action (for most tabs and other controls) or a "Page already
being processed by server" message (for routing and reloading of
documents).
Priority:
Assignee:
Votes:
Major
Richard Slabach
0
Not Specified
Not Specified
Comments
Comment by Jain Waldrip (Inactive) [ 20/Feb/13 ]
UPDATE
I also encountered an alert with the text "OK" while loading a newly-created receiving
document at about 11:45 this morning.
Comment by Peri Subrahmanya [ 22/Feb/13 ]
Please go ahead and re-test as the this issue is anticipated to be pre-turnk upgrade and
deployment.
Comment by Jain Waldrip (Inactive) [ 25/Feb/13 ]
This issue was found in the Dev environment last Wednesday. I just encountered it again at 1:39
or 1:40, so I'm re-opening this issue.
Comment by Jain Waldrip (Inactive) [ 25/Feb/13 ]
This issue is starting to become a serious impediment to testing. I can work around it, but it's
slowing me down a lot to keep running into this error message.
Comment by Richard Slabach [ 21/Jun/13 ]
Jain, could you test this issue and comment here please?
Comment by Jain Waldrip (Inactive) [ 24/Jun/13 ]
I got this error to occur at 9:10 this morning. I was running an IDE script to create a requisition
with two line items. In filling out the second line item's accounting string, this error popped up.
The script had just clicked "add" on the previous accounting string (a clickAndWait), then it
clicked on the accounting line toggle for the second line item (also a clickAndWait command).
When it moved on to try to select "BL" from the chart selector drop-down, the command failed
and the target error message was displayed.
The requisition has Document ID # 3885, and I saved it after encountering the error.
Comment by Jain Waldrip (Inactive) [ 24/Jun/13 ]
(I think this error may occur when the page is still processing a command but has already
triggered a refresh event, sending the script on to its next command. We can probably avoid this
issue more deftly in future automation by making liberal use of conditional waiting and spin
asserts, which we aren't really able to do in Selenium IDE.)
Comment by Jain Waldrip (Inactive) [ 24/Jun/13 ]
Suresh, could you look into this issue please?
Comment by Surya Rajendrababu (Inactive) [ 19/Aug/13 ]
Jain, Can you please provide the selenium script, so that we can look into this where the
problem occurs. We tried many times in dev manually and we were not able to reproduce this
issue again.
Thanks
Comment by Jain Waldrip (Inactive) [ 19/Aug/13 ]
Surya, it looks like this ticket is a bit out of date. We're not really using Selenium IDE for
anything right now, and I haven't encountered a recurrence of the non-specific server error alert
in Watir-Webdriver (the tool we're using now to move toward Cucumber testing) since late
June.
I'm going to go ahead and close this issue. I'll create a new Jira ticket if we encounter any
similar errors, but I think somewhere between the system upgrades and the better conditional
waits in Watir-Webdriver, this issue has more or less resolved itself.
Comment by Jain Waldrip (Inactive) [ 19/Aug/13 ]
I have not seen a recurrence of this issue in the Test Environment since late June, and I do not
anticipate it coming up again, so I am closing this issue with a resolution of "Cannot
Reproduce."
Generated at Tue Feb 09 06:17:37 CST 2016 using JIRA 6.1.5#6160sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.