NI-VISA Runtime 4.3 Additional Installer problem

Hello,
I am using Project Explorer and I'm trying to include NI-VISA Runtime 4.3, but during the build I get a message that says:
Locate the "Activate" distribution. LabVIEW needs to copy a component installed or updated by the distribution to continue building the installer.
I don't know what the "Activate" distribution is or where to find it! Please help.
See attachments.
Message Edited by Sidd on 10-09-2008 02:02 PM
Solved!
Go to Solution.
Attachments:
additional_installers.JPG ‏87 KB
activate.jpg ‏25 KB

Thanks for the suggestion but I solved the problem a different way. I downloaded NI-VISA Run-time 4.3 from http://joule.ni.com/nidu/cds/view/p/id/989/lang/en then extracted it to a folder. I pointed Project Explorer to this folder and it found it properly.
I was then able to build the project successfully.
Sidd

Similar Messages

Runtime Error building Installer with NI-VISA Runtime

Greetings, I'm getting this error whenever I check the "NI-VISA Runtime" option in the installer app builder.
Everything builds fine when I check only the Runtime Engine. Shown below is what causes the RUNTIME ERROR and closes Labview Unexpectedly.
Any help you could provide would be very much appreciated.
Regards,
JD

Hi JD,
This is a relatively common error with the Application Builder that can happen for several different reasons, namely registry keys pointing to installations that no longer exist. The easiest way to identify the problem is to get detailed information about the installer build. Here are directions:
LabVIEW has the
ability to create a very detailed log of the events that occur when
building an application or installer. To enable this feature, open up
the LabVIEW.ini file and copy "CDK.EnableLog=true" to the bottom
of the file. Save the changes and close the ini file. The LabVIEW.ini
file is usually located in C:\Program Files\National
Instruments\LabVIEW X.X
Enabling this feature will create a log file in the %temp% directory of your computer (%...% means a computer variable) .
To
find out where this temp directory is located, go to Start>>Run.
Type in "cmd". Then type "set". This will return all of your computer's
variable names.
Look for TEMP in the list of variable names. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp".
Navigate to this directory using Windows Explorer.
You
should see a file named "Name.log" where "name" is the name of your
build specification. For example, you might see "My Installer.log" if
the name of your build specification is "My Installer".
This will give you a more detailed log of the attempted build and, if I'm correct about why this particular build failed, show you which installer is expected at that registry. If the registry points to a directory without the necessary installer (i.e. VISA), simply delete the registry and allow the App Builder to prompt you to to point to the correct location.
Michael K.
| Michael K | Project Manager | LabVIEW R&D | National Instruments |

Missing installer component NI-VISA Runtime

We use the LabWindows/CVI 2010 Version 10.0.0 (360) and have installed the new runtime from the installer package 5.0.3.31.
With different projects on different computers we have the same problem: The NI-VISA runtime can not be included in the installation package. With older projects which have been already distributed we get the error message when opening the tab "Drivers & Components" and click on the red entry for the visa runtime: "This component is not installed on this system, and cannot be included in distributions built on this machine". Reinstallation of the NI-VISA runtime does not help. The installation is visible in the MDF File and the registry (distributions and products). With a new project the entry NI-VISA runtime does not appear on the "Drivers & Comnponents" tab.
What went wrong? We are not able to create any distribution at this moment.
Solved!
Go to Solution.
Attachments:
ScreenInstallerError.jpg ‏334 KB

The items shown in the Drivers & Components tab are enumerated from the contents of the <program files>\National Instruments\Shared\MDF\Manifests directory. If you have NI-VISA 5.0.3 installed, you should have a file in that directory named 'NI-VISA Runtime 5.0.3 {85BA3FCF-AA00-4151-B97D-84A221E8198A}.xml'. From your experience, I would guess that maybe this file is somehow missing. That would be especially strange, given that you have uninstalled and reinstalled, but it seems to be the most logical explanation. I am attaching a zipped copy of that file here as a replacement, in case you are missing it. If you already have the file, or replacing it does not solve your problem, it will be handy to look at the debug build log. You should attempt to build the distribution, then after it prompts you and you abort, look for the file <user temp dir>\distBuildDbg.log and post it in your reply.
Mert A.
National Instruments
Attachments:
NI-VISA Runtime 5.0.3 {85BA3FCF-AA00-4151-B97D-84A221E8198A}.zip ‏5 KB

