Can't edit the message popup in teststand 4.2.1

[SeanJ]

Hi,

I installed the 2010 version of TestStand on my PC.

Everything has been fine until today.

Every time i try to edit a property loader I get the following error:

Error in cal to LoadPanelEx.

Parent Panel Handel: 0

UIR File Name: PropertyLoaderUI.uir

Panel Resource ID:3

hInstance: 0xZ

I click ok and a second window appears saying

File not found

Error -94

I rebooted the PC, tried a repair, checked the adapter and made sure the search directories covered the file PropertyLoaderUI.uir

Can anyone help with this?

Thanks,

Sean

[SeanJ]

Sorry,  The topic should have read, Can't edit the property loader in teststand 4.2.1

[RayFarmer]

hi,

can you post a simple example highlighting your problem

[Manooch_H]

Sean -

Have you moved the TSDBComponents.dll file from its original location? If so, have you also placed the PropertyLoaderUI.uir file in the same directory as the TSDBComponents.dll file?

You mentioned that the search directories cover PropertyLoaderUI.uir. If you were speaking of the TestStand search directories, this would not affect whether or not the PropertyLoaderUI.uir file is found.

From looking at the TSDBComponents.dll source code, it looks like we load the PropertyLoaderUI.uir file using just its name expecting it to be in the same directory as the TSDBComponents.dll file. CVI then searches for the file based on its search directories. In this case, it looks in the same directory as TSDBComponents.dll to find the UIR file.

If this is not the cause of the error you are encountering, please let me know and we can troubleshoot this further.

Hope this helps.

[SeanJ]

Hi Ray/ Manooch,

Sorry about the delay getting back.

I resolved the issue as follows:

I completely uninstalled and reinstalled the LabVIEW/ TestStand software.  The error occured again.  On looking through the search directories I noticed that I had put an old deployment in my working folder.  I had actually seen this issue on a deployment about a week ago that I had to redeploy to fix.

It appears the TestStand elements were being taken out of my deployment folder.

I removed it to fix the issue.

Thanks for the suggestions.

Sean