Upgrade to LabVIEW 2012 caused Additional Installers issue

Hello again all you helpful forum-goers!
I have been using LabVIEW 2010 (SP1) for a while on my Windows XP computer, but I recently purchased and installed LabVIEW 2012 for a future project. In the meantime, my previous projects must still use LabVIEW 2010 until I use my company's formal change tracking system to upgrade them. However, when I recently opened one of my older projects in 2010 to update it and rebuild the installer, I saw in the Additional Installers tab a bunch of blank lines at the end of the list (see attached screenshot). This doesn't directly hurt me, but I have to think it is a symptom of the root problem.
More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked. That seems like an upgrade oops on National Instruments' part to me. I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk. "FADEC_Emulator" is the name of my software. Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3. Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked. However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3). Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3? Confusing! And if it did that, why didn't it have that version handy already? And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
I'm afraid that since installing LabVIEW 2012 my system has gotten into an unstable state, and I now have possibly corrupted my project's LV project file. I need to have both 2010 and 2012 on my computer for the time being.
Does anyone have any idea what is going on with my system, and/or how to fix it?
Thank you very much in advance for your suggestions and time!
-Joe
Solved!
Go to Solution.
Attachments:
Additional Installers Blank Lines.png ‏45 KB

Hi Joe,
I tried to reproduce your issues, and encountered mixed results. Please verify with what I've provided below that we are testing under the same conditions
jmorris wrote:
More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked. That seems like an upgrade oops on National Instruments' part to me. I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
In this scenario, I built a test project with VISA RT 5.0.3 and LabVIEW 2010 configuration. I then installed LabVIEW 2012 and VISA 5.2.0 on top of the aforementioned setup. When I opened the 2010 project in 2012, VISA Run-Time 5.2 was checked (as expected, dissimilar to your configuration). As I mentioned earlier, this may have been because VISA 5.2.0 did not install properly.
jmorris wrote:
Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk. "FADEC_Emulator" is the name of my software. Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3. Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked. However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3). Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3? Confusing! And if it did that, why didn't it have that version handy already? And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
For this case, I built the installer on LabVIEW 2012 with VISA RT 5.2.0 then saved it for LabVIEW 2010 compatiblity. When I opened the installer in a LabVIEW 2010 with VISA 5.0.3 environment, VISA 5.0.3 was checked (as expected since LabVIEW will default to the latest version of VISA on the PC regardless of what the original installer referenced). I did, however, see three extra blank lines in the additional installers tab (more on this below) . I also tried to build the installer as you indicated, but did not get any prompts for disks and was able to build successfully.
One thing to keep in mind is that LabVIEW by default will use the version of the driver that is installed on the build PC, regardless of whether it is newer or older than the installer references. If you feel this negatively impacts your successes as a developer, please feel free to post a feature request (e.g. for a prompt when the driver version changes) in our idea exchange forum (http://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas ).
Lastly, regarding the empty lines in the additional installer specifications, this problem appears to be fixed in LabVIEW 2012 and only manifests itself in 2010. During my course of testing, this did not affect building the installers and is a minor inconvenience which has been fixed in subsequent versions.
Please let me know if you have any additional questions/comments regarding these issues.
Regards
Doug W
Applications Engineer
National Instruments

Similar Messages

Issues with windows 7 after Labview 2012 installation

Hi
I am having some issues after installing Labview 2012 on machines running Windows 7. Firstly, after installing a program on a user's machine, the machine sometimes takes 20 minutes to boot up before the user can log on. The 'Please Wait' message appears during this time. This is also the case on the development machine.
Secondly, on the development machine, I am having an issue when trying to run compiled programs created in Labview. When installing, everything works fine but when I go to open the program, it appears on the task bar for a brief period before closing. It does not appear in the task manager either. I have tried this on 2 other machines with windows 7 and Labview installed and still get the same issue.
Any help on these matters would be much appreciated. Thank you

Hi
Firstly, looking at the issue with the slow Windows 7 boot up time, as Norbert_B suggested the Windows Event Log is a good starting point to find the root of the problem. The following link describes how to launch “Event Viewer” and some common problems:
http://itexpertvoice.com/home/what%E2%80%99s-taking-so-long-how-to-fight-slow-startup-times-in-windo...
Aside from that, if your computer is part of a domain, the problem may be connected with certain Windows Services that start automatically on boot up. I recommend trying the following steps:
Open up “Control Panel” go to “System and Security” then “Administrative Tools” from here launch “Services”.
Sort the list by name and scroll down to “Network Store Interface Service” right click and select “Properties”. Under the startup type dropdown select “Automatic (Delayed Start)”.
Next scroll down to the “WebClient” service again under “Properties” this time select “Disabled” under the startup type.
As for the problem with running LabVIEW executables, I have a few questions:
Do you get any error codes when it closes automatically?
Does this occur for multiple executables or just one in particular?
Does the code run without a problem within LabVIEW?
Have you tried to update LabVIEW?
What hardware are you running?
Without this information I can only think it may be caused by the Windows Data Execution Prevention (DEP) security feature. So you can try the following steps:
Right click on “Computer” and select “Properties”.
Click on “Advanced System Settings” and select the “Advanced tab, then under the performance section click “Settings”.
Click the “Data Execution Prevention” tab.
Make sure it is activated for essential Windows programs and services only, or you have an exception for your EXE.
You may also find the following link helpful on debugging applications:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/debug_apps_dlls/
Let me know if these solve the problems.
Andrew.N
Applications Engineer
National Instruments

What files do I send to be upgraded from LabVIEW 5.1.1 to LabVIEW 2012?

OK. Just to be clear. I am a complete newb to ANYTHING LabVIEW or LabWindows related. I am a programmer, but I have never used any version ever. That said, I am responsible for the upgrade process of getting our old LabVIEW 5.1.1 system up to date. The old system (still running and doing it's job everyday), is an old Windows NT v4.0 SP6 system running LabVIEW 5.1.1. You can just imagine how ancient this is by today's standard.
Have I set the stage properly? I hope so. Newb, Ancient LabVIEW version 5.1.1, Windows NT 4.0, upgrading from 5.1.1 to 2012.
Now here is what I "think" I know about what is required. Because LabVIEW 2012 will not directly read in, process and /or compile LabVIEW 5.1.1 files, I must first open and save the files using an intermediate version of LabVIEW (specifically 8.2.1) to bring the files up to a version that 2012 can handle. I have noticed in reading the Version Conversion forum, that I can attach a zip file of my LabVIEW files and one of the resident Gurus will convert it for me and give them back - quite nice I think.
Now, I have what I think are all of the required LabVIEW vi and llb files that make up this system we have in place, but I want to be sure before I just post a bunch of stuff.
What exactly do I need to zip up and what can I leave out?
Are there LabVIEW vi and llb files in a "project" that are not needed?
Are there any setup/configuration/project specific files I need to include?
Are there any limitatations to this conversion process that I need to be concerned with - such as various toolkits/suites/modules that may have been used but are no longer supported?
Secondly, I am not really comfortable with posting my vi and llb files for the world to see (and possibly use) as I am not the owner of said modules, just the user/future developer who will be responsible for insuring they stay up to date. Is there any way I can send my files to a specific NI guru via email instead of just posting them?
Solved!
Go to Solution.

So if I understand you correctly, all I really need to do is to get LabVIEW 8.2.1, and update my .vi, .lib, and any .ctl files to that version.
Is it a simple matter of just opening the files and hitting something like SAVE AS, or just SAVE and it will do this? Once done, LabVIEW 2012 will then allow me to open them and do what I need to do? Do I have to save them into LabVIEW 2012 first, or is that automatic when I try to recompile them?
When I get a copy of LabVIEW 8.2.1 (eval version), do I have to get all of the pieces (modules, toolkits, etc.) in order to update the 5.1.1 files? Based on what is installed on that NT v4.0 system, we have the following items installed:
NI VISA
NI ComponentWorks 3D Graph
NI DataSocket
NI LabVIEW 5.1.1 Advanced Analysis Library
NI LabVIEW RTE 5.1.1
NI LabVIEW v5.1.1
NI Measurement and Auto Explorer 1.1
NI-488 2.1.60
NI-DAQ 6.6
NI-PAL 1.3.110
NI-Reports
NI-VXI/VISA
You mention DAQ. Our program uses NI DAQ v6.6 now. I have LabVIEW Developer 2012, so I just download the DAQ files for it and it will replace the NI DAQ v6.6 library files we use now?
Thanks for your help so far. If we had a support contract in place, this wouldn't be an issue. However, as I stated, I am not the owner of the files, just the currently assigned caretaker, and part of my task is to get from where we are now on this ancient hardware/software platform, to the latest and greatest. However, I am specifically not allowed to just place the files on a public forum for all to see. It just isn't done. We can send them to a known location and a known entity, but not to just anyone/anywhere as a public forum is by its very nature.
I know there is nothing you guys can do if I cannot give you the files, but thanks for helping me to do it myself. Getting an eval copy of 8.2.1, et. al is probably what I have to do here.

Issues with SharePoint 2013 after upgrading from windows 2012 to 2012 r2

We have a Sharepoint with Sp1 environment on windows 2012. Recently we upgraded the windows 2012 to 2012 r2. After the upgrade sharepoint environment is completely unstable.
At first all the sites returned 401 errors. After resolving by resetting the object cache accounts the sites are back.
Then i see that none of the performance point dashboards work. I figured that claims to windows token service is defaulted to local system account. I previously configured with a domain account. I reconfigured to work with domain account.
All the dashboard pages throw error.
Some Error logs:Failed to get document content data. System.ComponentModel.Win32Exception (0x80004005): Cannot complete this function at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow
Application error when access /Dashboards/Performance Dashboard/Main.aspx, Error=The EnableScriptGlobalization property cannot be changed during async postbacks or after the Init event. at System.Web.UI.ScriptManager.set_EnableScriptGlobalization(Boolean
value)
4. I tried to create a new dashboard and this time the performancepoint designer wont launch. After some troubleshooting i see that c2w host file didnot have the caller C:\Program Files\Windows Identity Foundation\v3.5.
I added <add value="WSS_WPG" /> and now it launches
5. Now the Dashboard launches and peruser identity works without having kerberos enabled at IIS. I have all the spn and required delegations setup for this url . But i did not configure at the IIS level
yet.
It looks like lot of things got messed up and reset. Can we upgrade to windows 2012 r2 with a sharepoint application inplace. what is the recommended approach and Whats happening with Performancepoint dashboards. IS there a known issue with sharepoint 2013
sp1.
Raj-Shpt

Thanks for the above article. Few issues are solved . One of the main issue is with Performancepoint Dashboard.
I have all the spn and required delegations setup for this url . But i did not configure at
the IIS level yet. Still per user identity works without having kerberos enabled at IIS.
Raj-Shpt

Measurement Computing USB-DIO96H driver issue with Labview 2012 SP1 on Windows 7 x64

Is anyone else having issues with measuremetn Computing's USB-DIO96H driver in Labview 2012 SP1. It throws warnings in Labview when loaded that are unresolvable as you can't save to the DLL driver file. Also it regularily crashes Labview randomly. I am not impressed with their driver. Anyone have any suggestion other than replacing with NI-DAQ solution, which I am working on?

I've taken a look and I don't see any drivers available for that device on ni.com. There are two potential workarounds that would both involve building your own driver:
1. Write a LabVIEW application that calls functions on the DLL you downloaded from Measurements Group
2. Write a LabVIEW application that addresses the device using NI-VISA and serial communication.
Some resources if you choose to go down that path:
http://www.ni.com/devzone/idnet/development.htm
http://www.ni.com/white-paper/3271/en/
http://www.ni.com/white-paper/3009/en/
Hope this helps!
Rob B
FlexRIO Product Manager

LabView 2012 Security System Main vi's have error 200559

The vi's give errors of 200559 in my LabView 2012 and NI application engineer "John Staskal" told me as "Another good step
is to recreate the VI in your current version of LabVIEW so that you know the error is not caused by upgrading the VI to a newer version of LabVIEW." I did all that, but not resolved.
Their application engineer John Staskal also told me as "In addition to working to resolve the error you may want to pursue is posting on our upgrade forum and asking the community to convert the VI to a current
version of LabVIEW. http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion".
I did all trouble shooting steps such as highlight execution, probes, etc as what their application engineer told me and still having error of 200559 in LabView 2012.
I appreciate help from any one.
Ali Tariq Bhatti
Ali Tariq Bhatti
Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
~~~Be nice, have faith in ALLAH(God)~~~
Attachments:
NI ELVIS II Security System VIs (2).zip ‏313 KB
Error 200559.docx ‏500 KB

RavensFan,
I) Yes, I open up the front panel of the Express VI's and probe into them.
2) I use the express vi's, but if you see my attached vi's file. You will see Security System Main vi is the main vi where the program is running and where I am getting the error of 200559.
3) I also attached the word document file, so I am getting error of 200559 in probes 3, 4, and 5 using Export Key Press and Voltage vi's in this post.
4)Do you know, how to convert these my attached vi's to 2011, 2010, 2009, or LabVIEW8.5 version. May be, it fix the problem, or if you know some one to get help from or get chance to use ELVIS II board, so let me know .Your help or any one's help is appreciated.
Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
~~~Be nice, have faith in ALLAH(God)~~~
Attachments:
did probes for Export Press and Key vi's file.docx ‏340 KB

