Installing LabView 8.2 runtime engine on Windows 7 64-bit

We have a product built on LabView 8.2
For a couple of years, we have been distributing this product on Windows 7 64-bit systems with no trouble at all.
Today, we received a customer complaint indicating that the LabView 8.2 runtime engine cannot be installed on Windows 7 64-bit.
Our verification team has confirmed this to be true.
Interestingly, we have several Windows 7 64-bit computers with the LabView 8.2 runtime engine already installed.
How is this possible?
Has something changed in Windows that no longer allows the LabView 8.2 runtime engine?
We are confused by the fact that this appears to be a new problem and the runtime engine did, at some point, install correctly on multiple Windows 7 64-bti computers.
Any thoughts would be extremely appreciated.
Attachments:
lv_install_error.jpg ‏22 KB

No, i dont think the 8.2 installer is corrupt, but it uses the Windows Installer service, which according the image has some problems. Maybe it recently updated? It's incompatible with that old installer so you need to downgrade it? It's corrupted and needs some fix?
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Similar Messages

Installing LabView 6.1 Runtime on Win 7 64 bit

Hi,
I have LabView 6.1 based program which I want to install and run in Windows 7 64bit. I tried to install LabView 6.1 Run time Engine. It looks like it starts loading then hang on for long time.
What is the issue here?
Regards

