Runtime Vs Dev environment - error 1307

[eximo]

Having difficulty in getting a foothold on troubleshooting an issue that only occurs in the runtime environment of my application.

I have a dozen subpanels in my application which all use the same subvi to call them.  In the newest version we are working on they all function normally in the Development environment but in the runtime environment one of the subpanels is generating a 1307 error.  The 1307 error is rather generic to subpanel issues, but explicitly means that the subpanel failed to open.

Any ideas what could be wrong or how to troubleshoot it?

Description of attached:

-Image one is front panel of error handler

-Image two is back panel that shows the subpanel open routine.  The purpose of the subpanel open routine is to open a subpanel named Serial Number.  One opened, it will light a led indicator and blink it until the subpanel is closed.

[RTSLVU]

For some reason I can not open your attachments but...

I have found that most of the time when code runs fine in the development environment, but the same code fails when compiled and deployed there is a race condition in the code.  

[JÞB · Accepted solution]

Also, take a look at your build spec.  The default Source file settings for sub-vis is to remove the front panel- It is very hard to open a vi front panel that does not exist!  In fact, if you try, you will get a 1307 error

[eximo]

Jeff,  i checked the build properties and vi properties first to see if there was any inconsistencies.  The fact that all of the other subpanels open normally and that this one doesn't is strange since I made sure to design them all the same way.

I'm running a test now where I have specifically selected to include the front panels of Subvis in the build to see if that affects the error. I also put check points to test the error conditions within the subvi that is responsible for calling the subpanel.

How do you check the quality of the reference during runtime?  I have only ever checked references using the probe tool in development.

I'm reattaching the two images.  It's weird that the NI forum won't serve them up.

[eximo]

Is there something wrong with my attachment file naming?  These are only jpegs.....they shouldn't have an issue.

---

@eximo wrote:

Jeff,  i checked the build properties and vi properties first to see if there was any inconsistencies.  The fact that all of the other subpanels open normally and that this one doesn't is strange since I made sure to design them all the same way.

I'm running a test now where I have specifically selected to include the front panels of Subvis in the build to see if that affects the error. I also put check points to test the error conditions within the subvi that is responsible for calling the subpanel.

How do you check the quality of the reference during runtime?  I have only ever checked references using the probe tool in development.

I'm reattaching the two images.  It's weird that the NI forum won't serve them up.

---

[RTSLVU]

Must be those crazy long file names?

This is what I get when I click on them...

[RavensFan]

They worked for me.  What browser are you using?  I'm using Firefox.  Try another browser.

[eximo · Accepted solution]

Kudos to Jeff

I took your advice and explicitly set the source file settings to set save settings for al contained items, to not use default save settings, and NOT remove the front panel.  This fixed the issue.  However, it doesn't resolve the WHY?  The rest of the subpanels work in either case (I verified by changing this setting back to the default and retesting).  Is there another setting that can affect this behavior?  Does changing the compile setting to not remove the front panel increase the compiled executable size on disk or slow down it's performance?

Attachment includes the settings that have been changed from default to mitigate the undesired behavior.

Answer these additional questions and I believe we will have the complete solution to the issue.

[RTSLVU]

---

@RavensFan wrote:

They worked for me.  What browser are you using?  I'm using Firefox.  Try another browser.

---

I am using Firefox...

Interestingly enough the last one worked just fine  (source settings - serial number subpanel failing to open.JPG ‏103 KB) but the other four toss up that same error.

[billko]

Just a wild guess, but maybe all the ones that open by themselves do something to implicitly call the front panel - like a resize for example?  Maybe they all do, except for the one that doesn't keep its front panel.