Additional Installers

Spoiler (Highlight to read)
We purchased a PXI8101 w Windows 7 and using Labview 2012. In the other PXI slots we have PXI6230, PXI2564, 2503 and 4065. From the Knowledge Base I understand I must include DAQmx for the 6230 in the additional installations tab of the application builder. I'm going to port to a target machine.
1) What drivers do I need for the other PXI cards to include ( additional installations tab) or does the daqmx support those? The 2564, 2530 and 4065??
2) do I need to include the MAX config.nce file?? I've given my DMM and relay cards "names" in MAX but I thought that was just for my interaction. In other words when I call up a vi that uses the DMM the id is DMM. When you create the exe the front panel goes away so does it still need MAX??
3) There are links on some discussion grp pages that are suppose to take you to the latest RT engine for LV but they're blank. Is that only if you need to purchase?? We have the full developemnt sys. Is the RTE included?
Thanks
Solved!
Go to Solution.

Wow lots of questions, sorry if I miss any.
Lets start with the Run-Time Engine (RTE). LabVIEW's RTE is free for deployment EXEs. If you build a EXE, then you build an installer, under the Additional Installers you'll want to select the RTE for the EXE you built. This is selected by default so no worries there. Then when you install this on a fresh normal Windows machine, a basic normal LabVIEW EXE should run. Your EXE may use other toolkits and need more additional installers. Which ones is an educated guess if you are unfamiliar with it. In 2013 NI made a way for the installers needed to be automatically selected. I haven't tried this but bet it is prone to issues. It can be partially a trial an error process. Build the EXE, build the installer, run the installer on a fresh machine and see if it runs without error. If the EXE is broken it will try to suggest the component needed. Then you'll need to figure out what is needed in the additional installers to make it work.
In your case you will need DAQmx that is a given and you mentioned it. You will probably only need the DAQmx Core Runtime, and DAQmx MAX Configuration Support. Do you use a serial port? Then you'll also need the VISA Runtime. Do you use XNET? Then you'll need to include that. This will make your installers baloon in size, but it will include all the needed drivers for all DAQ hardware/VISA/XNET based on what is selected. The goal is to make a single installer that you run and a fresh machine can run the EXE with.
As for the MAX config. In your code if you reference a physical channel, virtual channel, task, scale, or hardware by the alias made in MAX then you will need this same alias on your deployed system. The easiest way to do this is probably to make an Export in MAX of your config, then in your installer settings there is a page for Hardware Configuration and you can provide a NCE file to get imported after the install is done. For this to work properly you'll want the hardware in the system before the install, otherwise you'll need to import the NCE again after the hardware is installed.
EDIT: Here is a link to the LabVIEW 2012 SP1 RTE. You don't need to download this, checking the RTE from the additional installers is all that is needed, but I wanted to show you the link where you can get the RTE for free.
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.

Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path

