Warning during maintenance of IT0008

Hi All,
When i try to maintain Basic salary in IT0008, i get a warning "Basic Salary is not a part of the Pay Components".
Could anybody guide as to what is wrong and where?

Hi Muthu,
Thanx for your reply.
Emp Group in IT0000 was in place. However, the position assigned was incorrect and hence the warning was in display. Now the warning has been taken care of but IT0008 is giving run time error "WRITE_TO_OFFSET_TOOLARGE"
Error analysis
In a "WRITE src TO dest+off[(len)] [INDEX i]" statement, "off" contains a target field offset (3) which is larger than the length of the target field "dest" (4). This is not allowed.
Any clues??

Similar Messages

Define dateline category during maintenance of billing plan type

Hi, I am in the midst of setting up the SD configuration in my current system from scratch and this is the error message that I have encountered, "Define dateline category during maintenance of billing plan type". Basically, what I have done is to create a contract using tcode 'VA41'. This error happened on the second screen after inserting contract type, sales org, distribution channel and division. any guru out there, pls advise. Thanks!!!
Regards
Andy

Hi!! Andy,
Dateline category controls data such as the billing block and the billing rule at the billing date level of the billing plan.
We assign a date category to billing plan in t.code OVBJ. check the assignment, make them if neccessary.
Hope this will solve your problem.
Regards,
PATHIK
Dear Andy,
Please check & maintain the enteries in t.code OVKK.
Do give your feedback.
Regards,
PATHIK
Message was edited by:
Pathik Pandya

MacBook shuts down without warning during calibration (39% battery power)

