Please do not start a new question on a post that is several years old. Do start a new brand new post that is specific to your question and that you may mark as being answered. I have branched your question to its own thread, and moved to general "All Thing PI" space.
It may help to know your version numbers of PI Data Archive, AF, and Notifications. It is especially helpful to know if you are using Notifications 2012.
3 of 3 people found this helpful
It sounds the Notifications service doesn't have permission to create points on the server. History point creation is done via PI SDK but writes are done via PI API, so it's possible that you've got security configured in such a way that existing notifications work but new ones do not. Notifications 2012 logs *might* help but what might be better is looking at the data archive logs to understand why the login failed. Perhaps it did not match one of your trusts (e.g. it came in with a fully qualified domain name rather than just the machine name or IP). Notifications 2012 should appear as "PI Notifications Scheduler" in services:
"PI Notifications Service" is 2016 R2 or newer.
Thanks, It turns out that windows trust was higher than PI trust. Promoting PI trust to top of list solved my problem. I think windows may have been promoted to solve another issue a couple years ago.
Cogentrix Field Services<www.cogentrixfieldservices.com>
We'd recommend to slowly phase out the use of PI Trust and use PI Mappings instead. I simply wanted to mention this, since the solution to your issue was to use a PI Trust rather than configure a PI Mapping and use WIS. Our best practices are discussed in this KB article:
Happy to hear that you got your issue resolved! I just wanted to communicate our security best practices.