• State Verified Answer
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 486 views
  • Users 0 members are here
Options
Related

PI Archive Subsystem service not starting

Jwarren

I have a PI system that has been functioning for ~ 3 years and stopped functioning about 2 weeks ago. The first error thrown was "File system low on disk space". The C-drive still had about 90 GB free and the archive drive (D-drive) had about 75 GB free. I have since freed up some space and had no success getting it functional again.

I restarted the computer to see if it helped but since then I have not been able to get the PI Archive Subsystem service to start. I manually start it and it stops after 2 seconds. I used the PI OPCClient to verify I am receiving data from the source computer so I believe the issue is locally getting the archive to start functioning.


image.png
I tried to start piarchss.exe from command prompt to see the info and it appears to start and immediately shuts down.


image_1.png
Is there something else I should be checking prior to starting the PI Archive Subsystem?

  • 0

    Take a look at the windows event logs as well as the PI Server message logs.

  • 0

    I am unable to view the event logs from the initial failure but I restarted the computer and see this failure message pop up.


    Windows event log.png
    Looking in the PI messages There are about 40 errors related to the point table, other than that here is what I see:


    Pi messages.png
    Any thoughts for where to go from here?

    I think I'll try to start the OPC interface and see if the messages from that are useful but otherwise I'm not sure where to go.

  • 0

    I think we found our issue.

    Digging through some other info we ended up checking the archive manager data file and it was empty. Not sure how this happened and still looking for the source of the issue.

    When we repaired the piarstat.dat file we selected a random archive file as primary because our file names did not make it clear which was the primary file.

    This allowed the archive service to start but threw a different error for not having a primary archive file. We were able to re-register all of the old archives and found the primary file that way.

    The PI server appears to be back online and functioning now.