I am currently taking over a Project for someone who has recently left our company. The project itself seems to be working fine but we keep having this error appear in our Logs:
The project is fairly large, and I don't know where to being searching for what is calling this message handler. Is there any easy way to search for this throughout the project?
You can use the Find/Replace tool, but you need to be clear with where you're searching. By default, the tool only searches open resources - you'd want to be sure you're searching all resources. Also, the Find/Replace tool only works for resources of the current project. Does that logging entry give you any more information, or perhaps a magnifying glass or + which can be used to expand the entry for more info?
Unfortunately it does not give me anymore information. Just has a Logger as: DispatchManager, The Date Time, and the Message that I posted in the original post.
Maybe you could try creating a handler for it and examining the payload ? Might give you a clue as to where to look next.
Consider using a recursive grep in your gateway filesystem outside of Ignition. (Perspective project files are text-based.)
After using the Find/Replace I found the script. It looks as if the script was to time out a pop up after a certain amount of time. I am not sure which pop up the person who made the project had planned for this timer but the project seems to be running fine without it. After disabling the line that was causing the error, I got this error message.
Would this cause any issues in the long run? And is there somewhere I can go to see 'debug' messages?
What do you mean by "disabling the line" ? Did you comment out a line in a script ?
They should be in the logs. Click the + sign in the bottom right of the log entry to see the stack trace.
Yeah, I commented it out to see what would break, but it seems to be running the same.
Here is a picture of the whole script.
Considering all that script does is sending a message, you might as well disable it entirely instead of commenting out a line.
Commenting it just makes the call to sendMessage fail because the variable messageHandler doesn't exist anymore. This is why you get a new error in your logs, saying that the script failed to execute.
if you wanted to stop the message from being sent, without disabling the script completely, you should be commenting out the call to sendMessage, not just the declaration of the handler's name.
That being said, the comment saying "It's important that the message handler has been created" might indicate that whoever created this script expected someone reading this to actually create the appropriate handler.
Isn't there anyone that could help you figure this out ? Some doc that would point you in the right direction ?
Unfortunately not. Our previous Ignition designers did not leave any documentation for trouble shooting or anything along those lines.
We are going to just disable the message handler until we found out what the original intensions were for it.
No documentation? For shame...
One tool I've been loving to use is the Configuration Explorer - as long as you know the view, you can search for message handlers among many other things. I don't know if this applies to your situation (I didn't read this thread very carefully 
)