Hi everybody,
I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
<04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
<04-25-2014 02:06:47> ********************************************
<04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
minimum supported installed build version is [7804].
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Unsupported upgrade path;    Error;
Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
<04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Active Replica MP;    Passed
<04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Parent site replication status;    Passed
<04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
=====
<04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;
SQL Server sysadmin rights;    Passed
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;    SQL Server sysadmin rights
for reference site;    Passed
<04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Site server computer account administrative rights;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server security mode;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
<04-25-2014 02:07:09> INFO: Target computer is a Windows server.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Unsupported site server operating system version for Setup;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Domain membership;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Pending system restart;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server version;    Passed
<04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Edition;    Passed
<04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
Instance:.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Tcp Port;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
<04-25-2014 02:07:09> INFO: SQL Server memory is limited.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Configuration for SQL Server memory usage;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
<04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
Server to reserve a minimum of 8 gigabytes (GB) of memory.
<04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;    SQL Server process memory allocation;
Warning;    Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
http://go.microsoft.com/fwlink/p/?LinkId=233759.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Case-insensitive collation on SQL Server;    Passed
<04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFO: getaddrinfo returned success.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Validate FQDN of SQL Server Computer;    Passed
<04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
<04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Primary FQDN;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
=====
<04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
<04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Failover Cluster;    Passed
<04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Deployment Tools installed;    Passed
<04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;    Windows Preinstallation Environment
installed;    Passed
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
SMS Provider machine has same domain as site server;    Passed
<04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:10> ***************************************************
<04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
<04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
Prerequisite checking result into the registry
<04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
<04-25-2014 02:07:10> INFO: Setting registry values
If you wonder whether it might be related to this error:
-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
I've already tried the
Preinst /DELSITE XXX command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
Finally, the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
the impression that it's being cached somehow.
Any help would be highly appreciated,
Thank you.
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Hello again everybody,
I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
primary sites.
If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
DELETE
FROMServerDataWHERESiteCode='XXX'
DELETE
FROMSC_SiteDefinitionWHERESiteCode='XXX'
And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
Thank you all anyways for your answers and comments,
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

