Tag engine will not start after installing latest DSC update

[unclebump]

I just installed the new DSC6.1 updates dated 02/24/2003, and now the tag engine will not start. I get an error message "An exception occurred within the external code called by a call library node. This may have corrupted LABVIEWS memory. You should save any work to a new location and restart labview. stopped at node0x204 of sub-vi 'NET_TAGTODSURL.vi'". I also see the message "a sub vi is not executable. The full development version is req'd to fix the errors." I have the Professional Control Edition.

[Roli]

Thanks for giving us so fast notice... But could you do me a favor and try to masscompile the \vi.lib\lvdsc folder and the \project\lvdsc folder. And let me know if you still see the problem?

Roland

[unclebump]

The first error is corrected after mass recompile of the two directories, but the second error is still occurring. The error message that I am still getting when starting the tag engine is "a sub vi is not executable. the full development version of labview is required to fix the errors." I can open my .scf file to edit tags.

[Roli]

I guess this error happend before (see readme.txt 2.). NI has uploaded today a bvrtdatabase.dll which should work again (together with changes in 8.). Could you try to use the latest version from LabVIEW DSC 6.1 Fixes

Thanks for your patience and your cooperation.

Hope this helps (please, let us know)
Roland

PS: If the latest update would not prevent the NET_TagToDSURL.vi error, you should contact NI's support persons to exchange .scf/.vi to reproduce the problem, or attach it here.

[unclebump]

I have applied the latest update and recompiled the two directories. The tag engine still won't start and I have a new error message. "system error ... CCDB:error connecting to the ccdbinterface.dll"

[Roli]

Do you have the CCDBInterface.dll in hte \vi.lib\system directory? And the ddao35s.dll in the -directory?

If not, I would try to reinstall the Server Explorer part from the LabVIEW DSC installation.

I've a system here to double-check if I could load/run your .scf file. Did you try to start with a new .scf file (empty, or just one analog memory tag?)

Let me know
Roland

[unclebump]

Both of the files are present on my system. I also tried creating a new scf file with only one memory tag. The new scf will not start the tag engine either.

[unclebump]

I finally just uninstalled DSC and reinstalled up to the jan. 2003 update and was running again. After talking with the app's eng. today, he told me to install the feb. 26,2003 update again. I reinstalled and it locked up the tag engine again. Numerous vi's gave me a 'bad vi' message when I did a mass compile of the entire labview6.1 directory and some said they were not able to load because they were already in memory. Here are some of the names the showed as a bad vi: telog_dyn_log_various.vi, dscds_dyn_dsexec.vit, compression.vi, image compression.vi, aequalb.vi, avgv1.vi, avgv2.vi, cross.vi, debug.vi, fileread.vi, filewrit.vi, mult.vi, zzall.vi, subvi with error handling.vi, distribution plot indicator.vi, min-max plot indicator.vi. When I opened telog
_dyn_log_various.vi it showed the error "you have connected two terminals of diff. type" and was broken. The DCDS_DYN_DSEXEC.vit showed the error "subvi tagengine_log_proxy.vi bad linkage to subvi." How can I fix this mess and still be running the required updates?? Will I have to completely uninstall labview??

[Roli]

I don't know all these VIs you mention. But some are from LabVIEW DSC. LabVIEW load up some VIs (hidden) into memory to open them faster if needed. LV DSC does that by the lv_init.vi in the vi.lib folder. If you would rename lv_init.vi to e.g. to _lv_init.vi LabVIEW would load without LV DSC VIs and therefore they would not be in memory and could be masscompiled. Change it back to lv_init.vi when your are done and restart LabVIEW to be able to use LV DSC.

In your case to avoid a masscompilation over the whole LV directory, I would recommend to extract the DSC patch to a seperate folder, masscompile this folder and than copy it to the LabVIEW folder.

You might call again the app. eng. to get some more help.

Could you try on a "fresh installe
d" PC? At least, in my case this was working.

Hope this helps
Roland

[unclebump]

I completely removed all NI software in control panel. Reinstalled from the feb2003 CD set. I was able to start the tag engine with the default .scf file after doing this. I then installed the logos 4.4.0.15 update and the DSC update from 02-26-2003. I went into a new vi, loaded the tag editor with the default.scf file. The tag engine would not start now. I renamed the file above and I am mass compiling at the moment. I have it logging to a file and will post the file when it is done. I am using a win2000 machine with 850Mhz and 128Meg of ram.