Invalid server response when filtering on defects

  • Questions
  • Invalid server response when filtering on defects
Question ID: 107854
1
0

We ran the repair tool and completed the manual repairs that were suggested but we are still seeing the same "Invalid Server response" and "Value cannot be null" errors.
![alt text][1]

![alt text][2]

[1]: /storage/temp/682-201708240829543-invalid-server-response.jpg
[2]: /storage/temp/683-201708240933426-value-cannot-be-null.jpg

Marked as spam
Posted by (Questions: 199, Answers: 1)
Asked on September 5, 2017 6:58 pm
12 views
Answers (1)
1
Private answer

Here is the resolution to this issue:

The root cause was someone had copied and pasted HTML code into Description and Dev comments field. We finally narrowed it down to a specific defect based on what filters were cause ALM to stop

Also, you need to set the ''Sanitization Type'' to ''Text'' as shown in the following:
![alt text][2]

working turned out it was Deployment 31-Aug-17, Severity 3, Status new . That narrowed it down to a small enough number of defects that we were able to find the exact one causing the issue. To fix it we ran and update on those 2 fields in the database to remove the HTML this resolved the issue.
Remove

[1]: /storage/temp/686-html-code-in-defect.txt
[2]: /storage/temp/685-sanitization-type.png

Marked as spam
Posted by (Questions: 1, Answers: 213)
Answered on September 5, 2017 7:10 pm