SSRS 2012 Conditional Formatting Color Issues When Exporting to Excel

Hi all,
We recently upgraded to SQL 2012 from SQL2008 R2. I'm having a strange issue with SSRS2012.
One of the report has conditional formattings on cell background colors. Everything works fine when render the report in browser or preview mode. However, the conditional formatting stop working when export the report to Excel (no issues if
export to pdf). All cells are high-lightened with pre-defined color although it should only high-lighten those cells that fulfil the condition.
Has someone encountered this issue before ? Thanks for any help.

Hi ZZ02,
I have test the scenario in my testing environment, however, everything goes well when exporting to Excel format. The issue might be related to the expression for the conditional background color. To make further analysis, please post the expression as well
as the report design structure.
Additionally, in SQL Server 2012 Reporting Services, the Excel rendering extension renders a report to the native format of Microsoft Excel 2007-2010, the format of which is ExcelOpenXML. By default, the previous version of the Excel rendering extension,
compatible with Microsoft Excel 2003, is disabled. At this time, I suggest that you enable the Excel 2003 rendering extension by modifying the RSReportServer.config file. After that, the Excel 2003 rendering format will be available on report manager (not
available in Report Designer). So, please export the report from report manager and check the result again.
For more information about enable the Excel 2003 rendering extension, please see:
http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/0713de27-dcc0-4e51-81ac-5272647d171f
Regards,
Mike Yin
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Mike Yin
TechNet Community Support

