Thanks PhilRunning DBUpgrade for current version (15.2.0.1) and Custom version solved the issue.I have to make one comment - I ran the imports based on the Database Procedures Guide. It could be helpful to have a sentence in about this.
For the record: I have created a new profile in UAT, and attaching the mentioned DB to it still produces the error
Thanks, Phil I have attached the old UAT database, and DC works fine. But attaching the new DB DC crashes
Yes. I changed from UNC to IP as well (http was already in place)
Thanks, Lynn. I have tried that, and it did not help.Dispatch Console worked before I attached new databases to the user profiles (copied from our live environment), so my gut feeling is that the address is incorrect. In the database I find that dse_session.dse_server is 192.168.61.130 (the address for DSE-server in the live environment). Changing it to 192.168.61.99 (correct IP) + IISRESET does not solve this. Hmm
Thank you Phil. These phones have been in the field for a long time. We’ll just be forward compatible and get them new phones. I see no reason to use your or our time trying to get this sorted
Hi Ugo The users have deleted the app and downloaded from Play, so they should have 3.3.0. After specifying the server address, the app stops responding. I have just received specifics, and having old versions of Android seems to be what is in common. These phones have been used for Astea Mobile for years and years. Users with newer Samsungs or iPhone do not have problems
Thanks, Andrew. We finally figured out that it was the Mat. Return Reason module that needed some configuring. Solved now
Already have an account? Login
No account yet? Create an account
Enter your 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.