Runtime Installation Problem

I'm unable to install the latest runtime to a new installation of Vista 32bit..
(1) When running the online installer I get an error msg:
"This installation package could not be opened. Verify the package exists...."
(2) When running the offline installer I get the message:
"Error applying transform...."
Having read the various FAQ's and advice on this forum I have used Windows Installer Cleanup to confirm that there is not a failed partial install, and have used regedit likewise.
I previously installed the runtime on this same machine but with Vista 64 bit installed, and it worked normally.
Any advice would be gratefully received.

This seems to be a similar issue as discussed in bug:
http://bugs.sun.com/view_bug.do?bug_id=6542954
For Vista users:
Workaround is to look out for .msi file in the location mentioned below:
C:\Users\"username"\AppData\Local Data\Sun\Java
Inside the Java folder, look for a folder that corresponds to the version of Java being installed, such as "jre1.6.0_02" and open it. Run the .msi inside this folder to complete the installation.

Microsoft Visual C++ runtime error when building installer

I'm trying to build an installer for a very simple VI I've created in 8.2. Before the build is complete I get a Microsoft Visual C++ runtime error message pointing towards the labview.exe file. I've already tried re-installing LabVIEW and deleting older versions of the LabVIEW Runtime engines with no luck. I recently upgraded my system from LabVIEW 6.1 and I'm using Windows XP. Any suggestions?
Thanks.
LabVIEW 2012 - Windows 7
CLAD

I included waveform storage, runtime engine 8.2, ni-visa-runtime and ni-serial3.1. I tried to create a setup.exe by installer on an other pc. But it's completely the same behavior afterwards. I attached the error message. This message appears after I choose the path and continue the setup. It's the question which file is meaning.
I tried to create a setup.exe by installer without any additional.
The strange thing is it was unsuccessful with following message. Maybe this will be helpful to find the problem.
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_Open.vi
Attachments:
missing file message.JPG ‏15 KB

NI VISA Runtime engine

When "Building" a LabVIEW program containing NI-VISA sub VI's (e.g. to communicate with USB), I have had problems getting the "Built code" to find my NI VISA devices, even though the NI VISA USB Drivers are correctly installed on the "target machine".
(The "built" code WILL run if the target machine has a LabVIEW installation on it, including NI VISA)
So - will the NI VISA runtime engine be automatically included in the "Build" (Because of the NI VISA sub VI's), or do I have to specify this myself - And how?
Thanks. Peter.
Solved!
Go to Solution.

You specify installing the NI VISA Runtime Engine when you build and installer for your built executable. Look on the Additional Installers tab of the Installer Properties Dialog Box. The NI VISA Runtime Engine should be selected automatically but if it's not you can uncheck the Automatically select recomended installers checkbox and select any other installers you want to include in your install.
If you're not using an installer then no runtime engines are installed and you'll have to do that manually on each machine you copy the executable to.
This all assumes LabVIEW 2013. The selection process is slightly different in earlier versions but all the options are still available.
Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome

SQL Developer Installation Problems

Hi,
We are trying to find a workable alternative to TOAD and have tried to install SQL Developer with not much success.... I think I am just about to give up but hope this last attempt to post for help can create a miracle.
I would appreciate very much if any one knows of a comprehensive document out there that can help trouble shoot the installation problems.
Let me give you the hardware and software versions first and then the problems.
1) SQL Developer tried: sqldeveloper-1.2.1.3213-no-jre and sqldeveloper-1.2.1.3213
2) JRE tried: JRE 1.5 and JRE 6 (C:\Program Files\Java\jre1.6.0_03)
3) Window: XP Professional version 2002 Service pack 2
4) Hardware: Intel Pentium 4 CPU 2.80 GHz, 1.98 GB of RAM
Problems:
1) SQL Developer could not find native JDBC. I don't understand why, despite all the variables set in Oracleclient10g_basic in the registry, SQL Developer did not seem to be able to find a 10g client on a network drive. I have to install 10g client directly onto my pc (C:\oracle\product\10.2.0\client_1) to solve this problem.
2) SQL Developer abruptly disappeared after database login.
I was able to connect and log into an Oralce 10g database with TNS Connect Identifier approach. There were objects (tables, views, etc) showed up briefly on the left hand side of the SQL Developer and then it just completely disappeared without even an error message or a tearful good-bye.
The only thing I can find is this error log about EXCEPTION_ACCESS_VIOLATION. After hours searching through OTN for possible mentioning of this error with SQL Developer, I found nothing so far.
Why is it so difficult to install SQL Developer? Are there a set of un-spoken pre-requisites that has to be satisfied before it can be installed properly? If so, what are they? Path system variable? Registry? Anything else?
Here's the complete EXCEPTION_ACCESS_VIOLATION error log:
# An unexpected error has been detected by Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x2ca5683c, pid=952, tid=2576
# Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode, sharing)
# Problematic frame:
# C [OraOCIEI10.dll+0x4f683c]
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
--------------- T H R E A D ---------------
Current thread (0x04330400): JavaThread "Init Insight" [_thread_in_native, id=2576]
siginfo: ExceptionCode=0xc0000005, reading address 0x00000000
Registers:
EAX=0x31a28e40, EBX=0x00000000, ECX=0x03231622, EDX=0x00000000
ESP=0x04b0f168, EBP=0x04b0f1a8, ESI=0x00000001, EDI=0x0413ded4
EIP=0x2ca5683c, EFLAGS=0x00010297
Top of Stack: (sp=0x04b0f168)
0x04b0f168: 00000001 00a3fb8e 0000000a 00000001
0x04b0f178: 0413c78c 00000001 02c52aa8 0000000a
0x04b0f188: 00000020 00a4047e 090ea038 0413def4
0x04b0f198: 03231622 6d8a87b3 032325c1 0413c78c
0x04b0f1a8: 04b0f1d8 2ca57072 0413ded4 032325c1
0x04b0f1b8: 00000001 00000000 03231620 03231622
0x04b0f1c8: 00000000 00000000 00000000 00000000
0x04b0f1d8: 04b0f234 2ca56e06 0413c78c 0413ded4
Instructions: (pc=0x2ca5683c)
0x2ca5682c: 5c 00 a1 80 58 b3 31 88 9f c4 00 00 00 8b 14 98
0x2ca5683c: 8b 0a 81 e1 00 80 00 00 89 4d dc 0f 85 90 03 00
Stack: [0x04ac0000,0x04b10000), sp=0x04b0f168, free space=316k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [OraOCIEI10.dll+0x4f683c]
C [OraOCIEI10.dll+0x4f7072]
C [OraOCIEI10.dll+0x4f6e06]
C [OraOCIEI10.dll+0x419685]
C [OCI.dll+0x7333]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j oracle.jdbc.driver.T2CStatement.t2cParseExecuteDescribe(Loracle/jdbc/driver/OracleStatement;JIIIZZZZ[BIBII[SI[B[CII[SII[B[CII[I[S[BIIIIZZ[Loracle/jdbc/driver/Accessor;[[[B[J[BI[CI[SIZ)I+0
j oracle.jdbc.driver.T2CCallableStatement.executeForDescribe()V+271
j oracle.jdbc.driver.T2CCallableStatement.executeForRows(Z)V+41
j oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout()V+275
j oracle.jdbc.driver.OraclePreparedStatement.executeInternal()I+94
j oracle.jdbc.driver.OraclePreparedStatement.execute()Z+17
j oracle.jdbc.driver.OracleCallableStatement.execute()Z+60
j oracle.dbtools.raptor.insight.CompletionInsight.getInsightableOracleDatabase(Loracle/javatools/db/Database;)Loracle/dbtools/raptor/insight/InsightableDatabase;+70
j oracle.dbtools.raptor.insight.CompletionInsight.<init>(Loracle/ide/Context;Loracle/javatools/db/Database;)V+161
j oracle.dbtools.sqlworksheet.sqlview.SqlEditorMainPanel$5.run()V+52
j java.lang.Thread.run()V+11
v ~StubRoutines::call_stub
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
=>0x04330400 JavaThread "Init Insight" [_thread_in_native, id=2576]
0x0416ac00 JavaThread "Timer-4" [_thread_blocked, id=1460]
0x0412cc00 JavaThread "Timer-3" [_thread_blocked, id=2544]
0x04323800 JavaThread "WeakDataReference polling" [_thread_blocked, id=3756]
0x0315cc00 JavaThread "Image Fetcher 3" daemon [_thread_blocked, id=3412]
0x02c17c00 JavaThread "Image Fetcher 2" daemon [_thread_blocked, id=2124]
0x04324800 JavaThread "Image Fetcher 1" daemon [_thread_blocked, id=2088]
0x04321800 JavaThread "Image Fetcher 0" daemon [_thread_blocked, id=276]
0x02ca2c00 JavaThread "WaitCursorTimer" daemon [_thread_blocked, id=2096]
0x00296800 JavaThread "DestroyJavaVM" [_thread_blocked, id=3816]
0x02cb0400 JavaThread "Timer-1" [_thread_blocked, id=2832]
0x02c32000 JavaThread "IconOverlayTracker Timer" [_thread_blocked, id=1204]
0x04060800 JavaThread "Log Page Updater" [_thread_blocked, id=2160]
0x03323800 JavaThread "TimerQueue" daemon [_thread_blocked, id=3996]
0x032d1800 JavaThread "AWT-EventQueue-0" [_thread_blocked, id=4004]
0x032ca400 JavaThread "AWT-Windows" daemon [_thread_in_native, id=1488]
0x032c9800 JavaThread "AWT-Shutdown" [_thread_blocked, id=256]
0x032c8400 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=1064]
0x02c0d000 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=2956]
0x02c08400 JavaThread "CompilerThread0" daemon [_thread_blocked, id=3236]
0x02c07400 JavaThread "Attach Listener" daemon [_thread_blocked, id=3248]
0x02c06800 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=3232]
0x02bfe400 JavaThread "Finalizer" daemon [_thread_blocked, id=2328]
0x02bfd400 JavaThread "Reference Handler" daemon [_thread_blocked, id=1668]
Other Threads:
0x02bfc000 VMThread [id=2868]
0x02c0e800 WatcherThread [id=2940]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
def new generation total 1536K, used 500K [0x06960000, 0x06b00000, 0x090c0000)
eden space 1408K, 26% used [0x06960000, 0x069bd3b0, 0x06ac0000)
from space 128K, 100% used [0x06ac0000, 0x06ae0000, 0x06ae0000)
to space 128K, 0% used [0x06ae0000, 0x06ae0000, 0x06b00000)
tenured generation total 19372K, used 12857K [0x090c0000, 0x0a3ab000, 0x26960000)
the space 19372K, 66% used [0x090c0000, 0x09d4e400, 0x09d4e400, 0x0a3ab000)
compacting perm gen total 22272K, used 22205K [0x26960000, 0x27f20000, 0x2a960000)
the space 22272K, 99% used [0x26960000, 0x27f0f780, 0x27f0f800, 0x27f20000)
ro space 8192K, 62% used [0x2a960000, 0x2ae614a8, 0x2ae61600, 0x2b160000)
rw space 12288K, 52% used [0x2b160000, 0x2b7a7278, 0x2b7a7400, 0x2bd60000)
Dynamic libraries:
0x00400000 - 0x00423000      C:\WINDOWS\system32\java.exe
0x7c900000 - 0x7c9b0000      C:\WINDOWS\system32\ntdll.dll
0x7c800000 - 0x7c8f5000      C:\WINDOWS\system32\kernel32.dll
0x77dd0000 - 0x77e6b000      C:\WINDOWS\system32\ADVAPI32.dll
0x77e70000 - 0x77f02000      C:\WINDOWS\system32\RPCRT4.dll
0x77fe0000 - 0x77ff1000      C:\WINDOWS\system32\Secur32.dll
0x7c340000 - 0x7c396000      C:\Program Files\Java\jre1.6.0_03\bin\msvcr71.dll
0x6d7c0000 - 0x6da0a000      C:\Program Files\Java\jre1.6.0_03\bin\client\jvm.dll
0x7e410000 - 0x7e4a0000      C:\WINDOWS\system32\USER32.dll
0x77f10000 - 0x77f57000      C:\WINDOWS\system32\GDI32.dll
0x76b40000 - 0x76b6d000      C:\WINDOWS\system32\WINMM.dll
0x6d310000 - 0x6d318000      C:\Program Files\Java\jre1.6.0_03\bin\hpi.dll
0x76bf0000 - 0x76bfb000      C:\WINDOWS\system32\PSAPI.DLL
0x6d770000 - 0x6d77c000      C:\Program Files\Java\jre1.6.0_03\bin\verify.dll
0x6d3b0000 - 0x6d3cf000      C:\Program Files\Java\jre1.6.0_03\bin\java.dll
0x6d7b0000 - 0x6d7bf000      C:\Program Files\Java\jre1.6.0_03\bin\zip.dll
0x6d000000 - 0x6d1c3000      C:\Program Files\Java\jre1.6.0_03\bin\awt.dll
0x73000000 - 0x73026000      C:\WINDOWS\system32\WINSPOOL.DRV
0x77c10000 - 0x77c68000      C:\WINDOWS\system32\msvcrt.dll
0x76390000 - 0x763ad000      C:\WINDOWS\system32\IMM32.dll
0x774e0000 - 0x7761d000      C:\WINDOWS\system32\ole32.dll
0x5ad70000 - 0x5ada8000      C:\WINDOWS\system32\uxtheme.dll
0x73760000 - 0x737a9000      C:\WINDOWS\system32\ddraw.dll
0x73bc0000 - 0x73bc6000      C:\WINDOWS\system32\DCIMAN32.dll
0x6d2b0000 - 0x6d303000      C:\Program Files\Java\jre1.6.0_03\bin\fontmanager.dll
0x74720000 - 0x7476b000      C:\WINDOWS\system32\MSCTF.dll
0x7c9c0000 - 0x7d1d7000      C:\WINDOWS\system32\shell32.dll
0x77f60000 - 0x77fd6000      C:\WINDOWS\system32\SHLWAPI.dll
0x773d0000 - 0x774d3000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll
0x5d090000 - 0x5d12a000      C:\WINDOWS\system32\comctl32.dll
0x77b40000 - 0x77b62000      C:\WINDOWS\system32\Apphelp.dll
0x77c00000 - 0x77c08000      C:\WINDOWS\system32\VERSION.dll
0x03850000 - 0x0386a000      C:\sqldeveloper-1.2.1.3213-no-jre\sqldeveloper\ide\lib\idenative.dll
0x77120000 - 0x771ab000      C:\WINDOWS\system32\OLEAUT32.dll
0x6d570000 - 0x6d583000      C:\Program Files\Java\jre1.6.0_03\bin\net.dll
0x71ab0000 - 0x71ac7000      C:\WINDOWS\system32\WS2_32.dll
0x71aa0000 - 0x71aa8000      C:\WINDOWS\system32\WS2HELP.dll
0x6d590000 - 0x6d599000      C:\Program Files\Java\jre1.6.0_03\bin\nio.dll
0x605d0000 - 0x605d9000      C:\WINDOWS\system32\mslbui.dll
0x6d220000 - 0x6d243000      C:\Program Files\Java\jre1.6.0_03\bin\dcpr.dll
0x71a50000 - 0x71a8f000      C:\WINDOWS\System32\mswsock.dll
0x76f20000 - 0x76f47000      C:\WINDOWS\system32\DNSAPI.dll
0x76fb0000 - 0x76fb8000      C:\WINDOWS\System32\winrnr.dll
0x76f60000 - 0x76f8c000      C:\WINDOWS\system32\WLDAP32.dll
0x66210000 - 0x66219000      C:\WINDOWS\system32\netware\NWWS2NDS.DLL
0x50d50000 - 0x50d98000      C:\WINDOWS\system32\NETWIN32.DLL
0x50d00000 - 0x50d15000      C:\WINDOWS\system32\CLNWIN32.DLL
0x50df0000 - 0x50e10000      C:\WINDOWS\system32\LOCWIN32.DLL
0x50db0000 - 0x50ddc000      C:\WINDOWS\system32\NCPWIN32.dll
0x71ad0000 - 0x71ad9000      C:\WINDOWS\system32\WSOCK32.dll
0x66220000 - 0x6622c000      C:\WINDOWS\system32\netware\NWWS2SLP.DLL
0x66250000 - 0x66257000      C:\WINDOWS\system32\NWSRVLOC.dll
0x76fc0000 - 0x76fc6000      C:\WINDOWS\system32\rasadhlp.dll
0x662b0000 - 0x66308000      C:\WINDOWS\system32\hnetcfg.dll
0x71a90000 - 0x71a98000      C:\WINDOWS\System32\wshtcpip.dll
0x6d560000 - 0x6d569000      C:\Program Files\Java\jre1.6.0_03\bin\management.dll
0x62f00000 - 0x62f13000      C:\oracle\product\10.2.0\client_1\ocijdbc10.dll
0x03e50000 - 0x03ea7000      C:\oracle\product\10.2.0\client_1\OCI.dll
0x2c560000 - 0x31bf6000      C:\oracle\product\10.2.0\client_1\OraOCIEI10.dll
0x77a80000 - 0x77b14000      C:\WINDOWS\system32\CRYPT32.dll
0x77b20000 - 0x77b32000      C:\WINDOWS\system32\MSASN1.dll
VM Arguments:
jvm_args: -Xmx512M -Xverify:none -XX:JavaPriority10_To_OSPriority=10 -XX:JavaPriority9_To_OSPriority=9 -Doracle.ide.util.AddinPolicyUtils.OVERRIDE_FLAG=true -Dsun.java2d.ddoffscreen=false -Dwindows.shell.font.languages= -Dide.conf=sqldeveloper.conf -Dide.home.dir.name=.sqldeveloper
java_command: oracle.ide.boot.Launcher
Launcher Type: SUN_STANDARD
Environment Variables:
PATH=C:\oracle\product\10.2.0\client_1;X:\oracle10g\product\10.2.0\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Intel\DMIX;C:\WINDOWS\system32\nls;C:\WINDOWS\system32\nls\ENGLISH;C:\Program Files\IDM Computer Solutions\UltraEdit-32
USERNAME=leexx255
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 9, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows XP Build 2600 Service Pack 2
CPU:total 1 (1 cores per cpu, 1 threads per core) family 15 model 2 stepping 9, cmov, cx8, fxsr, mmx, sse, sse2
Memory: 4k page, physical 2079468k(1385300k free), swap 4021668k(3516444k free)
vm_info: Java HotSpot(TM) Client VM (1.6.0_03-b05) for windows-x86, built on Sep 24 2007 22:24:33 by "java_re" with unknown MS VC++:1310
Is this a java problem? SQL Developer problem? Or something else?
Thanks in advance,
a TOAD lover

The problem you are seeing (the EXCEPTION_ACCESS_VIOLATION) is a result of a version mismatch between the JDBC driver being used by SQL Developer and the Oracle client that is found on the path.
This issue only occurs when trying to use the OCI version of the JDBC driver. The simplest fix is to switch to using the basic connection type and thus using the thin (all Java) JDBC driver. As no Oracle client is required in this case, the version mismatch won't be an issue.
However, the connection approach you are using should work, and if you wish to try to sort out the problems there, we should be able to further diagnose the underlying cause of the version mismatch.
To do this, I would need to see what SQL Developer thinks are the potential Oracle client installs, as well as which install it ends up picking. Can you copy/paste the output in the Log Window (Logging Page) that is present after SQL Developer starts (but before you attempt to connect to any database)? There should be a whole series of entries like 'Checking for ORACLE_HOME environment variable' and 'Checking JDBC driver at <some path>'
These log entries are output by SQL Developer as it tries to sort out the various bits of information about Oracle client installs and thus give a peek at the selection logic being used.
Oh, and also - the value of your PATH variable would be useful as well. It may be that there is an Oracle client install on the PATH that supersedes the install SQL Developer is finding via the registry or ORACLE_HOME variable.
- John McGinnis
SQL Developer Team

Application Installer Problem

I have created an application under Labview 8.2 and am now trying to create an installation which will enable me to run this executable on a target computer. I have specified Labview Runtime Engine 8.2 but when I try to run it on the taget pc the installer initializes but then returns with the error message "Labview 8.2".
Another question is that I have a VISA Serial Subvi in the application will this be defined under NI VISA Runtime 4.0.
A zip file of the project is attached.
Best regards
Javed
Attachments:
DownlinkOneShot.zip ‏35 KB

Did you include the serial port drivers as part of the build?
You have to select (include) "VISA support" before creating the executable.
In other words, when you build the installer, go to the additional installer page and select NI-VISA Run-time as a minimum. You can also include MAX and NI-VISA Configuration Support
RayR
Message Edited by JoeLabView on 06-24-2008 08:21 AM

Adding NI VISA RunTime to a LabVIEW app on Mac using PackageMaker

I would like to create a Mac installer that installs NI VISA Run-time in addition to my application. Actually, it would also include a 3rd party USB/UART bridge driver. I'm trying to figure out how to get the NI VISA RT and the bridge driver included in my installer package. I'm close--I can create a package that throws up 3 installer wizards. The problem is that both the NI VISA RT installer and the bridge driver installer wizards end with "Reboot" buttons. If a user clicks either of those reboot button too early, not everything will be installed.
Has anyone come up against this kind of issue?
Thanks

Yup. Install VISA after your program. If you set your own installer to NOT require a reboot, then you'll only have the requirement after VISA installs. This is how I did it I think.
Either that or I took out part of the VISA installer and re-incorporated it into my own installer. I'm not in the office now so I can't check.
I so wish NI would offer an installer package for LV on the Mac. Having to do this stuff manually is really not worthy of a $$$ product.
Shane.
Ps i should read better. I see you have two packages requiring a reboot. I think you can extract at least part of the installer package and re-incorporate it into your own installer. I haven't done an installer on Mac for a while so my memory may be rusty.
Message Edited by Intaris on 11-11-2009 04:22 PM
Say hello to my little friend.
RFC 2323 FHE-Compliant

Remove Enhanced DCS Deployment Support in additional installer for old Version

How can I Remove Remove Enhanced DCS Deployment Support in additional installer list for old labview Versions.
I installed labview 8.5 after installing labview 8.2 and I make a project and create setup for it but when I build, it has problem. it need labview 8.2 install directory (i.e. C:\National Instruments Downloads\LabVIEW\8.2) but I have removed It from my PC,I think I must remove labview 8.2 Enhanced DCS Deployment Support to solve this problem. How Can I do it.
thanks

Dear Jeniffer
Only I checked these items:
NI LabVIEW Rutime Engine 8.5
NI-VISA Rutime 4.2
see attached pictures.
thanks
Attachments:
Additional Installer1.JPG ‏103 KB
Additional Installer2.JPG ‏94 KB

Additional installer

I am using LV2012 64 bit. When creating installer, in additional installer category LabVIEW RTE 2012 SP1 is selected. When testing the installer on the deployment machine it requires to install RTE before proceeding with the application installer. For some reason the RTE does not get installed and have to be done separately on deployment pc?
The other question is when using DAQmx which options in Additional installer should be selected so that it installs DAQmx on deployment pc.
TIA.

Depending on what DAQ you have you may need more, but you will need the NI-DAQmx Core Runtime. If you have some cRIO DAQmx you will also likely need the NI-RIO item. Did you do anything with DMMs? You'll need NI-DMM. Serial stuff? NI-VISA Runtime. Each application will need different additional installers, many times it is trial and error based on the error message you get when you try to run the EXE and are missing some component.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Can visa runtime engine be included in application build?

I just installed my program on a new machine and it wouldn't work. Turned
out I needed to also install the visa runtime engine. Is there any way to
automatically include that in the application build?

I've seen that you can tick of under the "additional installers" that Visa runtime is included, however, this will look for the installer files on the CD's. Is there a way to update this ? (I have 4.0 on the disc, and would like to included 4.2 in my build for installation/deployment.
The file I download from NI is a .exe, but the linking to the build configurator is some strange windows code (see attached screenshot)
/Brian
Attachments:
screenshot 13-08-2007 17.57.JPG ‏95 KB

Installation problems in MSCS ORACLE 10.2 ECC 6.00

I am writing to report some unexpected installation problems. I am installing SAP ECC 6.00 in a MSCS cluster environment (Windows 2003 / Oracle 10.2) in our production environment and I am having problems during the installing the central instance phase. The sapinst_dev shows the following error: CJS-30102 Checking the database for installation type failed, Also the jsourcecheck.log shows the following error: com. sap. engine. frame. core. configuration. Configuration Exception: Error while connecting to DB and java. sql. SQLException: Excepción de E/S: The Network Adapter could not establish the connection     at oracle. jdbc.driver. DatabaseError. throwSqlException (DatabaseError.java:112)
The database is currently running without any problem and all the services (SAP and Oracle) as well.
Following the installation guide, I performed the almost all the steps successfully:
     Oracle RDBMS, patches and Oracle fail safe software on both nodes (successfully)
     Install the central services instance for ABAP (ASCS) on the first MSCS node (successfully)
     Install the central services instance (SCS) on the first MSCS node (successfully)
     Cluster the first MSCS node (successfully)
     Install the database instance on the first MSCS node (successfully)
     Cluster the additional MSCS node (successfully)
     Install an enqueue replication server(successfully)
     Perform additional steps for the Oracle Fail Safe configuration (successfully)
     Create the Oracle Fail Safe group (successfully)
     Set up as shared database directory in your Oracle Home (successfully)
     Add the Oracle database resource to the Fail Safe group (successfully)
     install the central instance (Failed)
     install at least one dialog instance (not installed yet)
As you can observe, I have performed the create oracle fail safe group activity first and then the install the central instance later. Reading the sap note 967121 today, I just realized that there is a wrong installation sequence; the sap note 967121 (actualized date: 17/OCT/07 ) says that you must install the central instance before you create the Oracle Fail Safe group. Is this sequence compulsory? Or can I continue the installation process?
If this sequence is compulsory do I have to reinstall all the predecessor activities or should I undo just the create oracle fail safe group activity?
Please let me know if the error which is showed in the installation of the central instance phase is because the wrong sequence or it is due to another reason.
Our cluster configuration is:
4 network card
Public network cards:
Ip:192.168.2.240 (hostname: ccaribe3rp1, Node A)
Ip: 192.168.2.241 (hostname: ccariber3p2, node B)
Private network cards:
Ip: 10.10.10.1 (hostname: ccaribe3rp1.ceramicascaribe.com, node A
Ip: 10.10.10.2 (hostname: ccaribe3rp2.ceramicascaribe.com, node B
Clustergroup:
Cluster group name: SAPPRO
Cluster group Virtual IP: 192.168.2.239, network name: SAPPRO (subnet mask 255.255.255.0)
SAP cluster group:
Sap clustergroup virtual IP: 192.168.2.238, network name: sapgrp (subnet mask 255.255.255.0)
Database cluster group:
Database cluster group virtual Ip: 192.168.2.237, network name: dbgrp (subnet mask: 255.255.255.0)
We have performed the mapping of the host names to the IP addresses on the windows host file already.
I would be very grateful if someone kindly can help me to solve this problem.
Best Regards
Boris Romero

Hello Boris,
one of the main problems is that step
"Create the Oracle Fail Safe group (successfully)"
cannot be successful because you need to run configtool and change the secure store as described in installation guide. At this stage the configtool does not exists (documentation error for ECC6.0 guide), so the correct sequence is to install CI and cluster the DB, but not vice versa.
Which stage is the sapinst braking up?
Is this beginning, middle or end of installation?
Did you try to run configtool and modify secure store?
best regards

How to include the visa run-time into the installer?

Dear All,
          I made an USB device whose driver is developed by "NI visa driver development wizard".
          In my program, the COM is also be used. When it is builded and creats the installer, I have checked the Serial Port Suport in Advanced settings in Installer which I thought the visa run-time engine is concluded. In fact, when it is installed, the COM can work correctly, but the USB device's driver can't be installed. To fix it, the visa run-time engine must be setupped again.
          I see that I can add it to "run executable after installation" but during the installaion of run-time engine, some pages will be displayed which need user to choose some option.
         Would you please give some suggestion that the process of installation is automatic. Certainly the part of visa run-time engine which the USB driver is needed can be integrated to the installer of vi(like COM) is best.
          Thank you!
Hugo
PS: I am using LabVIEW 7.1

First, you can install a VISA Runtime Engine in the target PC, to verify it is VISA Run Time Engine issue.
If so, you can add a VISA Run Time Engine in LabVIEW when creating an Installer. It is much easy in LabVIEW 8 and still possible in LabVIEW 7.1. Follow the link.
http://digital.ni.com/public.nsf/allkb/E09BA0E2F31D304F86256A640070058E?OpenDocument

Labview 8 Application Builder and VISA Runtime Engine

Hi,
I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
Is this possible?
Ken

Hi,
this How-To explains about making those selections and including the different drivers :
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
and this tutorial covers the screenshots a little more step by step.
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

NI-VISA Runtime 4.3 Additional Installer problem

Similar Messages

Maybe you are looking for