Additional installer issue - NI system component missing - DVD

Hi,
I have trouble building my installer... when I try to add DAQ and Measeurement & automation explorer, the setup is asking me to provide file (that in my head are supose to be already in my PC). It says to find NI system component on DVD 1 of develloper suite.
When I insert DVD1 of the labview DVD I received to install Develloper suite on my PC, it tells me wrong DVD!!!!! I understand nothing... see pictures... what is the problem???
Thank you for helping.
ET
Attachments:
images.docx ‏172 KB

I assume that the additional installers you are refering to are programs you are installing from the Developer Suite DVDs, and not something you are installing from an installer you built - right?
The NI Device Driver 2014 DVD does not include "all" drivers - but rather the most recent version of each. If you would like to see which versions are included, take a look at the following link, in the Description section:
http://www.ni.com/download/ni-device-drivers-2014.02/4634/en/
Your 2014 DVD is asking you to provide the 2012 DVD?
Regards,
Shane C
Applications Engineer
National Instruments

Missing vi.lib files in Run-Time LabVIEW 2012

Hi
I've got a problem executing VI's under RT in LabVIEW 2012.
Our system consist of multiple independent modules which are opened and run from a Manager VI. VI paths to the modules are read from an .ini file by the Manager VI.
We have build a single executable (RT Launcher) that takes the path of the Manager VI as argument (Attachment : RT Launcher.png).
The RT Launcher is placed in the ..\National Instruments\LabVIEW 2012 folder as the LabVIEW.exe.
The RT Launcher is called from the CLI.
"C:\Program Files\National Instruments\LabVIEW 2012\RT Launcher.exe" "C:\Workspace\Labview\Manager.vi"
This will run the Manager.vi in the RunTime Environment and the Manager.vi will open the .ini file and execute the Module VI's one by one.
By calling the RT Launcher.exe from the same folder as the LabVIEW.exe, the search paths should be the same.
The system worked fine in LabVIEW 2010.
The Manager VI is opened with broken arrow and the errors indicate that vi.lib sub VIs are missing (attachment : Manager VI errors.png)
I know there are issues regarding object cache and separated compiled code from LV2010 -> LV2011 -> LV2012, but simply can't figure out how to come around this problem.
Can anyone explain the difference and how to solve the problem ?
Thanks
Regards Kahr
Certified LabVIEW Architect
CIM A/S
Solved!
Go to Solution.
Attachments:
RT Launcher.png ‏68 KB
Manager VI errors.png ‏35 KB

