Error on exit with LMS KO

I have a client using the Plateau LMS and every time they
exit the course with the Send Data KO (that which came with AW7,
not the Professional KO) they get an PostURL() error, IOStatus
5006. I have set the KO to track data,
Score = (no value)
Time Automatic
Location – Other (custom variable)
=bookmark
Status = CMIStatus
Lesson Data consists of a single variable which is a single
dimensional linear list (eg modCompletion=[0,1,0])
No Pre-Processing
Quit after sending (no optional url)
Any thoughts would be greatly appreciated.

Brandt Wagner,
Actually - the use of the CMI Functions and Variables could
(and probably
would) certainly cause the error you indicate, below.
Authorware automatically attempts to do it's own LMS tracking
with an AICC
LMS (but doesn't quite follow the standard) but not a
SCORM-compliant LMS,
when you use the CMI Functions and Variables. This conflicts
with the LMS
KOs communication with an LMS. So...
The LMS KO attempts to communicate with the LMS using the
data/variables you
entered in the KO wizard AND Authorware attempts to
communicate with the LMS
seperately, using the data it's aware of (which in this case
is so limited)
and it's this later communication that is causing the 5006
error to occur.
First recommendation is to NOT use the CMI
Functions/Variables, if you are
using the LMS KOs. Re-publish and import into your LMS. Make
sure you
remember to clear your browser cache.
Regards,
Andrew

