OTAP issue- server not found/ JAD server not found | Thales IoT Developer Community
May 10, 2017 - 9:32am, 3321 views
We are using Bgs5 module for our telematics project. The OTAP was working earlier after the updating a new version it is not accepting any further OTAP updates. There is no changes on server side as well. I need a technical support for this issue. it may be a configuration issue. i couldn't figure it out. Following message is the error log from the OTAP trace.
AT^SJOTAP = "cwm","http://220.127.116.11/TAP66.jad",,,,"gprs","www",,,,,"off","off"OK
AT^SCFG = "Trace/Syslog/OTAP","1"OTAP.OUT STARTED
[OTAP] midlets stopped
[OTAP] PS Detach
[OTAP] Starting installation
[OTAP] Try to get http://18.104.22.168/TAP66.jad ...
[OTAP] ERROR: Server not found.
[OTAP] Transfer finished.
[OTAP] DONE with status: JAD Server Not Found
[OTAP] operation failed
[OTAP] Reboot now.
Please contact me on following mail Id: firstname.lastname@example.org.
Could you please provide additional information - what version was used before and what version is used now - can you check ATI1 reply? What is the application doing?
Thanks for the reply. Here is the ATI1 response from our device.
I have tried to install and update your application on my BGS5 module (I've used your SJOTAP configuration without any changes) and it was possible with the same and newer firmware revision.
Could you answer some additional questions? Are you using the same MNO and same configuration? What changes have you made in the application since OTAP was working? Have you tried to install the application while it was not running to check if the running MIDlet has really an influence on the OTAP procedure result? Is it only one device that is failing and is it failing each time?
Sorry for the delayed response. I am using the same MNO but I am not sure the configuration is same. Recently I got KT from my ex trimble engineer. I followed his instruction to configure the eclipse. The OTAP is working once with the new configuration but it is not taking the OTAP again. I tried it multiple ***** on multiple devices I tried to rollback to old application versions but all the versions are getting the upgrade once and then its not taking anything. All the devices are getting the SERVER NOT FOUND error on OTAP TRACE. No other errors found. Are there any other way to track the issue during OTAP. If I have to check the configuration what are the configurations I need to check?. I am sharing few more version folders link for OTAP testing at your side.
1. http://22.214.171.124/J121/TAP66.jad -- old version(working)
2. http://126.96.36.199/J310133/TAP66.jad -- new Application version(not working)
3. http://188.8.131.52/J122/TAP66.jad -- onld versions(working)
I am able to OTAP the 133 version on 122 version. After this SERVER NOT FOUND error comes and exits OTAP process in few seconds.
I've tried updating the application version 133 a few ***** and then to 122 and again to 133 and I wasn't able to find this problem. But on my side the application may be working differently because there's no hardware connected.
Have you also tried to start OTAP while your application is not running to check if it has an influence on the result? By configuration I meant the GPRS APN and user/password if needed. But you could also check what are the differences in module configuration between versions - if there are for example additional AT commands used.
The only way to trace OTAP is the OTAP tracer. You could also try to send AT+CEER after the failure - maybe this will show something more.
Thanks for the response. The OTAP is working now. will check it in field vehicles.