Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Unable to access web console and "Initial pipe client failed! err=2" error appears in OfficeScan (OSCE) 11.0

    • Updated:
    • 8 Jul 2016
    • Product/Version:
    • OfficeScan 11.0
    • Platform:
    • Windows 10 32-bit
    • Windows 10 64-bit
    • Windows 2003 Datacenter 64-bit
    • Windows 2003 Enterprise
    • Windows 2003 Server R2
    • Windows 2003 Standard 64-bit
    • Windows 2008 Datacenter
    • Windows 2008 Datacenter 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2 Enterprise
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2008 Web Server Edition
    • Windows 2008 Web Server Edition 64-bit
    • Windows 2012 Datacenter R2
    • Windows 2012 Enterprise
    • Windows 2012 Enterprise R2
    • Windows 2012 Server Essential R2
    • Windows 2012 Server Essentials
    • Windows 2012 Standard
    • Windows 2012 Standard R2
Summary

OSCE 11.0 administrators are unable to view the contents of the server's web console properly. When the Case Diagnostic Tool (CDT) is used, the debug logs show entries similar to the following:

2014 07/21 17:30:36 [1798 : 09dc] (00) (W) [CGIOCommon][cgiShowSummary.exe][PipeSendAndRecvW] Initial pipe client failed! err=2 - [pipe_Util.cpp(66)]
2014 07/01 13:47:45 [077c : 10a4] (00) (W) [CMDHL2][ofcservice.exe]Initial pipe client failed! err=2 - [cmacl_Command.cpp(268)]
2014 09/23 13:27:37 [0cd8 : 3448] (00) (W) [CMDHL][ofcservice.exe]Initial pipe client failed! err=2 - [cmacl_Command.cpp(161)]
2014 09/23 13:27:37 [0cd8 : 4384] (00) (W) [CMDHL][ofcservice.exe]init pipe client [Global\LogPoolCommandManager] failed! err=[2] - [cmdlog_OutputCmd.cpp(66)]
2015 08/03 20:07:18 [2954 : 2b64] (00) (D) [][cgiRqHotFix.exe]CPipeServer::CPipeServer - Windows API GetNamedPipeClientProcessId is supported on this platform - [pipe_Server.cpp(33)]
2015 08/03 20:07:18 [2954 : 2b64] (00) (W) [][cgiRqHotFix.exe][PipeSendAndRecvW] Initial pipe client failed! err=2 - [pipe_Util.cpp(66)]
2015 08/03 20:07:18 [2954 : 2b64] (00) (D) [][cgiRqHotFix.exe]OutputCGIWithSign - Fail to send command - [cgi_Signature.cpp(87)]
2015 08/03 20:07:18 [2954 : 2b64] (00) (D) [][cgiRqHotFix.exe]OutputCGIWithSign - << - [cgi_Signature.cpp(114)]
2015 08/03 20:07:18 [2ab8 : 2a30] (00) (D) [][cgiRqHotFix.exe]OutputCGIWithSign - >> - [cgi_Signature.cpp(53)]

Error code 2 (File not found) means that the pipe client was not able to find the pipe server, which may be caused by the following:

  • Database corruption on the OSCE server
  • OSCE virtual directory issues
  • Client-server communication issues
Details
Public

Update the OSCE 11.0 servers and clients to the latest build in order to resolve unknown communication issues, and then troubleshoot:

  1. Make sure that OSCE 11.0 Service Pack 1 (SP1) (Build 2995) and osce-11-sp1-win-en-criticalpatch-4150-r2.exe (or later) have already been applied to the OSCE server and deployed to the client machines, so that you are using the latest public build of the product.
     
    The latest service packs and patches for OSCE 11.0 can be found here.
  2. After updating OSCE 11.0 to the latest build:

If following the steps above still does not resolve the issue, then enable debugging on the OSCE server and collect the debugging logs:

  1. Download and extract the full Case Diagnostic Tool (CDT) to the OSCE server.
     
    Do not use the CDT Light version for debugging purposes.
  2. Run the tool and reproduce the issue. Refer to the following article: Using The Case Diagnostic Tool (CDT).
  3. After reproducing the issue, collect the CDT logs from the OSCE server.
  4. Contact Trend Micro Technical Support to request for assistance in further troubleshooting the case and to submit the logs for analysis.
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1114247
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.