"LabVIEW Runtime won't install"

Hi Folks,
Am trying to install LVRT821 on a machine, but it refuses to show-up as installed list shown through \control-panel\Add-remove programs\National Instruments.
Machine had some NI stuff installed already and after first a couple of [unsuccessful] installs/restarts, began slowly removing current NI installations.
Am down to MAX and getting ready to install again (after a restart.)
OS is WinXP and I'm logged-in as an admin, running LVRT installer EXEs downloaded from NI today. (Have tried LVRT82 as well LVRT821.)
Any ideas?
Cheers!
Message Edited by bluesbros on 05-08-2009 03:08 PM

Problem "solved" by uninstalling all NI SW and deleting \Program Files\NI.
One thing I didn't notice initially -LVRT install indicated LVRT already installed (Leave as-is.) Regardless, it was missing from Add/Remove Pgms (could not be repaired) and EXEs would not run.
Cheers!

Similar Messages

Labview runtime 2013 silent install

HI,
I would like to install LV runtime 2013 silently. I tried to use /qb option in CMD to install silently (setup.exe /qb), but I got the "Invalid command line parameters" error. However, if I use setup.exe /r (suppress final reboot) it works. I checked that /qb option is specified in help.
Solved!
Go to Solution.

Please try:
setup /qb /AcceptLicenses yes
More info on Silent install can be found at http://digital.ni.com/public.nsf/allkb/878FC4C374013ADF8625733D00688F67?OpenDocument
Regards,
Andrej Korosec

Install MAX with only LabVIEW runtime engine

Hi,
I want to know if it is possible to install MAX from the Device Driver CD, when only LabVIEW RunTime engine is installed. There is no full installation of LabVIEW on that PC. That's MAX 3.1.1.3004 with LabVIEW RunTime Engine 7.1.
Patrick.

Dear Patrick,
The device driver CD usually does not have a single installation of MAX, but you can install MAX by installing most of the other drivers such as NI-DAQ, NI-488.2, NI-Serial, etc. MAX does not require LabVIEW, so you can have MAX and LabVIEW Run-Time without LabVIEW. Have a great day!
Sincerely,
Marni S.

Installing Labview runtime engine 2011

Hi,
Is it mandatory to uninstall any previous version of the Labview runtime engine before installing the 2011 verstion ?
Thanks.

No, you should actutally keep the older runtime engine installed in case you still have applications that depend on it. The 2011 run time will only support applications built with LabVIEW 2011.
LabVIEW Champion . Do more with less code and in less time .

CIN (Code interface node) LabVIEW runtime engine dependency

Hello:
Am I correct that the old style CIN (code interface node) is not dependent on what version of LabVIEW runtime engine is being used?
However if I create a dll from say LabVIEW 8.2 I must then alway have LabVIEW runtime 8.2 installed on any newer machine with newer version of LabVIEW?
Thank You!

GE Osmonics wrote:
Hello:
What I have are old CIN (no source) that work in LabVIEW7.1 but will not work in LabVIEW 2010 (link error, object code not loaded).
What I thought I could do is generate dll from the vi's that contain the CIN using LabVIEW 7.1 with application builder.
I could use the Call Library Function from LabVIEW 2010 to load the 7.1 generated dll to effectively do what the old CIN accomplished
provided I installed the LabVIEW 7.1 runtime engine on my LabVIEW 2010 machine
Thanks for the input
If the CIN resource doesn't load you most likely changed the LabVIEW platform. LabVIEW for Windows 32 Bit and LabVIEW for Windows 64 Bit are different platforms. Just as LabVIEW for Windows and LabVIEW for Macintosh or Linux. A 32 Bit DLL, which a CIN is internally can't be executed in a 64 Bit environment at all.
Your solution fails for more than one reason here. LabVIEW will try to load and link a LabVIEW DLL into its actual runtime environment to avoid interprocess communication latency which would be inavoidable if the DLL is started in a seperate runtime engine, which is in fact a new process. If your issue is 32 bit to 64 Bit you won't be able to link the 7.1 32 Bit DLL into your LabVIEW 64 Bit application through the Call Library Node at all.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Deploy simple Labview applications without installing the Labview runtime?