My MacBook has been shutting down without warning during recent calibrations (which I've done approximately every two months). Most recently it shut down after 2 hours and 20 minutes on battery power with a battery reading of 39% -- i.e., nowhere close to the 0% of a fully rundown battery.
The result is that:
I'm not seeing the 'low battery' warning dialog before the computer shuts down; and
(ii) I'm not able to save current work and close all applications when the battery's charge gets low, before the computer goes to sleep (because it just shuts down without warning)
Can I do anything about this? Is it just an unavoidable indication of declining battery performance?
My MacBook is 15 months old. Current 'battery information' is listed below.
Thanks. Replies appreciated.
Battery Information:
Battery Installed: Yes
First low level warning: No
Full Charge Capacity (mAh): 4792
Remaining Capacity (mAh): 4790
Amperage (mA): 0
Voltage (mV): 12477
Cycle Count: 23
------------------------------

stevenray1 wrote:
1. I'm not sure how to match the path you listed re: the '1.3 battery update' to what's on my MacBook. Maybe I just don't understand how to interpret it, but I don't have a root folder (or any other folder) identified as 'MacBook.' When I used Spotlight, I also didn't come up with a BatteryUpdater.bundle. A file named BatteryUpdate2007001.pkg was all that Spotlight turned up.
On my MacBoook my hard drive that I boot from is named Mort's MacBook. Yours may be similar I don't know. It is the drive you boot from. Mines shows in finder as the top level drive. The next level in column view. Then you find the System file and go from there.
If your not sure what you named your drive or which one it is click the apple in the upper left corner and then pick *About This Mac* You then should see *Startup Disk* and next to that the name is what you refer too when you look for the folder path I gave.
2. You recommended resetting the SMC. However, the info file you provided a link for says it shouldn't be "necessary except as a last resort in cases where a hardware failure of the power management system is suspected." Does that accurately describe the condition I reported? Also, the problems listed as possible reasons to reset the SMC don't include the one I posted about.
The reason I suggest resetting the SMC is that your changing one of the components that is controlled by the functions of the SMC. The battery is a big part of the system which the battery update changes. To get it to be sure to recognize the new bundle you reset the SMC. The instructions linked are not all inclusive but if you don't want to reset it that is up to you.
3. Similarly, re: the 1.2 Battery Update, it's not clear to me that any of the listed 'symptoms' of a faulty battery apply in my case -- unless what I reported indicates a "+low charge capacity/runtime+." Does it?
The battery update instructions are again not all inclusive. If you don't want to do it that is fine. All I know is you have a MacBook Pro update installed at the moment. You don't have a MacBook Pro. This suggestion of mine has helped many people with problems as reported by you. You do not have to do anything you don't want. That is your choice. Is your battery cutting off at 39% considered normal operating or capacity to you? I personally would call it a faulty battery, but thats just me.
What would be your definition of a faulty battery?
4. Apparently, you had a faulty battery which Apple replaced. I wasn't sure from your message whether you had other things going on that made it clear you had a faulty battery, or only the same symptoms I reported. Were there other power-related problems in your case, or only, as you wrote "the same thing as yours except mine cut off at 28%"?
I guess I misunderstood your original post, everything yours was doing mine was doing except mine cut off at 28% not 39%. I can only give advice on what you post. Are there other things happening that you didn't mention?
My idea of a faulty battery must be different than yours. If I don't get warnings I should and the battery does not work like it used to then that is a faulty battery in my opinion.
If your not comfortable with any of my suggestions contact Apple support and maybe they can help you. Possibly one of the other posters on here can give you different advice that you agree with. Never do anything advised in the forums unless you agree with it.

-200361 warning during DAQmx acquisition

Hello,
I have been getting this warning during acquistion with 6255 OEM. This interrupts the continous data acquisiton of my software. I have tried reducing the sampling rate but doesn't help. Can some one help me find the way of handling this situration in my program to avoid the interruption in the continous data acquistion?
Thanks.

MansoorEE wrote:
This program works fine when I am using a simple USB cable. But, now I am requried to use a USB extender with 100m long Ethernet cable. It works fine for a while; but at some point this warning occurs and acquisition stops.
That sounds like you were working on the hairy edge before and now that the communication bus is likely just a little bit slower due to the conversion, you fail.
Try setting your loop to run a little bit faster, like maybe 100ms. By reading the samples faster, you are less likely to reach your buffer limit.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Aggregate storage cache warning during buffer commit

h5. Summary
Having followed the documentation to set the ASO storage cache size I still get a warning during buffer load commit that says it should be increased.
h5. Storage Cache Setting
The documentation says:
A 32 MB cache setting supports a database with approximately 2 GB of input-level data. If the input-level data size is greater than 2 GB by some factor, the aggregate storage cache can be increased by the square root of the factor. For example, if the input-level data size is 3 GB (2 GB * 1.5), multiply the aggregate storage cache size of 32 MB by the square root of 1.5, and set the aggregate cache size to the result: 39.04 MB.
My database has 127,643,648k of base data which is 60.8x bigger than 2GB. SQRT of this is 7.8 so I my optimal cache size should be (7.8*32MB) = 250MB. My cache size is in fact 256MB because I have to set it before the data load based on estimates.
h5. Data Load
The initial data load is done in 3 maxl sessions into 3 buffers. The final import output then looks like this:
MAXL> import database "4572_a"."agg" data from load_buffer with buffer_id 1, 2, 3;
OK/INFO - 1270041 - For better performance, increase the size of aggregate storage cache.
OK/INFO - 1270041 - For better performance, increase the size of aggregate storage cache.
OK/INFO - 1270041 - For better performance, increase the size of aggregate storage cache.
OK/INFO - 1003058 - Data load buffer commit elapsed time : [5131.49] seconds.
OK/INFO - 1241113 - Database import completed ['4572_a'.'agg'].
MAXL>
h5. The Question
Can anybody tell me why the final import is recommending increasing the storage cache when it is already slightly larger than the value specified in the documentation?
h5. Versions
Essbase Release 11.1.2 (ESB11.1.2.1.102B147)
Linux version 2.6.32.12-0.7-default (geeko@buildhost) (gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) ) #1 SMP 2010-05-20 11:14:20 +0200 64 bit

