No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
Knowledge Base

failed to log in from eSpace mobile

Publication Date:  2016-06-10  |   Views:  629  |   Downloads:  0  |   Author:  h00453638  |   Document ID:  EKB1000118319

Contents

Issue Description

customer tried to login from my eSpace mobile, it showed error “server connection failure. Check network setting”
eSpace desktop can login with eSpace desktop(labtop and Mobile connected to same WLAN network).

Note: ECS version (V200R003C10SPC100), eSpace desktop version (v2.3.0.023) & eSpace Mobile version (v2.3.2.10).

Alarm Information

none

Handling Process

1.depend on customer feedback information:

customer tried to login from my eSpace mobile, it showed error “server connection failure. Check network setting”
eSpace desktop can login with eSpace desktop(labtop and Mobile connected to same WLAN network).

2.eSpace mobile login should passby MAA. so check MAA log ( (install path\eSpace_UC\eSpace_UC_Server\Logs\MAA )first:

There is a error as bellow:

       Line 21422: 2016.06.07 at 03:03:40 PDT ERROR com.huawei.ecs.im.sdk.forward.LoginApp 81 parseResponseMsg - login app server error93089

       Line 21696: 2016.06.07 at 03:03:45 PDT ERROR com.huawei.ecs.im.sdk.forward.LoginApp 81 parseResponseMsg - login app server error93089

this means the authentication fail between APPagent and MAA.

3.log in sql2008, check the appagent connect MAA password.

cid:image003.png@01D1C1A4.A261A2C0

it is not same as MAA configuration:

cid:image002.png@01D1C1A4.A261A2C0

 

Root Cause

the authentication fail between APPagent and MAA

Solution

  Modifying the AppAgent Application Authentication Service

Generally, you do not need to modify the parameters in the AppAgent application authentication service. Perform the following steps if you want to modify the parameters. The default value of Service ID is AppAgent, and the default value of Password is 1qaz@WSX.

http://localhost:7890/pages/DEE05081/04/DEE05081/04/resources/public_sys-resources/icon-note.gifNOTE:

You do not need to configure the default address for the service.

1.     Log in to the BMU as the admin user.

2.     Choose Functions > eSpace Maintenance > eSpace Service.

3.     Click the modification button next to Service ID whose value is AppAgent.

·         To change Service ID, change guid in AppServer of the MAA configuration file server_config.xml at the same time.

The path of server_config.xml is D:\Program Files\eSpace_UC\eSpace_UC_Server\Server\MAA\webapps\MBServer\WEB-INF.

<appserver>

                <!--appserver connection type tcp/http-->

                ...

                <guid>AppAgent</guid>

                <guid_pwd>b90a16df9be4614039ee186315017d31</guid_pwd>

                <url_ecs_login_action>/appServer/appserver/userlogin.action

                </url_ecs_login_action>

                ...

      </appserver>

·         To change Password, change guid_pwd in AppServer of the MAA configuration file server_config.xml at the same time. You must use a password encryption tool to encrypt the plaintext and write it to the configuration file.

a.     Obtain the encryption tool SecurityTool(v2.0).jar.

The path is D:\eSpace_UC\eSpace_UC_Server\Server\Tools\DBUpdateTool\lib\.

b.    Double-click SecurityTool(v2.0).jar.

c.     In Original String, enter the plaintext password, such as Huawei123 and click Encode. A ciphertext password dc821a5d2ac910fcea66881023c6ae9e is generated.

d.    Set the value of guid_pwd to the ciphertext password.

e.  <appserver>

f.                  <!--appserver connection type tcp/http-->

g.                  ...

h.                  <guid>AppAgent</guid>

i.                  <guid_pwd>dc821a5d2ac910fcea66881023c6ae9e</guid_pwd>

j.                  <url_ecs_login_action>/appServer/appserver/userlogin.action

k.                  </url_ecs_login_action>

l.                  ...

m.        </appserver>

Restart the MAA service.

Suggestions

none