Error in recording

hi,
I am using Adobe Captivate 4. I want to record a sooftware where I am using FMR with demonstration mode, but when I stop recording and the project get saved I get the screenshots of first and last screen and in between there is blank slide.
Can you please help me out in this......
Suhani

hi Mukul,
I have tried your option.  Created the Test folder... and then recorded the software again....
It doesnt work... again the same problem... in library it shows only two backgraounds which are there for first and second slide.
The second slide is blank but it is there on timeline for 15 seconds.
Regards,
Suhani

Similar Messages

  • Data length error in record 86.

    Data length error in record 86.
    Message no. FV147
    Diagnosis
    An error occurred in the processing of the data to be imported. It is highly probable that this is a data error.
    Contact your data provider.
    System Response
    Any account statement processing currently underway and any outstanding is being terminated.
    Procedure
    Check the structure of the supplied data. If the statement data you have obtained is error-free, you can simply restart the program. All those statements which have already been imported correctly will not be reimported.
    {1:F01SCBLINBBXXXX3446100003}{2:O9400634140719SCBLINBBXXXX34461000031407190634N}{3:{108:00000000000718}}{4:
    :20:14071905fr309439
    :25:52205785839
    :28C:611
    :60F:D140718INR792788,04
    :61:1407180718CR100000,00N169NONREF         
    :86:IN36701407187774 VIJBH14199069837
    IN36701407187774 VIJBH14199069837
    AGARWAL AGENCIES
    :61:1407180718CR150000,00N169NONREF         
    :86:IN36701407187251 SBIN414199017384
    IN36701407187251 SBIN414199017384
    EAGLE FOOTWERE
    :61:1407180718CR100000,00N169NONREF         
    :86:IN36701407187052 SAA96678573
    IN36701407187052 SAA96678573
    TANVEER TRADERS
    :61:1407180718CR98000,00N169NONREF         
    :86:IN36701407186828 SBIN314199982628
    IN36701407186828 SBIN314199982628
    MODERN AGENCY
    :61:1407180718CR179000,00N169NONREF         
    :86:IN36701407186029 SAA96670577
    IN36701407186029 SAA96670577
    BALAJI ENTERPRISES
    :61:1407180718CR60000,00N169NONREF         
    :86:IN36701407185397 367845438
    IN36701407185397 367845438
    SAKSHI ENTERPRISES
    :61:1407180718CR2000000,00N169NONREF         
    :86:IN3670140718H568 SBIN414199360804
    IN3670140718H568 SBIN414199360804
    RELAXO FOOTWEARS LIMITED
    :61:1407180718CR38000,00N169NONREF         
    :86:IN3670140718G554 CBINH14199566672
    IN3670140718G554 CBINH14199566672
    WONDER WALK AGENCIES
    :61:1407180718CR113000,00N169NONREF         
    :86:IN3670140718F851 JAKA140718621672
    IN3670140718F851 JAKA140718621672
    JYOTI SALES PROP MR AMIT VOHRA S
    :61:1407180718CR54200,00N169NONREF         
    :86:IN3670140718F006 BKIDN14199343033
    IN3670140718F006 BKIDN14199343033
    SHAH FOOT WEAR
    :61:1407180718CR64000,00N169NONREF         
    :86:IN3670140718F094 BKIDN14199343132
    IN3670140718F094 BKIDN14199343132
    MUSKAN TRADERS
    :61:1407180718CR114500,00N169NONREF         
    :86:IN3670140718F423 SBIN414199302946
    IN3670140718F423 SBIN414199302946
    GOUTAM DISTRIBUTORS
    :61:1407180718CR63000,00N169NONREF         
    :86:IN3670140718D651 SD1141261589
    IN3670140718D651 SD1141261589
    M K FOOTWEAR
    :61:1407180718CR67913,00N169NONREF         
    :86:IN3670140718D057 SBIN414199247753
    IN3670140718D057 SBIN414199247753
    SSS PG STORES
    :61:1407180718CR130000,00N169NONREF         
    :86:IN3670140718D183 UTBIN14199275937
    IN3670140718D183 UTBIN14199275937
    GOPAL SHOES
    :61:1407180718CR48000,00N169NONREF         
    :86:IN3670140718C628 CBINH14199546949
    IN3670140718C628 CBINH14199546949
    AGGARWAL FOOTWEAR
    :61:1407180718DR5000000,00N506PIRLXOIN01A00468
    PIRLXOIN01A00468                 
    :86:PIRLXOIN01A00468 SCBLR12014071800003757
    CASH SCBLR12014071800003757
    RELAXO FOOTWEARS LIMITED
    SIN09373C0000423 00001 PIRLXOIN01A0
    0468
    PIRLXOIN01A00468
    :61:1407180718DR4000000,00N506PIRLXOIN01A00469
    PIRLXOIN01A00469                 
    :86:PIRLXOIN01A00469 SIN09373Q0000468
    PIRLXOIN01A00469-SIN09373Q0000468
    SB3670140718HK96
    SIN09373C0000424-00001 PIRLXOIN01A0
    0469
    :61:1407180718DR1699195,25N699TRF            
    :86:316031790865 PAY001
    316031790865 PAY001
    GRAND WISE ENTERPRISES LIMITED
    AKMP037
    USD28,030.8 60.5755/INR743.76 1
    DEBIT IMEX CUSTOMER A/C
    :61:1407180718CR480000,00N195NONREF         
    :86:IL36701407182157 BARBR52014071800734481
    CASH BARBR52014071800734481
    APNA FOOT WEAR
    SENDER IFSCBARB0CHARMI
    IL36701407182157
    :61:1407180718CR235000,00N195NONREF         
    :86:IL36701407185517 SBINR52014071801147506
    CASH SBINR52014071801147506
    PRAKASH FOOT WEAR
    FUND TRF FRM 33174969142 TO52205785
    SENDER IFSCSBIN0016310
    IL36701407185517
    :61:1407180718CR500000,00N195NONREF         
    :86:IL36701407185083 SBINR12014071801142317
    CASH SBINR12014071801142317
    MODERN FOOTWEARS
    SENDER IFSCSBIN0001521
    IL36701407185083
    :61:1407180718CR800000,00N195NONREF         
    :86:IL36701407184746 HDFCR52014071851912408
    CASH HDFCR52014071851912408
    FASHION SQUARE
    SENDER IFSCHDFC0000412
    IL36701407184746
    :61:1407180718CR332000,00N195NONREF         
    :86:IL36701407184713 SBINR52014071801140001
    CASH SBINR52014071801140001
    WINGS POLYMERS
    SENDER IFSCSBIN0001581
    IL36701407184713
    :61:1407180718CR450000,00N195NONREF         
    :86:IL36701407184302 FDRLR52014071800031798
    CASH FDRLR52014071800031798
    ABHINAV ENTERPRISE
    SENDER IFSCFDRL0001492
    IL36701407184302
    :61:1407180718CR650000,00N195NONREF         
    :86:IL36701407183976 UCBAR32014071800058993
    CASH UCBAR32014071800058993
    GAYLORD SHOE AND CHAPPAL
    SENDER IFSCUCBA0000048
    IL36701407183976
    :61:1407180718CR700000,00N195NONREF         
    :86:IL36701407183860 SBINR52014071801134507
    CASH SBINR52014071801134507
    FOOTWEAR HOUSE
    RTGS TGH CHQ NO 172867
    SENDER IFSCSBIN0008602
    IL36701407183860
    :61:1407180718CR250000,00N195NONREF         
    :86:IL36701407183487 SBINR52014071801131379
    CASH SBINR52014071801131379
    PRATAP AGENCY PROP MRS SUNITA KUMRA
    SENDER IFSCSBIN0014152
    IL36701407183487
    :61:1407180718CR254740,00N195NONREF         
    :86:IL36701407182511 HDFCR52014071851915942
    CASH HDFCR52014071851915942
    HEPHZIBAH AGENCIES
    SENDER IFSCHDFC0001498
    IL36701407182511
    :61:1407180718CR398000,00N195NONREF         
    :86:IL36701407182496 BARBR52014071800726312
    CASH BARBR52014071800726312
    RAZA FOOT WEAR
    SENDER IFSCBARB0BASTIX
    IL36701407182496
    :61:1407180718CR300000,00N195NONREF         
    :86:IL36701407182349 KKBKR52014071800664337
    CASH KKBKR52014071800664337
    M M DISTRIBUTORS
    PAYMENT
    SENDER IFSCKKBK0000958
    IL36701407182349
    :61:1407180718CR61136,00N169NONREF         
    :86:IN3670140718C504 IOBAN14199026875
    IN3670140718C504 IOBAN14199026875
    M S CHINNS TRADERS
    :61:1407180718CR79995,00N169NONREF         
    :86:IN3670140718C142 SBIN414199219784
    IN3670140718C142 SBIN414199219784
    FRONTIER TRADING COMPANY
    :61:1407180718CR100000,00N169NONREF         
    :86:IN3670140718B731 SBIN414199200112
    IN3670140718B731 SBIN414199200112
    SHRI AMBEY TRADERS
    :61:1407180718CR125000,00N169NONREF         
    :86:IN3670140718B521 N199140025581074
    IN3670140718B521 N199140025581074
    SHYAM BROTHERS
    :61:1407180718CR68000,00N169NONREF         
    :86:IN3670140718A144 1205061871400003
    IN3670140718A144 1205061871400003
    POPULAR TRADERS PROP PISHORI LAL SETHI
    :61:1407180718CR41000,00N169NONREF         
    :86:IN3670140718A044 P14071849681718
    IN3670140718A044 P14071849681718
    AKSHAY FOOTWEARS
    :61:1407180718CR50000,00N169NONREF         
    :86:IN3670140718A099 BARBH14199284604
    IN3670140718A099 BARBH14199284604
    STAR ENTERPRISE
    :61:1407180718CR100000,00N169NONREF         
    :86:IN3670140718A002 SAA21370357
    IN3670140718A002 SAA21370357
    JAI OMKAR ENTERPRISES
    :61:1407180718CR120000,00N169NONREF         
    :86:IN36701407189725 UTBIN14199269504
    IN36701407189725 UTBIN14199269504
    SANTI STORES
    :61:1407180718CR100000,00N169NONREF         
    :86:IN36701407189538 SBIN414199107266
    IN36701407189538 SBIN414199107266
    VINAYAK TRADING
    :61:1407180718CR100000,00N169NONREF         
    :86:IN36701407189842 SAA3564919
    IN36701407189842 SAA3564919
    SKY STYLE MARKETING PROP.ABHISHEK S
    :61:1407180718CR120000,00N169NONREF         
    :86:IN36701407189384 MAHBH14199609866
    IN36701407189384 MAHBH14199609866
    ROYAL FOOT WEAR
    :62F:D140718INR1697499,29
    :64:C140718INR59273846,71
    -}{5:{CHK:CHECKSUM DISABLED}{MAC:MACCING DISABLED}}

    SAP REPLAY
    Regarding the incidence itself, kindly consider that The 86-record
    limitation is not a bug of the program, but the standard design.
    The error is coded as FV147, when the Note to Payee in Record 86
    exceeds 65 characters in Program RFEKA400.
    You will need to contact your Bank in order to obtain a correct file:
    I have attached some documentation on this message that will allow your
    bank to create it.
    Otherwise, you may use the following user-exit (SAP NOTE 494777):CMOD
    Enhancement Exit Name FEB00004 > EXIT_RFEKA400_001.
    This User Exit is called in RFEKA400 in the line: PERFORM
    PROCESS_RAW_DATA TABLES SWIFT. In Include ZXF01U06, you have
    the option to process the raw data.
    Hope this information is useful to you.

  • File system error: The record ID is incorrect. Physical file: . Logical file:

    Hi,
    I face this error message when I try to 'process update' a dimention, sometime it works but sometime it failed with the error below:
    Description: File system error: The record ID is incorrect. Physical file: . Logical file: . 
    My environment: Window Server 2008 R2+SQL Server 2008 R2.
    Note: this issue can be resolved by full cube process, but I can't to that every time if it failed, just want to know what happen at backend of SSAS, It block me neary 2 week without any finding, really appreciate that someone can help on this.
    I have do some research with google, I think the root cause here is not TopCount function(It may be a problem with SQL Server2005), also not the size limitation of 4GB size of .astore file.(I check the size of my cube under 'Data\XXX.db\' folder, which only
    have few MB size).
    Thanks,
    Tom

    Hi Tom,
    Here is a microsoft fix
    FIX: "File system error" occurs when you try to run a process update operation on a dimension in Microsoft SQL Server 2008 Analysis Services and in Microsoft SQL Server 2008 R2 Analysis Services
    In your acenario, in order to fix this issue, please apply the latest Cumulative update and Service Pack according to your SQL Server version. Besides, there are two workarounds in that fix, plese try it and check if it works or not.
    http://support.microsoft.com/default.aspx?scid=kb;en-US;2276495
    Regards,
    Charlie Liao
    TechNet Community Support

  • SQL Loader-704: Internal error: Maximum record length must be = [10000000]

    Hi,
    running SQL*Loader (Release 8.1.7.2.1) causes an error "SQL*Loader-704: Internal error: Maximum record length must be <= [10000000]". This error occurs when SQLLoader is trying to load several thousand records into a database table. Each record is less than 250 bytes in length.
    Any idea what could cause the problem?
    Thanks in advance!
    Ingo
    And here's an extract from the log file generated by SQLLoader :
    Number to load: ALL
    Number to skip: 0
    Errors allowed: 50
    Bind array: 1360 rows, maximum of 10485760 bytes
    Continuation: none specified
    Path used: Conventional
    Table "SYSTEM"."BASICPROFILE$1", loaded from every logical record.
    Insert option in effect for this table: APPEND
    TRAILING NULLCOLS option in effect
    Column Name Position Len Term Encl Datatype
    UUID FIRST * O(X07) CHARACTER
    DOMAINID NEXT * O(X07) CHARACTER
    LASTMODIFIED NEXT * O(X07) DATE DD/MM/YYYY HH24:MI:SS
    ANNIVERSARY NEXT * O(X07) CHARACTER
    BIRTHDAY NEXT * O(X07) CHARACTER
    COMPANYNAME NEXT * O(X07) CHARACTER
    DESCRIPTION NEXT * O(X07) CHARACTER
    FIRSTNAME NEXT * O(X07) CHARACTER
    COMPANYNAMETRANSCRIPTION NEXT * O(X07) CHARACTER
    FIRSTNAMETRANSCRIPTION NEXT * O(X07) CHARACTER
    GENDER NEXT * O(X07) CHARACTER
    HOBBIES NEXT * O(X07) CHARACTER
    HONORIFIC NEXT * O(X07) CHARACTER
    JOBTITLE NEXT * O(X07) CHARACTER
    KEYWORDS NEXT * O(X07) CHARACTER
    LASTNAME NEXT * O(X07) CHARACTER
    LASTNAMETRANSCRIPTION NEXT * O(X07) CHARACTER
    NICKNAME NEXT * O(X07) CHARACTER
    PREFERREDLOCALE NEXT * O(X07) CHARACTER
    PREFERREDCURRENCY NEXT * O(X07) CHARACTER
    PROFESSION NEXT * O(X07) CHARACTER
    SECONDLASTNAME NEXT * O(X07) CHARACTER
    SECONDNAME NEXT * O(X07) CHARACTER
    SUFFIX NEXT * O(X07) CHARACTER
    TITLE NEXT * O(X07) CHARACTER
    CONFIRMATION NEXT * O(X07) CHARACTER
    DEFAULTADDRESSID NEXT * O(X07) CHARACTER
    BUSINESSPARTNERNO NEXT * O(X07) CHARACTER
    TYPECODE NEXT * O(X07) CHARACTER
    OCA NEXT * O(X07) CHARACTER
    SQL*Loader-704: Internal error: Maximum record length must be <= [10000000]

    As a second guess, the terminator changes or goes missing at some point in the data file. If you are running on *NIX, try wc -l data_file_name.  This will give a count of the number of lines (delimited by CHR(10) ) that are in the file.  If this is not close to the number you expected, then that is your problem.
    You could also try gradually working through the data file loading 100 records, then 200, then 300 etc. to see where it starts to fail.
    HTH
    John

  • Error parsing recording file

    Hi,
    I am trying to open JRockit recorded xml file with JRA tool. Getting message ' Error parsing recording file'.
    Thanks
    ranga

    For older versions of JRockit, you had to use exactly the same version of JRockit when you created the recording as when you opened it.
    With more recent versions (R26.0 and later iirc) it is sufficient if the JRA reader version is >= the version of JRockit producing the recording. Or in other words, make sure you are running the latest version of JRockit on your developer workstation.
    -- Henrik

  • "ERROR SAVING RECORD" Message generated...

    Hi Everyone,
    I have a minor error with an Alert I made. I have an alert
    linked to both the Pre-Insert and Pre-Update Triggers at the
    Block level of my form.
    This alert fires when the Volume entered in the record is >50.
    It asks "Are you are sure the Volume should be larger than 50?"
    and has a Yes and No button on it. When you hit Yes, it saves
    and that is correct. When you press No it doesn't save, and
    that is fine, BUT after you press No, a window with a red X
    comes up and says in all capitals "ERROR SAVING RECORD". How
    can I get rid of this?
    Someone please help me out, I am stumped!
    Thanks in advance.
    Mike

    Didn't you forget to write in your triggers:
    IF alert_button=ALERT_BUTTON2 THEN
    RAISE Form_Trigger_Failure;
    END IF;

  • Calendar and Adressbook error: Duplicate records found for GUID

    Hi all,
    i have a Mountaion Lion Server running on a mac mini and everything was working well.
    This morning one user of mine is unable to connect to his calendar and adressbook.... i found this error in the log files:
    2013-06-30 15:19:50+0200 [-] [caldav-1]  [-] [twistedcaldav.directory.appleopendirectory.OpenDirectoryService#error] Duplicate records found for GUID ****USER_GUID****:
    2013-06-30 15:19:50+0200 [-] [caldav-1]  [-] [twistedcaldav.directory.appleopendirectory.OpenDirectoryService#error] Duplicate: ***USER_Shortname***
    Apperetnly there is a duplicate match in the database. how can i fix this issue?
    In Server App this user is only listed once.
    Mail and other services for this user are working correctly.
    Thanks for any advice!

    Hi Samuel,
    You may try:
    select code,count(code)
    from [dbo\].[@XTSD_XA_CMD\]
    group by code having count(code) > 1
    What is the result?
    Thanks,
    Gordon

  • SNMP trap on OutOfMemory Error Log record

    I would like to implement SNMP trap on OutOfMemory Error Log record.
    In theory SNMP LogFilter with Severity Level "Error" and Message Substring "OutOfMemory" should do the trick.
    In reality it does not work (doh)(see explanations below), I wonder if someone managed to make it work.
    Log entry has following format:
    ----------- entry begin ----------
    ####<Nov 12, 2003 3:09:23 PM EST> <Error> <HTTP> <ustrwd2021> <local> <ExecuteThread: '14' for queue: 'default'> <> <> <101020> <[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>
    java.lang.OutOfMemoryError
         <<no stack trace available>>
    ------------ entry end ------------
    Notice that java.lang.... is NOT part of the log record, yep it seems that exception stack trace is not part of log record! Thus filter could be applied only to "<[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>" string, which is really useless.
    Here is fragment of trap data (i had to remove Message Substring in order to get Error trap to work)
    1.3.6.1.4.1.140.625.100.50: trapLogMessage: [WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception

    Andriy,
    I dont think you could do much here, since Outofmemory is not part of
    log record SNMP agent cannot filter on this. I would be curious to hear
    if anyone got it to work using SNMP.
    sorry,
    -satya
    Andriy Potapov wrote:
    I would like to implement SNMP trap on OutOfMemory Error Log record.
    In theory SNMP LogFilter with Severity Level "Error" and Message Substring "OutOfMemory" should do the trick.
    In reality it does not work (doh)(see explanations below), I wonder if someone managed to make it work.
    Log entry has following format:
    ----------- entry begin ----------
    ####<Nov 12, 2003 3:09:23 PM EST> <Error> <HTTP> <ustrwd2021> <local> <ExecuteThread: '14' for queue: 'default'> <> <> <101020> <[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>
    java.lang.OutOfMemoryError
         <<no stack trace available>>
    ------------ entry end ------------
    Notice that java.lang.... is NOT part of the log record, yep it seems that exception stack trace is not part of log record! Thus filter could be applied only to "<[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>" string, which is really useless.
    Here is fragment of trap data (i had to remove Message Substring in order to get Error trap to work)
    1.3.6.1.4.1.140.625.100.50: trapLogMessage: [WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception

  • Error Data record has grouping value "" instead of 99

    Hi,
    We are implementing ESS and MSS for EP7.0 with ECC 5.0 and we get the following error: Data record 0000005900090      9999123120010910000 has grouping value "" instead of "99" when we try to edit and save the bank information.
    Please advise! Thank you!

    same error ,
    the report did not fix it .
    its coming up when ever i am trying to do a global assignment actions ...( this is occuring only for people with benefits infotypes)
    any idea..
    Please let me know
    Thanks

  • Error in(recording)  LSMW  while importing

    Hi All,
    I have did  LSMW for uploading some fields into IW41 transaction  i have  did a recording for it . It is working fine  in devlopment server but while importing to quality its showing as error message  that  error in recording unable to import . Couldn't trace where exactly the problem is ,Please kindly help me in this issue.
    Thanx in advance
    regards,
    Indira Bhanu.

    Hi,
    May be the sequence of the source structure fileds and the sequence of
    fileds in the file are not same, those need to be in same order.
    Hope it helps
    Regards
    Mansi

  • Message 614: Format error by recording for BDC

    Hi PP Gurus,
    I would be appreciable if anybody face the same problem and resole my issue.
    When we are trying to create a program from within the transaction recorder, Transaction SHDB, using the function 'Create program'. Then a
    termination occurs with the following message:MS614 Format error by recording: Field PLPOD-CKSELKZ not avaliable on screen.
    Thanks & Regards,
    Abu Arbab

    Hi R. Brahmankar,
    I've a doubt on your comment is once recording is done for some material's Say 'A' Rate Routing with internally generated Group (say 5000005), Counter-1 and all the things relevant to BDC finished. Now suppose we are uploading Rate routings for other materials. Can we upload Rate Routings for a material in the same Group but with many counters say 2,3,4,5.....?
    Do we need to do some special settings either in BDC program or that also be recorded in same recording? Or different recording has to be created?
    Thanks & Regards,
    Abu Arbab
    Edited by: abu arbaba on Oct 15, 2008 5:02 PM
    Edited by: abu arbaba on Oct 24, 2008 8:18 AM

  • Cannot process links - int error: bad record index

    Opening a publication I have recently been working on suddenly fails with "Cannot process publication's links - Internal error - bad record index".
    And then Pagemaker dies.   Is there anyway to get this publication back?  Hours of work.
    Only possibly anomaly I see is that the .pmd file was moved from one computer to another before this started happening, but we do this all the time in our shop.  As a matter of fact it was moved on a memory stick, not as an email attachment or some less reliable means.  The version on the stick fails the same way.

    Well that sounds close, but I (1) don't have any graphics on master pages, and (2) never performed a "diagnostic recomposition", and (3) can't do anything anyway since pagemaker crashes immediately after issuing the error message about the links.

  • Intellisync error "Duplicate records found"

    I am trying to sync my BB 8300 with Outlook 2007.  I am using Blackberry Desk Manager 4.2.2.14.
    I was able to sync before but now it get this error "Duplicate records found in the device" and it won't sync.
    Any ideas to fix this problem?
    I tried to un-install and re-install DM.
    I also tried to delete Intellisync folder
    Thanks! 

    JJKD wrote:
    I am trying to sync my BB 8300 with Outlook 2007.  I am using Blackberry Desk Manager 4.2.2.14.
    I was able to sync before but now it get this error "Duplicate records found in the device" and it won't sync.
    Any ideas to fix this problem?
    I tried to un-install and re-install DM.
    I also tried to delete Intellisync folder
    Thanks! 
    Hi JJKD;
    What is your email application?
    Backup your device.
    Review the BB KB Here...
    There are a couple of approaches to this. If your not needing to complete a two way sync, you can clear the calendar on the BB Handheld by going to BACKUP / ADVANCED and clearing the calendar on right side of the Advanced GUI. Then just try a regular sync.
    This can also work by clearing
    If you do need to complete a two way sync you can BACKUP the device and clear the Calendar (edit), then RESTORE just the the calendar in BACKUP / ADVANCED by menu'ing the backup you created and complete a restore of the calendar. By backing up and then clearing and then restoring, this will clear any issues with the calendar DB and reindex the data. Then try a regular sync and see if the symptom is taken care of.
    Good luck and let us know how your doing...
    Message Edited by hmeister on 10-10-2008 09:48 PM
    +++++++++++++++++++++++++++++++++++++++++++++++++
    If successful in helping you, please give me kudos in my post.
    Please mark the post that solved it for you!
    Thank you!
    Best Regards
    hmeister

  • ESS: Error in record worktime

    Hi,
    I am getting following error in record worktime iview of ESS.
    can you please help e resolving this:
    com.sap.pcuigp.xssfpm.java.FPMRuntimeException: The profile in use has                                                65 columns. A maximum of                                                40 columns are allowed
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:121)
         at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.setMessages(FcCatRecordInterface.java:1713)
         at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.setMessages(FcCatRecordInterface.java:1661)
         at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:452)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:234)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:484)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    Thanks
    Ankur

    Hi ankur,
    please check the data entry profile in use.
    In SAP there is a limitation of showing max of 40 columns only.
    go to t.code cac2 and check the columns showing for the data entry profile and ensure the correct profile is added to the user using CVR parameter in user profile in ECC system.
    This should solve the issue.
    Hope this helps.
    Cheers-
    Pramod

  • Unable to delete the error out record in Pending transactionsinterface form

    Hi Team,
    Help me having this issue....
    "Unable to delete the error out record in Pending transactions interface form".
    Version:11.5.10.2
    Regards,
    Arul

    Can you please give a more elaborate context?
    What application, responsibility and form, how are you trying to delete from the interface table, from front-end or via API?
    Thanks
    JD

  • Essbase Fatal Error: Invalid record in security file

    Hi,
    I'm newbie in Essbase, and I'm supporting Hyperion 7 for an pharmaceutical company.
    I have a serious problem with the Essbase services when I tried to start them.
    This message appears:
    Fatal Error: Invalid record in security file [16]
    I restarted the server but it's still doesn't work.
    I'll appreciate so much your quickly help.
    Regards.

    CL wrote:
    Easy, but unpleasant answer: your Essbase.sec file is probably, actually, almost definitely, bad.
    Some things you can try:
    1) Check to see if there is an Essbase.bak file in the Essbase\bin foler. If so, copy it to another name.
    2) Stop Essbase.
    3) Rename Essbase.sec to Essbase.sec.bad
    4) Rename Essbase.bak and start Essbase back up. You may have dodged a bullet.
    5) If #3 and #4 don't work for you, your best bet is to restore from tape.
    Regards,
    Cameron LackpourThe file essbase.sec is very easy to corrupt? We encountered this problem before but restored from essbase.bak.
    Any good practice to prevent similar problem?

Maybe you are looking for