11-15-2012 04:12 PM - edited 11-15-2012 04:27 PM
I'm facing below issue with jad installation from a webserver. I have placed all my cod files with a jad file in our weserver. and made call to jad file. After some secs getting message as below. The same thing is working with OS 6 version phone but not with OS 5
907 invalid cod exceeded the limit of number of bytes
Solved! Go to Solution.
11-15-2012 06:47 PM
So how large is the cod file?
I always decompress cod files that have sibling cods. Some older browsers, may be including OS 5.0, struggle to download a single large cod.
if you are not clear on sibling cod files, have at look at this Thread.
11-15-2012 06:57 PM - edited 11-15-2012 06:58 PM
1) So you have about 12 cod files?
2) And the actual download is identical in both OS 6.0 and OS 5.0? Same jad?
3) You are doing this download using the Browser?
4) and a silly thought - did you build this with OS 5.0?
PS. Welcome to the forums!
11-15-2012 07:03 PM
actual cod files 591 kb
1) yes it has 12 cods up to abcd-11.cod
2)yes used same jad in 2 simulators , os 6 is ok but not os 5
3) Yes downloading using browser.(any alternative ?)
4) Yes did with 5
11-15-2012 07:04 PM
One additional question. Are the OS 5.0 BES users?
have you seen this?
11-15-2012 07:22 PM
If you are testing on SImulators on the same PC running the same MDS Simulator, then the KB article about connections limits can't apply.
Sorry this one has me beaten, I have never had the OS 5.0 Browser throw up its hands on a download I have created, that the OS 6.0 Browser was fine with. Your file sizes are not huge.
If you really wanted to count the MDS Simulator out of the running, start WiFi on the OS 5.0 Simulator (Manage Connections --> Set up Wi-Fi Network, follow you nose, then start WiFi on device), then change the default browser configuration (Options --> Advanced --> Browser) to the Hotspot browser. Stop MDS Simulator and see if you can still Browse. Then try the download again.
11-16-2012 04:47 AM
I note that you have marked my preceding post as the solution. Does that mean that in your case the problem was caused by routing the download through MDS? Can you give us a little more informaiton please. Thanks