[Labview 8.21 - Windows XP]
Hello and a happy new year to all !
I have coded very simple Labview applications that basically read text files (exported from Ms Excel), make some string operations, array sorting and at the end write another text file that is then imported in Ms Access. Now I would like other people from the School parents association to use this application on their own PC but ideally without having to install the Labview run-time; for various reasons one of them being that they are not administrator of their PC, another reason being that I feel bad to ask them to install 100Mb of programs on their PC to execute my <1Mb applications. All that I can assume is that they have Excel and Access installed on their PC.
I have read some postings on the Forum and in the Knowledge base from which I understand that the only way to use my application without the Labview runtime is to build a shared library that maybe I could then link via a VBA code from inside Excel or Access. But I cannot find any usable example on how to do that practically. And maybe it is not possible.
What is the easiest way to run such very simple Labview compiled applications on a PC that does not have Labview installed? Is Labview not at all built for such use?
Thanks a lot for your help and ideas.
Christophe

You will need to have the runtime installed. There is a lot of other languages that also have the need for there own runtime, but they are commonly installed with the OS, so you don't realize it. Just building a dll won't solve this.
There might be a hack possible, though. People have managed to strip down the required installation and been able to deploy the required parts of the runtime only. If you want to go this way, search on LAVA. But I'm not sure if it works with LV 8.20, and you will need to invest some time to figure out the minimum requirements. But be aware that it is a hack, so it's on your own risk.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Labview 8.6 Microsoft Visual C++ Runtime error while installing

I am installing Labview 8.6 on my laptop which is having Windows Vista Home premium edition.
When the installation begins an error occurs (after the acceptance of licence step in the installation procedure) with the title on the error window "Microsoft Visual C ++ Runtime Library " and displays the program set up path with these statements " This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."
I am unable to install it on my laptop. Can anybody please help me.
Thank you

hi
broadly the error could be because of two reasons:
1. Runtime Engine exe file is corrupt in the CD you are using to install LabVIEW.
Solution: Download LabVIEW Runtime Engine 8.6 from http://joule.ni.com/nidu/cds/view/p/id/1101/lang/en
2. There's some problem with the windows installation in your PC.
Solution: you know reinstall windows
But before trying to reinstall, make sure you installed the msi.dll using "Regsvr32 (system folder path)\msi.dll" . I'm sure you did.
thanx
Ravi

Unable to determine the install root path for the LabVIEW Runtime Engine

Hi,
i have an issue with using a LabVIEW interop assembly in a .NET application. I get an exception "Unable to determine the install root path for the LabVIEW Runtime Engine" when calling the assembly.
The little test program is attached below. It's called dotNETHost.exe. If you excecute the programm a dialog with an button appears. Clicking the button shall open another dialog (the LabVIEW Interop component). But the only thing I get is the exception message. The ZIP folder also contains the complete exception meassage (ExceptionMessange.jpg & ExceptionDetails.txt).
The Interop Assembly was built with LabVIEW 2011. We use Visual Studio 2010 and .NET 4.0.. The dotNETHost.exe.config file is prepared as mentioned in Knowledge base - Loading .NET 4.0 assemblies.
The Interop assembly contains only one simple dialog (loop is finished by clicking OK) without calling any other VIs or other DLL's. In case of this there's also no support directory generated by the build process.
I have no idea why it doesn' work. I hope anyone can help me.
Thanks in advance
Kay
Attachments:
Debug.zip ‏75 KB

This may be unrelated, but Labview and .Net4.0 dont work well together. Not yet anyway. I had to compile my assembly in 3.5 to get it to work.
Please read the following:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configuring_clr_version/
http://digital.ni.com/public.nsf/allkb/32B0BA28A72AA87D8625782600737DE9
http://digital.ni.com/public.nsf/allkb/2030D78CFB2F0ADA86257718006362A3?OpenDocument
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Trouble installing labview runtime engine

Can not install labview runtime engine. Says there is already a higher version installed.

Yes, this is a pain - and I have no idea why NI would design their installers in this way. I can think of no rational reason. In any case, the work around is to uninstall everything and then reinstall in a different order. For example, I ran into the problem was trying to install a runtime executable on a machine that already has some NI drivers installed. Part of that installation was that it installed the V7.1 runtime engine. When I then went to install my executable which was built in V7.0 it wouldn't install. To get around this bug I had to uninstall all NI software and then reinstall my executable and then the drivers, in that order.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Installing of LabVIEW runtime is cause of InTouch can't find its licenses

