Does anyone know why this is happening for me? And how I can prevent or fix it?
Thank you for sharing your questions in PI Square!
Could you please provide us with some more information?
- Is this a new installation of PI Notifications?
- What version of PI Notifications are you running?
- What is the Operative System of the machine that runs the Notifications?
- If in the Pop-Up you press "View the message", what message do you get?
Thank you in advance!
For the additional information:
I "updated" the PI Notifications to the latest version, and this is when the error started. I guess this was when Notifications migrated into AF?? (bit of a novice - sorry!) For the installs I have Notifications2012a, but I am sure this was superseded by PI AF (which I have version 2016-SP2).
The specific notifications manager application (PINotificationsManager) that generates the desktop interaction is version 1.2.1205.10.
The host OS is Windows Server 2008R2 Standard (running as a VM).
The message is "blank" - when I view it I get an empty "CMD" box with nothing in it (see the capture!)
I provide this as I would like to get to the bottom of this specific problem. I appreciate James Devine's advise but I looked at my Services and this ISD service is already set to Manual. I could set to Disabled, but then perhaps I miss some other messages??
I have some more questions:
- I understand you have both Notifications 2012 and 2016 R2 installed on the machine. Right?
- If so, with which logon user are their services running?
- If running as Local System:
- Is Allow service to interact with desktop --> If so disable it
- Are the necessary trusts created for this machine/application?
- Despite this error, is the notifications service running and are the notifications working and being sent?
Thank you in advance,
It looks like I have both "PI Notifications 2012" and "PI Notifications Service 2016 R2" installed.
"PI Notifications Scheduler" runs the service as "Local System"; it does have "Allow service to interact with desktop" checked - I will un-check it. I'm afraid I don't know anything about trusts, etc.!
"PI Notifications Service" runs the service as "NT Service\PINotificationsService"
I thought the notifications were working as I did receive some test messages, etc. - but when I went to look in the AF explorer I got the following message.
So I guess something else is wrong, which might have led to the pop-up error in the first place. Any ideas what I can try next?? I know it was working - 'cos I've got some notifications!!
Is the error still appearing after unchecking "Allow service to interact with desktop"?
I question I still have is: After you installed the new version of Notifications, did you run the migration tool to convert your old notifications into the new ones (notification rules)? Are both Notifications Scheduler and Notifications Service running?
I believe that once you have run the migration tool, got rid of the old notifications and uninstalled Notifications 2012 the error you mention should disappear.
My bit of research uncovered Interactive Services Detection "Enables user notification of user input for interactive services, which enables access to dialogs created" (geek speak I know). This occurs due to the Interactive Services Detection feature available and usually active in older versions of Windows. In more recent versions this Windows this service is 'Disabled' or set to 'Manual' by default. Its purpose is to detect if a service is trying to interact with the Windows desktop. This feature can be disabled by editing this service on the Windows computer.
To disable Interactive Services Detection:
I hope that helps.
I took a look and my service is already set to manual - I guess the only option here is to disable it entirely, which is not ideal if I get another program that wants to send something to the Interactive Desktop (unlikely I know).
I will try it in the short-term, but really I would like to get to the bottom of why it started to happen in the first place - I'm sure it's something simple (or at least I hope so!!)
As James describes, the point of Interactive Services Detection is to alert users when a process running as a service attempts to interact with the user (because this is potentially a security issue).
While it's true that you could disable the Interactive Services Detection service, I think we should take a step back here and see if we can figure out why a service like PINotificationsManager is trying to "interact" with the user. In some cases, this can happen when the service actually crashes, and is trying to present some kind of dialog box to the user. So therefore my fear is that PINotificationsManager may actually be crashing, and we should be addressing the root cause of that, rather than disabling Interactive Services Detection. Could you check your Event Viewer logs for the time that you received that message and see if there was a service crash at that time?
TBH I didn't realize there was a migration tool; I suspect it wasn't used.
At the moment I cannot see what I have for notifications as, explained above, I get a "Failure Loading Notifications" message that prevents me from seeing anything within the AF Explorer.
To return to the earlier point I do not see any further error having disabled the "Windows" service, but to Gavin's point this is just obscuring not fixing the problem.
And the bigger problem now seems to be the loading failure!!
Any further advice from you folk would be gratefully received
All - I checked (and corrected) the migrated notification rules, found a bit of stuff about the SQL permissions (changed users and that stuff), and learned that following notifications migration you can uninstall Notifications 2012. This stops the "Failure Loading Notifications" message above.
I decided to reactivate the Windows Interactive Service Detection, and to date I have not had further windows messages (which were occurring about every 2 minutes) - so it looks likely this error was related to the legacy Notifications install/operation (the service was still running for example).
This uninstallation of Notifications 2012 was not clear during the migration process, but does appear to have solved my problem(s). Perhaps OSI could add a note suggesting Notifications 2012 could be uninstalled once migration is confirmed to be complete and successful. I wouldn't have thought to do this unless I caught the note at the very end of the migration tool YouTube video (OSIsoft: How to Migrate From PI Notifications 2012 to Notification Rules with AF Server 2016 R2 - YouTube ).
Thank goodness you have a great presence on YouTube.
Thanks to all of you who helped Gavin Chen, James Devine Jose Sanchez Colunga
Thanks for the update Stuart. I am in the process of practicing a migration from PI Notifications (a.k.a. Legacy Notifications) to PI Notification Rules. Your willingness to share some of the pitfalls you encountered should prove helpful to me and others about to take the same journey.
Retrieving data ...