LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem when starting DIAdem with LV Connectivity VIs

Hi Andreas,
 
I wanted to follow up on this issue with you.
 
I was able to replicate the behavior by calling the EXE directly from a script rather than an SUD dialog; however, I was unable to replicate your issue regarding DIAdem not starting.
 
With respect to your first issue, it has been discussed by R&D and we are working to verify a workaround.
 
With respect to you latest issue, are you still unable to start DIAdem?
 
Matt M.
NI
0 Kudos
Message 11 of 26
(1,062 Views)
Hi Matt,
the problem (DIAdem can´t be started) always occurs, when I want to make tests with my VI and forget to start DIAdem before. The "DIAdem Open Reference.vi" trys to open DIAdem, but failed and then it takes a lot of time to start DIAdem and I´m not sure what of my trys suceeded. Sometimes it helps to delete some tasks from the task-manager (nisvcloc.exe, nidmsrv.exe,nicitdl5.exe, nimxs.exe, nipalsm.exe, lkads.exe, lkcitds.exe, lktsrv.exe, nvsvc32.exe), but the last time it didn´t suceed and DIAdem stalls at "Lade: \ADDINFO\GFSODBC.DLL". After I started and ended DIAdem 8 I´m again able to start DIAdem 9.1
Andreas
0 Kudos
Message 12 of 26
(1,056 Views)
Andreas,

Does DIAdem only have this problem after you've had the error from LabVIEW? If so, this is probably happening due to the error occuring. If you open DIAdem 9.1 right after restarting the computer, do you see the same results?

Brandon Vasquez | Software Engineer | Integration Services | National Instruments
0 Kudos
Message 13 of 26
(1,047 Views)
Hi Brandon,
DIAdem has this problem only when I forget to start DIAdem 9.1 before I start the VI.
When I try to open DIAdem 9.1 after restarting the computer I see for a short time the DIAdem-Starting-Screen and then it´s gone and DIAdem isn´t opened.
My workaround: once starting and ending DIAdem 8.1 and after that DIAdem 9.1 can be started and works fine.
Andreas
0 Kudos
Message 14 of 26
(1,045 Views)

Hi Andreas,

Allow me to summarize to make sure I understand this correctly: If you attempt to use your icon to call the SUD which starts the DIAdem script when DIAdem is not open it hangs when DIAdem attempts to register gfsodbc.dll. Once this fails, you are unable to load DIAdem until you start a different version of DIAdem.

It sounds like the underlying issue is that DIAdem is failing to register the gfsodbc.dll. Once this is not registering correctly, it appears to be preventing you from starting DIAdem until this DLL is appropriately terminated.

Are you using ODBC connections in your SUD or your script? If not, you should be able to turn off whether the gfsodbc dll registers when you start DIAdem by following the steps in this KB. The KB will show you how to add a DLL, but you can remove them from there as well.

If you receive this error, you could also try manually unregistering the DLL using "regsvr32 /u <location>gfsodbc.dll" where <location> is the directory location of the dll and then try reloading DIAdem.

Let me know if this helps.

Regards,

Matt M.
NI

0 Kudos
Message 15 of 26
(1,032 Views)
Hi Matt,
I have two problems:

1. When I work on my VI and start it for testing, sometimes I forget to start DIAdem first and declare the variables, which the VI reads from DIAdem. After this I´m not able to start DIAdem commonly and I haven´t found a procedure which always works.

2. I´m not able to start the LabVIEW-VI.exe from a SUD-Dialog, when the calling vb-script was started from a DIAdem-link on desktop.

In my test-script and test-sud I don´t need ODBC connections, but the real program-script and dialoges need it (these are made from my colleague). So for me it is in principle no problem to remove the gfsodbc.dll registers, but I´m not sure this is provided by DIAdem 9.1.
"regsvr32" doesn´t work ("LoadLibrary fehlgeschlagen - Das angegebene Modul wurde nicht gefunden").
When I open in DIAdem 9.1 the "Registrierung von GPI-Erweiterungen" and click on "Standard..." I find the odbc.dll, but in this dialog is no remove-button.

Regards,

Andreas
0 Kudos
Message 16 of 26
(1,025 Views)
Hi Andreas,
 
If your script will eventually need the ODBC connections, I would not recommend removing them.
 
That said, the error you received when you tried to use the regsvr32 /u was interesting. That error usually indicates that the DLL does not exist in the path you specified. Does the DLL exist on your system and did you specify the path correctly?
 
Looking back at your two problems, the second problem is different than the one we experienced before. Previously you were able to run the LabVIEW exe; however, eventually an error was thrown. Now you are unable to start the EXE at all?
 
Furthermore, you said you haven't found a procedure that always works - does this mean that starting DIAdem 8 does not fix this every time?
 
Regards,
 
Matt M
NI
0 Kudos
Message 17 of 26
(1,019 Views)
Hi Matt,

to my second problem: I´m sorry, my last comment wasn´t quite correct. I´m able to start the LabVIEW-VI.exe, but it doesn´t work correctly and if I wait long enough an error is thrown.

I tried to unregister with from "Start\Ausführen..." and the gfsodbc.dll exists in that folder.

To your last point: You are right, starting DIAdem 8 does not fix my first problem every time and up to now I havn´t found a solution.

Thanks for your patience

Andreas
0 Kudos
Message 18 of 26
(1,011 Views)

Hi Andreas,

Since I don't know German, I have been using a translator. The error message you were receiving above translates as LoadLibrary failed - the indicated module was not found. This makes me think that when you tried to unregister the DLL, you entered the wrong directory (possibly through a typo) or the DLL doesn't exist. Since the DLL exists on your system, then the location of the DLL must have been specified incorrectly for that error (or I am interpreting it incorrectly). I would try navigating to that DLL through windows explorer and copying the directory path from the path bar. Then paste that path when you unregister the DLL and try the command out again.

Again, I'm not sure if unregistering the DLL after this issue arises will solve the problem; however, it would be something to try.

Regards,

Matt M
NI

0 Kudos
Message 19 of 26
(1,001 Views)
Hi Matt,

I can´t find an error, but maybe you want to take a look.

Regards
Andreas
0 Kudos
Message 20 of 26
(978 Views)