Hello All.
I need to run executable built with LabVIEW from Wonderware InTouch 2012 runtime. But If I install LabVIEW runtime to the target PC, InTouch runtime can't find its licenses and run in Demo mode only. When I uninstall LabVIEW runtime InTouch can find licenses again and operates in normal mode. Licences for InTouch consists of files on the hard drive and software protection dongle of unknown type, connected to USB port. I have tried LabVIEW runtime versions 2012, 2012f3 and 2013, installed from standalone distributions or with distribution of application built with LabVIEW, no differences. What can be cause of conflict? What can I try to do to run InTouch runtime and LabVIEW application simultaneously?
Target OS: Windows 7 Ultimate 64-bit MUI
Host OS: Windows XP Professional 32-bit Russian

Tortu wrote:
Have you verified if this behavior is present in other computers?
No, I have only 2 PCs for tests, both new and identical in hardware and software. I'm sure I will get same result on both.
Have you tried changing the port at which you connect the USB key?
Yes.
Did you restart the computer after installing the LabVIEW RTE?
Yes.
Have you tried installing the LabVIEW RTE before installing the Wonderware software?
Yes.
Can you access other USB keys when you have the LabVIEW RTE install or does all USB communications fail?
I have another software protection dongle for InTouch. I've tried it, it doesn't work too. USB in general is working (HID, USB flash drives, USB HDD).
Have you received any troubleshooting steps from Wonderware? Please let us know.
Wonderware support engineers sent me test license file which not require USB dongle. With this license file InTouch operates in normal mode when LVRT is installed. But it is impossible to use such license in production.

Windows error 998 by installing labview runtime 8.2.1 on windows xp

Hello,
I got Windows Error 998 during installation of the labview runtime engine 8.2.1 on windows xp system. The installation with the same package worked on serveral other systems with the same os.
Any ideas?
Thanks a lot and best regards,
Michael
Attachments:
Error_998.png ‏14 KB

Based on the message it appears it's having problems reading the file. Did you copy the files from a CD? From a network? The file itself may be corrupt. Try recopying the files to your hard drive. You may also want to check your hard drive for errors.

Profibus-Connection with NI LabVIEW Runtime-engine

Hi,
I have a Profibus network running in our porduction lane.
Now we want to report several states of this production continously.
Therefore I want to connect a desktop-pc via profibus to the PLC. But I want to run the VI on the PC as an application(exe) with the NI LabVIEW runtime engine because I won´t install LabVIEW on this PC. (on my development computer I have LabVIEW 2011)
My question is:
Does the Profibus communication work if I run the VI that way if I add the needed "additional installer" to my installer file?
I´m quite sure that it will work but I want to check this point before ordering a Profibus-Board.
I hope you understand my question and give me a positive answer so I can order an new Profibus-PCI-Board
best regards
Martin

Hi Martin,
the scenario you are describing sounds reasonable and that should work.
But in general, if you buy something at NI you can always call and describe your situation. Either the sales person can help you with your decision or in more complicated cases the sales person redirects you to a support engineer.
Best regards,
Christoph

Application (WMF 3.0) won't install during maintenance window, but will install when there is no maintenance window

Hi All,
I'm just getting into the Application model in SCCM 2012 R2 and I like what I see so far, but i'm running into an issue. When i set up an Application for WMF 3.0 with a prerequisite of .Net 4.0 and deploy it to a set of test systems that do not have
any maintenance windows applied to it, it works great. If it doesn't have .Net 4.0 it installs both that and WMF 3.0 and reboots. If it already has .Net 4.0, it will skip that and just install WMF 3.0 and reboot.
However, if i deploy it to systems that have a maintenance window applied, the application recognizes that it needs .Net and WMF 3.0 or just WMF 3.0, but it never actually runs.
Here is the applicable entry from the appintenteval.log, and i've bolded the line where it shows that WMF 3.0 is not installed
ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66/12 :- Title = WMF 3.0, Direct seleted dependencies = ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558/7 title=.Net
4.0,    AppIntentEval   4/24/2014 8:20:19 AM   1768 (0x06E8)
ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66/12 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Installed, ConfigureState = NotNeeded, Title = WMF 3.0   AppIntentEval
4/24/2014 8:20:19 AM   1768 (0x06E8)
ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558/7 :- Current State = Installed, Applicability = Applicable, ResolvedState = Available, ConfigureState = NotNeeded, Title = .Net 4.0   AppIntentEval
4/24/2014 8:20:19 AM   1768 (0x06E8)
ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/Application_de66c10e-111e-4d68-95a8-5cee3f144081/13 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Installed, ConfigureState = NotNeeded, Title = WMF 3.0   AppIntentEval
4/24/2014 8:20:19 AM   1768 (0x06E8)
ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/RequiredApplication_de66c10e-111e-4d68-95a8-5cee3f144081/13 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, ConfigureState = NotNeeded, Title = ApplicationIntentPolicy
AppIntentEval   4/24/2014 8:20:19 AM   1768 (0x06E8)
and here are the entries from the AppDiscovery.log that are relevant:
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558" AND Revision = 7)"   AppDiscovery
4/24/2014 8:20:19 AM   2776 (0x0AD8)
    Performing detection of app deployment type .Net 4.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, revision 7) for system.   AppDiscovery   4/24/2014 8:20:19
