Error FWM 01003 Server not found or may be dwon

server administration XI Server Discussion
1

I recently installed BO XI R3 on a machine. After the installation everythings works perfectly.

After a few day I got an error while attempting to connect to the CMC (error FWM 01003 server not found or may be down).

When I remove BO and reinstalled it, it works fine, but again after a few days I got the same error message.

I checked that the CMS is started.

Anyone have a suggestion?

pheldge (BOB member since 2008-07-29)

2

Hi,

I encountered the same problem: I installed XI 3.0 using mySQL for the security database. Everything worked fine until suddenly, after a couple of days I got the same problem as you.
The installation was done, using all default values, so the port for CMS = 6400.

Proceed as follows:

  • Start Central Configuration Manager (CCM)
  • Select Server Intelligence Agent (SIA)
  • Select Properties
  • Select the ‘Configuration’ tab. It mentions ‘CMS belongs to cluster name servername:6400’ (so this is OK)
  • Select the ‘Startup’ tab. Strange enough here I found not port = 6400, but port=6410. This caused the problem.
  • Notice that you can not change this if the SIA is running. To solve it:
  • Stop the SIA
  • Select the SIA again, select the Properties and select the ‘Startup’ tab. Now you can change the value into port = 6400.
  • Start the SIA again

Everything worked again. So I have a solution, but I don’t know the reason why the port changed.

Hope this helps. Good luck

(Note: thanks to Steven V. to assist me in this)

Henri Theuwissen :belgium: (BOB member since 2006-11-14)

3

Thanks for your suggestion Henri.

Anyway, I’ve checked the CCM and the SIA is correctly configured (6400 for startup and 6410 for configuration).

Thank you for your help.

pheldge (BOB member since 2008-07-29)

4

Hi,

I have the same problem, did you find a solution?

Regards

cedrickb :fr: (BOB member since 2005-08-19)

5

Did you tried with port number along with system name in CMC login page?

savala :us: (BOB member since 2005-04-14)

6

yes, and nothing changed…
I reinstall BO and I get the same problem…

What is weired is that my SIA server is running but when I try to see servers, I have the message “your cms is not runing”.

I tried to add an other intelligent server, it worked but when I want to see servers, the same message appears.

:hb:

thanks for your help!

cedrickb :fr: (BOB member since 2005-08-19)

7

here it seems to be same problem, different day, thanks for the tips that I have forwarded to my IT-Helpdesk.

:slight_smile:

ThomasE :denmark: (BOB member since 2008-12-07)

8

We reinstall the oracle middleware and everithing was ok after that…
We didn’t understand really well what happened!
hope this helps.

cedrickb :fr: (BOB member since 2005-08-19)

9

We had the same problem on BO XI 3.0 and following Henri’s work flow above, we have realised that the password on Oracle BO repository DB expired

:oops: :roll_eyes:

OtoZ :australia: (BOB member since 2002-08-28)

10

We are experiencing this after removing 3.1 Fix Pack 1.2. It seems that we now need a fully qualified name for each server.

maverick976 :us: (BOB member since 2004-07-06)

11

Henri Theuwissen, thank you for posting the solution! I actually followed your instructions and and received a different error.So I went back in and put the port back to 1610.Restarted the SIA and it all magically worked again. Now I am back on track! Thanks :slight_smile:

texeyes :us: (BOB member since 2009-10-02)

12

Some times we way to solve it might be as simple as double checking concerned servers are enabled, up & running in the CCM. Go to the Manage Servers in the CCM and after the authentication process check the server status state.

Jordi_Lopez (BOB member since 2009-11-04)

13

I have the Same Issue, I tried still its not responding :hb: [/quote]

AHMED SYED :us: (BOB member since 2010-01-05)

14

Hi there. First post…

I’ve found that this occurs when there is a problem with the CMS connecting to the CMS database.

For me, I had removed the default database for the user that was the owner of the CMS database. Attempting to log into SQL Server Management Studio with that user gave me a useful error, so I could fix up the user account. Everything then worked again.

David Gilbertson (BOB member since 2011-03-08)

15

I agree with David. I faced the same issue here and solved it by deleting the ODBC connections and creating new ones :smiley:

maximus2002 (BOB member since 2011-04-02)

16

Morning,

I encountered this problem after downloading the trial version of Crystal Server 2011. The challenge I am having is that nowhere in Central Config Manager do I have an entry called SIA.

How do I install the SIA?

Thank You
Aaron

ajevons (BOB member since 2011-06-28)

17

Thanks!
Itt worked for me,it was very helpful.

shilpa234 (BOB member since 2012-04-11)

18

Many Thanks.

This helped me diagnose my issue. In the spirit of sharing and contributing backl I thought I should say what brought me here.

My Server Intelligence Agent was shown as running in the “Central Configuration Manager” so I assumed it had started successfully but when I checked under the “Configuration” tab it popped up a error message stating that it couldn’t find the CMS database.
When I checked SQL Server I found that for some reason the CMS database couldn’t be accessed (I’ve no idea why it choose to die while my staging area and other databases are fine) so I restored by CMS database from a backup and restarted the Server Intelligence Agent.

It now works fine.

FreeZey (BOB member since 2007-12-07)

19

I have the same issues here. Our version is XI 4.0 SP5 and we are running it over a DB2 database.

Just like my friend FreeZey, that topic help me in find a less generic error.

Under the configuration tab, the message was something like: “DB2 running whith HADR enabled. That makes necessary that the column CMS-INFOOBJECTS7 from table PROPERTIES is defined like LOGGED. It can´t happens because the actual DB2 version does not support big blob columns. CMS will not be inicialized in this condition because a fail in this database could break the repository. We have two options: first, upgrade DB2 server to v9.5 fixpak 5 or later, 9.7 fixpack 1 or later, or, v10 or later. The second is deactivate HADR. (FWB00088)”

I´m in contact with our DB2 DBA and sooner i will post our solution here.

Regards!

Rabbit :brazil: (BOB member since 2011-08-25)

20

Hi Rabbit,

We spent a couple of hours with this same problem last night.

However, this is not a DB2 issue, it’s a bug in the patch. The resolution is to install SP 5.1 instead of SP 5.

Check out this note for more details 1819834 - CMS server is not coming UP after upgrading BI 4.0 to SP05

derekbarrett (BOB member since 2013-04-26)