Hi Kahr.
It sounds like you are making some dynamic calls to VI's, eg. by using 'Open VI Reference'. My answer is based on that assumption.
You are absolutely right. In LabVIEW2010 we introduced a function called 'Separating Compiled Code from VI'. At that time none of the VIs from VI.lib had that option enabled. In LabVIEW2011, many VI's in VI.lib have, by default, a separation of compiled code and VI. This option cannot be changed (greyed out) for these VI's as well. This feature was introduced in order to simplify source code control.
Separating Compiled Code from VIs and Other File Types
The drawback is, that it is no longer possible to call VI's dynamically from an application (executable), when this option in enabled, since the compiled code no longer exists. The method of calling a VI dynamically from an application has been (and still is) used to make some kind of a plug-and-play architecture, meaning we have one EXE-file that only gets distributed once and a set of subVI's that gets redistributed according to new versions (new features added to the subVI), meaning we can make changes in the subVI without having to redistribute the EXE-file.
With the release of LabVIEW2011 and LabVIEW2012 we can no longer distribute VI's that uses functions from vi.lib, this also include DAQmx calls even though the DAQmx driver is installed.
The simple explaining is, that it has never been intended that VI's got distributed. Eg, when Microsoft is making a new software update for Windows7, they don't send out the source code to all the users.
The solution is therefore to wrap up the source code into 'something' that includes all the compiled files. In LabVIEW we do that in a couple of different ways.
1) Include the VI's in the EXE-file.
When building the application, we have the option to include files, that normally is not included in builds. If we call a SubVI dynamically this will not automatically be included! However, the drawback of this method is, that if you need to change something in one of your SubVI's, you would need to build and distribute the entire application. Thereby, we are not making use of the plug-and-play architecture that we originally wanted. However, this method will fix the error.
Error 1003 When Using VI Server in a LabVIEW Application
2) Now, if we still want the plug-and-play architecture in LabVIEW2011+2012 (and this will properly be the same for the next many released of LabVIEW), this can still easily be achieved by making a Source Distribution. When we make a Source Distribution, we can include the VI's from VI.lib and thereby the compiled code. When using this method, two important things should be remembered:
a) Make the files into a LLB file. This will pack all the VI's into one single file, that is easy to distribute.
Go to Destinations ==> Destination Type ==> LLB.
b) Make sure not to 'Exclude files from vi.lib', as this method will then simply not work.
Go to Additional Exclusions ==> Remove checker mark in 'Exclude files from vi.lib'.
How Can I Call a VI Dynamically from an Executable Without Including Those VIs in the Build?
I have made a small example to demonstrate this:
Example: Using vi.lib
This example has two mainVIs and two EXE-applications. Build the two EXE-files, but do NOT build the source distribution yet.
1) Main(IncludeSubInExE). This version has included the subVI in the build distribution for the EXE-file. When running this EXE everything works fine, even when calling the subVI dynamically. However, since the subVI is build into the exe, we would have to redistribute the exe for every new version of the subVI. This breaks the hole idea.
2) Main. The subVI is no longer included in the build. When running and trying to call the subVI, you will get this error (on both your developer and run-time machine):
Now, build the Source Distribution and run this EXE again. The exe is running perfectly with no errors.
I hope this answers your question.
Best Regards
Alex E. Petersen
Certified LabVIEW Developer (CLD)
Application Engineer
Image House PantoInspect
Attachments:
Using vi.lib.zip ‏83 KB

