LabVIEW 8.6 + SourceGear Vault is not working

Hi there,
when I try to configure LabVIEW with Vault as source control client i get the error message "2972 - An internal error occured during the source control operation." (see picture)
So, what causes the problem and how can i configure the source control to work with my client?
deepearth
Windows
XP SP3, LV 8.6
Attachments:
error_msg.jpg ‏37 KB

This knowledge base lists various source control providers that have been tested with LabVIEW - http://digital.ni.com/public.nsf/allkb/41FBD516D8BC1DED862576AF007061B2
SourceGear appears to be developed by the same company that wrote SourceOffsite. SourceOffsite was found not to work with LabVIEW so it's possible that SourceGear has similar issues.
George M
National Instruments

Similar Messages

Vault does not work any more Aperture 2.1.1

Hi,
I just experienced that the vault function does not work anymore for me. When I click on the icon to show the vaults I created, nothing happens and Aperture seems to hang for some time. Sometimes it finally comes back and I can quite Aperture normally. Sometime I just need to force exit.
I switched to a different library, where no vaults have been created and when I tried to create one by opeing the vault area first, I got the same effect. When I select directly "create vault", it creates the file, but it does not put any content in.
I'm using Aperture 2.1.1 and MacOS 10.5.4.
Any hints ?

I had a similar problem. A portable Maxtor USB drive worked fine as a vault till this am, then message that there is not enough space. Get Info tells me about 54 GB available, and my entire Aperture Library is only 54 GB. Up till today it did incremental backups just fine.
I added a firewire drive and it seemed to work as a second vault, except while Get Info for the drive says it has a 50 GB Aperture library now, the Vault window in Aperture says this vault is backed up but it only used up 3 GB of the drive. The second widow for the original drive shows the expected amount used, ie about 50 GB.
So if I run Get Info on the firewire drive, it tells me I have a 50 GB Aperture library, but the small vault window in Aperture says only 3 GB.
I was going to reformat the original USB drive and re-try it, but this last information is coflicting, Any ideas on how to proceed?
Don

Secure Backup vaulting/autorunmmjobs not work

Dear guys,
I already set vaulting/autorunmmjobs to YES but when i do the backup, the backup job still require manual start job by command runjob. It seem the vaulting/autorunmmjobs not overide the defaults setting.
ob> lsp vaulting
autorunmmjobs                    yes
autovolumerelease                yes
invretrydelay                    2 minutes                   [default]
maxinvretrytime                  15 minutes                  [default]
minwritablevolumes               0                           [default]
offsitecustomerid                (none)                      [default]
reportretaintime                 7 days                      [default]
RMAN> backup device type sbt spfile;
ob> lsj
Job ID           Sched time Contents                       State
admin/20         none        database utest (dbid=1250626260) processed; Oracle job(s) scheduled
admin/20.1       none        datafile backup                retryable at 2013/11/01.17:05 ("lsjob --log admin/20.1" for details)
Job only run if i run it Manually.
ob> runj -n admin/20.1 -d Drive
ob> lsj
Job ID           Sched time Contents                       State
admin/20         none        database utest (dbid=1250626260) processed; Oracle job(s) scheduled
admin/20.1       none        datafile backup                running since 2013/11/01.16:45
So, how to set the autorunmmjobs overide the default setting for let the job run ???
So thanks and best regards.
Chuong

Hi,
The volume vaulting scan job also run sucessfully but rman backup job still pending.
How to get Rman backup job automatically run ?
Please help .

Vault does not work

I create 5 Vaults. No problem.
I tried to restore each of them. Aperture can't finish the task (it seems to stop on one or the other picture of my library each time) and then I have to reboot the computer (no message whatsoever from Aperture).
Do I have to forget about Vault and get things done "manually" or with the aid of SuperDuper.
Meanwhile I really worry about the integrity my Library if Vault can't restore it...

