Mise a niveau Labview 2013 vers 2014

Bonjour,
Je dispose d'un programme de labview dernierement compilé avec labview 2013, et apres installation de labview 2014, j'ai essayer d'ouvrir mon programme dernierement compilé avec labview 2013,avec labview 2014, mais cela souvre mais je n'arrive pas a le compilé et il m'affiche des erreurs sur une des mes sous VI,
Etant donné que je suis novice avec labview, puissez vous m'aider svp en m'éclairant sur cette question.
Je vous remercie d'avance de votre réponse;
Cordialement,

Kathiaswe wrote:
Hi,
My error is: your Vi can't executed, can you corect your error. ça donne ça car j'utilise la version en français.
Mercii
Il n'y a définitivement pas assez d'information pour être d'une quelconque aide. Ouvrir le sous-vi en erreur et cliquer sur la flèche blanche (run) et une fenêtre d'erreur ouvrira. Poster l'information détaillée de cette fenêtre d'erreur, à partir de cet information nous seront plus en mesure de vous aider.
Ben64

Similar Messages

How can I build a LabView application that uses the 2012 runtime, on a development system with LabView 2013 or 2014 installed?

I need to build a LabView application .exe to run with the 2012 Runtime, for legacy support. I currently have LabView 2013 installed on my development system, and have 2014 available. How can I build an application that uses the 2012 runtime on this development system? Do I have to downgrade to 2012? Thank you.

We have existing customers that have installed our application that was originally built with 2012 (provided by a contractor that is no longer available). Due to IT regulations, it is far easier to update these customers by simply replacing the .exe file, than creating an install that their IT department must run.
If I have to downgrade to LabView 2012, where can I get the installation for this?

When replacing Labview 2013 with Labview 2014, do I firstly need to uninstall Labview 2013?

I have just recieved my latest version Labview 2014 CD.
When installing this new version, do I firstly need to uninstall previous Labview versions?
Solved!
Go to Solution.

Bob_Schor wrote:
The reverse, however, is not true. Once you install one version of LabVIEW, you cannot install an older version without uninstalling everything and "starting over". Be warned ...
Not exactly true. You can install just an older version of LabVIEW. I have had LabVIEW 2012, 2013, and 2014 installed on a computer and then installed 8.2.1. It is all of the support drivers and what not that do not install side-by-side. So the real lesson here is that if you install an older version of LabVIEW, pray that your current drivers support that version of LabVIEW. You will need to reinstall the drivers to install the support for the older version of LabVIEW though. Installing just the support takes hardly any time.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Type Sensitive Popup LabVIEW 2013/2014

Hello,
I was a big fan of the Type Sensitive Popup program found:
http://lavag.org/files/file/31-type-sensitive-popup/
Recently, I am running LabVIEW 2013/2014 and notice that the demo no longer works. In particular: TSPopup.FG.Popup.vi
Has anyone else encountered this? Is there an easy way to fix this program?
Thanks much!
Attachments:
labview_2012.png ‏54 KB
labview_2012_2.png ‏62 KB
2013_error.png ‏64 KB

Is there a reason why you posted this question here instead of the support thread for this code? The thread is several years old but if anyone is monitoring it anymore it should be the author.
http://lavag.org/topic/10282-cr-type-sensitive-popup/
Personally I've never used it but it sounds neat, thanks for bringing attention to it.
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.

J'ai toujours rien recu après mon programme de mise a niveau vers mountain lion gratuit. J'ai mon mac depuis 2semaines seulement et j'attend le mail d'Apple depuis 20h pour avoir l'os mais j'ai aucun mail... Que faire? Est-ce normal?

J'ai toujours rien recu après mon programme de mise a niveau vers mountain lion gratuit. J'ai mon mac depuis 2semaines seulement et j'attend le mail d'Apple depuis 20h pour avoir l'os mais j'ai aucun mail... Que faire? Est-ce normal?

Bonjour du Canada!
Pour répondre à ta question concernant Balance, ton entreprise doit être parti d'une solution Entreprise pour activer cet service.
J'espère que ça t'aides.
(Excuse mon français, je suis Anglophone.)
- If my response has helped you, please click "Options" beside my post and mark it as solved. Clicking the "thumbs up" icon near the bottom of my response would also be appreciated.

Slow LabView 2013

