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

eSpace UC V100R002C01SPC100 eSpace mobile log in failed through MAA

Publication Date:  2015-11-15  |   Views:  321  |   Downloads:  0  |   Author:  h00453638  |   Document ID:  EKB1000089892

Contents

Issue Description

in a customer site, eSpace UC V100R002C01SPC100 all eSpace mobile log in failed through MAA.

Alarm Information

none

Handling Process

1. from the MAA log, we can see Appserver feedback wrong code 93018 to MAA, this means eSpace mobile log in failed.

 

2, for UC 1.1 version the MAA and BMU are installed in the same server with the same log file bmu.log. then we check the bmu.log file that analyze the Appserver configuration file eProxy.cfg.xml  failed.

3. check the eProxy.cfg.xml file, but this file is empty. we doubt the file is damaged by some reason.

4. download the same version eProxy.cfg.xml file to replace the old eProxy.cfg.xml file and reconfig it.

5. restart BMU servicce and test ok;

Root Cause

eProxy.cfg.xml file is damaged by some unsure reason.

Solution

1. from the MAA log, we can see Appserver feedback wrong code 93018 to MAA, this means eSpace mobile log in failed.

 

2, for UC 1.1 version the MAA and BMU are installed in the same server with the same log file bmu.log. then we check the bmu.log file that analyze the Appserver configuration file eProxy.cfg.xml  failed.

3. check the eProxy.cfg.xml file, but this file is empty. we doubt the file is damaged by some reason.

4. download the same version eProxy.cfg.xml file to replace the old eProxy.cfg.xml file and reconfig it.

5. restart BMU servicce and test ok;