COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Mobile => Topic started by: sergiord2016 on 28 Apr 2017 01:50:51 AM

Title: Unable to load balance the request because no nodes in the cluster are available
Post by: sergiord2016 on 28 Apr 2017 01:50:51 AM
Hi , after Cognos Mobile installations i get this error

MOB-SVR-1167 and DPR-ERR-2014 Unable to load balance the request because no nodes in the cluster are available, or no nodes are configured for the service: mobileService.

And i am now absolutely blocked....

Anyone can help me please?
Title: Re: Unable to load balance the request because no nodes in the cluster are available
Post by: MFGF on 28 Apr 2017 03:48:38 AM
Quote from: sergiord2016 on 28 Apr 2017 01:50:51 AM
Hi , after Cognos Mobile installations i get this error

MOB-SVR-1167 and DPR-ERR-2014 Unable to load balance the request because no nodes in the cluster are available, or no nodes are configured for the service: mobileService.

And i am now absolutely blocked....

Anyone can help me please?

It sounds like you have multiple servers in your architecture?

On each server with the application services tier installed, launch Cognos Configuration and select the 'IBM Cognos services' option on the left. Take a look at the 'Mobile service enabled' setting and make sure it is set to True not False. Re-start the Cognos service on that server.

Cheers!

MF.
Title: Re: Unable to load balance the request because no nodes in the cluster are available
Post by: sergiord2016 on 02 May 2017 06:20:39 AM
Hi ,

I have checked that the option is enabled and i have only one server... so that's not the problem...

any idea?

thanks in advance mates!
Title: Re: Unable to load balance the request because no nodes in the cluster are available
Post by: MFGF on 02 May 2017 08:17:48 AM
Quote from: sergiord2016 on 02 May 2017 06:20:39 AM
Hi ,

I have checked that the option is enabled and i have only one server... so that's not the problem...

any idea?

thanks in advance mates!

Ok - in that case:

1. Launch Cognos Administration
2. Click the Status Tab -> System and drill into your Dispatcher, so you can see the list of services displayed
3. Make sure that MobileService has a status of Available. If not, select the arrow next to the MobileService and choose 'Start'

Cheers!

MF.
Title: Re: Unable to load balance the request because no nodes in the cluster are available
Post by: sergiord2016 on 10 May 2017 09:38:22 AM
hello my friends ,

I have done that what you say and the Cognos Mobile Services shows Partial available (i translate from spanish).

(http://i64.tinypic.com/op4jgl.jpg)

Title: Re: Unable to load balance the request because no nodes in the cluster are available
Post by: Sus on 12 May 2017 01:59:24 AM
I have found this in the IBM page:

To work around the open defect, the pattern administrator must edit the configuration to include an SMTP notification server. After the configuration is edited, and the entire pattern is restarted, the Mobile service will start and all mobile reports will be available.

http://www-01.ibm.com/support/docview.wss?uid=swg21678999
Title: Re: Unable to load balance the request because no nodes in the cluster are available
Post by: Sus on 16 May 2017 10:09:27 AM
The problem continues.
I have looked the mob.log and this is the message error:

[Default Executor-thread-43] ERROR com.cognos.mobile.database.internal.schemaupgraders.ScriptEntry - execution of script 'D:\Program files\ibm\Cognos\c_10_64\configuration\schemas\mobile\sqlserver\upgrade-00-000-to-02-000.sql' failed
com.cognos.mobile.common.CMException: execution of script 'D:\Program files\ibm\Cognos\c_10_64\configuration\schemas\mobile\sqlserver\upgrade-00-000-to-02-000.sql' failed (code 1121)


please, any idea?
Title: Re: Unable to load balance the request because no nodes in the cluster are available
Post by: sergiord2016 on 22 May 2017 05:40:20 AM
Hello , anyone who can help us?
Title: Re: Unable to load balance the request because no nodes in the cluster are available
Post by: bdbits on 22 May 2017 05:41:42 PM
Have you opened a support ticket with IBM?