AM   2776 (0x0AD8)
+++ Discovered application [AppDT Id: ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, Revision: 7]   AppDiscovery   4/24/2014 8:20:19 AM   2776 (0x0AD8)
+++ Detected app deployment type .Net 4.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, revision 7) for system.   AppDiscovery   4/24/2014 8:20:19 AM
2776 (0x0AD8)
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66" AND Revision = 12)"   AppDiscovery
4/24/2014 8:20:19 AM   2508 (0x09CC)
    Performing detection of app deployment type WMF 3.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, revision 12) for system.   AppDiscovery   4/24/2014 8:20:19
AM   2508 (0x09CC)
+++ Application not discovered. [AppDT Id: ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, Revision: 12]   AppDiscovery   4/24/2014 8:20:19 AM   2508
(0x09CC)
+++ Did not detect app deployment type WMF 3.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, revision 12) for system.   AppDiscovery   4/24/2014 8:20:19 AM
2508 (0x09CC)
   ActionType - Install will use Content Id: Content_c6b448d0-7b59-4796-bb29-3f7fbfa6e70d + Content Version: 1 for AppDT "WMF 3.0" [ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66],
Revision - 12   AppDiscovery   4/24/2014 8:20:20 AM   2508 (0x09CC)
I have a 2 hour maintenance window applied to this system. From the serviceWindowManager.log:
OnIsServiceWindowAvailable called with: Runtime:7200, Type:2   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
No Service Windows exist for this type. Will check if the program can run in the All Programs window...   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
        Biggest Active Service Window has ID = {02B82DF5-3360-4BCC-8154-9258F0B856C3} having Starttime=04/24/14
08:20:00   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
            Duration is 0 days, 02 hours, 00 mins, 00 secs   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
FindBiggestMergedTimeWindow called with TimeStart=04/24/14 08:20:21 and TimeEnd=04/24/14 10:20:00   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
        Biggest Chainable Service Window for Type=1 not found   ServiceWindowManager   4/24/2014 8:20:21 AM   1768 (0x06E8)
I'm not sure what else to try next and appreciate any help anyone can offer.

Thanks. I checked that setting and i have it set to false, so i don't think that's it.
I've done a little more experimenting. I've changed my maintenance window back to 30 minutes. Prior to the MW opening, i'll run an application evaluation deployment cycle on the system. It will show the system as required WMF 3.0 but since
the MW isn't open, it won't install at the time.
When the MW opens, i'll watch the ServiceWindowManager.log and it sees that it's a 30 minute MW and that the run time is 15 minutes but it still says the program can't run:
ActiveServiceWindow has 1800 seconds left   ServiceWindowManager   4/24/2014 2:20:00 PM   2032 (0x07F0)
Program can run! Setting *canProgramRun to TRUE   ServiceWindowManager   4/24/2014 2:20:00 PM   2032 (0x07F0)
OnIsServiceWindowAvailable called with: Runtime:900, Type:6
ServiceWindowManager   4/24/2014 2:20:00 PM   2032 (0x07F0)
        Biggest Active Service Window for Type=6 not found   ServiceWindowManager   4/24/2014 2:20:00 PM   2032 (0x07F0)
Program cannot Run! Setting *canProgramRun to FALSE   ServiceWindowManager   4/24/2014 2:20:00 PM   2032 (0x07F0)
OnIsServiceWindowAvailable called with: Runtime:900, Type:2   ServiceWindowManager   4/24/2014 2:22:32 PM   816 (0x0330)
If however, i kick off another application evaluation deployment cycle on the system during the open MW, the deployment kicks off right away and finishes.
Program can run! Setting *canProgramRun to TRUE   ServiceWindowManager   4/24/2014 2:22:32 PM   2940 (0x0B7C)
OnIsServiceWindowAvailable called with: Runtime:900, Type:3   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
No Service Windows exist for this type. Will check if the program can run in the All Programs window...   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
        Biggest Active Service Window has ID = {02B82DF5-3360-4BCC-8154-9258F0B856C3} having Starttime=04/24/14 14:20:00   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
            Duration is 0 days, 00 hours, 30 mins, 00 secs   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
