Hello,
After updating the E6 to Belle 111.130.0622 using software update on the Nokia Suite I am not able to install my Qt application on it! It gives "System Error" message!
What could be the reason for this?
Hello,
After updating the E6 to Belle 111.130.0622 using software update on the Nokia Suite I am not able to install my Qt application on it! It gives "System Error" message!
What could be the reason for this?
Basically "System Error" does not sound like instalaltion time error, but actually run time panic, thus do check the panic code: http://www.developer.nokia.com/Commu...ded_panic_code
Is that an install failure or a run failure (even if the app is run at install time)? For run time errors see Jukka's comment. For install errors, see http://www.developer.nokia.com/Commu...er-debug-guide
-- Lucian
symbianyucca & Lucian,
The application installed well n worked fine before updating the device to Belle! And it's during the installation process, not run time. On installation of the smart-installer build, during the phase "Finalizing installation" it gives an error message reading "System Error".
So, both your links did't give me much information to solve this issue. What could be the problem with the software update?
ok, here's one more link: http://www.developer.nokia.com/Commu...er_for_Symbian check the Where to find help section and copy paste the logs here.
Here's the content from the generated log file: log-boot.txt
03/12/2012 2:11:27 SmartInstaller bootstrap begins
03/12/2012 2:11:27 + Init()
03/12/2012 2:11:27 * Ovi Store 0, profile 0
03/12/2012 2:11:27 + WaitForInstallComplete()
03/12/2012 2:11:27 Waiting for installer to become idle
03/12/2012 2:11:28 - WaitForInstallComplete(): 0x2002CCCF
03/12/2012 2:11:28 - Init()
03/12/2012 2:11:28 MachineUid = 0x20023767 (0)
03/12/2012 2:11:30 ADM (0x2002CCCE) = 1 (v2.02.0)
03/12/2012 2:11:30 + ReadConfiguration()
03/12/2012 2:11:30 configFile = C:\Private\2002cccd\config.ini
03/12/2012 2:11:30 configUrl = http://dl.qt.nokia.com/smartinstaller/ (default)
03/12/2012 2:11:30 - ReadConfiguration(): -1
03/12/2012 2:11:30 + SetFileNameInfo(): ver = 4
03/12/2012 2:11:30 Application sis 'c:\private\2002CCCE\import\anApp.sis'
03/12/2012 2:11:30 Filename is 'adm_changes.xml'
03/12/2012 2:11:30 + ValidateIAP()
03/12/2012 2:11:30 Getting new settings (3, 0, -1: 0)
03/12/2012 2:11:30 Browser IAP = 3, mode 2, SNAP 0 (0)
03/12/2012 2:11:30 Loading helper (0)
03/12/2012 2:11:33 Got 2 IAPs (0)
03/12/2012 2:11:33 IAP[0]=2
03/12/2012 2:11:33 IAP[1]=3
03/12/2012 2:11:33 Starting with IAP 2
03/12/2012 2:11:33 + SetIAP(): 2
03/12/2012 2:11:33 - ValidateIAPL(): 0, 2
03/12/2012 2:11:33 - SetFileNameInfo()
03/12/2012 2:11:33 + RequestState(): 0->2
03/12/2012 2:11:33 + StateDownloadL()
03/12/2012 2:11:33 Downloading 'C:\system\adm\adm_changes.xml'
03/12/2012 2:11:33 from 'http://dl.qt.nokia.com/smartinstaller/adm_changes.xml'
03/12/2012 2:11:33 Receiving 'C:\system\adm\adm_changes.xml'
03/12/2012 2:11:33 - Download()
03/12/2012 2:11:33 DlSt= 2, PrSt= 2054
03/12/2012 2:11:33 DlSt= 15, PrSt= 0
03/12/2012 2:11:33 DlSt= 2, PrSt= 500
03/12/2012 2:11:33 DlSt= 2, PrSt= 1000
03/12/2012 2:11:40 DlSt= 2, PrSt= 1020
03/12/2012 2:11:40 DlSt= 2, PrSt= 2020
03/12/2012 2:11:40 DlSt= 3, PrSt= 2021
03/12/2012 2:11:40 Starting download
03/12/2012 2:11:40 DlSt= 2, PrSt= 500
03/12/2012 2:11:40 DlSt= 2, PrSt= 1000
03/12/2012 2:11:40 DlSt= 2, PrSt= 1020
03/12/2012 2:11:40 DlSt= 2, PrSt= 2030
03/12/2012 2:11:40 DlSt= 2, PrSt= 2050
03/12/2012 2:11:40 DlSt= 2, PrSt= 2051
03/12/2012 2:11:40 DlSt= 2, PrSt= 3002
03/12/2012 2:11:40 DlSt= 4, PrSt= 0
03/12/2012 2:11:40 IAP set to 2
03/12/2012 2:11:40 + RequestState(): 2->3
03/12/2012 2:11:40 DlSt= 16, PrSt= 0
03/12/2012 2:11:40 + ParseFile('C:\system\adm\adm_changes.xml')
03/12/2012 2:11:40 - ParseFile()
03/12/2012 2:11:40 ADM is up-to-date (v2.02.0 / v2.02.0)
03/12/2012 2:11:40 + RequestState(): 3->6
03/12/2012 2:11:40 + LaunchAdm()
03/12/2012 2:11:40 LaunchCtrl: 3
03/12/2012 2:11:40 len 94
03/12/2012 2:11:40 Launching ADM.exe '1519 4 537054415 2 3 c:\private\2002CCCE\import\anApp.sis'
03/12/2012 2:11:40 Revealing ADM menu icon
03/12/2012 2:11:41 - LaunchAdmL(): 0
03/12/2012 2:11:41 + RequestState(): 6->7
03/12/2012 2:11:41 + StateDownloadL()
03/12/2012 2:11:41 - Download()
03/12/2012 2:11:41 + RequestState(): 7->9
03/12/2012 2:11:41 DlSt= 15, PrSt= 0
03/12/2012 2:11:41 + RequestState(): 9->9
03/12/2012 2:11:41 + RequestState(): 9->9
03/12/2012 2:11:41 + RequestState(): 9->9
03/12/2012 2:11:41 + RequestState(): 9->9
03/12/2012 2:11:41 + ExitApp(9): 0
03/12/2012 2:11:41 + CStateMachine::Stop()
03/12/2012 2:11:42 + StopWaitNote(6)
03/12/2012 2:11:42 + CStateMachine::RunError(-1003)
03/12/2012 2:11:42 ~SmartInstaller()
03/12/2012 2:11:42 ~StateMachine()
03/12/2012 2:11:42 DlSt= 13, PrSt= 0
03/12/2012 2:11:42 SmartInstaller bootstrap ends
That should not be a problem, it is the boottrap having an internall error but only *after* launching the ADM component (the real "smart installer"). Check the other log file created in the directory, the log.txt.
-- Lucian
That's the problem, the other log file "log.txt" is not created at all! Installed it twice to verify the same. But, both the times there was only this file in the folder!
Ok, we need to have a look at this. If your app is already published, please send me a link to it via PM. Otherwise please send me the SIS file at <username>@ovi.com
-- Lucian
Lucian,
Yes, the 1st version of the app is already published. I have dropped you a message with the link to it.
Is there any update on the same... we are also getting same error when we install our app on a Belle device, the same gets installed on older version of the OS.
-thanks
Hi madhavnarain, thanks for bring this up again.
RS3, I just run a test with your app (sorry for the delay) but I can't reproduce the issue. I installed the app twice, once with sideloading and once from the Nokia Store, with the same result: the app installs without any problems.
My test was done with E7 and not with the E6 (as in RS3's test) but they are expected to behave the same. I will try to find the time for an E6 test as well and update you on that, but the more input we have from you guysm about the devices and firmwares used, the easiest would be to find the source of the problem.
Update: Test done on E6 as well, no problem found.
-- Lucian