Boris Export Stops at 98%

Has this ever happened to you?
I made up some titles with Boris 3D. Everything looks good.
I put it in an NTSC-anamorphic timeline, added a freeze frame
so that the last line of text would hold at the end,
then exported it as a QT movie.
During the export, it gets to 98%, says "Less than a minute remaining"
and then stays there. What could be happening?

Trash preferences?

Similar Messages

  • Database export stops with the following warnings.

    Hello,
    I am doing a Database Export/Import Activity. My DB is MS SQL server 2000 and SAP R/3 (4.6C SR2 , 4.6D kernel).
    When i try to do a DB export with option split STR and EXT files, my export stops abruptly without giving any erorrs but with a whole list of warnings.
    My splitting procedure is using SPLITSTR.PL perl script. I am not using the latest java based split.
    For your reference i am pasting the whole DBEXPORT.log file.
    (sorry its bit large,,, i hope you dont mind ) )
    INFO 2008-03-29 14:36:21 CommandFileController SyFileVersionSave:736
        Saving original content of file
        C:\Users\prdadm\Install\DBEXPORT.R3S ...
    INFO 2008-03-29 14:36:21 CommandFileController SyFileCopy:676
        Copying source file C:\Users\prdadm\Install\DBEXPORT.R3S to
        target file C:\Users\prdadm\Install\DBEXPORT.R3S.1 ...
    INFO 2008-03-29 14:36:21 CommandFileController SyPermissionSet:2207
        Changing permission for file C:\Users\prdadm\Install\DBEXPORT.R3S
        from 777 to 666.
    INFO 2008-03-29 14:36:21 Main
        Preparation successfully completed.
    INFO 2008-03-29 14:36:23 DBEXPORTINSTANCE_NT_IND DefValForKey_OS:0
        R3Setup found the share 'SAPLOC' on drive E:.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:37:17 DBEXPSERVER_NT_IND InternalColdKeyCheck:0
        The CD CDEXPORT1 will not be copied.
    INFO 2008-03-29 14:37:36 DBEXPORTINSTANCE_NT_IND CheckValueForKey:0
        The installation phase is starting now. Please look in the log
        file for further information about current actions.
    INFO 2008-03-29 14:37:36
        Requesting Export Details
    INFO 2008-03-29 14:37:36
        Requesting Export Details
    INFO 2008-03-29 14:37:36 DBEXPCOMMONDBENV_NT_MSS SyCoprocessCreate:931
        Creating coprocess osql.exe ...
    INFO 2008-03-29 14:37:36 DBEXPCOMMONDBENV_NT_MSS SyCoprocessExecute:171
        The process osql.exe puts out:
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
        Version String read from MS SQL Server: Microsoft SQL Server
        2000 - 8.00.2039 (Intel X86)       May  3 2005 23:18:38       Copyright
        (c) 1988-2003 Microsoft Corporation      Enterprise Edition on
        Windows NT 5.2 (Build 3790: Service Pack 2)
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
        Major Version read from MS SQL Server: 800
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
        Minor Version read from MS SQL Server: 2039
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS SyCoprocessCreate:931
        Creating coprocess osql.exe ...
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS SyCoprocessExecute:171
        The process osql.exe puts out:
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS InternalInstallationDo:0
        You have a correctly configured MS SQL Server with charset cp850
        and sortorder bin_cp850!
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS InternalInstallationDo:0
    ooo MSGERR Wrong type of Parameter: area:74, id:1, typeofParam:4, char:d
    ooo MSGERR Dump of parameter with valid type:
    ooo MSGWAR MsgAreaName:SY_AREA_RI_MSGL, MsgIdName:RI_MSGL_MIN_MAJORVERSION
    ooo MSGERR --- SYLOGDATA:ParaNr: 1, Typ:4
    ooo MSGERR --- SYLOGDATA:ParaNr: 2, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 3, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 4, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 5, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 6, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 7, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 8, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 9, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr:10, Typ:1, long=0
    ooo MSGERR Wrong type of Parameter: area:74, id:1, typeofParam:4, char:d
    ooo MSGERR Dump of parameter with valid type:
    ooo MSGWAR MsgAreaName:SY_AREA_RI_MSGL, MsgIdName:RI_MSGL_MIN_MAJORVERSION
    ooo MSGERR --- SYLOGDATA:ParaNr: 1, Typ:4
    ooo MSGERR --- SYLOGDATA:ParaNr: 2, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 3, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 4, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 5, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 6, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 7, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 8, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 9, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr:10, Typ:1, long=0    Your actual major version of MS SQL Server is
    INFO 2008-03-29 14:37:37
        Requesting Export-Specific Parameters
    INFO 2008-03-29 14:37:37
        Testing the Database Connect
    INFO 2008-03-29 14:37:37 DBDBSLTESTCONNECT_NT_IND InternalInstallationDo:0
        See logfile dev_dbsl for further information.
    INFO 2008-03-29 14:37:37 DBEXPSERVER_NT_IND InternalWarmKeyCheck:0
        The CD CDEXPORT1 will not be copied.
    INFO 2008-03-29 14:37:37
        Requesting Information on CD-ROMs
    INFO 2008-03-29 14:37:37
        Creating the Export Directories
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB. If it does not
        exist creating it with user NULL_POINTER, group NULL_POINTER and
        permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\ORA. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\ORA from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\INF. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\INF from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\ADA. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\ADA from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\MSS. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\MSS from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\DB2. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\DB2 from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\DB4. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\DB4 from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\DB6. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\DB6 from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DATA. If it does not
        exist creating it with user NULL_POINTER, group NULL_POINTER and
        permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DATA from 777 to 7.
    INFO 2008-03-29 14:37:37
        Creating the R3load Control Files
    INFO 2008-03-29 14:37:37 R3LDCTL_NT_IND R3ldctlDo:0
        C:\Users\prdadm\Install\R3LDCTL.EXE -p C:\Users\prdadm\Install
    INFO 2008-03-29 14:37:37 R3LDCTL_NT_IND SyCoprocessCreate:931
        Creating coprocess C:\Users\prdadm\Install\R3LDCTL.EXE ...
    INFO 2008-03-29 14:37:38 R3LDCTL_NT_IND R3ldctlDo:0
        WARNING: no technical settings for table "A055" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "A056" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "A064" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "A065" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "AABLG" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "AANK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "AANL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMON" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMONA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMONO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMONQ" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANAR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANEV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANGA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLW" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "APQD" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "APQI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ATAB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "B015" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "B060" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BGPROT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BKORA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BKORR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BPHIER" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BSIW" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCEVTJOB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCJSTAT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCOPTIONS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCSED" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCSEV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCUEV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BUXPRA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BVOR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATCU" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATDB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CBPL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CCCFINI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0BAS4VI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0BAS5VI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0MC5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0T200TAB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0T210TAB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0TBSH001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CDCLS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE1S001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE2S001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE3S001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE4S_CP_FLAG" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "CF003" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CF005" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CFIS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CHGRP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKHT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKKS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKKT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKPP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKPS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKPT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CLRK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CLU4" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CNTLREM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "COKAA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "COOI_PI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "COSPP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRHH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRID" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRS_BLOCKS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRVP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CSLT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CSSK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVEP1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVEP2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER4" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DD02ALL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DEBI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DELM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DLIX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKALTLANG" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKCL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKID" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKSH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKSI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOSSH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOSSI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYCR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYLI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYLT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYSX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DVERS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DVPOOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DVPOOLTEXT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "E070N" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EANQ" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EBSEG" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EBUB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDFIL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDI30C" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDI40" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDIDOC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDIE5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDMAP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EIPA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EKAN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EKPB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EKUB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EPIDXB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EPIDXC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EREF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EREN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ERET" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST07" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST0B" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST0D" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST0F" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EWUCUSA2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EWUCUSAK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FEBKEY" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FINPL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FINS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FINV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FLAPP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FLEMP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FMCFSI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FMCOPI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FMGEBER" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FOH01" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FREF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GCLIENTS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLOO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLOO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLPO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLPO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLPO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLS2CLUS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLT0" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTPC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GSBLCA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GWFEODE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HLPNA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRARCENQ" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRMS_BIW_PPDELTA" in
        SAP data dictionary - defaults used
        WARNING: no technical settings for table "HRPMPROT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRPMSIM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRPY_RGDIR_TEMP" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "IMPREDOC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "INDX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "INETX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "INHB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "IXDIT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "IXTYP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "IXTYT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "JVT1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "J_1AWITNR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "J_1BCBTAXPROC" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "J_1BITEMTYPES" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "K002" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KALK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KAPE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KAPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KBPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KCPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KDPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KEPOOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KGPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNAS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNB5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNC1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNC3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNMTK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNOB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVD" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOCLU" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KONAIND" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOND" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KONR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTD001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE002" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE003" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE004" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE005" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTG002" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTG003" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KRED" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LDAN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LDKO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFAS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFB5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFC1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFC3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LISA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LISPLF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MASE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MAT1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBAN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBMP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBPR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBRK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCEKS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCVSRFP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCY1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEIK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEIN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEKK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEOR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MHNDO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MHNKA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MKLK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MKUB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MLIB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MODSAP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MOFF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MPRP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSAK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSEGO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSET" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSOA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSPOOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSTA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_ADMC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_ADRC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_ADRP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_AKTE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_CF01" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_CKKA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_CLFN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_DARL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_DGMI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_HORD" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IBEW" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IFLM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IIMA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IRLM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_J1BA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_J1IA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_J1IB" in SAP data
        dictionary - defaults used

    Hello,
    The version of perl is correct.
    Anayways i have solved the problem!
    there was problem with the DBEXPORT.R3S file. i referred a SAP note for the same.(Installation of 4.6c on windows). In this check the section for post installation activity.
    I hope this can be a input for other experts who may face such problem!!!
    Regards,
    Shridhar!!!!

  • ABAP OO BOR export parameter

    Hi, All!
    I am beginner at ABAP OO in workflow and get a problem with using BOR in OO methods. Exporting parameter of the method typed as OBJ_RECORD. In workflow builder (method container) this   parameter displays as reference to BOR, but has not exact type of the BOR. Task container parameter has not type of BOR too.
    If i trying to change task or method container parameter - system returns it back and not saves binding.
    I need instructions, how to mount BOR type for method parameters. 
    Thanks,
    Constantine

    Martin,
    there is many methods in my  OO class (like prepare something and create something).
    In create method last raws like
    swc_create_object ex_changemaster c_bortype_changemaster l_objkey.
    ** error handling
    endmethod.
    In example, ex_changemaster has not BOR type in method and task container. And i can only control  task to model binding using manual assignment. No BOR type controlled by the system.
    Regards,
    Konstantin

  • Datapump Export stops at "Estimate in progress...."

    Hi,
    I am facing an issue while doing Schema level Datapump Export in Oracle 10g. The export for a particular schema stops at "Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA" and more over it only spawns one worker(DW01) irrespective of the PARALLEL parameter value. For other schema the export works fine and even the table level export for the problematic schema.
    I am clue less, because the alert log does not show anything, can any one please advice....
    Here is how my Parfile looks like:
    userid=id/password
    directory=impdir
    parallel=2
    schemas=prod11sep12
    dumpfile=expC2P_20120925_%U.dmp
    logfile=expC2P_20120925.log
    job_name=expC2P_20120925
    tail -f expC2P_20120925.log
    bash-3.00$ expdp parfile=expC2P.par ESTIMATE=STATISTICS
    Export: Release 10.2.0.4.0 - 64bit Production on Wednesday, 26 September, 2012 16:44:30
    Copyright (c) 2003, 2007, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Starting "SYSTEM"."EXPC2P_20120925": parfile=expC2P.par ESTIMATE=STATISTICS
    Estimate in progress using STATISTICS method...
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    Alert log:
    kupprdp: master process DM00 started with pid=38, OS id=15156
    to execute - SYS.KUPM$MCP.MAIN('EXPC2P_20120925', 'SYSTEM', 'KUPC$C_1_20120926164430', 'KUPC$S_1_20120926164430', 0);
    kupprdp: worker process DW01 started with worker id=1, pid=46, OS id=15201
    to execute - SYS.KUPW$WORKER.MAIN('EXPC2P_20120925', 'SYSTEM');
    Thanks in Advance...

    Pl enable trace as per this MOS Doc to see if additional debug information can be gathered
    Export/Import DataPump Parameter TRACE - How to Diagnose Oracle Data Pump [ID 286496.1]
    HTH
    Srini

  • IMovie export stops halfway

    i've tried exporting a project to full quality.
    It says that the export will finish in 2 minutes...
    but the thing is that the minutes keeping going up.
    i don't know if its just me... but it stops half way
    then i look at the activity monitor and it shows that
    "encoderserver" is not responding. and I'm
    thinking that's why?
    if someone could help then it'd help alot.
    thanks in advance!
    Black Macbook   Mac OS X (10.4.8)   2 GHZ Intel Core duo w/ 1 GB memory

    While iDVD can behave as Sue suggested, iDVD actually isn't involved when we export an iMovie project to a Full Quality movie. Something else must be going on.
    Your description sounds there's something wrong with the movie, something causing the export to fail.
    Make sure, first of all, that the iMovie project is stored on a drive that is formatted as needed by iMovie. The drive must use a Mac OS Extended disk format. Use the Get Info window in the Finder to check the disk format. (If the project is stored on your internal drive then the drive is probably okay, unless you've done something pretty unusual with your Mac.)
    Make sure too that there's sufficient disk space for the exported movie. It will need about 13 GB per hour. If your drive is filling up, that can cause major problems, especially if the internal drive is filling up. Mac OS X needs elbow room to work, and it may be getting a bit crowded.
    Sometimes there can be a problem with an audio file imported to iMovie. If the export fails at the same place each time, it's a good chance that's what happening. You might try turning off the two audio tracks and exporting. If the export succeeds, that suggests a problem with the audio.
    The trick is find the precise problem. One way is to export increasingly small chunks of the project, dividing the project in half until you identify the problem area. Then replace the audio at that spot. Use the "Export selected clips only" checkbox in the export dialog window to limit the clips you export. (The selected clips must be contiguous in the Timeline.)
    It's pretty hard to tell from here what might be the problem. It might come down to trial and error on your part to find the problem spot, if there is one.
    Good luck.
    Oh, if you have third-party iMovie plug-ins or QuickTime add-ons you might want to try disabling them:
    http://discussions.apple.com/message.jspa?messageID=2920540#2920540
    Karl

  • NetFlow exporter stops sending packets

    Have a Cat 4507 with Supervisor 7-E, setup configuration to send NetFLow information to an external server, everything worked great but after 2 weeks, the exporter is showing zero packets sent and the following error is at the console:
    Nov  5 15:52:35.231: %C4K_HWFLOWMAN-3-NFEINTERRUPTSTATUS: (Suppressed 7336 times)module: fi InterruptStatus: 0x4
    Nov  5 15:53:05.235: %C4K_HWFLOWMAN-3-NFEINTERRUPTSTATUS: (Suppressed 7345 times)module: fi InterruptStatus: 0x4
    Nov  5 15:53:35.239: %C4K_HWFLOWMAN-3-NFEINTERRUPTSTATUS: (Suppressed 7341 times)module: fi InterruptStatus: 0x4
    Nov  5 15:54:05.243: %C4K_HWFLOWMAN-3-NFEINTERRUPTSTATUS: (Suppressed 7344 times)module: fi InterruptStatus: 0x4
    Nov  5 15:54:35.247: %C4K_HWFLOWMAN-3-NFEINTERRUPTSTATUS: (Suppressed 7341 times)module: fi InterruptStatus: 0x4
    4507#show flow exporter statistics
    Flow Exporter Netflow-to-Orion:
      Packet send statistics (last cleared 01:08:30 ago):
        Successfully sent:         0                     (0 bytes)
      Client send statistics:
        Client: Flow Monitor NetFlow-Monitor
          Records added:           0
          Bytes added:             0
    I can't find any information related to that error, I haven't restart the switch because this is a very critical switch on a production network and also I would like to do some troubleshooting before doing an IOS upgrade or hardware replacement.
    Any ideas?
    Oscar

    We're seeing the same issue on a 4506E Sup7e and cat4500e-universalk9.SPA.03.02.00.SG.150-2.SG.bin.
    Has this been fixed yet? CSCub56668 suggests not and CSCtq40467 is restricted so I can't read it.

  • Preview (export) stopped working

    Recently (i.e the last couple of days) I continually get an error message from preview/export saying "<filename>" cannot be exported as "<filename>".  Are there any solutions or suggestions?

    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen. Click the Clear Display icon in the toolbar. Then take one of the actions that you're having trouble with. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Cs6 video export stops half way through (10.9.2)

    what could be the problem with video export in cs6?  no problem in fcp.

    LOL — play that show all through its 59 minute length? Oh, I think not ...
    The claimed speediness of the network isn't that significant. More useful would be to look and see what speeds you're actually getting, using any of the speed test apps.
    Streaming performance on the iPad is also at least partially app-dependent. We routinely stream full-length movies over Netflix with few to zero problems. Next in order would be ABC leading Hulu+ by a neck, then YouTube a distant 4th.

  • Call export with java function stop after a time

    Hi
    we make a function java for call exp.exe.
    We pass at java's function a string
    we use this code
    /* * ExecuteCmd.java * This is a sample application that uses the Runtime Object * to execute a program. * */
    /* Import the classes needed for Runtime, Process, and Exceptions */
    import java.lang.*;
    //import java.lang.Process;
    import java.io.*;
    //import java.lang.InterruptedException;
    class ExecuteCmd {
    public static int Cmd(String args) {
    try {
    /* Execute the command using the Runtime object and get the
    Process which controls this command */
    Process p = Runtime.getRuntime().exec(args);
    /* Use the following code to wait for the process to finish
    and check the return code from the process */
    try {
    p.waitFor();
    /* Handle exceptions for waitFor() */
    } catch (InterruptedException intexc) {
    //System.out.println("Interrupted Exception on waitFor: " + intexc.getMessage());
         return -1;
    return p.exitValue();
    /* Handle the exceptions for exec() */
    } catch (IOException e) {
    // System.out.println("IO Exception from exec : " + e.getMessage());
    // e.printStackTrace();
         return 1;
    after a time the export begin but stop after some time.
    If the schema is little like not table but some sequence the export gone normally but if the schema is big the export stop after a time but we dont have a trace with log.
    Can you help

    I think you need to gobble up the output from the command you are exec'ing. If the exec'd command fills up your command space buffer it will stop when the buffer is full.
    Try adding the lines
    String s = new String();
    while ((s = p.readLine())!=null)
    after the try block to gobble up the output from your command call.

  • Book Module: Export to PDF and Blurb stops with error at two page spread

    I have a 66 page book created in the book module..
    When exporting to PDF the export stops with the error:
    "An error occurred while saving the book.
    There was an error creating the PDF file. "
    The same occurs (at the same book page) when exporting to BLURB
    "An error occurred while creating the book."
    The creation or export always stops at the same page which is a two page spread. Interestingly there is a two-page spread before that didn't throw an error. I tried to move the problem page to the end of the book. That didn't help because the next two page spread in the book throws an error.
    Any ideas or help?
    Lightroom version: 4.0
    Computer: Windows 7, Quadcore, 8 GB RAM

    Hi, sorry I do not have a solution but I too have a very similar issue in that the book is the same size but the export to PDF does not start at all
    I have tried reducing the image dpi settings. Jpg quality and still nothing
    The only success I have had is if I duplicate the book, delete all but 8 pages and then export at full dpi settings of 300 and 100 percent jpg quality
    Any more pages and nothing
    It's a great tool and would buy it if this feature actually worked. Oh yeah I only have the trial version at the minute to give it a good thorough test
    I have looked for solutions but like your query they are all unanswered
    Does adobe actually offer any support or is this all user solutions?
    Did you find a solution by the way?

  • Date issue stopping export program.

    Hi All,
    We are using Oracle 11g version.
    We are exporting the data from the DB to a .txt file. If the next run date of the report in a status table is greater than or equal to system date then export should happen.
    --Note: <Report Name> is the in param.
    Execute immediate 'ALTER SESSION SET NLS_DATE_FORMAT =''DD-MON-RR''';
    COMMIT;
    FOR i IN (Select reportid from status_table where reportname = <Report Name> and status = 'SCHEDULED' and *NextRunDate <= SYSDATE*)
    LOOP
      l_query := l_QueryFromTable;
    Select (NextRunDate) into lv_NextRunDate from status_table where reportname = <Report Name> and status IN ('SCHEDULED');
    Execute immediate 'ALTER SESSION SET NLS_DATE_FORMAT =''MM/DD/YYYY HH24:MI:SS''';
    COMMIT;
    -- Then start the export program......
    End Loop;The above code was working perfectly fine but it stopped working suddenly. I added TRUNC while selecting from table and comparing dates. It is working now.
    Now, Question is;
    How come the code stopped working which was working fine before? Is it happening because "nls_date_params" being altered?
    Is TRUNC solution resolves my issue permanently?
    Please let me know.
    Thanks and Regards
    Nagaraja Akkivalli.

    Thanks WhiteHat for the response.
    Yes, you are right. Cursor was not returning any data. Due to which, export stopped working.
    Normal comparision of the dates does not consider timestamp due to which we started altering nls_date_parameters.
    For example,
    We load files to transactionl tables. If the files loads @ 12:59:53 then we check the tables recors for this file as below.
    (TrxnTable.EntryCreatedDate) between  '12-DEC-2011' and '12-DEC-2011' does not returns the correct results.
    However, below two queries returns the proper results.
    (TrxnTable.EntryCreatedDate) between  '12-DEC-2011 00:00:00' and '12-DEC-2011 23:59:59'
    or
    trunc(TrxnTable.EntryCreatedDate) between  '12-DEC-2011' and '12-DEC-2011' Also, Many times we perform some operations on timestamp. That is why we are altering nls_date_parameters.
    Note: Defaults nls date param is 'DD-MON-RR'. Export program starts @ 6:00:00 AM.
    Table structure and data FYI.
    CREATE TABLE STATUS_TABLE
         REPORTID  NUMBER(20,0),
          REPORTNAME  VARCHAR2(100 BYTE),
          NEXTRUNDATE  DATE,
          CREATED_DATE  DATE,
          CONSTRAINT  STATUS_TABLE_PK  PRIMARY KEY ( REPORTID )  
    ReportID     Report Name     NextRun Date
    7503          ReportX          12/12/2011 8:01
    7502          ReportY          12/11/2011 8:01
    7491          RepiotZ          12/10/2011 8:01
    7490          ReportX          12/9/2011 8:01
    7489          ReportY          12/8/2011 8:01
    7488          RepiotZ          12/7/2011 8:01Hope this infomation suffices to explain why export program stopped working.
    Please let me know if you need any details.
    Regards
    Nagaraja.

  • How do you improve quality of QuickTime movie exported from Flash?

    Hi
    I have designed a Flash animation for a client who has asked me to also provide it in a format which can be used in a film he wants to produce in Apple Final Cut Pro.  I assumed the best format would be QuickTime but whenever I export the Flash file in to QuickTime the quality of the film is awful - the graphics leave fragments of themselves behind as they move (if that makes sense?!) and the overall quality isn't very crisp.
    I have tried various export settings and followed a few tutorials online but still having no success!  If anyone can make any suggestions I would really appreciate it or is there even another file format that can be used with Final Cut Pro?
    Thanks for your advice!!

    Whenever I export an animation out for video, I always export it uncompressed.  It gives a very large file, but then you don't have to worry about it getting compressed multiple times (as the video will be compressed when completed), and I have not had any problems with it.
    If you are still having problems with QT export - I have heard reports that setting a time in the export (stop after X time, rather than stop at last frame) will get rid of it.
    And, if you still have problems exporting to QT, then I suggest exporting to AVI and converting to MOV with a separate tool.

  • Exporting AVI clips (error: "[\Src\Win\WinFile.cpp-759]" after 4 %)

    The following problem:
    I have 2 adobe premiere project. both have the same film and film length but different video codecs.
    1. project (low quality video codecs (mpeg4)
    export works fine
    2. project (high quality video codecs (avi)
    export stops every time after 4% with the following error notice:
    "Premiere Pro has encountered an error.
    [..\..\Src\Win\WinFile.cpp-759]"
    or if I want export the project with other codecs, eg H.264 then Adobe premiere freezes and I can close Adobe Premiere then.
    Premiere memory settings (valid for both premiere projects):
    Installed RAM: 3,7 GB
    RAM reserved for other applications: 1,5 GB
    Ram available for Adobe: 2,2 GB
    Optimize rendering for: "Memory"
    computer details:
    system type: 64 Bit
    installed RAM: 3,75 GB
    processor: AMD Athlon, 2 x4 635 processor 2.90 GHz
    graphics card: ATI Radeon HD4200
    windows edition: 7
    How can I solve the problem, so that I can export my whole project in AVI codecs without freezing problems or error problems?
    Is it a hardware or software problem?
    Thanks in advance for your help

    Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link
    Most especially the SOURCE FILE codec used... see Question 1

  • AVI clips export (Fehlermeldung: "[..\..\Src\Win\WinFile.cpp-759]") Premiere friert ein beim export

    The following problem:
    I have 2 adobe premiere project. both have the same film and film length but different video codecs.
    1. project (low quality video codecs (mpeg4)
    export works fine
    2. project (high quality video codecs (avi)
    export stops every time after 4% with the following error notice:
    "Premiere Pro has encountered an error.
    [..\..\Src\Win\WinFile.cpp-759]"
    or if I want export the project with other codecs, eg H.264 then Adobe premiere freezes and I can close Adobe Premiere then.
    Premiere memory settings (valid for both premiere projects):
    Installed RAM: 3,7 GB
    RAM reserved for other applications: 1,5 GB
    Ram available for Adobe: 2,2 GB
    Optimize rendering for: "Memory"
    computer details:
    system type: 64 Bit
    installed RAM: 3,75 GB
    processor: AMD Athlon, 2 x4 635 processor 2.90 GHz
    graphics card: ATI Radeon HD4200
    windows edition: 7
    How can I solve the problem, so that I can export my whole project in AVI codecs without freezing problems or error problems?
    Is it a hardware or software problem?
    Thanks in advance for your help
    Ich bin Deutscher. Ich brauche schnelle Hilfe. deshalb habe ich aus dem englischen forum mein eintrag kopiert und hier eingefügt.
    Vielen Dank im Voraus

    Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link
    Most especially the SOURCE FILE codec used... see Question 1

  • Keynote 3.0.2  Will Not Export to Quicktime

    I have a put together a Keynote presentation that uses a Quicktime movie on one of the slides. The presentation plays fine within Keynote, but when I try to export the presentation to Quicktime, the export stops and tells me there's not enough memory or there's something wrong with the file. The message comes up when the export procedure reaches the slide that contains the Quicktime movie. Is it possible to export a Keynote presentation to a Quicktime Movie if the presentation has a movie in it? That's like a movie inside a movie. I can't get it to export to QTime.

    The other work around that I've found is to tell it "send to iDVD" but then quit iDVD when it pops that up. You'll end up with just the quicktime file it created.
    What I noticed is that when a "quicktime export" plays in QT, it has a fps rate of like 7 or 8 or even 13 but the dynamic "playing fps" goes up to 30 during transitions and back to 0 when there isn't a transition. At least with the iDVD cheat you end up with 24 fps. That may work for some people, that is film rate, but I'm in need of NTSC DV 29.97. So I import it into Final Cut Express, and do an export conversion.
    I don't use audio, so I don't know how that would work in this cheat, but since your voiceover (I'm guessing based on trying to put music to my slides) is one entire track, you can add that in FCE before that export and line it up there.
    If anyone else has suggestions to get a 29.97 export correct with the "export to quicktime", I'd love to hear it. This cheat takes too long for my work.

Maybe you are looking for

  • G4 to composite video

    I have a G4 mirror tower with an ATI 9000 video card. It has an DVI to VGA adapter. Do any of the VGA to Composite video adapters work to connect to a TV? Any other inexpensive way to do it?

  • Ipod won't go into disk mode for recovery

    This morning my IPod (80GB Video Ipod) wouldn't play, so I rebooted it, but it would not restart and it gets the red X sign. I followed the directions to get it to go into disk mode, but it still won't. It keeps going to the red X screen! I can't see

  • Itunes update fail with 1XE800000A what is it?

    Today i want to make an update for itunes.... but it fails with mistake number 1XE800000A Who knows what it means... Who can help? OS is win 7 64bit

  • Convertion from Decimal to Hexadecimal

    Hi, Can you please tell me the way to covert a given decimal number into hexadecimal (for example 4 -> 04, 20 -> 14 etc) and also the vice versa. thank you.

  • Crash / Kernel Panic related to Sudden Motion Sensor (SMS)

    I have been having frequent kernel panics on my Macbook Pro since replacing the hard drive. I recently realized that this appears to be related to moving or bumping the machine. For example, I was recently working while lying down resting the machine