My understanding is that storage cache setting calculation you quoted is based on the cache requirements for retrieval. This recommendation has remained unchanged since ASO was first introduced in v7 (?) and was certainly done before the advent of parallel loading.
I think that the ASO cache is used during the combination of the buffers. As a result depending on how ASO works internally you would get this warning unless your buffer was:
1. = to the final load size of the database
2. OR if the cache was only used when data existed for the same "Sparse" combination of dimensions in more than one buffer the required size would be a function of the number of cross buffer combinations required
3. OR if the Cache is needed only when compression dimension member groups cross buffers
By "Sparse" dimension I mean the non-compressed dimensions.
Therefore you might try some experiments. To test case x above:
1. Forget it you will get this message unless you have a cache large enough for the final data set size on disk
2. sort your data so that no dimensional combination exists in more than one buffer - ie sort by all non-compression dimensions then by the compression dimension
3. Often your compression dimension is time based (EVEN THOUGH THIS IS VERY SUB-OPTIMAL). If so you could sort the data by the compression dimension only and break the files so that the first 16 compression members (as seen in the outline) are in buffer 1, the next 16 in buffer 2 and the next in buffer 3
Also if your machine is IO bound (as most are during a load of this size) and your cpu is not - try using os level compression on your input files - it could speed things up greatly.
Finally regarding my comments on time based compression dimension - you should consider building a stored dimension for this along the lines of what I have proposed in some posts on network54 (search for DanP on network54.com/forum/58296 - I would give you a link but it is down now).
OR better yet in the forthcoming book (of which Robb is a co-author) Developing Essbase Applications: Advanced Techniques for Finance and IT Professionals http://www.amazon.com/Developing-Essbase-Applications-Techniques-Professionals/dp/1466553308/ref=sr_1_1?ie=UTF8&qid=1335973291&sr=8-1
I really hope you will try the suggestions above and post your results.

Warning during check table

hi everyone,
i create a new table and then check it, a warning like below will appear,"TABLES IS NOT YET CLASSIFIED". What will cause that? Any suggestion is appreciated.
Regards,
Julian

Hi,
"TABLES IS NOT YET CLASSIFIED".
this is because you have not classified your table
from menu EXTRAS->ENHANCMENT CATEGORY
now choose the one of the radio button ans press ok.
read the documentation of ENHANCEMENT CATEGORY also.
DE DE_RADIO_EXCLASS
Short Text
Enhancement Category Selection
Definition
Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
Cannot be enhanced
The structure must not be enhanced.
Can be enhanced or character type
All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
Can be enhanced or character-type or numeric
The structure and its enhancement must not contain any deep data types (tables, references, strings).
Can be enhanced in any way
The structure and its enhancement may contain components whose data type can be of any type.
Not classified
This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the categorycannot be enhanced in any case.
If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.
Regards
vijay

Application (WMF 3.0) won't install during maintenance window, but will install when there is no maintenance window

Hi All,
I'm just getting into the Application model in SCCM 2012 R2 and I like what I see so far, but i'm running into an issue. When i set up an Application for WMF 3.0 with a prerequisite of .Net 4.0 and deploy it to a set of test systems that do not have
any maintenance windows applied to it, it works great. If it doesn't have .Net 4.0 it installs both that and WMF 3.0 and reboots. If it already has .Net 4.0, it will skip that and just install WMF 3.0 and reboot.
However, if i deploy it to systems that have a maintenance window applied, the application recognizes that it needs .Net and WMF 3.0 or just WMF 3.0, but it never actually runs.
Here is the applicable entry from the appintenteval.log, and i've bolded the line where it shows that WMF 3.0 is not installed
ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66/12 :- Title = WMF 3.0, Direct seleted dependencies = ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558/7 title=.Net
4.0,    AppIntentEval   4/24/2014 8:20:19 AM   1768 (0x06E8)
ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66/12 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Installed, ConfigureState = NotNeeded, Title = WMF 3.0   AppIntentEval
4/24/2014 8:20:19 AM   1768 (0x06E8)
ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558/7 :- Current State = Installed, Applicability = Applicable, ResolvedState = Available, ConfigureState = NotNeeded, Title = .Net 4.0   AppIntentEval
4/24/2014 8:20:19 AM   1768 (0x06E8)
ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/Application_de66c10e-111e-4d68-95a8-5cee3f144081/13 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Installed, ConfigureState = NotNeeded, Title = WMF 3.0   AppIntentEval
4/24/2014 8:20:19 AM   1768 (0x06E8)
ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/RequiredApplication_de66c10e-111e-4d68-95a8-5cee3f144081/13 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, ConfigureState = NotNeeded, Title = ApplicationIntentPolicy
AppIntentEval   4/24/2014 8:20:19 AM   1768 (0x06E8)
and here are the entries from the AppDiscovery.log that are relevant:
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558" AND Revision = 7)"   AppDiscovery
4/24/2014 8:20:19 AM   2776 (0x0AD8)
    Performing detection of app deployment type .Net 4.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, revision 7) for system.   AppDiscovery   4/24/2014 8:20:19
