We have not seen this specific issue reported, but there are situations that can persist that might lead to unexpected behavior including the following:
1 - Are their problems with that specific instance of the node or with the diagram itself? Diagrams depend on a great many files as do the individual nodes. Should one of those files encounter a problem (e.g. corrupted, written on a bad hard drive sector, etc...), you can see strange behaviors. Solution - In cases like this, replace the node with a new one and see if the behavior persists. At times it might be necessary to build a new diagram (or even a new project) but these latter cases are extremely rare.
2 - Has the project been imported from a prior version or different operating system? Importing projects from older versions of the software or from different operating systems might lead to problems. Solution - In cases like this, it might be necessary to build a new diagram (or even a new project).
3 - Are you using the version of Java that was tested for your installation? Java versions are not always backwards compatible but your Java installation often prompts the user to install updates. Updating to newer versions of Java that have not been tested with your version of SAS Enterprise Miner can lead to strange behavior. Solution - In cases like this, you should modify your configuration so that the correct version of Java is being used by SAS Enterprise Miner.
4 - Are you having any issues with memory -- either Java memory, disk space, or RAM? When Java runs out of memory, it often leads to strange unreplicatable behavior. Likewise, if you are running low on disk space or your memory is being heavily used since there are several other applications running, you can also encounter unusual behavior. Solution - In cases like this, you should make more memory available, either through modifying your Java memory allocation, shutting down other applications, or archiving files to make more disk space available to SAS Enterprise Miner.
I hope this helps!
Doug
