2303117 - CMS cannot be started due to the error WSAEWOULDBLOCK | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2303117 - CMS cannot be started due to the error WSAEWOULDBLOCK

Symptom

  • Central Management Sever(CMS) cannot be started after Sever Intelligence Agent(SIA) has been started in Central Configuration Manager(CCM)
  • Users cannot log into BI Launch Pad, Central Management Console(CMC) and all the BI Client Tools
  • The error messages below occur when trying to start CMS in console mode

***LOG Q0I => NiBufIConnect: connection pending after 500ms: connect (10035: WSAEWOULDBLOCK: Resource temporarily unavailable)
*** ERROR => NiBufIConnect: non-buffered connect pending after 500ms (hdl 1;127.0.01:59818) [nibuf.cpp 4669]
*** ERROR => NI raw handle failed to be initialized at IDEL to CONNECTED, connection to agent destination failed to be established


Read more...

Environment

  • SAP BusinessObjects Business Intelligence Platform(BI) 4.0
  • SAP BusinessObjects Business Intelligence Platform(BI) 4.1
  • SAP BusinessObjects Business Intelligence Platform(BI) 4.2

Product

SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.0, feature pack 3 ; SAP BusinessObjects Business Intelligence platform 4.1 ; SAP BusinessObjects Business Intelligence platform 4.2

Keywords

BI,BO,BOE,CMS DB,MSSQL,SQLSERVER,ORACLE,ODBC,JDBC,DSN,dead,zombie,hang,manage servers,logon,crash,1828536,vh,severity,bi4.1,bip41,bip4.1,p1,consolemode,servermode,block,crash,db,connection , KBA , BI-BIP-ADM , BI Servers, security & CrystalReports viewing in BI platform , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.