Solved

Astea Mobile Customizer not working

  • 27 November 2023
  • 5 replies
  • 70 views
N
Rank
Userlevel 1
Badge +6

Hi Team,
Astea mobile Customizer not working.
Site is up and running but receiving errors.
 

Errors in browser console:
1) Failed to load resource: 500 (http://server_fqdn/asteamobilecustomizer/api/locale/getLocale?lang=en-US&part=portal)
2) Failed to load resource: 500 (http://server_fqdn/asteamobilecustomizer/api/security/account)

After clicking OK Button, we get a continuous loading screen.
 


Any suggestion or advice to resolve the issue will be appreciated.
​​​​​​​

icon

Best answer by Reid Gilbert 27 November 2023, 13:09

View original

5 replies

E
Rank
Userlevel 6
Badge +10

Hi Narendran, 

 

Thank you for asking question. Have you tried the same URL from Astea Native mobile app. We don’t support the Edge browser, you should use the Windows Native App or the iOS or Android Native App.

Kind Regards,

Eisha 

Phil Seifert
Rank
Userlevel 7
Badge +21

In addition to Eisha's statement, I see your URL is http:// which Google took out Chrome support for the SQLDB in general across non-encrypted connections.  I mention this as Edge is also using the Chromium engine too. Please use the Native App.

N
Rank
Userlevel 1
Badge +6

Hi Team,
Thanks for the suggestion. However, even in native, I am receiving some error.
PFA screenshot for reference.
 

Any other checks I must be doing? Let me know if I am missing something.

Reid Gilbert
Rank
Userlevel 7
Badge +15

Is the Redis Cache service actually up and running in this environment?  Try stopping those services and restarting those to see if that helps.  Then go into the \Program Files\Alliance Mobile Edge\AsteaMobileCustomizer\ folder and run the UpdateAll.bat file as an Administrator (right-mouse-click and select the Run As Administrator option).  Then check the resulting .txt file to see if any errors are captured in there.
Thanks,
Reid

N
Rank
Userlevel 1
Badge +6

Thanks for all your support.
By running updateAll.bat in utility server, the issue got resolved.

Reply


Terms & ConditionsCookie settings