5800 non-update

I had to do a hard reset a couple of days ago, and so needed to reinstall maps. I tried FOTA via the SW updater prompt, but after claiming to have downloaded, failed to install at about 1.5MB.
So I downloaded the installer to the PC (I won't use OVI suite - I've tried it and not only does it not do what it's told, it hogs so much PC resources and memory that it's more a liability than a help) and installed successfully from there. But as soon as I opened it, it offered me an update, so I clicked on it and - guess what - it failed!!!
Any ideas on where to go now? Are there some installation files (from FOTA) still hiding in the system? And if so how to get rid.....
All ideas welcomely received.

@rbruce1314
What version of OVI Maps is pre-installed on this version as can't remember?
Bear in mind that when updating from v3.04 to v3.06 existing map data needs to be deleted.
I would suggest that you delete E:\Cities +.qf file as folders will be recreated next time application is opened and also try going to Go to Menu > Settings > Application mgr. > Installed apps and uninstall any of these present: Open C LIBSSL,Open C LIBSSL Patch, OVI Maps Wi-Fi/Network Positioning, PIPS Installer, Share Location Agent, Share Location, Share Location Widget, Standard C++ Library Common, Standard C++ Library Patch, Symbian OS Pipes Upgrade, Symbian OS PIPS Upgrade & Upgrade for OpenC LIBZ Support.
Now try to update again.
Happy to have helped forum with a Support Ratio = 42.5

Similar Messages

Key flexfield - protecting one of the segment as NON-UPDATABLE/ READ-ONLY

Key Flexfield setup for "People Group Flexfield" consists of seeg1,seg2,seg3,seg4.
We would like to make Seg1 of this flexfield "READ ONLY" / "DISPLAY ONLY" / "Non-Updatable".
Please advise possible way of making this functionality.
I have tried, following but no luck :
1) Limitations of Forms Personalization [ID 420518.1]
Forms Personalization is not possible for any key flexfield structure or segments.
This is a limitation of Forms Personalization on Flexfield. There was an enhancement request Bug 5506506 - "PERSONALIZE FLEXFIELDS BY USING FORMS PERSONALIZATION" but it was rejected the enhancement request as this is not feasible. A Flexfield is a single field in a form but then when you click into it and it opens up the flexfields window, the multiple fields you see is actually a user exit with multi segment values, not form fields. No Form Personalization events are passed to flexfield windows (user exits). No Form Personalization events are passed to segments inside the flexfield window (user exit).
2) Key Flexfield Security Rules Enabled
Defining security rules on any segment in key flexfield makes all segments as read only. Per Oracle Document:"Defining security rule on key flexfield combination on one or more segments allows all segments to be not updatable"

In SSHR, I believe it is possible although I have not done it before, I have spoken to people who have.
You need to have access to jDeveloper and be able to open up the SSHR page in question. Find the internal ID of the flex item within the SSHR page in question.
Then you create a new item in personalization and set that new item to have the same ID as you retrieved from jDeveloper. Make that item read only and configured the 'default' flex to not show the segment in question.
That is basically the way this can be achieved but it is not straightforward and requires a cursory understanding of OAF.
I do not know if it is possible to do this in the PUI. Would be interested to know requirement behind essentially showing a static read only field in a professional form - can the admins not be trusted to leave it alone? One workaround would be coding a user hook or custom library to error if that field is updated. Not read only but would stop those pesky Administrators meddling with it!

Problem with non-updated idocs

Hi,
we have a problem after upgrading from 3.5 to 7.0. Lots of extractors end
in an error-message concerning non-updated idocs. Every day several
extractors have this problem. This are not always the same extractors. As
a result we must repair many extractions manually.
I know the procedure of how to repair, but I want te know how I can prevent
extractors from running into this problem in the first place.
Any suggestions?
This is the problem-message that we get...
Non-updated Idocs found in Source System
Diagnosis
IDocs were found in the ALE inbox for Source System that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs
manually using the Wizard or by selecting the IDocs with incorrect
status and processing them manually.

It has been happening on our env as well (BI 7.0 SP 12), time to time one load or the other gets into this problem and it waits yellow for few hrs before turning red.
I can correct the IDOC and move on or run the load again it works fine.. but the process chain gets held up not going to the next stage for hrs..
any resolution on your problem..
thanks
Mayil

Setting check box (in detail block) as (non) updatable...

Hi,
I have a master-detail form. The form does execute a query when it opens. Now, according to a condition i want to do the check box(in detail block) as non- updatable.
I have tried to write the appropriate code in:
WHEN-NEW-RECORD-INSTANCE(in the master block level)
WHEN-NEW-ITEM-INSTANCE (in the detail block level)
POST-QUERY(in the detail block level)
but it does not work 'perfectly'. I mean that in most cases even one of the above triggers does not execute (for example the 'WHEN-NEW-RECORD-INSTANCE' but only after i click on this new record instance. I mean that after this on this new record the condition is estimated....)
or
it does execute but after i click on the checkbox (for example the 'WHEN-NEW-ITEM-INSTANCE').
The code i tried looks like the following:
if :block.item=<condition>
then
set_item_property ('detail_block.chk_box',updatable,property_false);
else
set_item_property ('detail_block.chk_box',updatable,property_true);
end if;I consider to use the WHEN-CHECKBOX-CHANGED trigger and code which looks like:
if <condition>=true
then
    /*i set the value of the checkbox as the opposite of what it is just after the click on it...*/
