You see the following entry in the Windows Application Event Log : [1420:1432] Windows API function ReadFile failed for named pipe; status=109:0x6d:The pipe has been ended.
BCAAA is designed around two processes. The first is a persistent process called bcaaa.exe. This one accepts new connections from the SG and determines which version of the BCAAA API the SG needs to use.
The second process is the one that does all the processing. Once bcaaa.exe determines the API version it launches the corresponding bcaaa-xxx.exe process to handle the requests.
After being launched, bcaaa-xxx.exe attempts to talk to bcaaa.exe to get the identity of the socket connection back to the SG that it needs to take over. Bcaaa.exe and bcaaa-xxx.exe use a named pipe to talk to each other. For some reason this named pipe connection has failed.
Imported Document ID: 000014951
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.