Exeception caused by Call Library Node

[Solarman]

I'm getting a serious error  with LV DSC 7.1. I was making some changes to the scf file but when I went to save it I got the following error.

An exception occurred within the external code called by a Call Library Node. This may have corrupted LabVIEW's memory. You should save any work to a new location and restart LabVIEW. VI "dsc_DYN_TAInitDB.vi" was stopped at Node 0x48B4 of subVI "dsc_InitTagGroupsDB.vi"

When I restarted LV the error message appeared straight away and I could not start the Tag Configuration Editor. I have since tried repairing and reinstalling the DSC module. This let me get back into the TCE but I still got the error when I tried to save the SCF file. I thought the scf file may have been corrupt so I exported the data to a txt file and imported it to a new file but I still get the same error on saving.

I've just finished a complete reinstallation of LV, drivers and DSC module. When I open the TCE for the first time I created a new scf and and again imported the tag info from the txt file but again when I went to save it I got the error.

There are over 150 tags in the scf for an ethernet FieldPoint system. The PC is running XP Pro. The application was recently upgraded from V7.0 to 7.1. Everything was running fine until the edits to the scf. However, this was not the first edit to the scf I had made.

The knowledgebase contained details of a similar error for LV 6.1 and there were updated drivers available. Is there any ubdates for LV 7.1?

[RobSims]

Hi Solarman,

Thank you for posting on the NI Forums.

I have taken a look into your issue and it would seem that several customer's have seen this issue before, but the issue often seems not to be reproduceable.

In all cases I could find where this issue has occured under LV 7.x (as opposed to 6.x) the issue has been resolved by an uninstall of NI software, then a registry clean and then a reinstall. Please see the attached .doc for methodology of this.

If you could post your scf file to this forum then I can verify if your scf is indeed corrupt. Many thanks,

Rob

Message Edited by RobS (AE) on 05-22-2006 11:15 AM

[Solarman]

Hi Rob,

Thanks for your reply. However, I tried the uninstall, registry clean, reinstall as described but I still got the same error when I tried to save the scf after importing the tags from the text file. The error makes it impossible to open the Tag Configuration editor unless I uninstall and reinstall the dsc module which makes it very time consuming to even try anything different.

For now I'm going to go back to V7.0. I've attached the scf file and the exported tag data which I tried to import.

Thanks again

Paul

P.S It appears that .scf is not a valid extension for an attachement so I had to zip it.

[RobSims]

Morning Paul,

I'll take a look at your .scf file for you today and let you know what I find.

Thanks,

Rob

[Solarman]

Rob,

On reverting to V7.0 I found something which may or may not have something to do with the error but I thought I should share it with you. The reason for the edits to the .scf file was to add tags for an FP-DI-330 module which I recently installed (labelled OTR1.....SMT 111.... to 114....). In V7.1 I had been able to use these tags but when I reverted to v7.0 I found they didnt work and when I looked at them using the tag monitor they showed up as "access denied" under status. When I had a closer look at the configuration they had been set as Input/Output instead of Input only. Setting them to input only allowed access to be restored and the application now runs fine.

The fact that I could access the tags in v7.1 when they were not correctly configured suggests that something changed between versions.

Regards

Paul