This content has been marked as final. Show 2 replies
1 of 1 people found this helpful
This error generally has to do with the timeout not being long enough. The following KB article provides details on extending the length of the timeout:
Hope this helps!
Thanks for the help Tracy!!
That worked like a charm for me.