The VI is not executable. The full development version...

"The VI is not executable. The full development version of LabVIEW is required to fix the errors." That is the error I've been dealing with all day. Actually it is repeated 3 to 4 times in the error message, seen when first launching the EXE. Also of note is that the run-arrow is broken. This is in an EXE that was developed well before version 2013, but I recently upgraded it to 2013 to hopefully fix some random LVRT crashes. There is obviously no issue running the code on my development machine, only once it's deployed.
The good news is I've been able to solve the problem (mostly). My EXE now runs without the errors. I found that the problem wasn't actually in the EXE.
We have a separate project with no files, but in the build specification we have the LabVIEW 2013 Run-Time Engine, as well as NI-VISA for serial support. We then bundle the deployment in a self-extracting RAR and it does its business. In the past this has worked just fine, but with LV2013, it seems that there is a component missing from the deployment.
I found that if I download the Run-Time Engine directly from NI.com and run it, the only things I need to install are the Run-Time Engine, and the DEPLOYABLE LICENSE. If I do this, my EXE runs great, but with the custom installer, it is not included for some reason!
Putting aside the fact that I don't know why the Deployable License package is needed (we aren't connecting to remote panels), I can't seem to modify my custom installer to install the Deployable License. There are versions for LabVIEW 2009 and 2011 SP1 in the Additional Installers list, but I don't see 2013.
Can anyone explain why this is??? For now I will just distribute the 257MB Run-Time Engine and the NI-VISA installers separately I guess. But I'd really like to get back to a single, simple package to install all the prerequisites we need. HELP!