if :detail_block.chk_box=0
   then
     :detail_block.chk_box=1;
else
    :detail_block.chk_box=0;
end if;
set_record_property(currect_record,status,query_status);
set_item_property ('detail_block.chk_box',updatable,property_false);
end if;The truth is that i do not like very much this code, but is there any alternative...???
Note: I use Dev6i with patch 12
Thank you,
Sim

I build a little testform based on HR-schema-table DEMO_USERS and switch each second record to be not updateable, works without problems (code from POST-QUERY-trigger):
DEFAULT_VALUE('1', 'GLOBAL.SWITCH');
:GLOBAL.SWITCH:=3-:GLOBAL.SWITCH;
IF :GLOBAL.SWITCH=2 THEN
SET_ITEM_INSTANCE_PROPERTY('DEMO_USERS.ADMIN_USER', TO_NUMBER(:SYSTEM.TRIGGER_RECORD), UPDATE_ALLOWED, PROPERTY_TRUE);
ELSE
SET_ITEM_INSTANCE_PROPERTY('DEMO_USERS.ADMIN_USER', TO_NUMBER(:SYSTEM.TRIGGER_RECORD), UPDATE_ALLOWED, PROPERTY_FALSE);
END IF;     Edited by: Andreas Weiden on 31.03.2009 21:24

Non-updated Idocs found in Source System

Hi Experts,
I am getting an error Non-updated Idocs found in Source System
Plz help me to resolve this issue.

Hi
BD87 Update Idocs manually.
1. When you look in the Monitor screen for the first time on a day you mostly will see some Loads that have yellow traffic lights. When you click on the lowest line of the Load (with the time of Load start) you will get the next popup screen:
2. Here you can click on the "Yes" button. The Load specification window (right side of the screen) will now be filled with data.
3. You can now start the manual processing of the IDocs. You go to the "Details" tabpage of the right window. You right click on the line with the red traffic light stating "Request IDoc : IDoc ready to be transferred to application" on the "Details" tab page of the Load. In the option menu that appears choose the option "Update manually in OLTP" (click it).
4. You will get to the next screen (which is in fact a transaction in the source system (SAP R/3) where you can update the IDoc that is send by the source system)
5. Now click the "Excecute" button on the left of the screen (or press the F8 button on your keyboard). You will get to the next screen:
6. This states that the IDoc has been passed through to BW. You return to BW by clicking the "Back" button (or pressing the F3 button on your keyboard) twice. After the first time you will see the previous screen and after that the Monitor screen again.
7. You will now see that the Status of the Load has turned to yellow or green. When it is yellow you will have to wait a little time (the execution of the Load in BW is still running) and by clicking "Refresh Details" button on the left upper side of the screen (or pressing the F8 button on your keyboard) you will see the Load turn green.
Hope it helps

R3 to BW Extraction fails: Non-updated Idocs found in Source System

We load data from R3 to BW and this process has been successful for the past few days except last night. The error msg is listed below in between two dashed lines:
Non-updated Idocs found in Source System
Diagnosis
IDocs were found in the ALE inbox for Source System that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
I checked the system connection by right click the source system in the Source System page on BW and selecting "Check" and "Customizing for Extractors" from the context menu and find everything works fine.
Any idea about the IDOC thing?
Thanks

hi Subray/Bhanu,
With WE05, find some records with yellow status. How to find some missing data here?
With BD87, under BW system folder, there are two folders:
1. IDocs in outbound processing
2. IDoc in inbound processing
Under 1st folder, there is one yellow status folder called "IDoc ready for dispatch (ALE service)", continue to expand another folder called CREMAS under it, there is a blue information line which is "Receiver found , Data filtered , No conversion , No version change".
Under 2nd folder, there is one yellow status folder called "IDoc ready to be transferred to application", continue to expand other two folder under it called "BBPIV" and "RSRQST", find there is a red flash status line which is "No resources, immed. processing not possible: Too few free dialog work" under these two folders.
I need to go ahead to select these two red flash status lines and then press the Process button at the top bar?
Thanks
Message was edited by: Kevin Smith

How to make a record as Non Updatable

Hi all
I want to make the whole record(multi record block) as non updatable. My condition is, I have one status field in the base table block, when I query the form if the "status" field containing value 'Y', the user should not be able to update any item in the record. How to acheive the functionality?
Thanks in advance
ram.

Hi,
Have you tried using the set_item_instance_property('',update_alowed,..) built_in in the when_new_record_instance trigger on the block level?
You can check there the :block.status field,and set the item instances in that record to non updatable.