SierraDragon wrote:
Please de(scribe your hardware, OS, app versions, etc. Especially RAM and hard drives, how full and how connected.
-Allen Wicks
Mac OS 10.5.4 MacPro
Aperture 2.1.1
4 GB RAM
Partition on external HD 200 GB (Empty) via Firewire
Vault crashing (stuck on restore after a while) 40 GB
I tried other vaults from a little AP library (just for testing) with no problem.
Message was edited by: Oki

Dreamweaver CS3 and Sourcegear Vault?

Has anyone found a way to get Sourcegear Vault (SGV) to work
with Dreamweaver CS3? I don't have problems with using Dreamweaver
8 with SGV, but after upgrading all of our stuff to CS3 I'd rather
use the new version. Any thoughts? The SGV DLL used to go in The
"\program files\common\dreamweaver\source control\" folder, but I
can't find an equivalent folder in Dreamweaver CS3. Can anyone
point me in the right direction?

fnOptionF12 will work.
fn tells the keyboard to send the F-xx instead of the special function.
And like I said there is an option in the System Preference to reverse the use of fn and make the F-xx keys work as F-xx instead of the special function.

SourceGear Vault with LabVIEW 2009 gives error

Hi,
I try to evaluate SourceGear Vault for version control in LabVIEW 2009.
At their website they say that Vault is compatible with Microsoft SCC interface, but as soon as I select "SourceGear Vault Classic Client" as provider in LabVIEW I get the error "Error -2924 occurred at prefPage_Source Control.vi".
Does anyone successfully use Vault with LabVIEW?
Any ideas of things I might need to do to get i to work?

The text of the error is "An error occurred while opening a source control project or accessing a file.
The specified path is invalid." Some providers are expecting certain values in parameter calls based on assumptions on how they will be used by various IDEs (mainly Visual Studio). It is possible that valid information passed by LabVIEW to SourceGear's provider does not match what they expect. This would require testing on both LabVIEW's and SourceGear's side to determine what is going on. It would probably be a good idea to start with SourceGear's support to see if they can identify what is invalid.
George M
National Instruments

[LAVA Cross Post] CTRL+SHIFT+ Shortcuts sometimes not working in LabVIEW

Cross-post from LAVA: http://lavag.org/topic/15619-ctrlshift-shortcuts-sometimes-not-working-in-labview/
See the above post for more information - here's a synopsis:
CTRL+SHIFT modifiers are not working while running LabVIEW in a Parallels 7 virtual machine. This problem affects both LV2011 and LV2012. I'm not certain that this is a LabVIEW bug - could be an issue with my virtual machine environment or it's configuration - except that CTRL+SHIFT modifiers work in other applications on the affected VMs. It's just LabVIEW that appears to ignore shortcuts with the CTRL+SHIFT modifiers.
Any ideas?
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

X. wrote:
Still well and alive in Parallels 9 and LabVIEW 2013 SP1. Of course I could upgrade to the latest versions to check whether things have gotten any better.
Any news on that?
@mellroth figured out the solution :-)
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

My Labview Report generator is not working with 2013 excel version

Hi All,
My report generator tool kit which was developpend using labview 2011 was workign with excel 2010...after that i installed 2013 excel and the code is not working..
Do i need to enable some setting to work with excel 2013.
Basically this generator tool will copy the charts from excel and paste in power point...Please let me know.
Thanks,
Hareesh

Ah, I understand now - I had assumed you were using the NI Toolkit.
If you're not using the report generation toolkit, did you write your own VIs for communicating with Office or are you using a different toolkit? If you're using ActiveX to communicate with Office it may be that the ActiveX API has changed for Office 2013 - you will probably need to modify your program for the new calls.
Since it wasn't as obvious as I thought with the report generation toolkit, it would help if you posted some code to try and understand what might be happening. Are you getting any errors in your application when you try to use Office 2013?
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

NI-DAQmx 8.8 does not work properly after upgrade to LabVIEW 8.6

Hi,
I just upgraded to LabView 8.6 from version 7.1 and found out that the NI-DAQmx 8.8 drivers do not install correctly, since there is not Measurement I/O tab in the Functions palette (see attached document). The curious thing is that I can see all my NI-DAQmx devices in the MAX, and they all test correctly, i.e., they are working correctly. The sales representative for my area recommended me to uninstall , and reinstall LV8.6 and then reinstall the NI-DAQmx 8.8 drivers, but it did not work. I still do not see the Measurement I/O functions and my application says that it "cannot compile" the NI-DAQmx vi's. Thanks in advance for your help.
Peter
PS. Someone reported a similar problem back in 2003, but the final solution was not posted. Thanks again.
Attachments:
LV8.6.doc ‏116 KB

Dear Mallori,
Thanks for your help. You are right, I uninstalled and reinstalled LabVIEW 8.6 (update from LabVIEW 7.1) and reinstalled DAQmx 8.8. I still continue to have some problem that seem (to me) beyond compatibility issues. Here are the answers to your questions:
1. Before you reinstalled DAQmx 8.8, did you
uninstall it? If not, then I believe that the installer would see the
driver already present and not actually make any changes.
REPLY: No, I did not uninstall DAQmx 8.8. What do you recommend? Should I uninstall BOTH LabVIEW 8.6 and DAQmx 8.8 and then reinstall everything again?
2. When you say that the VIs are not responsive,
could you describe this a bit better? Perhaps post one of the error
messages about compiling that you mentioned in your first post?
REPLY: I am having a lots of "This SubVI is not executable" error messages in many of the library VI's not even mine. See the attached file.
3. If you open the NI Example Finder (Help»Find
Examples) and the expand Hardware Input and Output»DAQmx»Analog
Measurements»Voltage, are you able to run one of the example programs
and see the correct values that you see in the Measurement and
Automation Explorer Test Panels?
REPLY: I tried to runa couple of the examples for continuous voltage acquisition (internal clock) and both open with errors (see attachement).
Thanks again for your help. I am looking forward to your recommendation.
Regards,
Peter
Attachments:
LV8.6-3.doc ‏43 KB