Fair point, I hadn't forgotten XP Mode, but simply chose not to suggest it as a solution at this point. Not all versions of Windows 7 support XP Mode, so that isn't necessarily an option for the OP.
NI-DAQmx devices aren't supported in virtualised OSes like XP Mode, this is due to the nature of USB communication handling in virtualised OSes. Typically, they are optimised for HMI devices or Mass storage, but not higher performance devices such as USB DAQ. We don't know if the OPs application requires USB, another reason that XP Mode isn't necessarily a suitable option to suggest at this point.
Another noted issue with XP Mode is that it can brick certain USB devices for, as yet, unknown reasons. This is not limited to NI Hardware specifically, but with USB devices in general that do not fall under the HMI or MS categories and is a problem that Microsoft are actively working on. So rather than suggesting the use of XP Mode that could potentially cause problems with his hardware, if he is using any (which we don't know at this point), it is better to ask some more questions about the particular application and the OPs needs.
If the information from my last post was sufficient for the OP, then he/she needn't reply, if however, they require more information, then we can begin to explore other solutions such as XP Mode if it's appropriate.
When using older versions of LabVIEW, it is also a good idea to ascertain why/if an older version is required. It is possible to open VIs from certain older LabVIEW versions in current versions, which I'm sure you are aware, so it might be that the OP isn't aware of this and might be under the impression that he must use the same version to work with his VIs. Which isn't the case. Hence my last question regarding why LabVIEW 6.1 is required.
For the sake of the post, this information is available here. You can open LV 6.1 VIs in LV 2011.
I am completely aware that a simple search would have turned out those resources, that's exactly what I did to get the links to them. However, not all LabVIEW users are aware that there are extra sources of information available by searching ni.com in addition to the forum search, so it could be helpful to point this out just in case. Not all of the information I have sourced would necessarily be found by simply using the forum search bar, it might, but then again it might not.
Yes, I agree with you that there are other posts asking similar questions and Yes, I agree that in this instance searching for the issue at hand would probably have negated the need for this post to have been made, but whilst it is true that the OP might not have searched to see if he/she could resolve his/her issue, at least now he/she is aware of the resources that are available to him/her and can continue to be proficient and successful in the future.
hants1984: Having just read your last post, you should find the information you require in the above links. The question on LabVIEW 8.5 in Windows 7 64 bit has come up in the past a lot on these forums, the official answer is no. LabVIEW 8.5 is not supported in Win7 64, however, as discussed in the above post, XP Mode may be an appropriate solution for you.
Oli
LabVIEW Student Ambassador
National Instruments UK

Getting "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine

I am getting a "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine. I already tried running setup.exe as an administrator with the same results. I have Microsoft .NET Framework 4.5.1 installed on the affected machine. Could this be the cause of this issue? Or does someone know the root cause of such error?
Solved!
Go to Solution.

Hi - are you getting it at the start of installation, during or after 100% progress has finished?
Is it just LabVIEW you're installing, or is it drivers too, in which case, what was the last large package that was installing at the time?
This could be caused by the NVIDIA chipset driver :
https://decibel.ni.com/content/message/46299?tstart=-130
Thanks
Sacha
// it takes almost no time to rate an answer

RW-50004 error when installing Oracle EBS 12.1.1 on Windows 32 bit, 2003

Hi All
I am installing Oracle EBS 12.1.1 for Windows 32 bit on a Windows 2003 server, my pre-requisite checks have gone through successfully when checked by the oracle ebs installer.
However during the installation process i get RW-50004 error and the installation stops, the log file seems to have the following last entries
Mon 07/04/2011
05:05 PM
1 file(s) copied.
1 file(s) copied.
1 file(s) copied.
"afmkinit.cmd exiting with status 0"
ERRORCODE = 0 ERRORCODE_END
.end std out.
.end err out.
Skipping Profile Phase
Skipping Apply Phase
adcvmlog.xml renamed to C:\oracle\VIS\db\tech_st\11.1.0\appsutil\log\VIS_99a4659\adcvmlog.xml.07041705
[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:
<filename> <phase> <return code where appropriate>
[SETUP PHASE]
AutoConfig could not successfully execute the following scripts:
Directory: C:\oracle\VIS\db\tech_st\11.1.0\appsutil\install\VIS_99a4659
adsvdlsn.cmd INSTE8_SETUP 9020
AutoConfig is exiting with status 1
RC-50014: Fatal: Execution of AutoConfig was failed
Raised by oracle.apps.ad.clone.ApplyDBTechStack
Can some one please help me on what I am missing or how can i correct this. Thank you.

adsvdlsn.cmd INSTE8_SETUP 9020Search AutoConfig log file for adsvdlsn.cmd and you should find more details about the error.
Please see if (Rapidwiz R12 Failed at 66% with error: RW-50004: Error code received when running external process. [ID 418109.1]) is applicable.
Also, please run md5sum as per (MD5 Checksums for R12.1.1 Rapid Install Media (Doc ID 802195.1)) to verify the integrity of the stage area directory.
Thanks,
Hussein

LabVIEW Runtime engine on Windows Embedded Standard 7 P 32/64 bit?

Did anyone ever try to install and run LabVIEW Runtime engine (2011 or later) on Windows Embedded Standard 7 P 32/64 bit?
I am trying to figure out if this will work, for example on a Beckhoff CX5120 embedded PC. I will need to have some simple TCP/IP communication in order to exchange information with another PC, but nothing else, i.e. drivers, etc...
I hope someone tried to do this already. I just don't have the right hardware right now to check it out.
Solved!
Go to Solution.

As NI sells touch panels with WES7 installed here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/210551 it's pretty safe to assume they've used the RTE on WES7.
But yes, it's been done.

LabVIEW constantly tries to install CVI 8.1 runtime engine

I am testing LabVIEW on a VISTA laptop before we convert all our PC's from 2000 to VISTA. Software install looked OK including NI-DAQmx 8.72, I plugged my cDAQ-9172 in and MAX saw it correctly. As soon as I started a test panel the "CVI 8.1 Runtime Engine" window popped up and it configured CVI 8.1 runtime and asked me to restart. I restarted and the exact same thing happened, also happens if I start LabVIEW.
I tried NI-DAQmx 8.80 updated my installer from Microsoft and the problem still exists. Any ideas?
Thanks in advance
Tom
Solved!
Go to Solution.

After uninstalling and reinstalling LabVIEW and all the drivers several times I found that version 2.5 of the 488.2 was the problem. I did a complete removal, clean, and reinstall with LabVIEW 8.2.1, NI-DAQmx 8.8 and NI-488.2 2.6 in a Vista business version HP laptop. So far everything is playing nice.

Will labview 6.1 runtime engine install on a win NT 3.5.1 system??

I got an error when I tried to run the .exe file for the runtime install. The .exe file was downloaded from the software update section.

Similar to the development versions of LabVIEW, the run-time engine is only supported on NT 4.0. You would need to update your system before installing this software.
J.R. Allen

I can not open Excel (97, 2000, or 2003) spreadsheet in Win98 OS PC using LabVIEW 7.0 Runtime Engine

Hi,
I have a problem opening an Excel spreadsheet by a LabVIEW application that is using Runtime Engine 7.0 in a Windows 98 OS environment .
I tried LabVIEW 7.1, it will not install on Win98. Meanwhile, I installed Excel 97 and 2000 (Excel 2003 does not install on Win98) and tried to open the spreadsheet, no luck with any combination.
Same code can open the spreadsheet in a WinXP OS, RTE 7.0, Excel 2000/2003 environment.
What can I do? Any advise?
Regards,
LVLV

Hi,
I did some experiment, I found out that Run-Time Engine 7.0 running executable generated at LabVIEW 7.0 environment (code written in LabVIEW 7.1 but save as 7.0) cannot open Excel 2000 files. If I replace Excel 2000 with Excel 2003 application on my pc, the executable code will open the Excel file (Run-Time Engine 7.0 works with Excel 2003).
Is the Excel 2003 and higher versions will only work with Run-Time Engine 7.0 and higher code?
How can I make executables using Run-Time Engine 7.0 work with Excel 2000 (Windows 98 operating system)??? (I cannot change Excel and Run-Time Engine and OS versions due to limitations, how can I work with what I have?).
Thanks for your help.
Regards,
LVLV

Trouble installing LabView 7.1 / 8.0 under Windows 2000

When attempting to install LabView 7.1 on a PC running Windows 2000,
the installer produces the message
"Fatal Error. Unhandled MSI Error"
and fails.
I believe my PC account has full administrative privileges; furthermore, the Windows Installer
is version 3.1.4000.1823, ie. it should be up-to-date.
When attempting to install LabView 8.0 instead, the installer fails with the
message "Fatal Error!! Required NIPathsDir property LV80DIR is undefined".
Strangely enough, both installers appear to work on a different, but similarily configured PC;
however, I am unable to see what, if any, configuration differences there may be.
Ideas, anyone?

[quote]
didn't purchase the SSP, so I guess I can't even call NI for Installation assistance.
[/quote]
Sorry I cant help with the installation issue itself, but this part is incorrect. Installation assistance is technically free. SSP is used for development questions/ issues. If it will not install at all this is a valid reason to contact NIs engineers.

Error installing MaxDB 7.6.03.09 on windows 32 bit on NW70 SR2 sapinst

MaxDB experts,
Hello. I am trying to install SAP NW70SR2 (JAVA AS) on MaxDB 7.6.03.09 with windows 32 bit OS. Brand new install, JAVA AS central system.
Our problem is in the SAPINST phase:
Install database server software
I see this in the sapinst.log file:
starting installation phase of package Base 7.6.03.09 32 bit
ERR: InstallRegistry::newPackage(): can't add Package "Base" -> "c:/sapdb/programs": already exists!
installation exited abnormally at Th, Apr 09, 2009 at 16:19:41
ERROR      2009-04-09 16:19:41 [iaxxinscbk.cpp:282]
           abortInstallation
MDB-07020 The database installer reported an error. Some database applications are probably still running. Check the log file sdbinst.log.
And this is in the bottom of the sdbinst.log file
starting installation phase of package Base 7.6.03.09 32 bit
ERR: InstallRegistry::newPackage(): can't add Package "Base" -> "c:/sapdb/programs": already exists!
installation exited abnormally at Th, Apr 09, 2009 at 16:19:41
The sdbinst.log has lots of other interesting info:
This is the top of the file:
Installation of MaxDB
+     ***********************+
starting installation Th, Apr 09, 2009 at 16:18:56
operating system: Windows I386 NT 5.1 Service Pack 3
callers working directory: C:/Program Files/sapinst_instdir/NW04S/SYSTEM/ADA/CENTRAL/AS
installer directory: S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386
archive directory: S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386
starting preparing phase of package Base 7.6.03.09 32 bit
getInstalledReleasesWin(): wrong version format
checking interferences to other packages... ok
I'm not sure why there is a version info problem.
This is a windows PC I'm trying to put this on. It's 32 bit so that is why I had to get the SR2 DVDs. The SR3 DVD won't let you install via 32 bit OS.
I downloaded all the software from OSS marketplace and some from our delivered DVDs:
We have these DVDs
32 BIT BS_2005_SR2_SAP_Installation_Master 51033208
32 BIT NW_7.0_SR2_Kernel_WINDOWS__LNX_X86 51033262
NW 7.0 SR2 SAP Installation Export 51032246
NW 7.0 SR2 SP09 Java based SW Comp 51032257
I pulled this down off the marketplace (in the NW70SR3 area)
32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10
I've searched all through OSS/SDN for someone who has this same issue. All our other systems are AIX/oracle so trouble-shooting MaxDB is completely new to me.
Can anyone point me into the right direction to get this figured out? I'm tried just re-running the install, same error. And removing the c:/sapdb/programs, no good.
Thanks!
Nick

Natalia,
Here is the entire Install log for MaxDB. Also remember that this was called as part of an SAP system install:
MaxDBServer_install-10.04.2009-10.05.log
INSTALLER_INFO: Version = 7.6.03 Build 009-123-163-622
INSTALLER_INFO: Changelist = 163622
INSTALLER_INFO: MakeId = 267230
INSTALLER_INFO: Type = kit
SYS_INFO: Host name = DGW58J1L
SYS_INFO: System = Windows
SYS_INFO: Architecture = I386
SYS_INFO: Version = NT 5.1
SYS_INFO: Subversion = Service Pack 3
CALL: SDBINST -indep_prog C:\sapdb\programs -indep_data C:\sapdb\data -depend C:\sapdb\CEL\db -profile Server -b
STDOUT:
     Installation of MaxDB
STDOUT:      ***********************
STDOUT: starting installation Fr, Apr 10, 2009 at 10:04:43
STDOUT: operating system: Windows I386 NT 5.1 Service Pack 3
STDOUT: callers working directory: C:/Program Files/sapinst_instdir/NW04S/SYSTEM/ADA/CENTRAL/AS
STDOUT: installer directory: S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386
STDOUT: archive directory: S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386
STDOUT:
MSG: debug package SDBBAS.SDB is valid
MSG: debug package SDBKRN.SDB is valid
MSG: debug package SDBUTL.SDB is valid
STDOUT:
starting preparing phase of package Base 7.6.03.09 32 bit
STDOUT: -
MSG: service "sql6" in "C:/WINDOWS/system32/drivers/etc/services" found
MSG: service "sapdbni72" in "C:/WINDOWS/system32/drivers/etc/services" found
MSG: InstallRegistry: space check ok: 127249572 kb on C: (156288320 kb total) available
MSG: install registry successfully locked
MSG: read 12 PACKAGES
MSG: net registry size = 121301 bytes
MSG: InstallRegistry: reserved 1024 kb disk space
STDOUT: checking interferences to other packages... STDOUT: ok
STDOUT: collecting data finished:
STDOUT: independent data path: c:/sapdb/data
STDOUT: independent program path: c:/sapdb/programs
STDOUT: start extraction test run of "S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386/SDBBAS.TGZ"
STDOUT:
package Base successfully checked
STDOUT:
starting preparing phase of package SQLDBC 7.6.03.09 32 bit
STDOUT: -
WRN: try to install release "7.6.03.09" over existing "7.6.5.9"
MSG: update test: installed release newer
MSG: update from "7.6.5.9" to "7.6.03.09" not allowed
STDERR: cannot downgrade package
STDOUT: skipping package
STDOUT:
starting preparing phase of package SQLDBC 76 7.6.03.09 32 bit
STDOUT: -
STDOUT: checking interferences to other packages... STDOUT: ok
STDOUT: collecting data finished:
STDOUT: dbc path: c:/sapdb/programs
STDOUT: start extraction test run of "S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386/SQLDBC76.TGZ"
STDOUT:
package SQLDBC 76 successfully checked
STDOUT:
starting preparing phase of package Fastload API 7.6.03.09 32 bit
STDOUT: -
STDOUT: checking interferences to other packages... STDOUT: ok
STDOUT: collecting data finished:
STDOUT: fastload path: c:/sapdb/programs
STDOUT: start extraction test run of "S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386/FASTLOAD.TGZ"
STDOUT:
package Fastload API successfully checked
STDOUT:
starting preparing phase of package PCR 7104 7.1.04.45
STDOUT: -
STDOUT: checking interferences to other packages... STDOUT: ok
STDOUT: collecting data finished:
STDOUT: independent program path: c:/sapdb/programs
STDOUT: start extraction test run of "S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386/PCR7104.TGZ"
STDOUT:
package PCR 7104 successfully checked
STDOUT:
starting preparing phase of package PCR 7300 7.3.00.59
STDOUT: -
STDOUT: checking interferences to other packages... STDOUT: ok
STDOUT: collecting data finished:
STDOUT: precompiler 7300 path: c:/sapdb/programs
STDOUT: start extraction test run of "S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386/PCR7300.TGZ"
STDOUT:
package PCR 7300 successfully checked
STDOUT:
starting preparing phase of package PCR 7301 7.3.01.22
STDOUT: -
STDOUT: checking interferences to other packages... STDOUT: ok
STDOUT: collecting data finished:
STDOUT: precompiler 7301 path: c:/sapdb/programs
STDOUT: start extraction test run of "S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386/PCR7301.TGZ"
STDOUT:
package PCR 7301 successfully checked
STDOUT:
starting preparing phase of package PCR 7403 7.4.03.49 32 bit
STDOUT: -
STDOUT: checking interferences to other packages... STDOUT: ok
STDOUT: collecting data finished:
STDOUT: precompiler 7403 path: c:/sapdb/programs
STDOUT: start extraction test run of "S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386/PCR7403.TGZ"
STDOUT:
package PCR 7403 successfully checked
STDOUT:
starting preparing phase of package PCR 7500 7.5.00.46 32 bit
STDOUT: -
STDOUT: checking interferences to other packages... STDOUT: ok
STDOUT: collecting data finished:
STDOUT: precompiler 7500 path: c:/sapdb/programs
STDOUT: start extraction test run of "S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386/PCR7500.TGZ"
STDOUT:
package PCR 7500 successfully checked
STDOUT:
starting preparing phase of package SAP Utilities 7.6.03.09 32 bit
STDOUT: -
STDOUT: checking interferences to other packages... STDOUT: ok
STDOUT: collecting data finished:
STDOUT: : c:/sapdb/data
STDOUT: independent program path: c:/sapdb/programs
STDOUT: start extraction test run of "S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386/SAPUTL.TGZ"
STDOUT:
package SAP Utilities successfully checked
STDOUT:
starting preparing phase of package DB Analyzer 7.6.03.09 32 bit
STDOUT: -
WRN: try to install release "7.6.03.09" over existing "7.6.5.9"
MSG: update test: installed release newer
MSG: update from "7.6.5.9" to "7.6.03.09" not allowed
STDERR: cannot downgrade package
STDOUT: skipping package
STDOUT:
starting preparing phase of package JDBC 7.6.03.03
STDOUT: -
STDERR: cannot downgrade package
STDOUT: skipping package
STDOUT:
starting preparing phase of package Server Utilities 7.6.03.09 32 bit
STDOUT: -
WRN: try to install release "7.6.03.09" over existing "7.6.5.9"
MSG: update test: installed release newer
MSG: update from "7.6.5.9" to "7.6.03.09" not allowed
STDERR: cannot downgrade package
STDOUT: skipping package
STDOUT:
starting preparing phase of package Database Kernel 7.6.03.09 32 bit
STDOUT: -
STDOUT: checking interferences to other packages... STDOUT: ok
STDOUT: collecting data finished:
STDOUT: dependent path: c:/sapdb/cel/db
STDOUT: start extraction test run of "S:/NW70SR3-MAXDB-INSTALL/Extracts/32 BIT RDBMS_MAXDB_7.6.03_Build_09 51033492_10/DATA_UNITS/MAXDB_WINDOWS_I386/SDBKRN.TGZ"
STDOUT:
package Database Kernel successfully checked
STDOUT:
starting preparing phase of package Redist Python 7.6.03.09 32 bit
STDOUT: -
WRN: try to install release "7.6.03.09" over existing "7.6.5.9"
MSG: update test: installed release newer
MSG: update from "7.6.5.9" to "7.6.03.09" not allowed
STDERR: cannot downgrade package
STDOUT: skipping package
STDOUT:
starting preparing phase of package Loader 7.6.03.09 32 bit
STDOUT: -
WRN: try to install release "7.6.03.09" over existing "7.6.5.9"
MSG: update test: installed release newer
MSG: update from "7.6.5.9" to "7.6.03.09" not allowed
STDERR: cannot downgrade package
STDOUT: skipping package
STDOUT:
starting preparing phase of package Messages MSG 0.5603
STDOUT: -
STDERR: cannot downgrade package
STDOUT: skipping package
STDOUT:
starting preparing phase of package ODBC 7.6.03.09 32 bit
STDOUT: -
WRN: try to install release "7.6.03.09" over existing "7.6.5.9"
MSG: update test: installed release newer
MSG: update from "7.6.5.9" to "7.6.03.09" not allowed
STDERR: cannot downgrade package
STDOUT: skipping package
STDOUT: checking filesystem "C:"... free disk space ok
MSG: available = 127248680 kb
MSG: needed = 339145 kb
STDOUT:
starting installation phase of package Base 7.6.03.09 32 bit
STDOUT: -
STDERR: ERR: InstallRegistry::newPackage(): can't add Package "Base" -> "c:/sapdb/programs": already exists!
STDERR: installation exited abnormally at Fr, Apr 10, 2009 at 10:05:29MSG: packagedata of package SQLDBC not changed
MSG: packagedata of package DB Analyzer not changed
MSG: packagedata of package JDBC not changed
MSG: packagedata of package Server Utilities not changed
MSG: packagedata of package Redist Python not changed
MSG: packagedata of package Loader not changed
MSG: packagedata of package Messages not changed
MSG: packagedata of package ODBC not changed
MSG: writing 12 packages
MSG: net install registry size = 121301 bytes
MSG: wrote install registry (141250 bytes)
MSG: install registry successfully unlocked

Installing ofm_soa_generic_11.1.1.6.0_disk1_1of2 on windows 32 bit

Hi Guys,
Can any one installed installing ofm_soa_generic_11.1.1.6.0_disk1_1of2 on XP 32 bit . If installed means plz help me.
Regards,
Venkat

Pl do not post duplicates - soa installation on XP 32 bit

Can 64-bit runtime engine run a 32-bit vi?

I have an application which is built with LabVIEW 2011 (64-bit) and install on a 64-bit OS machine, and it will call some vi which I think is also writen by 64-bit LabVIEW, now I want to modify a vi, but I only have the 32-bit LabVIEW version, and it will show load error when I run the application, is the 64-bit run-time engine cannot load the 32-bit vi? If yes, then anyone can help me to transform the 32-bit vi to 64-bit (2011)?
I have attached my vi, thanks in advance.
James
email : [email protected]
Attachments:
tcp_driver.vi ‏17 KB

labviewmis wrote:
...I just want to transform my 32-bit vi to 64-it so that I can try it on the 64-bit machine, hope this will make things clear.
You can donwload and install the 64bit LabVIEW version and activate it with the same code you currently have for the 32 bit version. They both can coexist on the same machine. USe whatever is currently needed.
LabVIEW Champion . Do more with less code and in less time .

How to Install em12c (12.1.0.3) on windows 64 bit

Hi Guys,
I am trying to install 12 c 12.1.0.3 on windows 2008 R2 server. The server has met the all prerequisites. But when I am trying to launch the installer it will disappear immediately without any error message. I check the installation log file there is no error about anything:
LOGFILE:
Using paramFile: D:\temp\12cCloud\em12103_winx64_disk1\oms\Disk1\install\oraparam.ini
Checking swap space: must be greater than 500 MB.   Actual 3422 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 65536    Passed
Any idea why it is happening ?
Regards,

Hi, can you open an SR for this issue and share the number. Lets check few basic things:
a) can you make sure that all the zips are downloaded from OTN have correct byte and checksum information
b) Can you make sure that you unzipped all these zips files in a single folder
c) After unzipping can you check if you have following folders created ( not these folder are for linux but they will be same on windows) -
install      libskgxn      plugins     response     stage     WT.zip
jdk     oms     runInstaller      wls
d) Can you invoke setup.exe -debug
then look at the logs from -
C:\Users\aime\AppData\LocalTemp\2\OraInstall2013-07-09_04-10-59AM   ( for windows it will be orInstaller.err and log )
Since there is nothing in logs, opening an Sr will help us to have a web conference with you and identify the issue.

