Unexpected Application Builder log file

I am using Labview 5.1.1 application builder. When I compile up my
application, I find a log file in the same directory as the exe just build
(same name as exe but with a .log extension).
When I open this up it contains >>
Microsoft (R) Type Library Generator Version 2.20.4048
Copyright (c) Microsoft Corp. 1993-1995. All rights reserved.
app.odl (23) : fatal error M0001: Syntax error near line 23 column 15:
expected: {
The compiled exe seems to run, but should I trust it?
Anyone any thoughts on this, or an explanation as to what might be wrong?
regards,
Alistair Simpson

Most of the logs rotation for the different componets can be set in EM console but if you just want to do it with a cron or script here is what I have used in the past. Edit it to your needs.
#!/bin/sh
ORACLE_HOME=/home/oracle10FRS
apache_logs=$ORACLE_HOME/Apache/Apache/logs
webcache_logs=$ORACLE_HOME/webcache/logs
sysman_logs=$ORACLE_HOME/sysman/log
j2ee_logs=$ORACLE_HOME/j2ee/OC4J_BI_Forms/log/OC4J_BI_Forms_default_island_1
also_j2ee=$ORACLE_HOME/j2ee/home/log/home_default_island_1
max_size=1500000000
for file in `ls $apache_logs/*_log`
do
     size=`ls -l $file | awk '{print $5}'`
     echo "File $file is $size bytes"
     if [ "$size" -ge "$max_size" ]
     then
          echo "That's too big. Truncating"
          >$file
     fi
done
for wfile in `ls $webcache_logs/*_log`
do
     size=`ls -l $wfile | awk '{print $5}'`
     echo "File $wfile is $size bytes"
     if [ "$size" -ge "$max_size" ]
     then
          echo "That's too big. Truncating"
          >$wfile
     fi
done
for sfile in `ls $sysman_logs/*log`
do
     size=`ls -l $sfile | awk '{print $5}'`
     echo "File $sfile is $size bytes"
     if [ "$size" -ge "$max_size" ]
     then
          echo "That's too big. Truncating"
          >$sfile
     fi
done
for jfile in `ls $j2ee_logs/*.log`
do
     size=`ls -l $jfile | awk '{print $5}'`
     echo "File $jfile is $size bytes"
     if [ "$size" -ge "$max_size" ]
     then
          echo "That's too big. Truncating"
          >$jfile
     fi
done
for j2file in `ls $also_j2ee/*.log`
do
     size=`ls -l $j2file | awk '{print $5}'`
     echo "File $j2file is $size bytes"
     if [ "$size" -ge "$max_size" ]
     then
          echo "That's too big. Truncating"
          >$j2file
     fi
done

Similar Messages

  • How to have a live feed from application server log file (realtime viewr )

    how to have a live feed from application server log file (realtime viewr for apps log files)
    hi , thank you for reading my post.
    is there any way to have a live feed of Application server log ?
    for example is there any application that can watch the log file and show the changes as new log items come in ?
    can some one with more experience help ?

    Your question would be more suited to the Developer Forums
    http://devforums.apple.com
    but anyway...
    My goal is to develop a web application that is able to run on iPhone too, to capture the audio and video content from its camera and mic.
    Web Apps running in Safari don't have access to the camera or mic hardware.
    Or I should built a native application distributed through Apple store?
    That is your only option, although such a system already exists:
    http://itunes.apple.com/us/app/ustream-live-broadcaster/id319362690?mt=8

  • Application builder missing files

    Hi all,
    I'm new to LabView and I'm trying to deploy an application as an executable. I'm running LabView 2009 on Win XP Pro. I have the application  builder and ran the application builder tutorial. The tutorial worked fine, but doing the same steps on my project that calls sub-VIs from several different libraries didn't work. I'm not trying to build an installer yet, just a stand alone executable running on a machine with the LabView run time framework already installed. I'm not calling anything by reference, all sub-VIs are called explicitly.
    The VI I'm trying to deploy works fine running in LabView. Application builder successfully generates an executable. When the executable is run, it pops up a dialog looking for a bunch of sub-VIs. I attached a copy of the executable prompting me for a sub-VI contained in vi.lib
    First, is there a user's manual or something like that for Application Builder? LabView Help describes how to create a stand alone executable but doesn't describe all the settings in detail. I probably just have one of the settings wrong.
    Any other thoughts or suggestions on what to try next?
    Thanks in advance for your help. 
    Solved!
    Go to Solution.
    Attachments:
    app builder error.JPG ‏21 KB

    LV2011SP1
    I have been developing in the directory
    C:\Program Files\National Instruments\LabVIEW 2011\user.lib
    The source code is located in a subfolder in the "user.lib" folder
    The builds go into the destination subfolder "user.lib\builds"
    The executable built returns an error when it is run. It can't find one of the subvis.
    The subvi in question is listed under the dependencies for the main vi in the project.
    I copied the devlopmentto a new location, namely
    C:\Users\Me\Documents\LVcode\builderErrorTestFolder
    The executable built within this new project ran without error on the development machine, but the executable built with the installer in this project will not run on a non-development machine. In the case of the executable installed on a non-development machine, the error is a "can't find vis" error, but it is limited to NI_AALPROLvlib files and NI_AALBaseLvlib files
    What could be the problem?
    Attachments:
    cantFindFile.jpg ‏161 KB
    willNotFindNI_AALPROLvlibPwrSpectrm.png ‏150 KB

  • Java application - build JAR file & include JCO library

    Hello everyone,
    I have a problem with my Java application that <i>connects to SAP system using JCO </i>library <b>(sapjco.jar)</b>.
    I would like to create a JAR file from my Java application but when I run the JAR file that I created I get an error that <b>NoClassDefinitionFoundError com/sap/mw/jco/JCO at [...]</b>
    That means that the JCO and associated DLL files <b>(sapjco.jar, librfc32.dll and sapjcorfc.dll)</b> were <u>not</u> included/packed in my JAR file.
    <b>-- How can I include the JCO lib in JAR file?
    -- If there is a problem with the DLL files, how can I include the JCO lib externally (dynamicly read the JCO whenever my JAR in run)?</b>
    I am using Eclipse 3.2 and Export to JAR option when I click right button on Project.
    THANKS IN ADVANCE FOR HELP!!!

    Hi,
    The problem is that you don't have defined the libraries in the Manifest file of your jar-file. So the jar doesn't know what to use at runtime.
    Add following entry to the MANIFEST.MF file:
    Class-Path:/<lib_folder>/<lib1_name>.jar; /<lib_folder>/<lib2_name>.jar and so on.
    Regards,
    Daniel

  • Mac OSX quits unexpectedly when opening Logis Files!?

    I have this issue where my computer quits all of a sudden where I have to turn it off and re-start. After it reboots the message " The computer was restarted after Mac OSX quit unexpectedly" comes on.
    Does anybody else have this problem. It doesn't happen very often but still I want to get this fixed. Strangely, it happens when I try to open certain Logic Projects. I can open some of them but some of them crash.

    As a Test:
    Hold down the option (or alt) key and launch iPhoto. From the resulting menu select 'Create Library'
    Import a few pics into this new, blank library. Is the Problem repeated there?
    Post back with the result.

  • App Builder not creating log file (CDK.EnableLog=True)

    Hi All,
    I am busy trying to get a small to medium size project to build in LV 8.6.1.
    During the build I get all kinds of weird errors (1503, 1357), even with a trivial app that uses a typedef that has all the classes bundled together.
    As mentioned, the app uses LVOOP, and also lots of similarly named VIs (in different library namespaces though), and I am 99% sure LV is struggling to resolve the same VI name issue.
    In order to debug the build process I have tried inserting the CDK.EnableLog=True key into LabVIEW.ini, but no log file is produced during any of my builds (good or bad!). I have tried using TRUE, true, True for the key but none of these seem to work, when I look in %TEMP% there are files related to the build name_log.txt, but they contain only very basic information like the name and OS etc.
    Any ideas how to get the build log file to appear???
    nrp
    CLA

    Hi,
    The build log process is shown here: http://digital.ni.com/public.nsf/allkb/2E19F4E72C29CF5C862570D2004FC604?OpenDocument
    However this only shows detailed information when creating an installer, is this an executable that you are attempting to distribute when the errors mentioned appear or do the errors occur during the creation of just the executable? (This could be why you get a log with very little information)
    Kind Regards, 
    Applications Engineer

  • Redirect DBMS_OUTPUT to calling application and to log file

    Hi,
    I have a procedure to insert a set of records into a table using Merge statement and capture the inserted record count.
    Currently i display the record count using DBMS_OUTPUT in Oracle SQL Developer tool using DBMS_OUTPUT.ENABLE.
    How do i redirect this output to both calling application and Log file on Unix server.
    I have more DBMS_OUTPUT statements in Exception handling to handle failed inserts. How do i redirect these statements to Calling Application and Log file on Unix.
    Can we send any email to a group from PL/SQL if at all program fails and Exception handle is triggered OR if the program complete successfully.
    I appreciate your responses.

    user10405899 wrote:
    Hi,
    I have a procedure to insert a set of records into a table using Merge statement and capture the inserted record count.
    Currently i display the record count using DBMS_OUTPUT in Oracle SQL Developer tool using DBMS_OUTPUT.ENABLE.
    How do i redirect this output to both calling application and Log file on Unix server.
    I have more DBMS_OUTPUT statements in Exception handling to handle failed inserts. How do i redirect these statements to Calling Application and Log file on Unix.
    Can we send any email to a group from PL/SQL if at all program fails and Exception handle is triggered OR if the program complete successfully.
    I appreciate your responses.DBMS_OUTPUT is not the correct tool to be using for outputting information. It writes data to a buffer on the server, and then it's up to the client tool to read the data out of that buffer using the DBMS_OUTPUT.GET_LINE call.
    You could try implementing something like that in your own application if you wanted, but in truth, if you're wanting to capture some trace of what's happening in your application then you are better logging those things to a table using an autonomous transaction procedure, and then have whataver application you want just query that table.

  • Re: identifying server log file when runningdistributed

    Hi John, I can give you some TOOL code which will get the process
    id, but I do have to stray outside of Framework :-). The following
    code uses classes from the SystemMonitor project which was
    introduced in release 2 of Forte (this code won't work on R1):
    partAgent : SystemAgent;
    pidInst : ConfigValueInst;
    pid : TextData;
    partAgent = SystemAgent(task.Part.Agent);
    pidInst = ConfigValueInst(partAgent.FindInstrument('ProcessId');
    pid = TextData(pidInst.GetData);
    The result is that the variable pid contains the process id in string form.
    This could be converted to numeric form if needed.
    If what you're really after is the partition's log file name, then the following
    code will do the trick (it takes into account the differences in how the log
    files are named for interpreted vs. compiled partitions):
    partAgent : SystemAgent;
    logFileInst : ConfigValueInst;
    logFileName : TextData;
    -- Get our agent and try to get the log file inst
    partAgent = SystemAgent(task.Part.Agent);
    logFileInst = ConfigValueInst(partAgent.FindInstrument('LogFile');
    -- Interpreted partition don't have their own log file, so check
    if (logFileInst = NIL) then
    pidInst : ConfigValueInst;
    pid : TextData;
    -- We must be an interpreted partition get our pid
    pidInst = ConfigValueInst(partAgent.FindInstrument('ProcessId');
    pid = TextData(pidInst.GetData);
    -- Build log file name
    logFileName = 'forte_ex_';
    logFileName.Concat(pid);
    else
    -- Get the name of the log file from the instrument
    logFileName = TextData(logFileInst.GetData);
    end;
    The available agents and their instruments and commands are documented
    in the manual "SystemMonitor Project". I'm at home now, so I don't have
    the page numbers. Some additional agents (which were added after this
    manual went to press) can be found in Tech Note #10475. Also, econsole
    and escript can be handy since any instrument you can see in these tools
    can be accessed from TOOL code. Hope this is of some use.
    Sean
    At 05:24 PM 7/30/96 -0700, John L. Jamison wrote:
    >
    I'd like to solicit some ideas from you folks. As many of you are probably
    aware, when running in distributed mode, log output for server partitions is
    written out to log files on the server partition. However it is sometimes a
    trick trying to identify the process which is running your individual
    partitions, and
    thus knowing which log file to read.
    At one client, we added a 3gl call-out to obtain the process id and return it
    to the client. However this is not a good option at a new client which uses
    Sequent (3gl wrappering difficult in statically linked environments such as
    sequent). I am also aware that Econsole allows you to browse active
    partitions and display log files, but you still have to know which active
    partitions to watch.
    I have not yet seen a way to programmatically obtain the process ID for a
    partition within TOOL and using FrameWork classes.
    What kinds of strategies are folks employing out there?
    Thanks in advance,
    -John
    John Jamison
    Sage Solutions, Inc.
    353 Sacramento Street, Suite 1360
    San Francisco, CA 94111
    415 392 7243 x 508
    [email protected]

    Hi John,
    I think that Sean Fits answered your question about TOOL code to get the PID
    number. I just want to complement on the loging strategy.
    There is one log file for every active partition of an application. I think
    it is useful in some cases that a distributed application gets a centralized
    log file to trace the exact sequential flow of processing among all the
    partitions. This is useful during the initial debuging and tuning. In fact
    something similar to the UNIX syslog file.
    For doing so it is easy to implement a custom central log Mgr in one
    partition and to have all partitions use it when needed (it doesn't prevent
    to continue using the standard LogMgr in addition). This central LogMgr
    automatically adds the date&time plus the node name, partition name, ... to
    the log messages it receives.
    The flags which apply are those of the partition where the central Log Mgr is.
    Because of potential concurency requests from the several partitions
    accessing the central Log Mgr, it is not possible to support the "Put" and
    PutHex" methods. Only complete lines can be logged (Putline and PutHexLine).
    Attached is the TOOL code of my TraceService plan that implements it.
    Remark : the "Phr" in the names relate to the name of the application we
    have here under development.
    To use the central Log Mgr, a partition must create an object of class
    PartitionLog, and then log messages must be sent to it the way you send them
    to the standard LogMgr; it will manage to send them to the central Log Mgr.
    At 17:24 30/07/96 -0700, John Jamison wrote:
    >
    I'd like to solicit some ideas from you folks. As many of you are probably
    aware, when running in distributed mode, log output for server partitions is
    written out to log files on the server partition. However it is sometimes a
    trick trying to identify the process which is running your individual
    partitions, and
    thus knowing which log file to read.
    At one client, we added a 3gl call-out to obtain the process id and return it
    to the client. However this is not a good option at a new client which uses
    Sequent (3gl wrappering difficult in statically linked environments such as
    sequent). I am also aware that Econsole allows you to browse active
    partitions and display log files, but you still have to know which active
    partitions to watch.
    I have not yet seen a way to programmatically obtain the process ID for a
    partition within TOOL and using FrameWork classes.
    What kinds of strategies are folks employing out there?

  • Display string from a log file on a Dashboard?

    Hello everyone,
    I need a little guidance on how to solve this problem in SCOM 2012 R2.
    I need SCOM to do this:
    Read a log file on a specific application server (say its hostname is server21)
    Look for the text: Total number of users: 15
    Display the text “Users on Server21 =
     15” on a SCOM dashboard (or something to that effect)
    Sounds simple enough? Well, I am stumped :-(
    I have read and followed tutorials on internet, telling me how to create a rule and alerts. However I don’t want alerts. I want this data to be simply shown on a dashboard.
    How can I do that?
    PS: I hear that I may have to create my own management pack with only server21 in it. Is that right?
    -Rajeev rajdude.com

    Thanks for the tip. The powershell grid widget is pretty powerful. However it will take me quite some time and effort to write a PS script which can extract the exact info I need from that application's log file. I was hoping SCOM's own log parsing
    capabilities would do it.
    By the way, yes, we can create a MP and have only one server in it. We can use the (free) 
    MPAuthor to make a MP with only one server in it. Here is a video showing how to do it...
    http://www.silect.com/static/mpauthor/MP_Author_Creating_a_New_Single_Server_Application_MP.mp4
    I tried doing what I want using MPAuthor, but it again boiled down to me writing a PS script which can extract the exact info I need
    from that application's log file.
    -Rajeev rajdude.com

  • Managing and configuring log files for Oracle 9ias

    Hi all,
    I'm wondering where I can find documentation on managing and configuring log files like:
    ORACLE_HOME/admin/ sid/*dump/* ORACLE_HOME/assistants/opca/install.log ORACLE_HOME/webcache/logs/*
    ORACLE_HOME/dcm/logs/*
    ORACLE_HOME/ldap/log/*
    ORACLE_HOME/opmn/logs/*
    ORACLE_HOME/sysman/log/*
    ORACLE_HOME/j2ee/ OC4J_instance/log/*/* ORACLE_HOME/config/schemaload.log ORACLE_HOME/config/useinfratool.log
    because I didn't find anything in document like:
    Oracle9 i Application Server
    Administrator�s Guide
    Release 2 (9.0.2)
    May 2002
    Part No. A92171-02
    So, if anyone has any idea...
    Thanks in advance

    Does anyone know how or if it is possible to send the stdout and/or stderr to the log4j type of logging? I already capture the stdout and stderr to the flat file. But I would like to timestamp every line to compare and diagnose problems with each application that encounters problems. Each web app is using log4j to their own application log4j log file. When they encounter errors or resource draining problems, I would like to see the container logs and see what was occuring inside the container at around that same time.
    Any ideas?

  • DB2, Log File has reached its saturation point" DIA8309C Log file was full,

    Hello Experts,
    I have successfully installed a ECC 6.0 System-ABAP + JAVA (DB2 v9.5 windows server 2008-x64 bit).
    Kernel: 700 , Patch: 185 ; SP level : rel 700 , level 17.
    However now i suddenly cannot connect to database and SAP is down.
    C:\Users\dsqadm.DUCATI>r3trans -d
    This is r3trans version 6.14 (release 700 - 16.10.08 - 16:26:00).
    unicode enabled version
    2EETW169 no connect possible: "DBMS = DB6                              --- DB2DB
    DFT = 'DSQ'"
    r3trans finished (0012).
    db2diag.log:-
    ADM1823E  The active log is full and is held by application handle "51886".  Terminate this application by COMMIT, ROLLBACK or FORCE APPLICATION.
    "Log File has reached its saturation point" DIA8309C Log file was full.
    "Backup pending.  Database has been made recoverable.  Backup now required."  DIA8168C Backup pending for database .
    Also, regarding DB2 licensing,i have a query:
    db2licm -l gives the following:
    C:\Users\db2dsq.DUCATI>db2licm -l
    Product name:                     "DB2 Enterprise Server Edition"
    License type:                     "CPU Option"
    Expiry date:                      "Permanent"
    Product identifier:               "db2ese"
    Version information:              "9.5"
    Enforcement policy:               "Soft Stop"
    Features:
    DB2 Database Partitioning:        "Licensed"
    DB2 Performance Optimization ESE: "Licensed"
    DB2 Storage Optimization:         "Licensed"
    DB2 Advanced Access Control:      "Not licensed"
    DB2 Geodetic Data Management:     "Not licensed"
    IBM Homogeneous Replication ESE:  "Not licensed"
    Product name:                     "DB2 Connect Server"
    License type:                     "Trial"
    Expiry date:                      "10/19/2009"
    Product identifier:               "db2consv"
    Version information:              "9.5"
    I have applied both sap and DB2 license. Is everything ok regarding licensing of DB v9.5 for using with SAP?
    I am new to DB2 database and looking for expert guidance regarding the above mentioned issues.
    Thanks,
    Rakesh

    C:\Users\db2dsq.DUCATI>db2 get dbm cfg
              Database Manager Configuration
         Node type = Enterprise Server Edition with local and remote clients
    Database manager configuration release level            = 0x0c00
    Maximum total of files open               (MAXTOTFILOP) = 16000
    CPU speed (millisec/instruction)             (CPUSPEED) = 4,723442e-007
    Communications bandwidth (MB/sec)      (COMM_BANDWIDTH) = 1,000000e+002
    Max number of concurrently active databases     (NUMDB) = 8
    Federated Database System Support           (FEDERATED) = NO
    Transaction processor monitor name        (TP_MON_NAME) =
    Default charge-back account           (DFT_ACCOUNT_STR) =
    Default database monitor switches
       Buffer pool                         (DFT_MON_BUFPOOL) = ON
       Lock                                   (DFT_MON_LOCK) = ON
       Sort                                   (DFT_MON_SORT) = ON
       Statement                              (DFT_MON_STMT) = ON
       Table                                 (DFT_MON_TABLE) = ON
       Timestamp                         (DFT_MON_TIMESTAMP) = ON
       Unit of work                            (DFT_MON_UOW) = ON
    Monitor health of instance and databases   (HEALTH_MON) = OFF

  • Where to find the BUILD Log??

    Hi Friends,
    Could anyone pls let me know where can i find the BUILD Log file. My DC build is failed. I dont know where to find the Build Log for DCs.
    Thanks,
    Raghavendra Pothula

    Hi Raghavendra,
    just to add some info: Since activation triggers a build the build log really is the result of the activation, isn't it?
    There is one pitfall: If activation fails due to build errors you have to use this way (Or navigate to the request using the CBS WebUI and then check the activation results there). If you check the last build log for the DC (nagivating to the DC via CBS WebUI) you usually see the last succesfull build, i.e. a different build log.
    Regards,
    Marc

  • Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)

    Hi all,
    I have TFS2012 and run several projects.
    We encounterwed with such an error while using Build server.
    Overall Build Process
    Initial Property Values
    AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
    BinariesSubdirectory = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MSBuildArguments = 
    MSBuildPlatform = Auto
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TestResultsSubdirectory = 
    Verbosity = Diagnostic
    00:00
    Get the Build
    00:00
    Update Build Number
    Initial Property Values
    BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
    Final Property Values
    BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
    Result = Ephone_DIT_Deploy_20150424.1
    01:56
    Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
    Initial Property Values
    MaxExecutionTime = 00:00:00
    MaxWaitTime = 04:00:00
    ReservationSpec = Name=*, Tags=
    00:00
    Get the Build Directory
    Initial Property Values
    Result = d:\temp\217\CTI\Ephone_DIT_Deploy
    01:53
    If Not String.IsNullOrEmpty(ConfigurationFolderPath)
    Initial Property Values
    Condition = True
    01:53
    Run TfsBuild for Configuration Folder
    Initial Property Values
    BinariesSubdirectory = 
    BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
    CommandLineArguments = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MaxProcesses = 1
    NodeReuse = False
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TargetsNotLogged = 
    TestResultsSubdirectory = 
    ToolPath = 
    ToolPlatform = Auto
    Verbosity = Diagnostic
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp" 
    00:08
    Getting sources
    00:02
    Labeling sources
    00:19
    Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
    00:19
    Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
    00:19
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
    00:05
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:10
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:05
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    MSBuild Log File
    00:08
    Generating list of changesets
    00:20
    Built Skins\SkinEPhone.cs for default targets.
     Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
    Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
       at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
       at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
       at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
       at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
       at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
       at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
    00:03
    Creating work item
     Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
    Exception Stack Trace:    at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
       at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
       at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
    Final Property Values
    BinariesSubdirectory = 
    BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
    CommandLineArguments = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MaxProcesses = 1
    NodeReuse = False
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TargetsNotLogged = 
    TestResultsSubdirectory = 
    ToolPath = 
    ToolPlatform = Auto
    Verbosity = Diagnostic
    Final Property Values
    Condition = True
    Final Property Values
    MaxExecutionTime = 00:00:00
    MaxWaitTime = 04:00:00
    ReservationSpec = Name=*, Tags=
    Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
    Final Property Values
    AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
    BinariesSubdirectory = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MSBuildArguments = 
    MSBuildPlatform = Auto
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TestResultsSubdirectory = 
    Verbosity = Diagnostic
    Please have a look and guide where to find a problem
    Thanks ahead

    Hi Hooi,
    I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
    From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
    Best regards,

  • Can't open Flash Builder - "See the log file" error.

    I have been using Flash Builder 4.5 and for some reason it has stopped opening correctly - I get the following error then it just shuts down.... :
    "An error has occured. See the log file."
    and if i check the log file it refers to then i see the following text:
    !SESSION 2011-06-22 13:53:43.658 -----------------------------------------------
    eclipse.buildId=M20100909-0800
    java.version=1.6.0_16
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
    Command-line arguments:  -os win32 -ws win32 -arch x86
    !ENTRY org.eclipse.osgi 4 0 2011-06-22 13:53:59.598
    !MESSAGE Application error
    !STACK 1
    org.eclipse.swt.SWTError: No more handles
        at org.eclipse.swt.SWT.error(SWT.java:4109)
        at org.eclipse.swt.SWT.error(SWT.java:3998)
        at org.eclipse.swt.SWT.error(SWT.java:3969)
        at org.eclipse.swt.widgets.Widget.error(Widget.java:468)
        at org.eclipse.swt.widgets.Control.createHandle(Control.java:633)
        at org.eclipse.swt.widgets.Composite.createHandle(Composite.java:305)
        at org.eclipse.swt.widgets.Control.createWidget(Control.java:649)
        at org.eclipse.swt.widgets.Scrollable.createWidget(Scrollable.java:134)
        at org.eclipse.swt.widgets.Control.<init>(Control.java:110)
        at org.eclipse.swt.widgets.Scrollable.<init>(Scrollable.java:75)
        at org.eclipse.swt.widgets.Composite.<init>(Composite.java:95)
        at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java :159)
        at org.eclipse.ui.splash.BasicSplashHandler.getContent(BasicSplashHandler.java:265)
        at org.eclipse.ui.internal.splash.EclipseSplashHandler.init(EclipseSplashHandler.java:86)
        at org.eclipse.ui.internal.Workbench$8.run(Workbench.java:782)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.ui.internal.Workbench.createSplashWrapper(Workbench.java:798)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2467)
        at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
        at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
        at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at com.adobe.flexbuilder.standalone.FlashBuilderApplication.start(FlashBuilderApplication.ja va:108)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
    This is incredably frustrating as you can imagine as it effectively means i cant work anymore, it is clearly some kind of problem with eclipse but i have no idea what.
    I have tried re-installing Flash Builder twice and no luck.
    Can anyone help with this???
    Thanks !!!!
    Elliot.

    There is a similar thread with exact same stackstrace and problmes reported with earlier verison of FB. You can check it here http://forums.adobe.com/thread/832073. Thre is also representation of Adobe engineers on this thread. Aprarenlty there are certain updates(Eclipse / java) that FB doen't encourage, post FB is installed in stanadlone mode and workarounds are suggested on this thread to overcome this problem. If you are workign in plugin environment with FB, I guess updates are not affecting FB installtion. Please try out the solutions presented on this thread and let us know.

  • Parsing sendmail log file in a Java application

    Are there any good parsing libraries for sendmail log files?
    I already found these libraries but I'm not sure if they do what I need:
    http://www.opennms.org/documentation/java-apidocs-stable/org/opennms/netmgt/syslogd/package-summary.html
    http://code.google.com/p/jsyslogd/

    >
    I've written a simple text editor, and this editor saves files with a particular extension. It can both open and save files. I've put the text editor program in a JAR. What I'd like to do, if possible, is associate the file extension with the text editor program. That is, I'd like to, when I click on a file with the extension, have the text editor come up with the file opened in it.
    Can anyone give me ideas on how to do this, please? >If the editor is launched using webstart, the launch file can suggest a file association.
    Note that an application that accesses the local file system needs to be digitally signed before it can break out of the applet like 'sandbox' in which it runs, unless it uses the JNLP API to access the files. The JNLP API is available to any app. launched using webstart.
    There is an example of both claiming a file extension, and accessing files using the JNLP API, in this [File Service Demo|http://pscode.org/jws/api.html#fs]. The complete source and a build file can be downloaded from the filetest.zip just near the launch buttons.
    I suggest you try the sandboxed version first - if you think that will suit your user, go with that.
    As an aside, for best chance of a solution, I recommend folks add [Duke stars|http://wikis.sun.com/display/SunForums/Duke+Stars+Program+Overview] to match the importance of the task.

Maybe you are looking for

  • Can't print pdf - no Adobe in printer menu

    Hello, Firstly I should explain that my computer is running OSX 10.5.3. One of my applications doesn't work properly on Leopard, so I recently installed my old Panther (10.3.7) onto an external drive and boot off that in order to work in that program

  • SolMan 7.1 Java for ABAP Stack ?

    Hello Witch JVM for SAP Solution manager 7.1 OS: Linux x86_64 DB: MAxDB SAP JVM for Diagnostic agent PAM provide SAP JVM or IBM JAVA for Java stack, but for ABAP ? Regards Eric

  • How to run servlets in debugger

    Is it possible to start up or attach a debugger to a java servlet in WebLogic 5.1 that is using JDK 1.2.2? Thanks, Sean

  • IPhone wont update

    Hi,      I have an IPhone 3GS and just tried updating it and it crashed so i restored it to factory and now im trying to activate it and it keeps coming up with activation server is temporarily down. it keeps saying it and ive been trying for over an

  • How to Fetch the Data from Screen(Structure) Leval

    Hi, In HR I have to retrive some fields from Screen leval ..Ex.Q0002..genaraly we are able to retrive the data from PA0002. in this Scenari how can i fetch data from Q0002. Thanks in Advance