Hi
I have Labview 2013 Professional Dev Sys SP1 ver 13.0.1f2 (32-Bit) and it is slow when I develop any aplication.
For example, if I have a tab control and I change to another tab, it takes about 2 seconds to change tab after I click it.
If i wire a new line, it takes 2 seconds to appear that line in block diagram, and so on.
I have a new computer Dell Optiplex 7010, i7 Processor 3.40Ghz, 64-Bit, 4Gb RAM, WIndows 7 enterprice SP1
If i run Windows task manager it shows 17% CPU usage and 2.14 GB Memory.
If I run for example, excel 2013 it does not seems slow.
Do you have any suggestions ?
Regards
Solved!
Go to Solution.

EDGAR_PLATRONICS wrote:
Hi Yamaeda:
I am not sure about mass compile. You mean rewrite code ? Or create exe file and test?
A this moment I have checked with only one Vi but it is very large. Many sub VIs and code.
Actually it worked correctly in labview 8.5 but i converted to LV 2013.
I will research about transparent borders overlapping.
Hi Altenbach:
17% is overall. 3 cores are high % than others.
The problem is at edit mode and also when I run program.
Yes I have many front panel indicators, but I do not think they have tons of data but I will double check.
When I open my VI in labview it shows 118 MB memory when running and 124MB at edit mode
By the way, last week when by mistake I moved a part of code to some centimeters below, block diagram was frozen and was been updated to new position but line by line until complete full screen. I took about 5 minutes to work normally.
I am using 2 monitors in my PC. One to display LV panel and one for LV code.
I meant Tools -> Advanced -> Mass compile and recompile your upgraded code. In the same manner a ctrl+run array will force recompile your program. It can help. Else you're down to e.g. using VI analyzer tool to find the culprit, it might be some VI that's corrupted and needs to be moved to a new VI.
/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

Where can i download the trial version of the Labview 2013 64bit Report Generator Toolkit for Microsoft Office?

Hi all,
I am having trouble locating a LabVIEW Toolkit. Could somebody please send me a link to somewhere where I can download the eval version of the Report Generator Toolkit for Microsoft Office for LabVIEW 2013 64bit.?
Thank you in advance,
Bob

Yes here is the 2013 version.
http://download.ni.com/evaluation/labview/ekit/other/downloader/2013RGT_downloader.exe
And here is the 2014 version.
http://ftp.ni.com/evaluation/labview/ekit/other/downloader/2014RGT_downloader.exe
I believe both are for 32 bit LabVIEW, which works in both 32 bit and 64 bit Windows. Honestly until all toolkits support 64 bit Windows, I still don't see much of a reason to go with 64 bit LabVIEW. The support is just better with 32 bit.
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.

LabVIEW 2013 SP1 Compile Worker Fails

Hello,
after receiving the new DVDs with LabVIEW 2013 SP1 and successfull installation, I wanted to compile my FPGA.vi.
The Compile Worker does not start an I get the attached error Message. The additional Download of Xilinx Compilation tools 14.4 from the NI Website does not help.
When I choose the FPGA Compilation Tools via the Start menu, the Compile Worker does not start. When I try to start the FPGACompileServerConfiguration an Error occurs (see picture).
At the Moment I hav not Idea what to do. Perhaps someone can help.
What does I have to do to convert my system back to the Version 2013?
Attachments:
FehlermeldungCompileWorker.jpg ‏41 KB
ErrorwhenstartingFPGACompileServerConfiguration.jpg ‏15 KB

dfschunk,
Thanks for your post. We are aware of an issue with the compile tools installed from the 2014 developer suite (2013 sp1) where the compile worker is installed with missing dependencies. We are taking immediate action to push out a fix for this and you will receive a notification through NI update service when the fix is available.
In the meantime, our recommendation is to downgrade to the 2013 installation of the Xilinx tools. No fixes were made between 2013 and 2013 sp1 in the compile worker or in the Xilinx tools so no worries there.
Go to Control Panel >> Programs and Features and select National Instruments Software.
This will launch a window where you have the option to select various NI software products and modify/repair/remove them.
Select NI LabVIEW FPGA Xilinx 14.4 Tools and select Remove.
After the software has been un-installed, go to the NI LabVIEW 2013 FPGA Module Xilinx Tools 14.4 donwloads page and install this version of the tools (released with 2013) or you may install the tools from your original LabVIEW 2013 developer suite disks.
Please post back or call support if you have any problems with this process, we want to make sure you are up and running until we push out a fix.
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

