The request failed with HTTP status 401: Unauthorized

  • 14 December 2007
  • 1 reply
  • 6 views

Badge +2

Hello All,


I have created a sample work flow in the K2.net and created a list in the sharepoint with Column Names EmpNo, Firstname, Lastname, DeptNo. and used SharePoint 2003 List to link Sharepoint site list(Name EMP), Im able to get all the required information while running template. (i.e. i mean when i give server name,site directory name, im able to see the list i want to link with K2.net), and values are passing from VS2005(.aspx pages) to K2.net datafields, these fileds are linked with sharepoint list column names,.


when i run my application im sure that im getting values to K2.net datafields, but not able to create new list item in the share point list. In the K2.net service manager it is shwing the following error in the error profile.


System.Net.WebException: 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 K2SPSList.CreateListItem(String SiteUrl, String ListName, String xmlListItems, Int32& ListItemId, String& ErrorMessage)
   at K2Code6830.Main(ServerEventContext& K2) 


please help me.


 Note: The List Item creation user is set to the Service Account user used for the K2.net 2003 Server Service.


i found this while searching, if this error occurs bcoz of this, tell me where to do the settings to aceive this.


Thanks


 


1 reply

Badge +6

I would recommend reviewing KB171 (401 errors - http://kb.k2workflow.com/articles/kb000171.aspx)


Also, please refer to KB123 (Kerberos configurations, Delegation, etc.)http://kb.k2workflow.com/articles/kb000123.aspx.


When troubleshooting 401 or authentication errors, I find it easier to think about determining what is breaking and where (between client/IIS? IIS/K2? K2/SQL?) and try things directly from the local IIS machine and from remote clients hitting the IIS machine (you may get different results). If K2 Server (console mode) isn't acknowledging the client request, the breakdown is likely between the client and IIS.


Also check permissions of the various AppPool Identities.


 


 

Reply