BI Composer install in OBIEE 11.1.1.6 (windows 32 bit)

Hi, I'm trying to test out the BI composer functionality in 11.1.1.6 on my laptop. After following the installation instructions, I'm no longer able to log in to OBIEE at all - start getting 404 errors.
Has anyone gotten BI Composer to work on 11.1.1.6?
Thanks,
Scott

Hi Scott,
Yes, I have got it working. High level steps that I followed for this were
1. Stopped all BI services.
2. Extended BI domain with the oracle.bicomposer_template_11.1.1.jar template by invoking the config wizard in wlserver_10.3\common\bin.
The documentation had some issues through in this step as It says to skip some screens like 'Configure JDBC Data sources'. I noticed that the screens were populating wrong values and there were validation errors also when I try to skip it without correcting. So I had to correct these details before I went ahead.
3. Modifying the instanceconfig.xml to add the tag
<BIComposer>
<Enabled>true</Enabled>
</BIComposer>
4. Starting all the services .
5. Changing the preferences through MyAccount to use BIComposer instead of Editor.
Thank you,
Dhar

Runtime Engine installer spawns from unrelated software

Hello all,
When I run a completely unrelated app (Quickbooks timer, in case you're wondering), Windows Installer launches and attempts to install LabVIEW 7.1 runtime engine. Has anyone else encountered this, and why would it occur? Is there an easy solution besides installing the runtime engine?
Thanks

Hello CT_JIM,
We are probably seeing this behavior because your application (Quickbooks Timer) is querying Windows to confirm that all MSI installers are installed properly. In this case some part of the LabVIEW RTE must not have been installed completely and Windows is trying to correct it.
This can typically be resolved by reinstalling or repairing the RTE to fix the install.
Please let me know if you have any questions.
Regards,
Matt F
LabVIEW Run-time Engine Version 7.1 for Windows 2000/NT/XP
Keep up to date on the latest PXI news at twitter.com/pxi

Installing LabView 8.2 runtime engine on Windows 7 64-bit

Similar Messages

Maybe you are looking for