Is the cRIO 9067 compatible with LabVIEW 2013?

I just purchased 2 cRIO 9067s and I'm trying to configure one of them to use. I got the IP address set and booted it into safe mode. The status light blinks twice, then pauses. The documention says this means I need to download software. NI MAX only suggests using versions 14.?, which I'm assuming is LabVIEW 2014, but that option is grayed out. And if I try to do a custom install, everything in the list produces a concfict and wont download. Is the 9067 only compatible with LV 2014? Or am I missing a step? the version of LV that I am using is 2013. I'm installing 2014 to test this theory, but I'm no thopeful. Thanks for the help people.
Solved!
Go to Solution.

The cRIO-9067 does require LabVIEW and NI-RIO 2014. You can use http://download.ni.com/pub/gdc/tut/crio_software_versions.htm to look up the minimum software support for cRIO products.
I don't see how I can link directly to the result, but if you select "CompactRIO Chassis and Controllers" from the drop down and then "cRIO-9067" you should see this table.
NI cRIO-9067
Minimum Software Support
Software
CompactRIO (FPGA Interface)
CompactRIO (Scan Interface)
✔ Supported
✔ Supported
LabVIEW
2014
2014
LabVIEW FPGA Module
2014
LabVIEW Real-Time Module
2014
2014
Device Driver Software
NI-RIO Device Drivers August 2014
NI-RIO Device Drivers August 2014
NI-DAQmx
Other Minimum Software

NI-USRP 14.0 driver ,and labview 2013 64 bit

Hi
Is it possible to use the NI-USRP 14.0 (64 bit driver) with Labview 2013 64 bit ?
have someone tried to install NI-USRP 14.0 drivers and then convert the driver ("instr.lib \niUSRP" directory) back to 2013 version ?
or do i need to purchase the 2014 version if i want to run 64 bit labview & USRP?
Thanks

Hi again
i installed the 32 bit verision of niusrp 14.0 driver (selected to install the driver for labview 2013 ,32 bit version)
& copied the installed files from 32 bit labview directories to the 64 bit version directories
, when opening a usrp vi (like "open rx session.vi" ) it says :
"error loading "niusrp.dll" A dynamic link library (DLL) initalization routine failed.
if i then try to point to another niusrp.dll like the one placed at C:\windows\SysWOW64\ , i got :
" the library selected is not valid for the current platform. for example ,you are running 64 bit labview and the library might be a 32 bit library"
where can i find the "right" niusrp.dll ?
so it seems that the niusrp 14.0 driver does not support labview 2013 64 bit version, ?

Usrp driver 1.3 do not support for Labview 2013 64 bit ??

Hello, dear all
Is anyone install the latest USRP driver 1.3 for LV 2013 64 bit ? I found there is no version for 64 bit LV 2013.

Currently the 1.3 driver supports only LabVIEW 2013 32 bit (even on 64 bit computers.)
The LabVIEW 2014 version will support 64 bit and will be available to download very soon.
Please check here within the next week or so: http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/ssnav:drv/q/usrp/

Reconnaissance TPC 2106 avec labview 2013

Bonjour,
Je suis passé à labview 2013 depuis peu (auparavent sous lv2009). Nous possédons plusieurs écrans tactiles TPC2106 mais ils ne sont plus supportés par labview 2013.
Ma question est donc : quelqu'un connait-il le "truc" pour remédier à ce problème ?

Bonjour Buckaroo,
Malheureusement, le support de votre TPC 2106 s'est arrété à LabVIEW 2012.
Voici la liste des TPC compatibles avec LabVIEW 2013 :
Cordialement,
Vincent.O
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Été de LabVIEW 2014
12 présentations en ligne, du 30 juin au 18 juillet

SharePoint Foundation 2013 - March 2014 Update Issue - Need help

We've just applied the SharePoint Foundation 2013 March 2014 Update, it always requires that we run the SharePoint Products Configuration Wizard at the end of install, but this time it's getting stuck at step 9 of 10 (the profile sync service cannot be
started even as admin). Is anyone else having any issues with this update? Has anyone else applied it yet? Is anyone else planning to apply it?
If anyone can help with advice on this I'd appreciate it.