ActiveServiceWindow has 1571 seconds left   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
Program can run! Setting *canProgramRun to TRUE   ServiceWindowManager   4/24/2014 2:23:49 PM   816 (0x0330)
This is not the behavior i would expect. I would think that if the client knows it has a pending application deployment that is required, when the MW opened up, it would start the install immediately or close to the beginning of the MW. It shouldn't
need to have an application evaluation deployment cycle kicked off during the MW.

"Add-On Software" CD for LV6.1 won't install.

Following NI Forums Knight Dan Knutson's advice to install a LV version earlier than 8.5 in order to convert 40 VIs written in LV5.1 to LV8.5.1, I attempted to install LabVIEW 6.1. There is a CD that won't install. It is the "Add-On Software" LV6.1 CD. The CD does not autoinstall when it's put in the CD drive. When I right-click the Autorun > Install icon, the installer returns, "Error. Installation failed." The CD has LabVIEW, and Measurement Studio folders, an autorun setup information file and and Eagle icon. There is no setup.exe on the installation CD main directory. Could anyone please suggest how to install the LabVIEW and Measurement Studio folders?
I tried to go into the individual sub-folders of the "Add-On Software" CD, but when I reached LabVIEW\Enterprise\SPC\Install\disk1\ and click Setup.exe, I get "Setup Installation Error. Setup has detected that UnInstallShield is in use. Please close UnInstallShield and restart Setup. Error 432." Running MSCONFIG to remove isUninst.exe from the Startup folder fails because no IsUninst.exe application runs on startup, rebooting does not help, it's not an Administrator issue because my account already has Administrator privileges, and searching the Internet does not give useful clues.
Could an expert please solve either of these two problems?
Thanks,
BenCh01

Hello All,
I may be confused on the topic of a Compact RIO integrated with LabVIEW version 5.1? Version 5.1 pre-dates the release of Compact RIO hardware. The Compact RIO platform uses neither NI-DAQmx, nor the Traditional NI-DAQ driver, it is built on a separate driver platform in NI-RIO. May I inquire as to why version 8.5.1 was selected for the upgrade process, and not the latest version in 2009 SP1?
As you may have experienced already, the process of upgrading across 10 releases of the LabVIEW development environment may present issues, as the environment has been significantly changed through the years. For additional information on the upgrade process please see the following information:
How to Upgrade or Revert a VI to a Different Version of LabVIEW
http://zone.ni.com/devzone/cda/tut/p/id/8387
Upgrading to the Latest Version of LabVIEW
http://zone.ni.com/devzone/cda/tut/p/id/7417
More realistically, does this application contain highly customized code, or functions, that are not integrated into the newer platform? With regard to hardware integration, if you intend on working with the Compact RIO platform, you will be working to develop brand new code using the LabVIEW Real-Time (and possibly LabVIEW FPGA) Module, as any code written in LabVIEW 5.1 will not support the Compact RIO platform. With respect to any additional hardware that may have been used, you will need to verify the device support in either the NI-DAQmx or Traditional DAQ releases, this information can be found at http://www.ni.com/support. I believe time spent developing on a supported platform, for the new hardware set, may be more effective than looking to directly upgrade the 5.1 code.
Please post any additional questions you may have.
Patrick Corcoran
Application Engineering Specialist | Control
National Instruments

Hf901-00001 won't install at all on some instances.