AM   2776 (0x0AD8)
+++ Discovered application [AppDT Id: ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, Revision: 7]   AppDiscovery   4/24/2014 8:20:19 AM   2776 (0x0AD8)
+++ Detected app deployment type .Net 4.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, revision 7) for system.   AppDiscovery   4/24/2014 8:20:19 AM
2776 (0x0AD8)
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66" AND Revision = 12)"   AppDiscovery
4/24/2014 8:20:19 AM   2508 (0x09CC)
    Performing detection of app deployment type WMF 3.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, revision 12) for system.   AppDiscovery   4/24/2014 8:20:19
AM   2508 (0x09CC)
+++ Application not discovered. [AppDT Id: ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, Revision: 12]   AppDiscovery   4/24/2014 8:20:19 AM   2508
(0x09CC)
+++ Did not detect app deployment type WMF 3.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, revision 12) for system.   AppDiscovery   4/24/2014 8:20:19 AM
2508 (0x09CC)
   ActionType - Install will use Content Id: Content_c6b448d0-7b59-4796-bb29-3f7fbfa6e70d + Content Version: 1 for AppDT "WMF 3.0" [ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66],
Revision - 12   AppDiscovery   4/24/2014 8:20:20 AM   2508 (0x09CC)
I have a 2 hour maintenance window applied to this system. From the serviceWindowManager.log:
OnIsServiceWindowAvailable called with: Runtime:7200, Type:2   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
No Service Windows exist for this type. Will check if the program can run in the All Programs window...   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
        Biggest Active Service Window has ID = {02B82DF5-3360-4BCC-8154-9258F0B856C3} having Starttime=04/24/14
08:20:00   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
            Duration is 0 days, 02 hours, 00 mins, 00 secs   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
FindBiggestMergedTimeWindow called with TimeStart=04/24/14 08:20:21 and TimeEnd=04/24/14 10:20:00   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
        Biggest Chainable Service Window for Type=1 not found   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
I'm not sure what else to try next and appreciate any help anyone can offer.

Thanks. I checked that setting and i have it set to false, so i don't think that's it.
I've done a little more experimenting. I've changed my maintenance window back to 30 minutes. Prior to the MW opening, i'll run an application evaluation deployment cycle on the system. It will show the system as required WMF 3.0 but since
the MW isn't open, it won't install at the time.
When the MW opens, i'll watch the ServiceWindowManager.log and it sees that it's a 30 minute MW and that the run time is 15 minutes but it still says the program can't run:
ActiveServiceWindow has 1800 seconds left   ServiceWindowManager   4/24/2014 2:20:00 PM   2032 (0x07F0)
Program can run! Setting *canProgramRun to TRUE   ServiceWindowManager   4/24/2014 2:20:00 PM   2032 (0x07F0)
OnIsServiceWindowAvailable called with: Runtime:900, Type:6
ServiceWindowManager   4/24/2014 2:20:00 PM   2032 (0x07F0)
        Biggest Active Service Window for Type=6 not found   ServiceWindowManager   4/24/2014 2:20:00 PM   2032 (0x07F0)
Program cannot Run! Setting *canProgramRun to FALSE   ServiceWindowManager   4/24/2014 2:20:00 PM   2032 (0x07F0)
OnIsServiceWindowAvailable called with: Runtime:900, Type:2   ServiceWindowManager   4/24/2014 2:22:32 PM   816 (0x0330)
If however, i kick off another application evaluation deployment cycle on the system during the open MW, the deployment kicks off right away and finishes.
Program can run! Setting *canProgramRun to TRUE   ServiceWindowManager   4/24/2014 2:22:32 PM   2940 (0x0B7C)
OnIsServiceWindowAvailable called with: Runtime:900, Type:3   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
No Service Windows exist for this type. Will check if the program can run in the All Programs window...   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
        Biggest Active Service Window has ID = {02B82DF5-3360-4BCC-8154-9258F0B856C3} having Starttime=04/24/14 14:20:00   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
            Duration is 0 days, 00 hours, 30 mins, 00 secs   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
