Error 1 when create a new Request.

[SAndreas]

Hi, I always get an error 1 and a very corrupt Module when scripting a private request after creating a public request.

Steps to reproduces:

1. Create new a new project and add a new module (I tried with a singleton)
2. Add a new private request
3. Add a new public request
4. Add a new private request
   1. You receive error 1
   2. The event case from the previous create public request catches now the new private event
   3. At the end of the event structure, an empty event case occurs
      

I tried to manually fix the module, but this seems to break our application in a very strange way. We always got some funny VIs breaking during build process errors.

Click the link below to visit the Application Builder support page. Use the following information as a reference:

Error 1502 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Save.vi

Possible reason(s):
LabVIEW: (Hex 0x5DE) Cannot save a bad VI without its block diagram.
An error occurred while running the ExecuteBuildSpec operation.

It looks, as not only the script failed but although let LabVIEW in a very instable state.

Any inputs would be very welcome.

Best wishes

Andreas

[Darren]

The error you're seeing is related to the relative fragility of scripting events in LabVIEW. The problem is partially addressed by a bug fix (Issue #947) in the next release of DQMH, while the DQMH Consortium also has another open issue (Issue #935) to continue researching ways to more permanently solve the problem in future DQMH releases.

[Ludwig72]

I have similar errors when creating private and public requests in mixed order. I realized that the creation of a private request tries to overwrite events of other public requests inside the EHL.

It forces me not to use private requests but public only or to create them manually.

[SAndreas]

Hi Darren 

Thanks for the fast update.

I figured out, the issue is strongly related to the fact that the scripter adds the public request event reference below the private cluster.

Workaround:: In my case, everything works fine, if I manually reorder the events cluster to have all public events above the private event cluster.

Is there a way to extend the scripts with custom functionality, so that we can add the feature to reorder the cluster by our self and do not need to wait for the next DQMH Release? Is there already a date defined for when the release with that fix is planed?

[joerg.hampel]

Thanks everybody for sharing details and potential solutions here. We will discuss in the Consortium how to expedite a fix.

Andreas, take a look at this page (and have a little more patience): https://documentation.dqmh.org/dqmh/7.1/ScriptingPlugins.html