Non-updated Idocs found in Business Information Warehouse

Hi,
I got the following error while trying to load data:
"Non-updated Idocs found in Business Information Warehouse
Diagnosis
IDocs were found in the ALE inbox for Business Information Warehouse that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually. "
Please help me solve this issue.

Hi,
Actually i tried all these options. I updated the idoc manually, and now the following message comes :
"Request still running
Diagnosis
No errors found. The current process has probably not finished yet.
System Response
The ALE inbox of BI is identical to the ALE outbox of the source system
or
the maximum wait time for this request has not yet been exceeded
or
the background job has not yet finished in the source system.
Current status
Data packets were found that have not yet been rea "
And the process is on for the past 5hours. Can i do something regarding this?

Idocs error: Non-updated Idocs found in Business Inormation Warehouse

Hi
I have found this error for delta load.
"Non-updated Idocs found in Business Information Warehouse"
I know that if the non-updated idocs found in source system, we can use
BD87 to manual update.
But it is with in the BI.
Can someone please help with steps involved.
Thanks

I will suggest you to set the delta load request to red and then reset the delta flag. Reload the last repested delta will include all missing idocs. That way it is much cleaner.
Good Luck,
CL

How to create editable form with non-updatable vo

Hi,
i need to create a new form on non-updatable VO.
My requirement is: i have Data base View, based on that view i have created VO, based on this VO i need to create new form, when ever i submit a request, web service will invoke and that validate the data and sends to the data base.
when ever i drag drop the vo i couldn't able to enter any data bcoz all the data are coming in the form of output boxes.
can any one help how can i create this.

Check the setting of your viewobject attributes settings, most probably they are 'updatable never', set them to "updatable always".
This way you can drag the view as an editable form.
About sendind data to the database, i guess you have an idea how to do it afterwards :)

Display description, but non-updatable data block

To display my Item_Description, I've created a post-query trigger to lookup Item_Description based on Item_Num, which works fine, except if the user does not have update priveledge. By default the data block is non-updatable. If the user has update, then the block is set updatable at run-time.
Problem is, for a non-update priveledge user, the form errors when the trigger attempts to set the description field. [Even though the field is set updatable by default.]
What am I missing? Thanks.

I'm confused. You say:
"By default the data block is non-updatable."
but then you say:
"...the field is set updatable by default."
If the data block is not updateable, then you can't make the item updateable.
Assuming the default is non-updateable, and a user does not have update privilege, then the error message you are getting is correct because the trigger is trying to do an update when the item is non-updateable.
If you need the trigger to do an update, then you need to make the item updateable. If you don't want the trigger to do an update for this user, then first check if the item is updateable (use the get_item_property), and if it is updateable, then let the trigger do the update.
Message was edited by:
Mark Roberts

Nokia 5800 Software Updater ....

Well I just Bought My Nokia 5800 XM 3 Days Back And Updated to Firmware v50
In that time I was able to See Quick Office.
Today i noticed that the application is missing. So i tried to reinstall using nokia software updater.
It downloaded the latest Firmware. Then i got this Message
My Nokia is connected to back of my pc. So I am assured that it isn,t connected to any hub or keyboard docking station.
Also I tied to change the USB location. but none of the work.
So how shoul i Reinstall the Firmware??????

And i Forgot one thing to mention that i updated the firmware from Nokia Care.

5800 after update (V51.0.006) no Bluetooth

After installing the last Version(V51) on my Nokia 5800, I cant enable the bluetooth!
After input the code *#2820# the bluetooth MAC adress is empty!
Following I have tested, but nothing works:
- hard-reset
- soft-reset
- remove accu for a long time
- format Memorycard
Is it possible to make a "downgrade".
thanx for help.
Gerald

Hi, have you turned bluetooth on? After updating my n97 my macadress was empty untill I had turned bluetooth on for the first time.
Go to menu->settings->connectivity->bluetooth->bluetooth ON. Then try again.
You can not downgrade.

Nokia 5800 Firmware update V20

Hi all ,
can anyone advise if this works with the phone as i keep hearing about system failure notice with the new version ?
who has installed it on there phone and does it make any difference ??
Message Edited by 5800uk on 19-Feb-2009 05:47 PM

yes v20 was buggy thats why Nokia have removed it off there NSU. It shouldnt be long til the next update comes out on NSU. Nokia 5800 is a very demanding phone and Nokia will make new firmware qucikly so users who have v20 firmware can update to later version which will solve handset issues and those 5800 that people purhcase of the net some come with v20.
If you find my post useful then click on
Kudos!Nokia N96 (v20.050 / RM-247)
www.shaysoft.net | Competitions!

5800 Software update V20.0.012

I updated my Nokia 5800 with V20.0.012 (Custom Version 20.0.012.217.06). The dictionary and search facility have not installed. Any advice would be most welcome.
Solved!
Go to Solution.

When installing an other application via nokia suite, the dictionary and search facility magically appeared!

5800 non-update

Similar Messages

Maybe you are looking for