Hi,
We can still access CA but sync will not start. Tried rebooting after the failed configuration and tried to run it again but it didn't work.
4/2014 10:45:16 5 ERR            Exception: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc
that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException:
No connection could be made because the target machine actively refused it 127.0.0.1:32843
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForLegacyLoginContext(Uri context)
   at Microsoft.SharePoint.SPSite.InitUserToken(SPRequest request)
   at Microsoft.SharePoint.SPSite.SPSiteConstructor(SPFarm farm, Guid applicationId, Guid contentDatabaseId, Guid siteId, Guid siteSubscriptionId, SPUrlZone zone, Uri requestUri, String serverRelativeUrl, Boolean hostHeaderIsSiteName, SPUserToken
userToken, Boolean appWebRequest, String appHostHeaderRedirectDomain, String appSiteDomainPrefix, String subscriptionName, String appSiteDomainId, Uri primaryUri)
   at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)
   at Microsoft.Office.Project.Server.Upgrade.FullFarmDependentProjectDatabaseSequence.SPSiteExists(Guid siteId)
   at Microsoft.Office.Project.Server.Upgrade.ProjectDatabaseSequence.AddNextLevelObjects()
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
4/2014 10:45:16 5 ERR            An exception of type System.ServiceModel.EndpointNotFoundException was thrown. Additional exception information: There was no endpoint listening at
http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at //localhost:32843/SecurityTokenServiceApplication/securitytoken. that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException,
if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:32843
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties)
   at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForLegacyLoginContext(Uri context)
   at Microsoft.SharePoint.SPSite.InitUserToken(SPRequest request)
   at Microsoft.SharePoint.SPSite.SPSiteConstructor(SPFarm farm, Guid applicationId, Guid contentDatabaseId, Guid siteId, Guid siteSubscriptionId, SPUrlZone zone, Uri requestUri, String serverRelativeUrl, Boolean hostHeaderIsSiteName, SPUserToken
userToken, Boolean appWebRequest, String appHostHeaderRedirectDomain, String appSiteDomainPrefix, String subscriptionName, String appSiteDomainId, Uri primaryUri)
   at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)
   at Microsoft.Office.Project.Server.Upgrade.FullFarmDependentProjectDatabaseSequence.SPSiteExists(Guid siteId)
   at Microsoft.Office.Project.Server.Upgrade.ProjectDatabaseSequence.AddNextLevelObjects()
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, SPDelegateManager delegateManager)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
4/2014 10:45:16 1 ERR          One or more configuration tasks has failed or some tasks were not run
4/2014 10:45:16 1 INF          Leaving function TaskDriver.OnTaskDriverStopping
04/14/2014 10:45:16 1 INF        Leaving function TaskDriver.ExecuteTasks
04/14/2014 10:45:16 1 ERR        One or more configuration tasks has failed to execute
4/2014 10:45:16 1 ERR          Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review
the extended error information located at D:\Logs\PSCDiagnostics_4_14_2014_10_44_8_154_1605984328.log, fix the problem, and run this configuration wizard again.
04/14/2014 10:45:16 1 INF          Entering function StringResourceManager.GetResourceString
4/2014 10:45:16 1 INF      Leaving function TaskDriver.Run
04/14/2014 10:45:16 1 ERR      Post setup configuration was not run successfully when using the command line task driver module
04/14/2014 10:45:16 1 INF    Leaving function PsconfigCommandLineMain.Main
This is the meaty part of the errors we are getting. Right now our entire site is down. If you know of anything to remedy these errors let me know.

Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).

Hi all. Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop). This really slows things down! Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini. Has anyone seen similar, and/or any hints towards a solution?

Jeff-P wrote:
As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.
I thought that the message: "Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini" might indicate that the labview.ini file cannot even be created... strange...
LabVIEW Champion . Do more with less code and in less time .

Report Generation Toolkit labview 2013 64bits?

Muy buenas tardes.
Estoy buscando el Report Generation Toolkit para labview 2013 64bits, lo he buscado pero no logro encontrarlo y con este mismo pero de 32 bits me marca error al instalarlo.

Hola Antonio,
Intenta con esta liga : http://www.ni.com/gate/gb/GB_EVALTLKTREPGEN/US
Espero que por aqui lo puedas descargar,
saludos
Erwin Franz R.

Mise a niveau Labview 2013 vers 2014

Similar Messages

Maybe you are looking for