Trackpad not working in Mac OS X Lion Pre-Boot Authentication (PBA) with File Vault 2

I set up File Vault 2 in Mac OS X Lion with Pre-Boot Authentication (PBA). In PBA-login my Trackpad on my MBP Mid. 2010 is not working. I cannot select the user i want to log in with.
My Magic Trackpad reconnects if i click the power button but i usually leave it at home and i am now unable to use my Macbook Pro after i have to restart while away from home.
Any suggestion is appreciated.

http://support.apple.com/kb/HT2311?viewlocale=en_EN

Labview 2009 .exe not working with windows 2000

I created a simple vi with Labview 2009 to reset a counter in registry key. I changed it to an exe. The program runs fine on any machine with XP but it does not work on the machine I need it on which is running Windows 2000 SP4. I installed the 2009 runtime but I continue to get an error when it starts up saying the vi is not executable and that I need the full development to fix the errors. But like I said it works every where else. I've tried other exe wrote in LV2009 on this machine and they work. Is there something in my vi that is not compatible with Windows 2000?
Thanks
Solved!
Go to Solution.
Attachments:
Serial Number Reset Cell 2.vi ‏15 KB

There was an issue with building DLLs on Windows 2000 - http://digital.ni.com/public.nsf/allkb/431C9BD8F3482033862576A90073441F. Since you say you are trying an EXE, this may not be applicable.
George M
National Instruments

Labview 7 for Linux on Redhat9,NI example Finder not working.

I have Labview7 for Linux on Redhat9, installed at /usr/local/lv71. "NI example Finder" is not working, the function of browser, search,submit,none is working. When I try to close it, the window looks dead, cannot close it. I will force to close it. What is the problem? Where are the examples?
Another question: the simple help text is working, but the details help is not working. I can open the help file by Mozilla. But I want the help could be linked, like what it is in Windows platform.
Thanks

Hello �
If whenever you type �labview� at the prompt, LabVIEW 7.1 is launched, it probably means that the paths are setup to launch 7.1 but it doesn�t necessarily mean that you do not have LabVIEW 7.0 installed.
If you only installed LabVIEW 7.1 in that computer, it is possible that somebody else had installed LabVIEW 7.0 before.
What I suggest doing is to run the UNINSTALL scripts for both, LabVIEW 7.0 and 7.1, and reinstall LabVIEW 7.1 as root, not as user.
Hope that helps!
S Vences
National Instruments

Executable run-time error: "Failed to process adress of Labview Program. Occurences will not work."

When I run my VI it works fine. However, when I create it into an executable and try to run the exe, it gives me an error, "Failed to process adress of Labview Program. Occurences will not work." Why?

I am using Labview 7.0. I have attached a screen shot and the code. thanks for checking it out and let me know if you need any more info.
Attachments:
Labview_Error.bmp ‏2305 KB
Main.vi ‏230 KB
PAIN_Generator.exe ‏2186 KB

Calling Quit LabVIEW function in a callback VI is not working

calling Quit LabVIEW function inside a Callback VI (of an activeX component) is not closing the current instance of LabVIEW.
does anyone else have this issue?
RENN
LV2012SP1 64bit
Kudos always welcome for helpful posts

Sounds similar to this - https://decibel.ni.com/content/message/48506#48506
The bug is that the Quit LV function does not work when called from a VI launched through Asynchronous Call By Reference
AQ said that that bug was resolved in the 2013 beta, so you could try joining the beta to see if that solution also works for your case.
Try to take over the world!

ActiveX not working with LabView 6.0i Evaluation Version

I am trying to run some ActiveX container samples in LabView 6.0i Evaluation Version.But it is not working and no error message is displayed. Is ActiveX supported in LabView 6.0i Evaluation Version.

[email protected] (pl) wrote in <506500000008000000CD610000-1031838699000
@exchange.ni.com>:
>I am trying to run some ActiveX container samples in LabView 6.0i
>Evaluation Version.But it is not working and no error message is
>displayed. Is ActiveX supported in LabView 6.0i Evaluation Version.
>
Don't know for sure, but with the Student editions this is certainly the
case so it is possible.
The student editions do not allow:
1.AxtiveX
2.External Code (DLL's, CINS)
3. and somethjing else that escapes me at the moment.
Try simple examples such as the MSBrowser and the Adobe PDF reader AX
controls - these always work if Ax is going to work at all.
Not a solution, sorry ;-)
cheers, Alex.
Alexander C. Le Dain, PhD
ICON Technologies Pty Ltd
http://www.icon-tech.com
.au
* The LabVIEW FAQ http://www.icon-tech.com.au/thelabviewfaq.html *

LabVIEW 8.6 + SourceGear Vault is not working

Similar Messages

Maybe you are looking for