Error: Unable to open a socket to talk to CMS (FWM 01005)

[Former Member]

Hi Experts,

We have: BusinessObjects Enterprise XI 3.1 (FixPacks: 1.1, 1.2, 1.3)

On the Windows2008 Server with MS SQL Server 2008 database.

Everyting was OK after the installation with FixPacks. But in a few days BO doesn't work.

There was an error message: Server not found or may be down (FWM 01003).

I found the resolution on this Forum: The CMS Port number was changed from 6400 to 6410.

When I changed it back into: 6400, this error went away, but new one is appeared.

New error message: Unable to open a socket to talk to CMS (FWM 01005).

Our server name is: custwin

I found some suggestions on the forums (in the Tomcat's dsws.properties file change the domain), but the error is still there.

Could you help me? Any idea?

Many thanks!

János

[denis_konovalov]

First of all, what workflow produces the error ?

On a default installations port 6410 is SIA port and 6400 is CMS port.

Can you login to CMC ?

Can you see all servers running there ?

[Former Member]

Hi Denis,

First of all, what workflow produces the error ?

CMC, InfoView... everywhere is this error message.

Can you login to CMC ?

No. There is the same error message.

I can use just the Central Configuration Manager (CCM)

Can you see all servers running there ?

In CCM are 4 services

Run: Tomcat, SIA, WWW

Doesn't run: WinHTTP

[denis_konovalov]

In task Manager, do you see CMS.exe ?

Can you run netstat -anb in dos prompt and post results ?

Or simply reboot the box and see if this clears things up

[Former Member]

There isn't the CMS.exe

netstat -anb answer is too long

What rows are you intresting?

Could I send you the file?

A few rows from that:

TCP 0.0.0.0:6400 0.0.0.0:0 LISTENING sia.exe

TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING tomcat5.exe

TCP 127.0.0.1:6400 127.0.0.1:49285 ESTABLISHED sia.exe

TCP 127.0.0.1:8005 0.0.0.0:0 LISTENING tomcat5.exe

TCP 127.0.0.1:49267 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49268 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49269 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49270 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49271 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49272 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49273 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49275 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49276 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49277 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49278 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49279 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49280 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49281 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49282 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49284 127.0.0.1:6400 TIME_WAIT

TCP 127.0.0.1:49285 127.0.0.1:6400 ESTABLISHED sia.exe

[denis_konovalov]

If there is no CMS.exe - we don't need netstat - your CMS server is not running.

You need to review CMS logs in the logging direcrtory to see why CMS is not starting.

Double check it's connection information, ports assigned etc.

Try stoping the SIA and starting it again.

[kalpesh_pandey]

Hi, Do you have Web server and Processing servers (SIA etc) installed on the same machine or its a setup where web server is in DMZ and processing servers are inside networ?

Bye

[denis_konovalov]

Ok, looking at nestat results abouve - looks like CMS.exe is not running, but something is still listening on port 6400. That something apear to be SIA.

So, to resolve this :

1. Make sure SIA and CMS server have different ports assigned to them.

2. After #1 , reboot the box to make sure all ports are released and see if CMS starts.

3. If cms.exe still not running - look in logging directory for any sia or cms logs, they should have the reason for this problem.

[Former Member]

Hi Pandeyji,

Everything is on the same machine: Win2008 server.

[Former Member]

Hi Denis,

When the ports are different (SIA: 6410), I got the error message FWM 01003 - see my first description above.

Tomorrow I will try again what you suggested me, and write back to you. Thanks!

Have a nice holiday.

János

[denis_konovalov]

Well, they have to be different, otherwise it's just not going to work.

If they are different and cms.exe is running and you still can't login, then we have to look at CMS logs to see the reason.

Maybe SIA needs to be running uner domain account or there is CMS DB access issues etc..

[Former Member]

Hi Denis,

OK. Now SIA port is again 6410 (like it was originally), and CMS has 6400.

CMS doesn't run jet.

In the CMS log is the message: Unable to register APS with local nameserver

But there is no local namserver there on this server!

For the Database the bo user has owner rights.

LATER:

It's RUNNING!

I found [here the resolution|http://www.forumtopics.com/busobj/viewtopic.php?p=411513&sid=374d536f5b0ee34511707f0c38d56de7#411513].

We have to put into the "hosts" file the "localhost".

In the c:\Windows\System32\drivers\etc\hosts file are these new lines now:

127.0.0.1 localhost

::1 localhost

And it's running.

Many thanks for you!

[Former Member]

Hi all,

I have a very similar issue:

SIA is running and using port 6410.

CMS is not running, even that is using port 6400.

In the last log file of the CMS is see the following:

(err.m_IDSError == IDS_ERR_CMSSYSTEMDB_NODATABASECONNECTIONSAVAILABLE : Error refreshing CMS listeners: ).

The database look ok, so i guess there is somthing i can not see.

How can i find the issue with teh DB? or maybe it relates to somthing else....?

Thanks,

Doron