cancel
Showing results for 
Search instead for 
Did you mean: 

BI launch pad Viewing dashboard error "FWM01014"

zhang_jiwen
Participant
0 Kudos

Hi,Experts:
Recently, we are doing test for upgrading  BI4.0.


Environment:
     1.BO 3.1: Win2k3 + Sql2000 + tomcat5.5 + bo xi 3.1 sp2
     2.BO 4.0: Win2k8 + Sql2008 + tomcat6 + bo bi 4.0 sp5


After upgrading BI content in BO4.0 system with upgrade management tool from BO3.1,when we were accessing the BI workspace dashboard,there came the following error:"soapenv: Server.generalException: CMS BA1: 6400 and Type can not serve cms
For the null cluster @ BA1: 6400 find the server. All such server may be down or management
Members disabled.(FWM 01014)"


When we checked out  the log viewer of BO4.0 server and found the following problems:
     1.Out of memory in the Event Server
     2.CMS is unstable and will shut down immediately. Reason: SAP
BusinessObjects BI platform CMS: Unable to connect to the CMS system
database "MSSQLServer4CMS". Reason: [Microsoft] [ODBC SQL Server Driver]
[SQL Server] Cannot open database "CMS" requested by the login. The
login failed.
     3.Report Server Windows Service (MSSQLSERVER) cannot connect to
the report server database.
     4.SAP BusinessObjects BI platform CMS: Lost a CMS system database
connection to "" MSSQLServer4CMS "". 2 CMS system database connections
are remaining. Reason: [Microsoft] [ODBC SQL Server Driver] Communication
link failure
     5.SAP BusinessObjects BI platform CMS: Lost a CMS system database
connection to "" MSSQLServer4CMS "". 3 CMS system database connections
are remaining. Reason: [Microsoft] [ODBC SQL Server Driver] [DBNETLIB]
ConnectionWrite (send ()).
     6. Other platform server error. For example: CMS Server Watcher: server
named 'BA1.AdaptiveProcessingServer' is being marked as down because it
is unresponsive


However, we still can log on to the CMC and BI launch pad, and the servers list server uptime.
We infer possible reasons:
     1.BO4.0 server configuration some low memory 4G, memory usage is kept at 90%
     2.CMS connection CMS database, but used for odbc connection tested no problem
     3 We want to see the CMS server configuration file, but do not know how to start.


Please help me, thank you in advance!

Best regards!

Accepted Solutions (0)

Answers (3)

Answers (3)

DayaJha
Active Contributor
0 Kudos

Hi Zhang,

For Your Query:

2.CMS is unstable and will shut down immediately. Reason: SAP BusinessObjects BI platform CMS: Unable to connect to the CMS system
database "MSSQLServer4CMS". Reason: [Microsoft] [ODBC SQL Server Driver] [SQL Server] Cannot open database "CMS" requested by the login. The
login failed.

Solution:


Please follow the steps below:


  • As you mention yo are using Windows Server 2008 as a Operating system
  • Check the logs in the Event Viewer regarding CCM (Central Configuration Manager)
  • Stop the SIA (Server Intelligence Agent Node)
  • Check the ODBC Connection (Remap it Once Again and pass the User credential of your SQL Server 2008 Information in ODBC parameters)
  • Then Restart the SIA (Server Intelligence Agent Node)


     4.SAP BusinessObjects BI platform CMS: Lost a CMS system database connection to "" MSSQLServer4CMS "". 2 CMS system database connections
are remaining. Reason: [Microsoft] [ODBC SQL Server Driver] Communication link failure

Solution:

Follow the same steps as above

     5.SAP BusinessObjects BI platform CMS: Lost a CMS system database connection to "" MSSQLServer4CMS "". 3 CMS system database connections
are remaining. Reason: [Microsoft] [ODBC SQL Server Driver] [DBNETLIB] ConnectionWrite (send ()).

Solution: Follow the same steps as above


     6. Other platform server error. For example: CMS Server Watcher: server named 'BA1.AdaptiveProcessingServer' is being marked as down because it
is unresponsive

Solution:

Issue is regarding your EIM Adaptive Processing Server.


Please follow the steps below:


Failing Adaptive Processing Server:

Ultimately I removed some services from the AdaptiveProcessingServer which solved my problem. In this documentation I’ll explain how to enable AdaptiveProcessingServer

Log on to the CMC and go to ‘Servers’ and then ‘Servers List’ check the status of the APS (AdaptiveProcessingServer). In case it is not stopped, stop it manually by right clicking.

Once the APS is stopped, right click to ‘Select Services’.

I removed 14 services from the APS:

Then I saved the settings and restarted the APS. Charts are now showing up again.

For Your References Best Practices for SAPBO BI 4.0 Adaptive Processing Servers


http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50e5019f-bfdf-2f10-2188-c40ede52c...


http://www.dallasmarks.org/blog/2011/09/adaptive-processing-servers-in-sap-businessobjects-bi-4-0/


http://www.dallasmarks.org/blog/2011/11/sizing-the-adaptive-processing-server-in-bi-4-0/

Hope this help you as well.


Thanks,

Daya

TammyPowlas
Active Contributor
0 Kudos

This is the top level BI space.  I will move this to the BI platform space.

Tammy (Moderator)

zhang_jiwen
Participant
0 Kudos

ok,thanks,Tammy.

Former Member
0 Kudos

Hi there,

We just started getting this error after applying patch 4 for BI4 SP05 to fix promotion manager issue.

Did you find a solution ?

Lee Lewis

Former Member
0 Kudos

Hi,

According to my knowledge these is completely server issues that means the default port is 6400 which bo using is not in listen state

use netstat -a  command to find the ports which are in which state

Thanks,

Ashok

zhang_jiwen
Participant
0 Kudos

Hi ASHOK BABU,

     Thank you for your quick reply.

      I ran the "netstat -a|findstr 6400",here is the result:

       TCP    0.0.0.0:6400           BA1:0                  LISTENING

       TCP    10.10.104.113:6400     BA1:56086              TIME_WAIT

       TCP    10.10.104.113:6400     BA1:56331              TIME_WAIT

       TCP    10.10.104.113:6400     BA1:56332              TIME_WAIT

       TCP    10.10.104.113:56086    BA1:6400               TIME_WAIT

       TCP    10.10.104.113:56332    BA1:6400               TIME_WAIT

       TCP    10.10.104.113:56400    BA1:6410               TIME_WAIT

       TCP    [::]:6400              BA1:0                  LISTENING

Former Member
0 Kudos

Hi,

By see that your ports are not in a listen state .check with network guys and make how to bring to listen state or take support from sap support.

Thanks,

Ashok

zhang_jiwen
Participant
0 Kudos

Hi Ashok,

    What's about  "TCP    0.0.0.0:6400           BA1:0                  LISTENING"?

Former Member
0 Kudos

Hi,

That shows some port is trying to listen with out IP it is not possible to determine which one it is .

Thanks,

Ashok