Hi,
We have multiple servers with CF 9.0.1 installed, all with the multiple servers configuration and all with multiple instances.
Yesterday I started patching to hf901-00001 (http://kb2.adobe.com/cps/890/cpsid_89094.html). It worked properly on 30 some instances over 4 servers but for a few instances on one server it just won't install.
The server in question has 7 instances + 1 main cfusion instance. The patching worked fine for 4 of them, but with the others it blew up the CF admin and I had to restore my CFIDE from a backup.
Right now I am trying to get cfusion up-to-date here's what I see.
Server Product: ColdFusion
Version: 9,0,1,274733
Edition: Enterprise
Serial Number ******
Operating System: Windows 2003 OS Version 5.2
Adobe Driver Version: 4.0 (Build 0005)
JVM Details Java Version: 1.6.0_17
Java Vendor: Sun Microsystems Inc.
When I try to update with the hf901-00001.jar file, everything seems to work as it should. I get the "For the hotfix to get applied, you must restart the ColdFusion Service." so I restart Macromedia JRun CFusion Server and it starts up fine.
However when I go back to the CFAdmin I still see
Version 9,0,1,274733.
I don't see Update Level /C:/JRun4/servers/CF_Academic2a/cfusion.ear/cfusion.war/WEB-INF/cfusion/lib/updates/hf901 -00001.jar
So I assume that patch isn't going through. If I look in C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib\updates\ I can see the hf901-00001.jar files though. At this point if I proceed with the rest of the patching (Copying CFIDE, WEB-INF, etc) the CFAdmin starts throwing error --- class def not found on some critical CF parts.
As anyone else had issue with this patch or have any suggestion as what to try next? Any pointers would be greatly appreciated.

Charlie,
Thanks for the reply, ok going to double check everything point by point. Going to use my main cfusion instance for my testing.
Before patching:
My CFIDE is mapped to C:\inetpub\wwwroot\CFIDE (from the mapping section)
C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib\updates has only one file empty.txt
ColdFusion version is 9,0,1,27473 from the CF administrator information section.
Version confirmed by dumping server.coldfusion.productversion (9,0,1,27473)
Patching process:
Using hf901-00001.jar from update (http://kb2.adobe.com/cps/890/cpsid_89094.html#main_ColdFusion_9_0_1)
Successful, I get "For the hotfix to get applied, you must restart the ColdFusion Service"
Restarting "Macromedia JRun CFusion Server"
C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib\updates\ now has 2 files, empty.txt and hf901-00001.jar
Checking log for the restart in C:\JRun4\logs\cfusion-out.log, everything start up as it should but there's an error. No details though, see dump below.
Starting Macromedia JRun 4.0 (Build 108858), cfusion server
02/25 09:18:42 info JRun Naming Service listening on *:2904
02/25 09:18:43 info No JDBC data sources have been configured for this server (see jrun-resources.xml)
02/25 09:18:43 info JRun Web Server listening on *:8300
02/25 09:18:43 info JRun Proxy Server listening on *:51020
02/25 09:18:43 info Deploying enterprise application "cfusion-ear" from: file:/C:/JRun4/servers/cfusion/cfusion-ear/
02/25 09:18:43 info Deploying web application "Adobe ColdFusion 9" from: file:/C:/JRun4/servers/cfusion/cfusion-ear/
Ignoring invalid file in updates directory: hf901-00001.jar
02/25 09:18:45 INFO License Service: Flex 1.5 CF Edition enabled
02/25 09:18:45 INFO Starting Flex 1.5 CF Edition
02/25 09:18:45 user FusionReactor: FusionReactor Rev. 3.5.0, Build: FusionReactor.74.14844
02/25 09:18:45 user FusionReactor: Initializing configuration
At this point if I continue with the manual steps and copy the file in CFIDE and WEB-INF it break the instance and I can't access it without restoring from a backup. (ClassDefNotFound errors). So the jar isn't being applied for some reason, the log is quiet as to why it's rejecting the file or think it's invalid. It's the same file used to patch the other instances. I suspected a corrupted jar and redownloaded it, same result for those 4 instances only after I patched another production server, our development, acceptance and lab servers the same way.
One thing that I noticed, the one that did patch correctly have chf9000001.jar in their /lib/updates directory which is hotfix1 for CF 9.0.0. I am under CF 9.0.1 so it shouldn't be required right? Not sure why it's missing from the cfusion instance.
I tried copying chf9000001.jar and restarted and it shows up as my update level in CFAdmin. I still get the invalid file error for hf901-00001.jar though.
I never installed Cumulative Hotfix 1 (CHF1) for ColdFusion 9.0.1 (http://kb2.adobe.com/cps/862/cpsid_86263.html) as Adobe only recommend it if you experience one or more of the issue listed.
Other points I checked following your post:
1) neo-runtime.xml does have <var name='/CFIDE'><string>C:\inetpub\wwwroot\CFIDE</string></var> so as far as I can tell I am using the correct /CFIDE
2) You say "Or are you using the external web server (IIS or Apache)? If trying one, what happens if you try the other?"
I am using IIS default website to access it (it's currently bound to port 8080). How do I try the other? In JRun Launcher I see my Web port as 8300 for cfusion but if I go to http://localhost:8300/ I get a blank site (it just shows Index of /)
The only thing I have to go on is that the jar isn't loaded as per the log, but there is no error or anything so I am kind of at a lost as to what I can try next.

"LabVIEW Runtime won't install"

Similar Messages

Maybe you are looking for