Hello @Phil Seifert & IFS team,Thank you so much for helping us resolve issue.
Hello @Phil Seifert , Thank you for your response and direction.We have successfully completed the task.
We have already asked users to perform that activity but still issue is there.
Hello @Phil Seifert , Thank you so much for your quick response.We are checking on your suggestion and update you.
Hello @Phil Seifert , Thank you so much for the very quick response.
Hello @Phil Seifert , Thank you so much for your quick and in detail response.
Thank you So much, @Phil Seifert for your help.It resolves my request.
Thank you @bskallerud & @Phil Seifert for your quick response and help.I appreciate your help & very quick response
Under Dispatch Console Session that node was inactive.But we are not sure how this one node got deactivated.
We have fixed this.
Thank you @Phil Seifert .That works for HF27. Now I can see the Google Map on the Dispatch Console and the error message also disappear from the screen.
Hello @Phil Seifert , Thank you for your quick response. We have V14 (HF27) in our test environment which we will be going to deploy on production soon but on HF27 also we see the same error. message “An error occurred while trying to load the map: The remote server returned an error (404). Not Found. Save the Event log so that it can be sent to Astea for analysis.” Can we follow the same steps as mentioned in option B (Manually change the file)?
Hello @Reid Gilbert , Yes, an error is from service order module.
Hello @Reid Gilbert , Thank you for your reply.I have attached the screenshot.
Hello @Eisha Hasnain, Thank you so much for your help.
Hello @Eisha Hasnain, Yes, we tried in a test environment. I have unchecked the box in logistic settings but still in the mobile application Autosource checkbox is enabled.
Hello @Pranavan Paranthaman,Thank you for your response.We are using Astea Alliance (14.0.0.24) in production and the Auto Source checkbox is not enabled but it is still visible in the mobile application.
Yes, We tried IISRESET but it has not resolved the issue.Yesterday we have restarted all our production servers after windows OS patching and after that Astea Mobile is giving this error on Login page.
Thank you Phil. I will raise ticket.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
