Okay so now that I'm connected to my virtual learning environment I'll go to PIClient01 and
open the PI Vision display. There's a shortcut for the PI Vision display on your desktop,
you can double click on it. Alright the PI Vision display shows that the tag is
indeed not updating. So the next thing we're going to do is to go to PISRV01 which is the
machine where PI Vision is installed and then change the collective priority. We can use the
PI SDK utility to do so. So I'm going to click on that to open it and what you can
do to go to the member setup is to right-click on this server and then select member setup.
So here you can see that the priority of the primary is negative 1 which means that every time
PI Vision opens it'll connect to the secondary one, it'll prioritize connecting to the secondary
one. So I'm going to change this to 1 enter and then okay. For this change to apply to PI Vision
I'm going to do an IIS reset. I'll right click on start, open command prompt as administrator.
Okay now that this is done I'm gonna go back to PIClient01 and I'll refresh my browser. Here we
have data now. The issue is resolved. No, the issue is actually not resolved this means that
buffering was either set up incorrectly or it is not set up at all. So we need to go to the
interface node and check the buffering status. But before we do that we can check the current
values for both members of the collective to see what the values look like. I can use this button
to clear everything that's loaded to the current values plug-in and then we'll do a tag search.
I'll look for example tag. Actually instead of doing a text search on example tag I'll search
everything that has a point source of OPC and then search. I'll select all and then
click OK. So this actually just loaded the data for PISRV01 so what I want to do is to
check PISRV02 and do the same search again. So I'll do tag search, select all and then
okay. And now you can see that the tags from both servers are loaded. Let's find example tag here.
Okay so it looks like example tag is currently updating on PISRV01 and it's not has not been
updating on PISRV02 since the 6th of February. Next we'll go to the interface node and check
for a buffer configuration. Alright so in the interface node to open buffering I need to go
to tools buffering so this tells me that buffer has not been configured yet and it's asking if I
would like to configure it no. I'll click on yes, continue with configuration, select my collective,
next okay. Here we see that buffering does not have permissions on the data archive. What we
can do is change the PI buffering service to run under service account that does have permission.
All right so I already created a mapping for PIBuffss, these are the credentials for it
we'll go ahead and change this to run under the service account. The user is PISchool
SVC PI buffer. I'll use Windows account and the password is recover meal specialist. Next you see
here that I passed the security test. Next, okay it has completed, but it says that there there
has been some errors so let's view the messages. So we see the 10401 errors. I happen to know that
these errors mean that the buffer service does not have permission to write to the PI points,
but if you did not know what those meant you could either do a Google search or go to your
customer portal and search this error, you'll find articles that will indicate what this error means.
Looks like we've been getting those errors for all of our PI points because buffering
does not have permission on any of them. We're going to close, I'll go back to
PIClient01 because that's where I have SMT opened, I'll go to a point builder, general,
then I'll type in example tag. I'll go to security and add the buffer identity so that I can give it
the appropriate permission it needs on this PI tag. Add, PI buffers is mapped to the service
that's running buffering. I'll add that okay this identity only needs read access to the PI point
so they can read the PI point configuration and then under data security I'll add the
identity but then on data security it will need to read and write so that you it write the data
to it. Go ahead and save. Okay if we go back to current values let's see if our tags are updating.
Play, sure enough example tag is updating on both members of the collective. Now we need to
apply the change to the rest of the PI points and we can use PI builder to easily apply that
change to the rest of them. So go to start and I'll open Excel. Okay open a blank workbook,
I don't need this book anymore so you can go to the PI builder ribbon make sure that the correct
servers have been selected, I'll go to PI points, find PI points and then I'll search for PI points
with point source OPC. So my previous search was that so it will already be in there but
you can remove it and then add OPC or any other point source and you'll be able to search for
all of the tags associated with that. So okay and here I have the option to select
the columns that I would like to edit, the only things that I'm interested in are data security
and point security and I already have those pre-selected so I'll go ahead and click OK.
So here you can see that the data security for example tag differs from the rest of
the tags and this is because we added the PI buffers identity to example tags. So I'll go
ahead and copy this. Actually it might be even easier if I did this and then paste
that there and then just double click on here so that it can apply the change the
rest of the rows. Okay now that I made my change I'll go ahead and publish and I just
want to edit the tag configuration so I'll click Edit only. Okay. The requested action
is complete go ahead and close. Now let's go back to PI SMT to make sure that the changes
have been applied and you can see that the working tags are updating with good values.
The next thing we're going to do is reinitialize PISRV02, so we can go to PISRV01 and open the
collective manager. Okay you want to select PISRV02, right click on it and then reinitialize
server. So if you had multiple archive files here you'll be selecting only the archive files
that cover the time range of the missing data in PISRV02 so they can copy them over from PISRV01
to PISRV02. Next, this is just telling us that the archive file will be backed up and then will
be copied and then this check mark shows that it will be deleted the backup will be deleted
after it's been copied to the secondary. Okay you can just click next until the end of it.
Okay PISRV02 has been successfully reinitialized,
finish. Alright when you have the green check mark and you confirm that everything looks good
we can go ahead and close collective manager. This concludes lesson 2.
In the next lesson we're going to talk about asset framework and how to set
up an alert to notify users when your data goes stale and/or if you receive bad data.