Similar Messages

  • ...can any one offer any advice ... My iMac crashed :( I need it for work :( :( the error is Exited with signal 8 Fsck failed ! ... There is a bunch of text b4 that and  little bit after but that seems to the main thing ..? Any help would be amazing

    My iMac crashed ... When I try to reboot I get nonlove... The error message is Exited with signal 8.... Fsck failed ! And then it says a few line and killing all processes and then it turns it self off again ...
    ANy any suggestions would be fantastic

    Start with this comprehensive troubleshooting article:
    https://discussions.apple.com/docs/DOC-3521
    Look at this one for possible solutions:
    https://discussions.apple.com/docs/DOC-3353
    Ciao.

  • HELP!! Process exited with exit code 128.

    Hi all,
    I am using JDeveloper 10G to develop a struts project. I use the struts-tiles.tld to construct the layout.
    <tiles:insert page="classicLayout.jsp" flush="true">
    <tiles:put name="title" value="User and Assigned Role" />
    <tiles:put name="header" value="menuTemplate.jsp" />
    <tiles:put name="menu" value="TestPoint.jsp" />
    <tiles:put name="body" value="ARM001800.jsp" />
    <tiles:put name="footer" value="DebugPage.jsp" />
    </tiles:insert>
    However, when I run the project, then the OC4J Server terminated with this error code : Process exited with exit code 128.
    What happen??
    PS: I tried to remove the last 2 tags: body and footer. The Server did not terminate, but with some exceptions which related to tiles library.

    This type of error may occur because of developers mistake.
    This error occurs when any function is called recursively in a loop.
    The server calls the same function again and again in a loop and hence the server goes in infinite loop. This gives the error "Process exited with exit code 128".
    You need to check your code thoroughly for such mistake.
    Nital.
    i-engineering.com

  • "process exited with exit code 128"

    I have a problem. I downloaded the new Jdeveloper 10.3.1. When a try to
    run a class i always receive the error: "process exited with exit code
    128". The compilation is correct. My OS is Win2003 server SP1, I
    tried in a pc with the same OS and it doesn't work correctly.
    Someone has got an idea?

    I have the same "process exited with exit code 128" in my Win 2003 server environment running AMD 64 processor. My Win 2000 server setting runs okay.
    I can work that around by changing the Virtual Machine setting. Select anything other then 'ojvm' with run ok. I guess, the Oracle custom add-on is not working properly.
    Follow this path to change.
    goto Project properties->Run/Debug
    ->select your run configuration (Default if you have no others)
    -> change 'Virtual Machine:' to server, client, or hotspot.
    ojvm is the only virtual machine that doesn't work.
    There is one catch, however, by making this change code coach, and all other profiling tools will not run.

  • Process exited with exit code -1073741790     in jdeveloper

    Hi,
    When I try to run a simple Helloworld program in Jdeveloper, The compilation and all is fine, when I try to run it I got the error "Process exited with exit code -1073741790".
    However I found one solution that, my computer is under a secured network, the Security Agent was seems stopping.
    I changed the security level to LOW from MEDIUM , then its running fine.
    Is there any other solution where I can work without reducing the security level.
    While writing this post, I checked one more option of adding the jdeveloper.exe to trusted application in the Security agent. This seems resolved the application and working fine now.
    -- Khaleel

    Christy,
    what is the operation system you are running JDeveloper on ?
    To further debug the problem, can you open a command line at <Jdeveloper Directory>\j2ee\home
    (assuming Windows) type
    ..\..\jdk\bin\java oc4j.jar
    provide an administration password when asked. This command starts the embedded OC4J as a stand-alone server and prints messages to the console window
    Let us know if this gives more detailed error messages or if it starts up
    Frank

  • Process exited with exit code -1073741819+jdeveloper 9.0.5.1

    Hi,
    I am using JDeveloper 9.0.5.1 version.When i am compiling the java file it is compiling fine. But when I am running it it is throwing the error
    Process exited with exit code -1073741819.
    What is that error code means........?

    Hello,
    It could mean that the cause is a StackOverflowError.
    It could be that you are not running against your JDeveloper 9.0.5.1
    embedded OC4J, but without noticing it, you are running your program
    against another OC4J which would be incompatible!
    May be you are running several JDevelopers on your machine, or
    having a standalone OC4J and deployed your application against
    such a different OC4J.
    Try shutting down all the OC4J listeners on your machine, restart JDev
    and run your java code again.
    Hope this can help you.
    Stephan

  • RMAN Backup is failling with "RMAN exited with return code '1' " via tape.

    Hi Everyone,
    Backups are getting failed continously with below error.can you plese suggest me what is problem exactly
    L1_OracleL1_Daily completed
    Failed:  ***-rac-a16-001-vip.*****.dom*
    --- Unsuccessful Save Sets ---
    ** ***-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup savegrp: suppressed 43 lines of output.*
    ** ***-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup*
    ** ***-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup Recovery Manager complete.*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup The backup process failed:*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup RMAN exited with return code '1'.*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup Exiting with error:*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup RMAN exited with return code '1'.*
    ****-rac-a16-001-vip.uidl1.dom: RMAN exited with return code '1'.*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup nsrnmostart returned status of 255*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup /usr/sbin/nsrnmobkp exiting.*
    Thanks,
    Prasanth

    Hi Hemanth/imran,
    storage team is shown below error for failure of backup in their log.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-12502: TNS:listener received no CONNECT_DATA from client
    Recovery Manager complete.
    The backup process failed:
    RMAN exited with return code '1'.
    Exiting with error:
    RMAN exited with return code '1'.
    uidl1-rac-a16-001-vip.uidl1.dom: RMAN exited with return code '1'.
    Any changes we need to do
    Thanks,
    Prasanth

  • Error while running a OA framework Page  Process exited with exit code 1.

    Hi all,
    I downloaded the Patch 4573517 from Metalink for JDEV with OA extension release 11i.I followed all the instruction of the setup init and installed the Jdev,also mytutorial pages got compiled successfully,but when i trie dto run the page
    Run > Run test_fwktutorial.jsp from the main menu.
    it gives me error.The error is as follows
    [Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
    C:\D drive\OA_2008\jdevbin\jdk\bin\javaw.exe -client -classpath C:\D drive\OA_2008\jdevbin\j2ee\home\oc4j.jar;C:\D drive\OA_2008\jdevbin\jdev\lib\jdev-oc4j.jar -Xbootclasspath/p:C:\D drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\D drive\OA_2008\jdevbin\jdev\appslibrt\nls_charset12.zip -DFND_JDBC_STMT_CACHE_SIZE=200 -DCACHENODBINIT=true -DRUN_FROM_JDEV=true -mx256m -Doracle.j2ee.dont.use.memory.archive=false -Xverify:none -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 com.evermind.server.OC4JServer -config C:\D drive\OA_2008\jdevhome\jdev\system9.0.3.5.1437\oc4j-config\server.xml
    [waiting for the server to complete its initialization...]
    java.lang.NoClassDefFoundError: drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14/jar;C:\D
    Exception in thread "main"
    Process exited with exit code 1.
    I am not understanding why it is going in exception.One reason which i doubthere is the line
    java.lang.NoClassDefFoundError: drive\OA_2008\jdevbin\jdev\appslibrt\ojdbc14/jar;C:\D
    here in this line the last word is ojdbc14/jar,i think it should have been ojdbc14.jar.
    Can any body please help me out on how to correct this problem.Thanks
    Manish

    Manish,
    You should ask on the OA Framework Forum.
    john

  • SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

    Hello,
    We are doing an installation of SAP NW 7.01 SR1 on V6R1.
    <br>
    We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
    <br>
    We are again getting error in following steps:
    <br>
    sapinst.log
    <br>
    <br>WARNING 2009-09-30 23:25:28.477
    Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
    J9VM - 20090309_31291_BHdSMr
    JIT  - 20090210_1447ifx1_r8
    GC   - 200902_24)
    I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
    <br>Loading of 'SAPNTAB' import package: OK
    <br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
    Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
    Loading of 'SAPAPPL1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
    Loading of 'SAPSDIC' import package: OK
    Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
    Loading of 'FUPARAREF' import package: OK
    Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
    Loading of 'TODIR' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
    Loading of 'E071K' import package: OK
    Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
    Loading of 'SAPAPPL0' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
    Loading of 'SAPSSEXC' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
    <br>
    WARNING[E] 2009-09-30 23:25:28.524
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
    <br>
    ERROR 2009-09-30 23:25:28.914
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    <br>
    <br>import_monitor.log.
    <br>****************************************************************************************************************************************************
    <br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is successfully completed.
    <br>
    WARNING: 2009-09-30 23:31:31
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-09-30 23:31:31
    1 error(s) during processing of packages.
    INFO: 2009-09-30 23:31:31
    Import Monitor is stopped.
    <br>*************************************************************************************************************************************************
    <br>SAPAPPL02.LOG
    <br>**************************************************************************************************************************************************
    <br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) INFO: TVV1 created #20091001110304
    <br>
    (DB) INFO: TVV1 deleted/truncated #20091001110304
    <br>
    (IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
    <br>
    (DB) ERROR: DDL statement failed<br>
    (ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
    DbSlExecute: rc = 99<br>
      (SQL error -539)<br>
      error message returned by DbSl:
    Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
    Your inputs will help a lot.
    Regards,
    Prasad

    Hello,
    We are doing an installation of SAP NW 7.01 SR1 on V6R1.
    <br>
    We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
    <br>
    We are again getting error in following steps:
    <br>
    sapinst.log
    <br>
    <br>WARNING 2009-09-30 23:25:28.477
    Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
    J9VM - 20090309_31291_BHdSMr
    JIT  - 20090210_1447ifx1_r8
    GC   - 200902_24)
    I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
    <br>Loading of 'SAPNTAB' import package: OK
    <br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
    Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
    Loading of 'SAPAPPL1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
    Loading of 'SAPSDIC' import package: OK
    Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
    Loading of 'FUPARAREF' import package: OK
    Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
    Loading of 'TODIR' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
    Loading of 'E071K' import package: OK
    Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
    Loading of 'SAPAPPL0' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
    Loading of 'SAPSSEXC' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
    <br>
    WARNING[E] 2009-09-30 23:25:28.524
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
    <br>
    ERROR 2009-09-30 23:25:28.914
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    <br>
    <br>import_monitor.log.
    <br>****************************************************************************************************************************************************
    <br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is successfully completed.
    <br>
    WARNING: 2009-09-30 23:31:31
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-09-30 23:31:31
    1 error(s) during processing of packages.
    INFO: 2009-09-30 23:31:31
    Import Monitor is stopped.
    <br>*************************************************************************************************************************************************
    <br>SAPAPPL02.LOG
    <br>**************************************************************************************************************************************************
    <br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) INFO: TVV1 created #20091001110304
    <br>
    (DB) INFO: TVV1 deleted/truncated #20091001110304
    <br>
    (IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
    <br>
    (DB) ERROR: DDL statement failed<br>
    (ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
    DbSlExecute: rc = 99<br>
      (SQL error -539)<br>
      error message returned by DbSl:
    Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
    Your inputs will help a lot.
    Regards,
    Prasad

  • SAP ECC error:'Migration Monitor' exits with error code 103.

    Hi All,
    I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
    I am stuck at the import ABAP.Getting error
    ERROR 2008-08-08 16:10:53
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    1) imort_monitor.java.log-->contains
    java version "1.4.2_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
    Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
    Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
    Loading of 'SAPVIEW' import package: ERROR
    Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
    2)import_monitor.log
    ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPVIEW' import package is interrupted with R3load error.
    Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
    For mode details see 'SAPVIEW.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    INFO: 2008-08-08 16:10:52
    All import packages are processed.
    WARNING: 2008-08-08 16:10:52
    1 error(s) during processing of packages.
    INFO: 2008-08-08 16:10:52
    Import Monitor is stopped.
    3)SAPVIEW.log
      error message returned by DbSl:
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001"  ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001",  T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
    DbSlExecute: rc = 103
      (SQL error -942)
      error message returned by DbSl:
    (DB) INFO: disconnected from DB
    D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
    D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
    Only SAPDB: SAPSID srvice of SAP DB is only up.
    No other services of database are  up.And i am not able to up the other services also.
    Is it required to up the other services?
    If not?
    Why this error is occuring?
    Any help will be appreciated.
    Thanks&Regards
    Manisha das

    Hello Manisha,
    The one of the possible reasons for this is due to lack of H/W.
    Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
    If the issue is with H/W, then this should fix the issue.
    Hope it helps,
    Regards,
    Satish.

  • Error MSB3073: The command exited with code -1

    I am getting this error while deploying the biztalk project from visual studio using Deployment Framework for Biztalk (BTDF).
    Please guide me what needs to be done. Here's the code :-
    <?xml version="1.0" encoding="utf-8"?>
    <!--
    Deployment Framework for BizTalk
    Copyright (C) 2008-14 Thomas F. Abraham, 2004-08 Scott Colestock
    -->
    <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" DefaultTargets="Installer" ToolsVersion="4.0">
    <PropertyGroup>
    <Configuration Condition="'$(Configuration)' == ''">Debug</Configuration>
    <Platform Condition="'$(Platform)' == ''">x86</Platform>
    <SchemaVersion>1.0</SchemaVersion>
    <ProjectName>HelloWorld</ProjectName>
    <ProjectVersion>1.0</ProjectVersion>
    <IncludeOrchestrations>False</IncludeOrchestrations>
    <IncludeTransforms>False</IncludeTransforms>
    <IncludeSSO>True</IncludeSSO>
    <UsingMasterBindings>True</UsingMasterBindings>
    <RequireXmlPreprocessDirectives>False</RequireXmlPreprocessDirectives>
    <ApplyXmlEscape>True</ApplyXmlEscape>
    <SkipIISReset>True</SkipIISReset>
    </PropertyGroup>
    <PropertyGroup>
    <!-- Properties related to building an MSI for server deployments -->
    <!-- BizTalk App Version Upgrade -->
    <!-- For each new product release to be deployed to your BizTalk servers: -->
    <!-- 1) Increment ProductVersion -->
    <!-- 2) Generate a new GUID and update ProductId with the new GUID -->
    <!-- This allows the new MSI to automatically uninstall (not undeploy!) the old MSI and install the new one. -->
    <ProductVersion>1.0.0</ProductVersion>
    <ProductId>084986b1-d675-4383-b0ed-da2e3f4e3998</ProductId>
    <!-- BizTalk App Version Upgrade -->
    <ProductName>HelloWorld for BizTalk</ProductName>
    <Manufacturer>Deployment Framework User</Manufacturer>
    <PackageDescription>HelloWorld</PackageDescription>
    <PackageComments>HelloWorld</PackageComments>
    <!-- NEVER change the ProductUpgradeCode. -->
    <ProductUpgradeCode>4975288c-1b94-4d42-868b-f166cdc02224</ProductUpgradeCode>
    </PropertyGroup>
    <!-- Under TFS Team Build, set CustomizableOutDir property to true in TFS 2005/2008/2010 UpgradeTemplate. -->
    <!-- With a workflow build, copy the default template then modify the MSBuild task for the solution build. Set OutDir to blank and -->
    <!-- CommandLineArguments to String.Format("/p:SkipInvalidConfigurations=true;TeamBuildOutDir=""{0}"" {1}", BinariesDirectory, MSBuildArguments). -->
    <PropertyGroup Condition="'$(Configuration)' == 'Debug'">
    <DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>
    <OutputPath Condition="'$(TeamBuildOutDir)' == ''">bin\Debug\</OutputPath>
    <OutputPath Condition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>
    <DeployPDBsToGac>false</DeployPDBsToGac>
    </PropertyGroup>
    <PropertyGroup Condition="'$(Configuration)' == 'Release'">
    <DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>
    <OutputPath Condition="'$(TeamBuildOutDir)' == ''">bin\Release\</OutputPath>
    <OutputPath Condition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>
    <DeployPDBsToGac>false</DeployPDBsToGac>
    </PropertyGroup>
    <PropertyGroup Condition="'$(Configuration)' == 'Server'">
    <DeploymentFrameworkTargetsPath>Framework\</DeploymentFrameworkTargetsPath>
    <!-- Get our PDBs into the GAC so we get file/line number information in stack traces. -->
    <DeployPDBsToGac>true</DeployPDBsToGac>
    </PropertyGroup>
    <ItemGroup>
    <PropsFromEnvSettings Include="SsoAppUserGroup;SsoAppAdminGroup" />
    </ItemGroup>
    <!-- !!! TODO !!! -->
    <!-- Add ItemGroup elements that contain one or more Schemas, Orchestrations, Transforms, etc. elements that describe -->
    <!-- the specific artifacts in your solution that need to be deployed. Use IntelliSense as a guide. -->
    <ItemGroup>
    <Schemas Include="HelloWorld.dll">
    <LocationPath>..\$(ProjectName)\bin\$(Configuration)</LocationPath>
    </Schemas>
    </ItemGroup>
    <!-- !!! TODO !!! -->
    <Import Project="$(DeploymentFrameworkTargetsPath)BizTalkDeploymentFramework.targets" />
    <!--
    The Deployment Framework automatically packages most files into the server install MSI.
    However, if there are special folders that you need to include in the MSI, you can
    copy them to the folder $(RedistDir) in the CustomRedist target.
    To include individual files, add an ItemGroup with AdditionalFiles elements.
    -->
    <Target Name="CustomRedist">
    </Target>
    </Project>
    Error :-
    Starting build...
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" /nologo /t:Deploy /p:Configuration=Debug
    Build started 08-04-2015 17:43:51.
    Project "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" on node 1 (Deploy target(s)).
    SetModeDeploy:
    DEPLOYING APPLICATION TO BIZTALK...
    SetWinVer:
    Running on Windows V62
    Detected IIS 7
    Detected 64-bit OS
    GetSoftwarePaths:
    Using .NET Framework Install Path 'C:\Windows\Microsoft.NET\Framework\v4.0.30319'.
    Using BizTalk Install Path 'C:\Program Files (x86)\Microsoft BizTalk Server 2013\'.
    Using Deployment Framework Install Path 'C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\'.
    Using Deployment Framework Tools Path 'C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools'.
    Using BizTalk ESB Toolkit Install Path 'C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\'.
    ExportSettings:
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\EnvironmentSettingsExporter.exe" "C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\SettingsFileGenerator.xml" "C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings"
    Environment Settings Spreadsheet to XML Exporter 1.6.1
    [http://EnvSettingsManager.codeplex.com]
    Copyright (C) 2007-11 Thomas F. Abraham. All Rights Reserved.
    Importing from SettingsFileGenerator.xml...
    Output format is XmlPreprocess (multi-file).
    Exporting to Exported_LocalSettings.xml...
    Exporting to Exported_DevSettings.xml...
    Exporting to Exported_TestSettings.xml...
    Exporting to Exported_ProdSettings.xml...
    Finished.
    InitSettingsFilePath:
    Using settings file C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml
    SetPropertiesFromEnvironmentSettings:
    Setting properties from environment settings file (C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml)
    Setting property to value 'BizTalk Application Users'.
    Setting property to value 'BizTalk Server Administrators'.
    InitializeAppName:
    BizTalk Application Name is HelloWorld
    PreprocessBindings:
    Checking syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml'...
    Syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml' appears to be valid.
    Clearing file attributes for 'PortBindings.xml'.
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\xmlpreprocess.exe" /v /c /noDirectives /i:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml" /o:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" /d:CurDir="C:\BTDF\Walkthrough1" /s:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml"
    XmlPreprocess v2.0.18.0
    Copyright (c) 2004-2013 Loren M Halvorson
    XML File Preprocessor
    Settings XML file: "C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml"
    Preprocessing "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindingsMaster.xml" to "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml"...
    PortBindings.xml : Set the value 'HelloWorld' of 2 node(s) matching XPath '//ApplicationName'.
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\ElementTunnel.exe" /i:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" /o:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" /x:"C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\adapterXPaths.txt" /encode+
    Nested XML Encoder/Decoder v5.5.100.0
    Copyright (C) 2005-2014 Scott Colestock, Tim Rayburn, Thomas F. Abraham
    XML encodes/decodes content of element(s) by XPath. Applies escaping rules such
    as &gt; for '<'. Namespace decls, PIs, etc. of nested XML are not preserved.
    XPaths : 16
    Transformed Nodes : 0
    Empty Nodes (skipped) : 3
    No Transform Req'd (skipped) : 3
    Total Matched Nodes : 6
    Complete - output file has been saved.
    Checking syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml'...
    Syntax of XML file 'C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml' appears to be valid.
    DeployFileAdapterPhysicalPaths:
    Configuring FILE adapter physical paths from binding file PortBindings.xml...
    Processing FILE adapter physical paths (Send)...
    Setting up path 'C:\BTDF\Walkthrough1\Out'...
    Directory already exists.
    Granted 'BUILTIN\Users' Full Access permissions.
    Processing FILE adapter physical paths (Receive)...
    Setting up path 'C:\BTDF\Walkthrough1\In'...
    Directory already exists.
    Granted 'BUILTIN\Users' Full Access permissions.
    TerminateServiceInstancesConditional:
    Attempting to terminate all service instances for BizTalk app 'HelloWorld'...
    Terminated 0 service instances for BizTalk app 'HelloWorld'.
    VerifyBizTalkAppExists:
    Checking for existence of BizTalk application 'HelloWorld'...
    Did not find BizTalk application 'HelloWorld'.
    DeployAppDefinition:
    BTSTask.exe AddApp -ApplicationName:"HelloWorld" -Description:"HelloWorld"
    Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
    Copyright (c) 2013 Microsoft Corporation. All rights reserved.
    Information: Adding new BizTalk application "HelloWorld" to configuration database (server="BDDBESBWMV01", database="BizTalkMgmtDb")...
    Information: Added application "HelloWorld".
    Command succeeded with 0 errors, 0 warnings.
    UndeploySchemas:
    Adding assembly name 'HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f' to item group.
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\gacutil.exe" /u "HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f"
    Microsoft (R) .NET Global Assembly Cache Utility. Version 4.0.30319.1
    Copyright (c) Microsoft Corporation. All rights reserved.
    Number of assemblies uninstalled = 0
    Number of failures = 0
    DeploySchemas:
    BTSTask.exe AddResource -Type:BizTalkAssembly -Source:"..\HelloWorld\bin\Debug\HelloWorld.dll" -ApplicationName:"HelloWorld" -Options:GacOnAdd,GacOnImport,GacOnInstall
    Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
    Copyright (c) 2013 Microsoft Corporation. All rights reserved.
    Information: Adding resource (-Type="System.BizTalk:BizTalkAssembly" -Luid="HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f") to application "HelloWorld"...
    Serialized BizTalk assembly "HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f" from "..\HelloWorld\bin\Debug\HelloWorld.dll".
    Information: Validating resources (count=1)...
    * Validating resource (-Type="System.BizTalk:BizTalkAssembly" -Luid="HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f")...
    Information: Performing change requests...
    Information: Calling BeginTypeChangeRequest for all selected resource types...
    PerformingBeginChangeRequest
    Adding resource (-Type="System.BizTalk:BizTalkAssembly" -Luid="HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f") to store.
    Information: * Performing change request on type "System.BizTalk:BizTalkAssembly" (count=1)...
    Information: Deploy server="BDDBESBWMV01" database="BizTalkMgmtDb" assembly="C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll"
    Information: Installed the "C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll" assembly into the Global Assembly Cache. (force=True)
    Information: Deploy operation succeeded.
    Information: Deploy server="BDDBESBWMV01" database="BizTalkMgmtDb" assembly="C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll"
    Saved schema "Microsoft.Samples.BizTalk.HelloWorld.POSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
    Saved schema "Microsoft.Samples.BizTalk.HelloWorld.InvoiceSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
    Saved map "Microsoft.Samples.BizTalk.HelloWorld.POToInvoice".
    Saved message type "Microsoft.Samples.BizTalk.HelloWorld.POMessageType".
    Saved message type "Microsoft.Samples.BizTalk.HelloWorld.InvoiceMessageType".
    Saved port type "Microsoft.Samples.BizTalk.HelloWorld.ReceivePOPortType".
    Saved port type "Microsoft.Samples.BizTalk.HelloWorld.SendInvoicePortType".
    Saved orchestration "Microsoft.Samples.BizTalk.HelloWorld.HelloSchedule".
    Saved schema "Microsoft.Samples.BizTalk.HelloWorld.POSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
    Saved schema "Microsoft.Samples.BizTalk.HelloWorld.InvoiceSchema, HelloWorld, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1a3b87e04e203d0f".
    Saved map "Microsoft.Samples.BizTalk.HelloWorld.POToInvoice".
    Saved message type "Microsoft.Samples.BizTalk.HelloWorld.POMessageType".
    Saved message type "Microsoft.Samples.BizTalk.HelloWorld.InvoiceMessageType".
    Saved port type "Microsoft.Samples.BizTalk.HelloWorld.ReceivePOPortType".
    Saved port type "Microsoft.Samples.BizTalk.HelloWorld.SendInvoicePortType".
    Saved orchestration "Microsoft.Samples.BizTalk.HelloWorld.HelloSchedule".
    Information: Installed the "C:\Users\dopdevbiztalkadmin1\AppData\Local\Temp\BT\PID9536\BizTalkAssembly\4b4a4387187988d2dc55c72b16113199\HelloWorld.dll" assembly into the Global Assembly Cache. (force=True)
    Information: Deploy operation succeeded.
    Information: Deployed the following 1 BizTalk assemblies:
    HelloWorld.dll
    EXEC : warning : If any of the assemblies were previously loaded by a Host Instance, it may be necessary to restart the Host Instance for changes to take effect. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
    Information: Commit the change requests...
    * Performing EndTypeChangeRequest for resource type "System.BizTalk:BizTalkAssembly".
    Command succeeded with 0 errors, 0 warnings.
    DeploySharedAssemblies:
    Deploying additional assemblies to GAC...
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\gacutil.exe" /f /i "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileReader.dll"
    Microsoft (R) .NET Global Assembly Cache Utility. Version 4.0.30319.1
    Copyright (c) Microsoft Corporation. All rights reserved.
    Assembly successfully added to the cache
    Finished deploying additional assemblies to GAC.
    ImportBindings:
    Copying file from "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" to "C:\BTDF\Walkthrough1\HelloWorld.Deployment\HelloWorld_PortBindings.xml".
    BTSTask.exe AddResource -Type:BizTalkBinding -Overwrite -Source:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\HelloWorld_PortBindings.xml" -ApplicationName:"HelloWorld"
    Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
    Copyright (c) 2013 Microsoft Corporation. All rights reserved.
    Information: Adding resource (-Type="System.BizTalk:BizTalkBinding" -Luid="HelloWorld_PortBindings.xml") to application "HelloWorld"...
    Information: Validating resources (count=1)...
    * Validating resource (-Type="System.BizTalk:BizTalkBinding" -Luid="HelloWorld_PortBindings.xml")...
    Information: Performing change requests...
    Information: Calling BeginTypeChangeRequest for all selected resource types...
    PerformingBeginChangeRequest
    Updating resource (-Type="System.BizTalk:BizTalkBinding" -Luid="HelloWorld_PortBindings.xml") in store.
    Information: * Performing change request on type "System.BizTalk:BizTalkBinding" (count=1)...
    Information: Commit the change requests...
    * Performing EndTypeChangeRequest for resource type "System.BizTalk:BizTalkBinding".
    Command succeeded with 0 errors, 0 warnings.
    Deleting file "C:\BTDF\Walkthrough1\HelloWorld.Deployment\HelloWorld_PortBindings.xml".
    BTSTask.exe ImportBindings -Source:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" -ApplicationName:"HelloWorld"
    Microsoft (R) BizTalk Application Deployment Utility Version 3.10.229.0
    Copyright (c) 2013 Microsoft Corporation. All rights reserved.
    Information: Importing bindings "C:\BTDF\Walkthrough1\HelloWorld.Deployment\PortBindings.xml" into application "HelloWorld" in BizTalk configuration database (server="BDDBESBWMV01", database="BizTalkMgmtDb")...
    Information: Imported application "HelloWorld" bindings.
    Command succeeded with 0 errors, 0 warnings.
    DeploySSO:
    "C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileImport.exe" "HelloWorld" /settingsFile:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml" /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"
    Error persisting to SSO:
    System.Runtime.InteropServices.COMException (0xC0002A18): The format of the account name is not valid. Domain accounts must include the domain name. Local accounts must not include a domain or computer name.
    at Microsoft.BizTalk.SSOClient.Interop.ISSOAdmin.CreateApplication(String applicationName, String description, String contactInfo, String userGroupName, String adminGroupName, Int32 flags, Int32 numFields)
    at SSOSettingsFileManager.SSOHelper.CreateApp(String appName, String userGroup, String adminGroup)
    at SSOSettingsFileManager.SettingsFileImport.SaveSettingsToSSO(String affiliateAppName, String inSettings, String userGroupName, String adminGroupName)
    at SSOSettingsFileManager.SettingsFileImport.Main(String[] args)
    C:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1701,5): error MSB3073: The command ""C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileImport.exe" "HelloWorld" /settingsFile:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml" /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"" exited with code -1. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
    Done Building Project "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" (Deploy target(s)) -- FAILED.
    Build FAILED.
    "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" (Deploy target) (1) ->
    (DeploySchemas target) ->
    EXEC : warning : If any of the assemblies were previously loaded by a Host Instance, it may be necessary to restart the Host Instance for changes to take effect. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
    "C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj" (Deploy target) (1) ->
    (DeploySSO target) ->
    C:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1701,5): error MSB3073: The command ""C:\Program Files (x86)\Deployment Framework for BizTalk 5.5\Framework\DeployTools\SSOSettingsFileImport.exe" "HelloWorld" /settingsFile:"C:\BTDF\Walkthrough1\HelloWorld.Deployment\EnvironmentSettings\Exported_LocalSettings.xml" /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"" exited with code -1. [C:\BTDF\Walkthrough1\HelloWorld.Deployment\Deployment.btdfproj]
    1 Warning(s)
    1 Error(s)
    Time Elapsed 00:00:54.94

    Hi Pratibha,
    Thank you for posting in MSND forum.
    Since
    this forum is to discuss: Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.
    Based
    on your issue, since it is related to the Deployment Framework for Biztalk (BTDF), so I suggest you could consult this issue directly to this Deployment Framework for Biztalk (BTDF) website:
    https://biztalkdeployment.codeplex.com/discussions , you will get better support.
    Thanks for your understanding.
    Best Regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Error in Communicating with DCR Server LMS 4.0

    I´m receiving this error when I try do add a device in isolated form or by discovery:
    Error in communicating with DCR Server.
    DCR Server may be down. Please start the DCR Server and then refresh the page.
    I am using windows 2008 standard server RC1 SP1, and CiscoWorks LMS 4.0.
    I had applied all of patches includes.
    The DCRserver is running. ( I did restart it)

    You're using Windows 2008 RC1 (a release candidate version)?  LMS is only supported on the final shipping version of Windows 2008, and not yet on R2.
    If you're running on the final version of 2008 server, post the output of the pdshow command as well as the dcr.log, DCRServer.log, NMSROOT/MDC/tomcat/logs/stdout.log and stderr.log.

  • Error in communicating with DCR Server. in LMS 3.1

    I am receiving this error when I try to ad device: Error in communicating with DCR Server.
    DCR Server may be down. Please start the DCR Server and then refresh the page.
    The DCRserver is running. ( I did restart it)
    I am using Windows version of LMS 3.1
    CiscoWorks Common Services 3.2.0 Licensed Not applicable
    Campus Manager 5.1.4 Purchased 300
    CiscoView 6.1.8 Licensed Not applicable
    CiscoWorks Assistant 1.1.0 Licensed Not applicable
    Device Fault Manager 3.1.3 Purchased 300
    Internetwork Performance Monitor 4.1.0 Purchased 300
    Integration Utility 1.8.0 Licensed Not applicable
    LMS Portal 1.1.0 Licensed Not applicable
    Resource Manager Essentials 4.2.0 Purchased 300
    Health and Utilization Monitor 1.1.0 Evaluation(Expired) 100

    Hi,
    This issue most likely is related to a communication problem with the database or a corruption as we can see from the logs :
    2010/11/21 19:44:41 main ani ERROR POStore: Failed resolving object because: java.lang.NullPointerException
    2010/11/21 19:44:41 main ani ERROR AniMain: java.lang.NullPointerException
    ANI Server failed to load from the database.
    Please stop and restart the system. You may need to re-initialize the database.
    If this does not work, please contact technical support.
    The next step is to re-initialize the Campus Manager database. This procedure will delete all the records and maps that you have in Campus Manager, you would need to run a new Campus Data Collection and User Tracking Acquisition to have clean and fresh database information.
    If that ok with you, you can try the below steps to re-initialize the Campus database. By doing this, it will not effect any other database of LMS will clean Campus Manager database.
    +) Stop the daemon manager:
    net stop crmdmgtd
    +) cd CSCOpx\bin\
    +) Type the following command (case sensitive):
    perl dbRestoreOrig.pl dsn=ani dmprefix=ANI
    +) Start the daemon manager:
    net start crmdmgtd
    Now, wait another 15 minutes and wait for dmgtd.lock file to release from location CSCOpx\objects\dmgtd\ready.
    Now check the status of ANIServer with command :- pdshow ANIServer ( case sensitive)
    it should have the status Busy with Flag set.
    Thanks,
    Gaganjeet

  • "Error intitializing communications with the LMS" in Captivate 8.0.1

    After updating to 8.0.1.242 and publishing projects as SCORM 1.2 in html5, I get the error message "Error intitializing communications with the LMS" both in the LMS we use and in ScormCloud. This happens in IE 10.0.9200. I am pretty sure we have not had this message before. I had a colleague generate the same project for me using 8.00.145 and I get no error message. Any input on what causes this would be appreciated.

    Can you share your project on id: [email protected]
    we will try to investigate this at our end. Also please send the exact steps how you are able to get this error.
    Regards
    Shriyansh
    Adobe Engineering Team

  • [Error during Export] R3load exited with return code 11

    Hi guys,
    While performing and Unicode Migration, during Export Phase, Migration Monitor returned the following error while exporting a package
    ERROR: 2014-06-01 10:57:44 com.sap.inst.migmon.LoadTask run
    Unloading of 'REGUC' export package is interrupted with R3load error.
    Process '/usr/sap/ECP/DVEBMGS00/exe/R3load -e REGUC.cmd -datacodepage 4102 -l REGUC.log -stop_on_error' exited with return code 11.
    For mode details see 'REGUC.log' file.
    Standard error output:
    sapparam: sapargv(argc, argv) has not been called!
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    REGUC.log details:
    (As you see, it does not provide reasons of this error, all messages are informative and alike all other Packages logs)
    /usr/sap/ECP/DVEBMGS00/exe/R3load: START OF LOG: 20140601105052
    /usr/sap/ECP/DVEBMGS00/exe/R3load: sccsid @(#) $Id: //bas/740_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
    /usr/sap/ECP/DVEBMGS00/exe/R3load: version R7.40/V1.8
    Compiled Jul 23 2013 21:30:53
    /usr/sap/ECP/DVEBMGS00/exe/R3load -e REGUC.cmd -datacodepage 4102 -l REGUC.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): US7ASCII
    (EXP) INFO: check NameTab widths: Ok.
    (DB) INFO: Export without hintfile
    (RSCP) INFO: UMGCOMCHAR read check, OK.
    (RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
    (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    (RSCP) INFO: UMGSETTINGS nametab creation: ok.
    (RSCP) INFO: Global fallback code page = 1160
    (RSCP) INFO: Common character set is  not  7-bit-ASCII
    (RSCP) INFO: Collision resolution method is 'fine'
    (RSCP) INFO: R3trans code pages = Normal
    (RSCP) INFO: EXPORT TO ... code pages = Normal
    (RSCP) INFO: Check for invalid language keys: activated
    (RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
    (RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
    (RSCP) INFO: I18N_NAMETAB_ALT_ALLOW  = 10000
    (RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
    (RSCP) INFO: I18N_NAMETAB_OLD_ALLOW  = 0
    (RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
    (RSCP) INFO: init SUMG interface (3#$Revision: #1 $); package name: "REGUC".
    (RSCP) INFO: "REGUC001.xml" created.
    (GSI) INFO: dbname   = "ECP20030615080638
    (GSI) INFO: vname    = "ORACLE "
    (GSI) INFO: hostname = "ecp "
    (GSI) INFO: sysname  = "SunOS"
    (GSI) INFO: nodename = "ecp"
    (GSI) INFO: release  = "5.10"
    (GSI) INFO: version  = "Generic_142900-13"
    (GSI) INFO: machine  = "sun4u"
    Tried to find what does R3load Return Code 11 means, but I couldnt find further information on this.
    Any hint of what is causing this error?
    (Please disregard any Filesystem issues since all of them have available space)
    Best!

    After using latest R3load patch, it provides furher information on the log file.
    -------------------- Start of patch information ------------------------
    patchinfo (patches.h): (0.070) R3ldctl: fix CDS views creation in upgrade export mode (note 2
    017805)
    DBSL patchinfo (patches.h): (0.022) Smaller corrections in release 7.40 (th, dp, vmc, dpmon)
    (note 1821404)
    --------------------- End of patch information -------------------------
    process id 27326
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): US7ASCII
    (EXP) INFO: check NameTab widths: Ok.
    (DB) INFO: Export without hintfile
    (RSCP) INFO: UMGCOMCHAR read check, OK.
    (RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
    (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    (RSCP) INFO: UMGSETTINGS nametab creation: ok.
    (RSCP) INFO: Global fallback code page = 1160
    (RSCP) INFO: Common character set is  not  7-bit-ASCII
    (RSCP) INFO: Collision resolution method is 'fine'
    (RSCP) INFO: R3trans code pages = Normal
    (RSCP) INFO: EXPORT TO ... code pages = Normal
    (RSCP) INFO: Check for invalid language keys: activated
    (RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
    (RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
    (RSCP) INFO: I18N_NAMETAB_ALT_ALLOW  = 10000
    (RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
    (RSCP) INFO: I18N_NAMETAB_OLD_ALLOW  = 0
    (RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
    (RSCP) INFO: init SUMG interface (3#$Revision: #1 $); package name: "REGUC".
    (RSCP) INFO: "REGUC003.xml" created.
    (GSI) INFO: dbname   = "ECP20030615080638
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "ecp                                                             "
    (GSI) INFO: sysname  = "SunOS"
    (GSI) INFO: nodename = "ecp"
    (GSI) INFO: release  = "5.10"
    (GSI) INFO: version  = "Generic_142900-13"
    (GSI) INFO: machine  = "sun4u"
    (GSI) INFO: instno   = "6120023288"
    (RTF) ########## WARNING ###########
            Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
    (RDI) WARNING: /respaldo/ECP_Export/ABAP/DATA/REGUC.STR: cannot find version token "ver:" at line 1
    (RDI) WARNING: /respaldo/ECP_Export/ABAP/DATA/REGUC.STR: unknown file format, assuming version 2
    (EXP) INFO: table REGUC will be exported with sorting (task modifier)
    ------------------ C-STACK ----------------------
    [0] t_splay ( 0x1020df850, 0xb3, 0x4386, 0x100a02078, 0x0, 0x1020df870 ), at 0xffffffff7b9629
    94
    [1] t_delete ( 0x1020df850, 0x4348, 0x1d9870, 0x1000d0408, 0xffffffff7bb3c000, 0x0 ), at 0xff
    ffffff7b9627e4
    [2] realfree ( 0x101ee7590, 0x1f82b1, 0x1d9cd0, 0x1f82b0, 0xffffffff7bb3c000, 0x101ee7590 ),
    at 0xffffffff7b9623b0
    [3] _malloc_unlocked ( 0x7d40, 0x200000, 0x101edf840, 0x0, 0x101ee7580, 0x0 ), at 0xffffffff7
    b961eb4
    [4] malloc ( 0x7d39, 0x2388, 0x1da428, 0x10038fe84, 0xffffffff7bb3c000, 0x2000 ), at 0xffffff
    ff7b961c28
    [5] rstg_get ( 0x2, 0x0, 0x2, 0x7d10, 0x0, 0x10077d8c0 ), at 0x10038ff4c
    [6] c3_uc_new_cache ( 0x100a02078, 0x284db0, 0x284c00, 0x10077d8c0, 0x100a02108, 0xb3 ), at 0
    x1000d1ce8
    [7] c3_uc_seek_cache ( 0xb3, 0xff79, 0xffffffff7ffcae3e, 0x100a02078, 0x10189fa48, 0x10077d8c
    0 ), at 0x1000d188c
    [8] c3_uc_new_tabcache ( 0x0, 0xb3, 0x4386, 0x100a02078, 0xb3, 0x10077d8c0 ), at 0x1000d13fc
    [9] c3_uc_insert_record_in_cache ( 0xffffffff7ffcb04e, 0x10189fa48, 0x100a02078, 0x100a024c8,
    0xb3, 0x1058c8f84 ), at 0x1000d0408
    [10] c3_uc_insert ( 0x0, 0x100a02078, 0x0, 0x0, 0x10077d8c0, 0xffffffff7ffcb04e ), at 0x1000c
    f944
    [11] c3_uc_convert_table_entry ( 0x1015c61f8, 0x0, 0x100a02078, 0x0, 0x10189f408, 0x31a000 ),
    at 0x1000ce314
    [12] c3_uc_convert_logic_table ( 0x1015c61f8, 0x100a02078, 0x0, 0x4a, 0x100638dc0, 0x10077d8c
    0 ), at 0x1000cdb18
    [13] c3_uc_convert_cluster_data ( 0x100a02078, 0xffffffff7ffcbc50, 0x1015c6428, 0x1015c61f8,
    0x10077d8c0, 0x0 ), at 0x1000cd10c
    [14] c3_uc_convert_cluster_item ( 0xffffffff7ffcbc78, 0xffffffff7ffcbc50, 0x100954770, 0x1038
    6f6e0, 0xffffffff7ffcbb8c, 0x100a02812 ), at 0x1000be1d4
    [15] process_task ( 0xffffffff7ffcbc78, 0xffffffff7ffcbc50, 0x100954770, 0x100a02810, 0x10063
    32e0, 0x10077d8c0 ), at 0x1000b2f58
    [16] CnvCluster ( 0x1014642d0, 0x100954670, 0x100aa9610, 0x2849b8, 0x284800, 0x6cb978 ), at 0
    x1000b1f8c
    [17] cnv_clust2 ( 0x100aa9580, 0xffffffff7ffcc258, 0x100954770, 0xfc0, 0x107d00, 0x100954670
    ), at 0x100062714
    [18] cnv_cp ( 0x100aa9580, 0xffffffff7ffcc258, 0x100aa95e0, 0x0, 0x10077d8c0, 0x1d6c00 ), at
    0x100064644
    [19] process_buffer ( 0x100aa9580, 0xffffffff7ffcc258, 0xfff00, 0x100a97bd0, 0x10, 0x100aa95b
    0 ), at 0x10007162c
    [20] execute_table_unload ( 0xffffffff7ffed610, 0xffffffff7ffdc4b0, 0x0, 0x100aa9580, 0xfffff
    fff7ffcc258, 0x10077d8c0 ), at 0x10006c488
    [21] export_table_task ( 0xffffffff7ffed610, 0x0, 0xffffffff7ffdc368, 0xffffffff7ffcc330, 0xf
    fffffff7ffeedb8, 0xffffffff7ffeec60 ), at 0x10006c934
    [22] db_unload ( 0x100a97b0d, 0xffffffff7ffed610, 0x0, 0x10077d8c0, 0xffffffff7ffeec60, 0xfff
    fffff7bb47540 ), at 0x10006d148
    [23] main_r3ldmain ( 0x72ec00, 0xffffffff7ffff448, 0xffffffff7ffff228, 0xffffffff7bb47540, 0x
    1005fc290, 0x0 ), at 0x1000514e0

Maybe you are looking for