ActiveServiceWindow has 1571 seconds left   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
Program can run! Setting *canProgramRun to TRUE   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
This is not the behavior i would expect. I would think that if the client knows it has a pending application deployment that is required, when the MW opened up, it would start the install immediately or close to the beginning of the MW. It shouldn't
need to have an application evaluation deployment cycle kicked off during the MW.

Change error message to warning during pricing condition upper limit check.

Hi All,
I have a header condition ZFMN to which maximum amount that can be entered is set to $5000. When I enter the amount greater than this, it gives me error message.
Could we change it to warning message?

During Creation of PO when you click PO Check, What Include you are using.
Cann't you use the BADI ME_PROCESS_PO_CUST and write the code whatever you want in PO_CHECK,
There during Check you use any FM POP_TO_CONFIRM OR POP_TO_INFORM or show any information Message too.
Try it once.
Thanks
Arbind

SOLUTION to iPhoto 6 crashing without warning during library upgrade

THE PROBLEM
The problem which I and some others in this forum were facing was that iPhoto 6 would CRASH WITHOUT WARNING halfway through the process of updating our previous iPhoto 5 library. This is a different problem from the permissions issues which some other users have faced, which iPhoto 6 does warn you about.
THE EXPLANATION
After trial and error, I concluded that there was a corrupted photo in my library that iPhoto was choking on during the upgrading process. Unfortunately, there was no easy way to identify which of my 3000+ photos this was. Hence, the solution was to laboriously test my library year-by-year, to isolate the year in which the problematic photo was hiding. This meant creating individual copies of my iPhoto library, one for each year, and then test-upgrading each individual copy. Each individual year upgraded fine, except for 2004. Thus, I could deduce that the problematic photo was in 2004. I then created a new copy of my iPhoto 5 library, containing all photos except for those in 2004. It upgraded fine. I then manually dragged my photos from 2004 back into iPhoto. Thus, all my comments/ratings/keywords for other years were intact, and I only had to re-do 2004.
THE STEPS
In order to use this solution, you must have a backup of your iPhoto 5 library. It also helps if you can install a fresh copy of Mac OS X 10.4 and iPhoto 6 (SIX) on another partition. The steps are:
1. Reinstall/'downgrade' to iPhoto 5 (this requires deleting the iPhoto 6 application and also all iPhoto receipts in the /Library/Receipts folder, before reinstalling from iLife '05)
2. Create multiple copies of your iPhoto 5 library backup (the entire iPhoto Library folder from your iPhoto 5), and title the backup copies 'Early Photos', '2003', '2004', '2005' and '2006'.
3. By holding down Option while launching iPhoto 5, open each copy of your library, and delete photos from each copy so that only one year of photos remains in each copy, i.e. you should have one library containing only 'Early Photos' (pre-2003), one containing only 2003 photos, etc.
4. Test-upgraded each individual 'annual' library on another installation of iPhoto 6. Those that can be upgraded are fine. The one that crashes obviously contains the corrupted photo.
5. Go back and create a fresh copy of your iPhoto 5 library, and open it in iPhoto 5. Delete only the photos from the problematic year, leaving all the rest behind. Before deleting the photos, drag them into a folder on the desktop, so that you can re-import them later.
6. Now re-install iPhoto 6 (the end is near, trust me) and open the fresh copy of your iPhoto 5 library. Upgrade it. You will now have a upgraded library, minus all the photos from the excluded year.
7. You should now be able to re-import photos from the excluded year, by dragging them into iPhoto 6. However, this may mean reintroducing the corrupted photo into your library. I really can't help you beyond this - re-import at your own risk, and always keep backups.
8. Enjoy (after much frustration).
ALTERNATIVES
It isn't necessary to test your library year-by-year. For example, if you only have photos from one year, then you'd have to find some other way to break your library into logical chunks, and test each chunk using the procedure above. Again, the chunk that crashes during upgrading contains the corrupted photo. It's really up to you how finely you want to sub-divide and test your iPhoto 5 library, to isolate the corrupted photo.
(P.S. Really, this should be addressed by Apple. It is murder and really tedious to do this, and I suspect it would be difficult for anyone not familiar with Mac OS X, and also difficult if you don't have multiple partitions/drives to install separate copies of iPhoto 5 and iPhoto 6.

Thanks for your help. It should work with some iPhoto libraries, but unfortunately not with mine.
iPhoto was crashing, so I found the guilty album, deleted it, retried: but it crashes on another album, etc. I think I have more than one corrupted picture/album, so the only solution to make iPhoto complete the update was to remove 90% of my pictures... not a real solution

Compile-time warning during javac of a Class that implements Comparable

Hello All,
I have defined a class as follows;
public class CardTiles extends JButton implements Comparable{
During normal compilation with javac, it tell me to use Xlint to compile and the warning it throws is below:
CardTiles.java:4: warning: [serial] serializable class CardTiles has no definition of serialVersionUID
public class CardTiles extends JButton implements Comparable{
^
1 warning
What does this warning mean?
Many thanks!

ejp wrote:
you can choose to to differentiate between various versions of your CardTiles classThat's back to front. Serialization will always do that unless you stop it, which you can do via a fixed serialVersionUID. This tells Serialization that different versions of your class are compatible under serialization.I suppose I see it this way because I wouldn't have a serializable object without an ID. Without having an explicit ID the process isn't as transparent to me. It's the same sort of thing as using braces for statements when they're not necessary, e.g.
          if(check)
               System.out.println("check is on");
          else
               System.out.println("check is off");     versus
          if(check) {
               System.out.println("check is on");
          } else {
               System.out.println("check is off");
          }

Suggestions for redirecting site during maintenance

We currently have a custom web application running under an OC4J instance within the application server of Oracle Collaboration Suite.
Since our application is "live" 24/7 we are looking for the best way to post user-friendly message during times when we need to update code and restart the OC4J instance. In other words, we would like to post an "Application Unavailable Due to Scheduled Maintenance " message during the time of our upgrades.
We tried to deploy a maintenance page to another OC4J instance with the same context-root as the application. The idea was to shut down the application's OC4J instance and start the maintenance page OC4J instance during times of scheduled maintenance. However, the application server gets confused by the fact that two OC4J instances have the same context-root and crashes.
Any suggestions would be appreciated.

Middaymag
Since my post yesterday I think I figured out a way to make the Web Server redirect work. I was attempting to redirect on a 500 error by using an .htaccess file. This actually worked fine for pages that were not redirected to oc4j but not for ones that were.
However, turns out you can specifiy global error pages directly in the httpd.conf file (probably this is obvious to Apache gurus -- I am clearly NOT one). Here is what works for me:
- In httpd.conf I added a line like this: "ErrorDocument 500 /custom500.html"
- in the web root I put my custom500.html
- Restarted the web server
That's it. Now whenever the OC4J instance is down, the system correctly redirects to my custom page. This solution does have a couple limitations which may be obvious but I will mention anyway:
1. The web server has to stay up -- Out scripts that bring the system down for maintenence currently stop everything including the web server so we will have to change them -- no big deal.
2. You can't serve dynamic content. My error page is static HTML in the web root. I guess having said that, there is no reason you couldn't redirect to another OC4J instance if you had a need to serve up dynamic content -- I don't need that.
Hope this helps!
Chris

Updates not installing during Maintenance Window

Hi,
I have a task sequence that runs on the weekends and when it runs it puts the server into maintenance mode so that updates can then be installed by the task sequence. I do this for about 40 servers and about half of them failed to install the updates. Before
the weekend I did verify that the updates were already available on the servers. I have been looking at many of the log files and the only thing I can find is the following:
<![LOG[Auto install during non-business hours is disabled or never set, selecting only scheduled updates.]LOG]!><time="00:00:02.647+240" date="04-25-2015" component="UpdatesDeploymentAgent" context=""
type="1" thread="708" file="assignmentsmanager.cpp:500">
<![LOG[A user-defined service window(non-business hours) is available. We will attempt to install any scheduled updates.]LOG]!><time="00:00:02.647+240" date="04-25-2015" component="UpdatesDeploymentAgent" context=""
type="1" thread="708" file="updatesmanager.cpp:1558">
<![LOG[Attempting to install 0 updates]LOG]!><time="00:00:02.647+240" date="04-25-2015" component="UpdatesDeploymentAgent" context="" type="1" thread="708" file="updatesmanager.cpp:1581">
<![LOG[No actionable updates for install task. No attempt required.]LOG]!><time="00:00:02.647+240" date="04-25-2015" component="UpdatesDeploymentAgent" context="" type="1" thread="708"
file="updatesmanager.cpp:2914">.
<![LOG[Time to retry for program * advertisement USA20126]LOG]!><time="03:30:03.756+240" date="04-25-2015" component="execmgr" context="" type="1" thread="2200" file="execreqmgr.cpp:5815">
<![LOG[Could not find the policy in WMI for package USA001B6 program *]LOG]!><time="03:30:03.849+240" date="04-25-2015" component="execmgr" context="" type="2" thread="2200" file="softdistpolicy.cpp:2851">
<![LOG[Child policy does not exist for program *. This program will retry.
I have redistributed all the packages to be sure everything is there so I am not sure what else I can try at this point. Any ideas what I might be able to adjust or what the issue could be why not all servers are getting updated? TIA

Ok, we have these 40 servers in a collection with a MW set for the weekend on a Saturday. So we deploy the TS to this collection that is immediately available but with an assignment schedule 2 hrs before the MW begins. So the MW for the servers begins
at 5am and I have the TS set with an assignment schedule of 3am. The task sequence does not run until the service window is reached. But for these few servers it seems as though it never even runs or I get the errors above. Sorry maybe its just not clear enough
how it works in my environment. I just didn't know if there was something I was missing in the TS deployment etc..

Exclusively locked files warning during startup on my A100 Satellite

I get a warning about (at least?) 2 exclusively locked files occuring during startup. How do I identify them and how do I "unlock" them? I am not going to ask how they got exclusively locked.
I have tried updating the bootup file but I'm told by the updater that my bootup file is identical to the update.
I have done a complete Vipre scan which has pronounced my laptop to be clean.
Thnaks,
John

Which Satellite A100, John? What's the part number?
Which Windows?
Please quote the precise message you get on startup. Put it on a line by itself. No paraphrasing. Spelling counts.
-Jerry

OOB warning during IPS 4260 signature update via CSM

Hi,
During the recent IPS signatures updates via CSM, i have noticed that there was warning (below).
>OOB change detected - Out of Band(OOB)and sensor configuration change happened on device. But you selected to continue deployment in case of OOB. Continuing...
what is the cause & impact of such event?
As i suspected there is a mismatch of configuration, my inline interfaces are no longer applied to the virtual sensor 'VS0'. Could it be due to the mis-synchronisation?
Apprepriate for any advice.
thanks
cash

CSM keeps an internal copy of the configuration it last pushed to the sensor.
Each portion of the configuration has a configToken assigned to it by the sensor. The config token is a base 64 encoding of that configuration portion.
Each time CSM goes to push a new configuration it will compare the configToken of it's previously saved configuration for that sensor against the configToken of the configuration currently on the sensor.
If the 2 configTokens match, then no configuration change has been made since the last time that CSM pushed a configuration to the sensor. CSM can safely push the new configuration to the sensor.
If the 2 configTokens do not match, then an Out Of Band (OOB) configuration change has been made to the sensor. This means that the sensor's configuration has been modified by something other than CSM. This may have been a user changing something through the CLI or IDM instead of using CSM.
In these situations CSM gives you the option of either stopping the push of the new configuration so the detected changes can be imported and evaluated by the user, or to go ahead and push the changes to the sensor.
If you decide to go ahead and push the changes to the sensor, the outcome of the configuration change is not guaranteed.
The sensor may wind up merging the OOB changes in with the new configuration from CSM, or the CSM changes may wind up overwriting the OOB changes.
So telling CSM to push the new configuration even when OOB changes have been detected can be risky and can cause loss of some of your configuration.
I fyou will be making changes with CLI or IDM, then it is always best to import those changes into CSM before making further configuration changes in CSM.

Performance issues during Maintenance

Using 2014 SP1
During weekend maintenance, we're experiencing poor performance when a particular PO's maintenance is running. Webaccess is...

Company merged one of us a 30ish N shop with GW 2012 the other a 27 user MS shop with exchange 2003
We've (the other IT guy and I) decided to create...

Warning during maintenance of IT0008

Similar Messages

Maybe you are looking for