Error Reading From The Pipe: Unrecognized Error 109 (0x6d)
kbt129298
PRODUCTK2 blackpearl 4.7
BASED ONK2 blackpearl 4.7
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
Issue
Error found in the K2TokenService.exe.log located in the folder: D:Program Files (x86)K2 blackpearlToken ServiceBin. This error occurs regularly and floods the log which in turn increases the log file "Exception: System.ServiceModel.CommunicationException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). ---> System.IO.IOException: The read operation failed, see inner exception."Symptoms
K2TokenService.exe.log will increase in size due to an error detected in the TokenService.exe.log.
Resolution
Following these steps will resolve this issue:
- Open "Services" and navigate to "K2 Claims To Windows Service" then view its properties, and select the "Log On" tab, from here ensure that according to K2 Out Of The Box settings this is set to use the "Local System Account".
- Now Open "Services" and navigate to SharePoint claims service called "Claims To Windows Service" and view its properties, once again select the "Log On" tab and ensure that according to K2 Out Of The Box settings this is set to use the "Local System Account" as well.
- Navigate to your TokenService.exe.config file which is usually found in this location "C:Program Files (x86)K2 blackpearlToken ServiceBin" and edit the TokenService.exe.config file. In the config file you would need to add your WSS_WPG into the <allowedCallers> section.
To get your WSS_WPG you will have to navigate to your Internet Information Services Manager (IIS) then select the "Application Pool" option on the left and locate the "K2 Blackpearl" as well as "K2 Smartforms" application pools from the list. They will each have their own WSS_WPG listed in the "Identity column" (both K2 Blackpearl and SmartForms should have the same value in the Identity column). Referencing Microsoft Claims to Windows Token Service (c2WTS) and Reporting Services
Article
- Now add the Identity value in this piece of code (<add value="WSS_WPG" />) for it to look as this example does, example: <add value="Denallix/administrator" /> and paste the code sniplet into the TokenService.exe.config file as indicated in this code example:
<allowedCallers>
<clear />
<add value="DENALLIXAdministrator" />
</allowedCallers>
<clear />
<add value="DENALLIXAdministrator" />
</allowedCallers>
- You will now need to rename your TokenService.exe.log file to TokenService.exe.log_bak in order for a new log file to be generated.
- Now restart the "K2 Claims To Windows Service" from services, clear your browser cache and then from K2 Designer click the green "Sign out" button in the top right corner.
- Should you be on Windows STS your Designer will auto sign back in otherwise if you are using Forms STS you will need to sign back into the K2 designer, eitherway a new TokenService.exe.log file should be generated after doing this.