NI-VISA does not appear in the addition installers window

Its seems that i cannot add any NI-VISA packages to my "additional installers" window.
The dev system has VISA 4.0 and LV 8.0 and even after downloading and installing the VISA runtime especially to fix this problem, i still cannot see it in the list!!! There also seems to be lots more missing from what i have seen in screenshots on previous posts. Why oh why is this happening!
Alex.
:. LV2010 SP1 ... W7 .:

Thanks for your reply! It seems to have worked a treat!
I did the following steps:
1. uninstalled VISA 4.0 and DAQmx 8.x
2. installed DAQmx 8.6 (i wanted to upgrade to this a some point anyway)
3. installed VISA 4.2
I can now open the Installer Properties => Additional Installers window and have the following options:
and now that i can select the Measurement and Automation Explorer it has solved a second issue for me that i posted on this forum (see:
Problems with building and installer - hardware config). An error used to occur when i tried to include the "Hardware Configuration from MAX" but there are no errors now. Im sure it has something to do with also including the MAX in your installer. See Below:
Happy days for a monday
Message Edited by ali66b on 11-19-2007 11:21 AM
:. LV2010 SP1 ... W7 .:

Labview 2012 SP1 f5 halting on Win 6 x64

I am using the latest Labview 2012 x64 SP1 with f5 update and am finding that it halts and forces me to close labview and restart. Anyone else having the issue or knows what might be causing the issue?

I regularly get 2012 SP1 f5 shut-downs but these tend to only occur when I am working on a project with a nested LVOOP hierachy and I'm making changes to that hierachy.
I don't know what activities you are doing that cause the re-start but it might help to know what you are working on when it happens; or post your LV internal error report to NI (I assume NIER is doing it's job).

Inline upgrade from server 2012 to server 2012r2

just wanted to see peoples experience for upgrading server 2012 to server 2012r2 on an inline upgrade? is this ok to do or a reimage is best?
thanks

Hi iworkhere,
I have a Windows Server 2012 DC and a Windows 2012 member server in my lab environment. I have upgraded them to Windows Server 2012 R2 with no issue. After upgrading, you will
have a Windows.old folder under C:\ and as there is no disk cleanup tool in Windows Server versions without the Desktop Experience feature, you may have to delete it manually if needed.
In addition, if no data needs to be kept in Windows Server 2012, you can choose either a clean installation or a upgrading. Personally, I prefer the clean installation.
Hope this helps.
Jeremy Wu
TechNet Community Support

Require additional installers?

Hey,
I am looking for advice on the following, I am attempting to build a stand alone application, i am unsure as to how to go about achieving this as its the first time i have attempted it. I have built an application with my main vi as the start up vi and all the dependencies are attached so there are no vis to choose from for the source files for the always included window.
My next step was to build an installer, i assume the source files to attach to this is the one i selected for the start up in building the stand alone application. Now within my vi i use NI-IMAQdx 4.0 aquisition software i was wondering what additional installers i require or will my code execute? Do i need to add drivers etc.
Regards,
Damien

Hi guys,
I have added the NI-IMAQ 4.7.0, NI-IMAQdx 4.0.0, the chroma driver, NI-Serial and the NI-VISA Configuration support 5.2, NI-VISA Runtime 5.2 and NI-VISA Server 5.2. Do i install Vision Run-Time Engine 2012 also?
I have a serial number for the labview professional development licence and it contained the vision acquisition module along with the vision builder and toolkits etc. I also have a different serial number this is the vision development module run time licence which is the vision acquisition product. So this is the one i activate on the deployed computers? Thanks for the help i am just a bit cautious as to what i can activate.
Thanks
Damien

Upgrade to LabVIEW 2012 caused Additional Installers issue

Similar Messages

Maybe you are looking for