"sl.policyevaluator.PolicyEvaluator" could not be found

[UTAC_MLee]

SystemLink is giving me this error every few seconds and once it reaches 1000, my web VI stops working/running. Does anyone know how to resolve this issue? The error comes up on any page on the SystemLink Server, not just the webvi I have.

---

[MilanR]

The WebVI runs inside of an iframe so I would not expect those error messages to impact the execution of the WebVI itself.

Can you provide more detail about the behavior: "once it reaches 1000, my web VI stops working/running"?

Do you see any messages or additional errors related to the WebVI in the console or does the diagram result in any errors?

[UTAC_MLee]

My WebVI reads SystemLink Tags(around 100-200 tags) and changes LED(10) properties (On/Off, Boolean Text, and Colors). This is happening around 2Hz. After a certain time period, the webvi no longer functions/updates properly and I was assuming it was because of the policy evaluator error showing in the console. I have 3 instances of this web vi running, each on their own individual SystemLink servers. It seemed that it was related to the policy evaluator error, however the systemlink server that this policy error does not occur on also has issues with updating the webvi after given some time to run.

Thoughts?

[MilanR]

---

After a certain time period, the webvi no longer functions/updates properly.

Thoughts?

---

Unfortunately that isn't really enough information to provide more insight. Some ideas:

• Make sure you doing error handling so any errors that occur on the diagram will be seen in an error indicator for debugging.
• Check if you see any messages or additional errors related to the WebVI in the console that might help give more clues as to what is going on.
• It sounds like a fair amount of data may be handled by the WebVI. Maybe monitor in task manager for large memory leaks that may be occurring on the diagram.
• Reading 100-200 tags at a time is quite a large number. Using the Multi Read VI in the Tags >> Advanced palette will help you read multiple tags efficiently.

[UTAC_MLee]

I use an HTTP Get request to read multiple tags(100-200 tags) and then parse the data accordingly. It is able to get the data and parse it within time (max 300ms). I benchmark tested the code to see the time it takes to execute, and it is working as expected without significant delays. It's just after some time it doesn't seem to be updating as expected (changing LED's colors when expected or updating anything on the front end). It's almost as if the web VI isn't running anymore. There may be a memory leak somewhere and I don't have error handlers for everything, however I expected all unhandled errors would show on the console, right? I don't have any reference opening done inside my ongoing while loop. All of the references opened for the LED's and Textboxes are handled initially and then passed into my loop. I'll monitor the browser memory and will update once I do further debugging.

Thanks,

[MilanR]

---

I don't have error handlers for everything, however I expected all unhandled errors would show on the console, right?

---

G Web follows pretty much the same automatic error handling rules for debugging a WebVI as LabVIEW. So in general unhandled errors will be logged but depending on the wiring some errors are assumed to be handled. For example, errors wired to a tunnel are assumed to be handled in both. Note in the following example that we only see error 2 in both for automatic error handling via logging / popups respectively: