Showing posts with label Exception Message: Thread was being aborted.): Infopath. Show all posts
Showing posts with label Exception Message: Thread was being aborted.): Infopath. Show all posts

24 October, 2012

Exception occurred during request processing. (User: Form Name: , IP: , Request: Form ID: , Type: ThreadAbortException, Exception Message: Thread was being aborted.): Infopath


Issue:
Today in our environment we saw an SCOM alert which was continuously getting triggered.

SCOM Alert: Exception occurred while processing an InfoPath form template request
Source: spmwprodweb3
Path: spmwprodweb3.nam.nsroot.net
Alert Raised Time: 10/23/2012 3:21:06 PM Last modified by: System Last modified time: 10/23/2012 3:21:07 PM Alert description: Event ID 5367 from Source Office SharePoint Server on agent computer spmwprodweb3.nam.nsroot.net has triggered this Alert Description : Exception occurred during request processing. (User: Domain\User ID, Form Name: , IP: , Request: https://infopathformlib.site.url, Form ID: , Type: ThreadAbortException, Exception Message: Thread was being aborted.)

In Event logs

Event Type:  Error
Event Source:          Office SharePoint Server
Event Category:     Forms Services Runtime
Event ID:       5367
Date:              10/23/2012
Time:              2:21:55 PM
User:              N/A
Computer:    SPMWPRODWEB1
Description:
Exception occurred during request processing. (User: Domain\User ID, Form Name: , IP: , Request: https://infopathformlib.site.url, Form ID: , Type: ThreadAbortException, Exception Message: Thread was being aborted.)

In ULS logs

10/23/2012 14:28:19.68            w3wp.exe (0x2080)                                  0x327C          Forms Server                              Forms Services Runtime               82fp   Critical           Exception occurred during request processing. (User: Domain\User ID, Form Name: , IP: , Request: https://infopathformlib.site.url, Form ID: , Type: ThreadAbortException, Exception Message: Thread was being aborted.)          

Troubleshooting:
Checked on Google and it refers to the issue with anonymous access on the site http://vettekerry.wordpress.com/2008/06/03/login-required-on-anonymous-site.
MSDN community refers to the issue with “NT AUTHORITY\autenticated user" access on the site http://social.msdn.microsoft.com/Forums/pl/sharepointinfopath/thread/e0312df4-b950-4e42-ba49-a648055c8934.

In our environment we are neither using anonymous access on the site nor client have added “NT AUTHORITY\autenticated user" on the site.

Resolution:
The above article was referring to the permissions related issue. Hence tried to find the if the user is added on the site from “All People” group and no reference was found. Since there were 100 users it was very difficult to check them one by one. Asked the site admin if he has any reference list of users and he also confirmed that these users are yet to be permissioned on the site. Confirmed with the client they all treid to access the site before they were permissioned on the site resulting in SCOM Alert trigger for the InfoPath.

As alert was so huge in nature only a small portion of it was a cause of the issue i.e. user identified was not permissioned on the site. 

If you have any questions do let me know.