Error "Open InfoPath Task"

  • 9 April 2009
  • 9 replies
  • 3 views

Badge +4

Hi,


we have deployed a process which works fine. Two users get the following error message, whereas, all other users (>100) don't get that message. All users are authorized by using groups in which the concerned two users are members too.


Open InfoPath Task


The following error prevented the Workflow InfoPath Task to open:


The request failed with HTTP status 401: Unauthorized. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at.....


Does anyone know what the problem might be? We can't find any errors in the log files (IIS, Eventlog).


Many thanks!


amanax


9 replies

Badge +5

Hi Amanax,


Could you please ensure that the 2 users failing to open the worklist items have access to the MOSS site.


Also could you please give the full error message including the entire stack trace.


Kind Regards,


Gert


 

Badge +4

Hi Gret,


thank you for your answer.


I had a look over the access rights, both users do have contributor rights (as all other users).


Here the whole error message incl. the stack trace


Open InfoPath Task  


     Logged in User: XXXX 


The following error prevented the Workflow InfoPath Task to open:


 


The request failed with HTTP status 401: Unauthorized. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at SourceCode.SharePoint.WebServices.K2SPFiles.UploadDocument(String listNameOrTitle, String folderUrl, String fileName, Byte[] oByte, Boolean overWrite, String xmlMetadataFields) at SourceCode.Workflow.RuntimeServices.OpenInfoPathTask.OpenFormsServerPage(String infoPathFormData, String fileName) at SourceCode.Workflow.RuntimeServices.OpenInfoPathTask.OpenSharePointLocation(WorklistItem wli, String xmlFieldName, String libURL, Boolean openAsWebPage, String spSiteURL, Boolean isSingleInstance) at SourceCode.Workflow.RuntimeServices.OpenInfoPathTask.Page_Load(Object sender, EventArgs e) System.Object[] ReadResponse(System.Web.Services.Protocols.SoapClientMessage, System.Net.WebResponse, System.IO.Stream, Boolean)


 


Please contact your administrator.


amanax

Badge +11

A few other ideas:


-Even though the users have contributor access to the site, make sure they also have access to the form library.  I have seen a couple of odd instances where even though a user is a contributor or higher they specifically do not have access to the form library.


-If you are using any SmartObjects or web services to get data from a SharePoint list, make sure those users have at least read access to the list.

Badge +4

Hi David,


thanks for your ideas.


Both users have access to the site collection, site and form library.


Moreover, they have access to all webservices, which we are calling (including smartobjects).


amanax

Badge +11
Next step is to start tracking down the SharePoint logs and IIS logs.  Use those to find out exactly what resource is being denied.  If you find it is a particular URL, what happens if they use their browser to go directly to the URL?
Badge +4

I had a deeper look in all log files but, however, I couldn't find anything.
Moreover, I took all URLs which are called in the process. I sent them to the concerned users but they don't receive any error...


These are the URLs:
http://MOSS/site/_layouts/FormServer.aspx
http://MOSS/site/form_lib/the_infopath_form.xml
http://MOSS/site/_vti_bin/K2SPFiles.asmx
http://MOSS/RuntimeServices/OpenInfoPathTask.aspx
http://MOSS/RuntimeServices/InfoPathService.asmx
http://MOSS/site/_vti_bin/userprofileservice.asmx


Are there any other URLs left which are called implicitly.


amanax

Badge +3

Hi,


We are experiencing a very similar problem with an InfoPath process, where some users are receiving this 401 error when they attempt to open thier Task form.


One interesting thing we have observed is that when the user reboots their machine, they are able to open the workflow task.  However, after some period of time without rebooting, the problem resurfaces again.  For this reason, we do not believe the problem is related to any site/process permissions.


If anybody has any suggestions, please let me know.


Thanks,


Brian


 

Badge +2

I ran into this very same issue yesterday and initially thought it might be due to a known issue with InfoPath Forms Services delegating control to the K2 Service account; however, it turned out to be a security error on the form library (as previously mentioned).  I gave all authenticated users Contribute access to the library and the issue was resolved.

You might also check the Internet Options of your user's browser - I think unless the FQDN is in the Intranet Zone AD credentials won't get passed automagically and thus your users wouldn't get properly authenticated.

 

Good luck. 

Badge +4

Hi,


I have forgotten to post the solution. Sorry for that!



We have found out what was causing the error. As we are using custom permission levels, "Edit items" was not checked in the assigned permission level, whereas, "Create items" was checked. So users could open their tasks for the first time but afterwards (when the xml-file has already been created), they couldn't reopen it... Those users who had no problems opening their items, had submitted the item too so that they hadn't to open it again...


greetz,


amanax

Reply