iannicholson wrote:
Yes, but then every installer I build will contain the runtime engine. That gets very large very quick. So I have an installer for JUST the runtime engine and VISA runtime.
Just remove them from the "Additional Installers" tab of the Installer dialog.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

  • Error "The application could not execute the required function"

    Hi All,
    When I try to activate the DTP the following error occurs."the application could not execute the required function".
    I was able to activate the DTP for the same DataSource 2 days back but now I am unable to activate .
    Kindly suggest what could be the possible reason for the same.
    Regards,
    Santosh Mani

    If you have transformation, check it is active. Is the object 0plant is acitve or not?
    Ravi Thotahdri

  • A full development version of labview required to fix the errors.

    When i tried to run my exe file, it gives following error.
    "A subvi is not executeable.A full development version of labview required to fix the errors."
    i do have full version of 6.02.
    Am i missing something something when i built exe?
    any Help will be appreciated.

    Well, here we go again...
    I have seen this error way too many times in my day.
    The problem is you have a bad linkage, or unsaved or compiled VI in your hierarchy when you built the application.
    Open your main, or otherwise open (into memory) ALL VIs in your hierarchy. Then, do a save all from the file menu. This should solve the issue.
    The other reason I have seen this is if you have bad linkage. As there is no real way to tell what your linkage is, you need to go into the hierarchy, select View Full Path in Title and make sure everything is where you think it is. I have often seen this occur even when the application I was building from was in perfect condition. Often times, when the app builder is used, VIs will be called from locations you
    don't expect.
    You have to be VERY careful about developing in a hierarchy. I actually got to a point where I had to even place all the NI VIs into my directory structure.
    Take a careful look at the hierarchy. Chances are the executable is calling the wrong code, or is compiling with the wrong version.
    If in doubt, go to a fresh machine, and move all of your VIs (individually if you have to, or as a .llb preferably) to the new machine and build it from there. Alternatively, you can try doing a save as from your main and select "application distribution" this will resolve any issue with VI locations, except where Dynamic VIs are being used.
    Good luck, 'cause you are going to need it.

  • I recieve the following error when running an executable ("This VI is not Executable. The full development version of Labview is required to fix the errors"

    I recieve the following error when trying to build and run a labview executable. I am able to build the executable but when trying to run the executable, a pop up window comes up asking the user to select a dll. (please see screen shot attached). Once the DLL is selected, I get the error that This VI is not Executable. The full development version of Labview is required to fix the errors. (please see screen shot attached). I have also attached a snapshot of the project window.
    I have the professional development system
    I can run the main VI
    all the required DLL's are in the dependencies section of the project window.
    I am trying to find the root cause of this error but to no avail. can anyone give me a clue to what i am missing here. Any suggestions on where i should look to find the problem ?
    Thanks in advance to all labview users for your help
    Attachments:
    project window.PNG ‏36 KB

    other PNG
    Attachments:
    Broken Arrow on EXE.PNG ‏179 KB

  • Please help suggestions for solving built-only compiler error: 'The VI is not executable. The full development version of LabView is required tofix this error.'

    We have develoepd a software tool and build it on regular basis. It currently runs error free when compiled in the editor, but when we built it and run the executable stand alone we get the error.
    'The VI is not executable. The full development version of LabView is required tofix this error.' plus a broeken error.
    This menas an compiler error that is not present in the editor but in the stand alone version. We tried to identify errors as suggested in several posts in this forum, but so far unsuccesfull.
    As the editor and its compiler do not see the error  and are running fine and the stand alone version just syas 'find the error in the editor' in this case LabView is of no help.
    Can anyone suggest a sensible or 'good practice ' way of searching for the source of this error?
    Our project  comprises hundreds of Vis over several libraries.
    Thanks,
    Chris

    Thanks Craig for all your suggestions.
    We seem to have located the problem in a new vi just added to the package causing conflicts by using the same vi names as other vis already present in the package. Excluding this vi removed the error.
    It seems related to a conflict by having two vis with the same name, which was mentioned by LabView and interactively resolved when running the main vi from the editor. When successfully building the main vi the builder did not mention this conflict and reported a successful build, but when trying to run the executable it gave the cryptic error. The error caused us problems because there was no hint for the cause, just the suggestion to solve this in the editor, while at the same time in the editor the VI was running fine.
    We will post about this in detail after we have positively proven that this actually was the case.
    The .net version issue was already checked.
    Performance was the same on all machines we tested on including the dev machine.
    Debugging was tried nut did not help as the vi could not run (broken arrow). We assumed that debugging only helps in running faulty functioning vi''s. We did not check for broken arrows in sub-vis (after connecting), that could have helped, although our application has hundreds of our own vis.
    In relation to your remark: 
    'Are you using many classes? Have you verified that the proper access scopes are set for functions calling those vis?'
    Could you elaborate on setting access scopes. We were not aware of this option in LabView, although we realize this is a basic element of the underlying c code.
    Ragrds,
    Chris

  • "VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors"

    Hi,
    I had created an executable in LabVIEW 8.6 on a windows XP 32 bit PC. The application uses some Vision VIs. The executable runs in most of the PCs except one. the PC is a windows 7 64bit. Initially i got the error "Labview Load error code 3: could not load front panel". I fixed this by changing the source file settings in the application builder. Now i am getting the error "VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors" and the exe shows a broken run button.
    But if i build the exe in the same PC i get no errors and it works fine. Moreover i have tested this exe in a different PC with the same configuration, it works there. I have tried reinstalling labview in the PC the problem still persists.
    Solved!
    Go to Solution.

    Hi Rajshekar.
    > Which version of LabVIEW are you using on PC with Win7 64bit? would like to check if there are any issues with LV2009 32bit on 64bit OS..
          - The version of Labview on the win7 64bit PC is also lv8.6 full development system.
    > Do you get the same error on the other PC with same config(Win7) when running the .exe generated using LV 8.6 on WinXP 32bit? just to make sure the problem is with OS or LV..
          - the same problem occured at one more PC with the same configuration. but when i tested in an another PC of the same config it worked i am not able to isolate and decide that the error is based on one particular PC config.
    I have listed the environments in which application ran and how the application was put in to the PC.
    I would also like you to know that i have created an installer for the exe. I am also using NI vision in my application and this is the error "An error occured loading VI 'IMAQ GetImagePixelPtr'. LabVIEW load error code 3: could not load front panel"....and rest is what i said in my previous post
    1. Use the installer to install the application.
    2. just copy the exe created in LV 8.6 into a PC that already has LV development system installed in it
    3. The PCs might either be a blank one with no history of LV installed in them
    4. The PCs might have diffrent versions of LV development systems installed in them (8.2,8.5,8.6,2009)
    All PCs that have LV development system(s) installed in them, was able to run the application except the one with win7 64, where i have tried uninstalling all NI software and use only the installer to install, install LV 8.6 full development system and try runnning the exe, nothing works.
    Thanks

  • LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File Open and verify that it is runnable.

    When trying to run a sequence on a deployment machine I get this error. When I switch the Adaptor back to the Development System the problem goes away however I do not have the luxury of keeping the full Labview development on the test machine. Is there a know fix for this problem and what is the cause of this error. Here is the software and versions I am using. It seems that the vi's that are broken are using Invoke and Property Nodes within them, I am not sure if this is just a coincidence. It appears it is more related to the invoke node than the property node. Any help is greatly appreciated. Why does it seem everything works great until you try and deploy it on a test machine. This is not the first time I have had these kinds of problems using Nation Instruments software.
    Labview 8.2.1
    TestStand 4.0
    Solved!
    Go to Solution.

    I have a similar problem.
    A bit of background - I had developed a test suite with a Labview front panel for manual operations, and a Teststand project which used some of the same lower level vi's, and specific test step vi's. It was developed on LV 2010 32-bit and Teststand 2010. All was fine.
    Recently i had to rebuild my development machine and installed only LV 64-bit 2011 and the latest (2010) Teststand from the 2012 Dev Suite.
    I knew that i wanted to run some new hardware drivers in 64-bit versions due to another problem, so i replaced the .dll in the very lowest level VI with the 64 bit version. And ran the manual interface. All ok.
    But when i try the Teststand execution, i get one of two errors:
    - If i set Teststand to use the LV runtime engine 11.0.1 (2011 SP1), the i get a "Unable to load VI xxxxx with the runtime engine version '11.0'" Despite the fact that each VI does run correctly in LV dev when loaded individually, and i've saved them as version 11.
    - If i set it to use the development system (which shows in the config menu 'active version:32-bit' even though 32-bit LV is not installed), then i get the "The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located." error, even though i when i open each VI in the LV 2011 it runs ok.
    Any ideas?
    How can i set TS dev system to use the 64-bit version? Or is there a separate 64-bit deployemrnt of TS?
    Labview 2010, TestStand 2010

  • The process could not execute 'sp_repldone/sp_replcounters' error for Log Reader Agent and SQL Server Assertion 17066 & 3624 errors in SQL Logs

    One of our SQL Server started creating SQLDUMP file and and on investigation I found the error longs are filled with Errors 3624 & 17066. There is transnational replication configured on one of the databases is the LogReader Agent is failing error "The
    process could not execute 'sp_repldone/sp_replcounters' on XXXXX". 
    Not sure if both these Assertion & Logreader Agent errors are related. Before I remove and put the replication, I wanted to check if anyone has experienced the same issues or aware of what the cause. 
    ***********Error messages from SQL Logs******
    **Dump thread - spid = 0, EC = 0x0000000111534460
    Message
    A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to
    Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
    Error: 3624, Severity: 20, State: 1.
    SQL Server Assertion: File: <logscan.cpp>, line=2123 Failed Assertion = 'UtilDbccIsInsideDbcc () || (m_ProxyLogMgr->GetPru ()->GetStartupState () < RecoveryUnit::Recovered)'. This error may be timing-related. If the error persists after rerunning
    the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
    Error: 17066, Severity: 16, State: 1.
    External dump process return code 0x20000001.
    External dump process returned no errors.
    Thank you in advance.

    You need to determine if this error is a transient one or a show stopper one.
    It sounds like your log reader agent has crashed and can't continue.
    If so your best bet is to call Microsoft CSS and open a support incident.
    It also sounds like DBCC CHECKDB was running while the log reader agent crashed.
    If you need to get up and running again run sp_replrestart, but then you might find that replicated commands are not picked up. You will need to run a validation to determine if you need to reinitialize the entire publication or a single article.
    I have run into errors like this, but they tend to be transient, ie the log reader agent crashes, and on restart it works fine.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Error 1003 - The vi is not executable​. Simulated DAQ-cards.

    Hi all,
    I am updating an application written in LabVIEW 7.1 for a customer. The code is not made by my company and is pretty horrendous but it works. I can not develop the code on the machine that it is supposed to run on so I have to do it on my own computer which means that I have to simulate two DAQ-cards that the program needs. I have pretty much finished the program and I want to test if I can build an exe-file. This is where I run in to trouble an get the error message:
    Error 1003 occurred at \\Server1\Users\martinh\LabVIEW Data\app\internal.llb\_Main.vi
    Possible reason(s):
    LabVIEW:  The VI is not executable.
    I know that this has been discussed at length here and that one has to look out for global variables, dynamically loaded VI:s etc. My question is, does anyone think that the simulated DAQ-cards give me trouble? Do they use some VI:s placed somewhere odd which I need to include when I build the application?
    Sincerely
    Martin

    Hi Martin,
    I suggest you try what is suggested in this link, some of the information is already covered in the posts above but some might be new.
    http://digital.ni.com/public.nsf/allkb/705C2ECA081​F3C7986256C0F00559B02?OpenDocument
    If you are using the office toolkit, it might be an idea to masscompile the _office folder and you might also need to uncheck the "Disconnect type definitions and remove unused polymorphic VI instances".
    Good Luck
    Andreas E
    Applications Engineer
    National Instruments

  • Could not execute the job

    Hi,
    when i execute the job a a window appear with the massage" ERROR: could not execute the job .Error returned was 1
         MESSAGE is : Could not open command file...
    And i can't find from where it comes any suggestion?

    When today i execute the job i had this list of error
    13860    15384    REP-100109        27/05/2014 08:22:10       |Session TF_SGFA
    13860    15384    REP-100109        27/05/2014 08:22:10       Cannot save <History info> into the repository. Additional database information: <SQL submitted to ODBC data source
    13860    15384    REP-100109        27/05/2014 08:22:10       <SIGSIRDDB01\SQLSIRDBD> resulted in error <[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object
    13860    15384    REP-100109        27/05/2014 08:22:10       'dbo.AL_HISTORY_INFO' in database 'DS_REP' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded
    13860    15384    REP-100109        27/05/2014 08:22:10       files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files
    13860    15384    REP-100109        27/05/2014 08:22:10       in the filegroup.>. The SQL submitted is <INSERT INTO "AL_HISTORY_INFO" ("OBJECT_KEY", "NAME", "VALUE", "NORM_NAME",
    13860    15384    REP-100109        27/05/2014 08:22:10       "NORM_VALUE") VALUES (430, N'TRACE_LOG_INFO',
    13860    15384    REP-100109        27/05/2014 08:22:10                N'F:\SAPDS/log/JobServDS/sigsirddb01_sqlsirdbd_ds_rep_dsuser/trace_05_27_2014_08_22_09_10__3a4327b0_92c8_4abe_ac24_96d49123242a.
    13860    15384    REP-100109        27/05/2014 08:22:10       txt', N'TRACE_LOG_INFO',
    13860    15384    REP-100109        27/05/2014 08:22:10                N'F:\SAPDS/LOG/JOBSERVDS/SIGSIRDDB01_SQLSIRDBD_DS_REP_DSUSER/TRACE_05_27_2014_08_22_09_10__3A4327B0_92C8_4ABE_AC24_96D49123242A.
    13860    15384    REP-100109        27/05/2014 08:22:10       TXT') >.>.
    13860    15384    REP-100112        27/05/2014 08:22:10       |Session TF_SGFA
    13860    15384    REP-100112        27/05/2014 08:22:10       Cannot save <History info> for repository object <>. Additional database information: <Cannot save <History info> into the
    13860    15384    REP-100112        27/05/2014 08:22:10       repository. Additional database information: <SQL submitted to ODBC data source <SIGSIRDDB01\SQLSIRDBD> resulted in error
    13860    15384    REP-100112        27/05/2014 08:22:10       <[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'dbo.AL_HISTORY_INFO' in database 'DS_REP'
    13860    15384    REP-100112        27/05/2014 08:22:10       because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup,
    13860    15384    REP-100112        27/05/2014 08:22:10       adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.>. The SQL submitted is
    13860    15384    REP-100112        27/05/2014 08:22:10       <INSERT INTO "AL_HISTORY_INFO" ("OBJECT_KEY", "NAME", "VALUE", "NORM_NAME", "NORM_VALUE") VALUES (430, N'TRACE_LOG_INFO',
    13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/log/JobServDS/sigsirddb01_sqlsirdbd_ds_rep_dsuser/trace_05_27_2014_08_22_09_10__3a4327b0_92c8_4abe_ac24_96d49123242a.
    13860    15384    REP-100112        27/05/2014 08:22:10       txt', N'TRACE_LOG_INFO',
    13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/LOG/JOBSERVDS/SIGSIRDDB01_SQLSIRDBD_DS_REP_DSUSER/TRACE_05_27_2014_08_22_09_10__3A4327B0_92C8_4ABE_AC24_96D49123242A.
    13860    15384    REP-100112        27/05/2014 08:22:10       TXT') >.>.>.
    13860    15384    REP-100112        27/05/2014 08:22:10       |Session TF_SGFA
    13860    15384    REP-100112        27/05/2014 08:22:10       Cannot save <History info> for repository object <>. Additional database information: <Cannot save <History info> into the
    13860    15384    REP-100112        27/05/2014 08:22:10       repository. Additional database information: <SQL submitted to ODBC data source <SIGSIRDDB01\SQLSIRDBD> resulted in error
    13860    15384    REP-100112        27/05/2014 08:22:10       <[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'dbo.AL_HISTORY_INFO' in database 'DS_REP'
    13860    15384    REP-100112        27/05/2014 08:22:10       because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup,
    13860    15384    REP-100112        27/05/2014 08:22:10       adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.>. The SQL submitted is
    13860    15384    REP-100112        27/05/2014 08:22:10       <INSERT INTO "AL_HISTORY_INFO" ("OBJECT_KEY", "NAME", "VALUE", "NORM_NAME", "NORM_VALUE") VALUES (430, N'TRACE_LOG_INFO',
    13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/log/JobServDS/sigsirddb01_sqlsirdbd_ds_rep_dsuser/trace_05_27_2014_08_22_09_10__3a4327b0_92c8_4abe_ac24_96d49123242a.
    13860    15384    REP-100112        27/05/2014 08:22:10       txt', N'TRACE_LOG_INFO',
    13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/LOG/JOBSERVDS/SIGSIRDDB01_SQLSIRDBD_DS_REP_DSUSER/TRACE_05_27_2014_08_22_09_10__3A4327B0_92C8_4ABE_AC24_96D49123242A.
    13860    15384    REP-100112        27/05/2014 08:22:10       TXT') >.>.>.
    and thank u.
    Sincerly

  • HT6030 I downloaded Mail Update for Mac OS X 10.5.6 and was told it could not be installed because it was from an unidentified developer.  Tried installing download from MailUpdate & advised the disk did not meet the requirements for update. Hmmmm.

    I downloaded Mail Update for Mac OS X 10.5.6 and was told it could not be installed because it was from an unidentified developer.  Tried installing download from MailUpdate & advised the disk did not meet the requirements for update.   Expect it's due to being at 10.9.1.  Mail is still teetering between dysfunctional and non-functional.  Advice?

    I'm not sure what "Mail Update for Mac OS X 10.5.6" is. Mac OS X 10.5.6 is Leopard, a system that is quite old at this point. There have not been any Mail updates for Leopard in quite some time. If you are trying to install some old Mail update for Mac OS X 10.5.6 in Mavericks, that won't work.
    If you are trying to install the Mavericks Mail update manually, that's not necessary if you have updated through the App Store. If the App Store shows no updates, you don't need this. (The error message doesn't make sense, and may indicate some other problem with your system, assuming that you were downloading this update from Apple's site.)
    I'd advise you to start a new topic in the Mavericks forum and describe the problems you are having with Mail. Be sure to include specifics, but try to avoid speculating on causes, as responses that may be related to an inaccurate assumption on your part can cloud the issue.

  • Could not execute the css file

    Hi,
    I have this code:
    named: email11.java
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.sql.*;
    import java.util.*;
    import business.User;
    import data.UserDB;
    import util.MurachPool;
    public class EmailServlet extends HttpServlet{
    private MurachPool connectionPool;
    public void init() throws ServletException{
    connectionPool = MurachPool.getInstance();
    public void destroy() {
    connectionPool.destroy();
    public void doGet(HttpServletRequest request,
    HttpServletResponse response)
    throws IOException, ServletException{
    Connection connection = connectionPool.getConnection();
    HttpSession session = request.getSession();
    String message ="";
    try{
    Vector users = UserDB.readRecord(connection);
    session.setAttribute("users", users);
    RequestDispatcher dispatcher =
    getServletContext().getRequestDispatcher(
    "/email11/show_email_entry.jsp");
    dispatcher.forward(request, response);
    }catch(SQLException sqle){
    message = "EmailServlet SQLException: " + sqle;
    session.setAttribute("message", message);
    RequestDispatcher dispatcher =
    getServletContext().getRequestDispatcher(
    "/email11/join_email_list.jsp");
    dispatcher.forward(request, response);
    connectionPool.freeConnection(connection);
    and this code in jsp file:
    named: show_email_entry.jsp
    <!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
    <%@ taglib uri="../WEB-INF/tlds/murach.tld" prefix="mma" %>
    <html>
    <head>
    <link rel="stylesheet" type="text/css" href="DisplayData.css">
    </head>
    <body>
    <h1> Test</h1>
    <table cellspacing="0" cellpadding="1" border="1">
    <tr valign="bottom">
    <td class="headerColumn" align= "center">First Name</td>
    <td class="headerColumn" align= "center">Last Name</td>
    <td class="headerColumn" align= "center">Address</td>
    <td class="headerColumn" align= "center">Phone Number</td>
    <td class="headerColumn" align= "center">Cell Number</td>
    <td class="headerColumn" align= "center">Email Address</td>
    </tr>
    <mma:users>
    <tr>
    <td><%= firstName %></td>
    <td><%= lastName %></td>
    <td><%= address %></td>
    <td><%= phoneNumber %></td>
    <td><%= cellNumber %></td>
    <td><%= emailAddress %></td>
    </tr>
    </mma:users>
    </table>
    </body>
    </html>
    This is the css file code that I like to apply to the show_email_entry.jsp
    named: Displaydata.css
    This rules are for background color for data display
    /*td.column{
    background-color: #f0f8ff;
    background-color: #fffacd;
    td.headerColumn{
    background-color: #daa520;
    font-weight: bold;
    font-family: sans-serif,Verdana, Arial, Helvetica;
    font-size: 10pt;
    td.column{
    font-family: sans-serif,Verdana, Arial, Helvetica;
    font-size: 10pt;
    white-space: nowrap;
    background-color: #fffacd;
    a{
    text-decoration: none;
    h1{
    color: red;
    They are working fine. However, it just does not execute the css file in the show_email_entry.jsp. Another word, the headerColumn should show some color as I coded it in the css file. But it shows only white background and black text. I have the file named DisplayData.css in the same directory as the file named show_email_entry.jsp. But it still does not work.
    if I create a test.jsp and use with the DisplayData.css file above then it would work fine. But when I used it with the servlet file, then it would not work.
    Anyone knows why ?
    Thanks
    zbonzbon

    Pls, disregard this thread. I have found my answer..
    Thanks,
    zbonzbon

  • When I touch my iPad screen to execute an app, the screen goes dark then the app icon reappears. The app does not execute.

    When I touch my iPad screen to execute an app, then the screen goes dark then the app icon reappears. The app does not execute. Any thoughts?

    Try a Reset...
    Press and hold the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears. Release the Buttons.
    Basic troubleshooting
    From Here
    http://www.apple.com/support/ipad/basics/

  • Runtime.exec not executing the command !

    Hi all,
    I'm connecting to Progress Db thru JDBC trying to execute a stored procedure
    which has a statement
    Runtime.exec("ksh -c aa") where aa is aunix script which i'm trying to run from java snippet .
    when i run this code as a seperate java program it executes the script
    "aa" but thru JDBC connection it does not execute the command
    what could be the reason ???
    thanx in advance,
    Nagu.

    Hi Rick,
    "aa" is the shell script which is lying in the user DIR .
    It is returning a non-zero value. what kind of permissions be there for to execute the Shell command?
    Regards,
    Nagarathna.

  • Servlet not executing the a file at server?

    i am trying to execute a java file at server
    using the following servlet. I am using
    Process proc=runtime.exec("C:\\j2sdk1.4.1_01\\bin\\javac HelloServlet.java"); I am compiling the code succesfully
    and when i call the servlet at browser it displays HELLO
    but not executing the command. I am using Tomcat and winows NT.
    here the servlet code ....please help.........
    import java.io.*;
    import java.util.*;
    import javax.servlet.*;
    import javax.servlet.http.*;
    public class Hello extends HttpServlet {
    public void doGet(HttpServletRequest request,
    HttpServletResponse response)
    throws ServletException, IOException {
    response.setContentType("text/html");
    PrintWriter out = response.getWriter();
    String docType =
    "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0 " +
    "Transitional//EN\">\n";
    out.println(docType +
    "<HTML>\n" +
    "<HEAD><TITLE>Hello</TITLE></HEAD>\n" +
    "<BODY BGCOLOR=\"#FDF5E6\">\n" +
    "<H1>Hello</H1>\n" +
    "</BODY></HTML>");
    try
    Runtime runtime=Runtime.getRuntime();
    Process proc=runtime.exec("C:\\j2sdk1.4.1_01 \\bin\\javac HelloServlet.java");
    BufferedReader br=new BufferedReader(new InputStreamReader(proc.getInputStream()));
    PrintWriter com_out=response.getWriter();
    com_out.println("<pre>");
    String line=null;
    while((line=br.readLine())!=null)
    { com_out.println(line);
    catch (Exception e)
    out.println("Listener *not* started!");

    thanku for the cooperation. i kept as below but still it is not working.......
    String path = getServletContext().getRealPath("C:\\Tomcat 4.1\\webapps\\examples\\WEB-INF\\classes\\Hello.class");
    Runtime runtime=Runtime.getRuntime();
    Process proc=runtime.exec("C:\\j2sdk1.4.1_01\\bin\\javac HelloServlet.java" +path );                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

Maybe you are looking for