"Service not registered; InSQLIndexing;5; Access is denied"

Hello, We have a customer who came with the error on his historian "Service not registered; InSQLIndexing;5; Access is denied"  From one of the past cases this error was resolved by running the aahSecurity.exe, he ran it and it resolved that error in historian but he got the PCS error "Unable to determine the Default PCS Solution from the configuration. For more information, see the **Repairing or Re-installing Platform Common Services” section of the AVEVATm Common Services Portal User Guide**, he followed the TN10500 to resolve the PCS error, but the historian error came back again. This is Aveva Historian 2020 R2. Does anyone know what is the cause of this?

Parents
  • Normally there isn't any interaction between "InSQLIndexing" (a local Virtual Service Account used by the "aahIndexSvc.exe" service) and PCS components. Several questions about this:

    1. Have you manually changed the identity of any of the Historian services (e.g. through the Windows Services console) or kept the default?
    2. What other AVEVA software is running on the Historian node (e.g. Application Server, InTouch, etc.)?
    3. What other AVEV A software is running remotely and using the same SMS configuration?
    4. What triggers the "not registered" message (e.g. attempting to start Historian)?
    5. Where does this "not registered" message appear (e.g. in the SMC Log)?
    6. Does it make any difference if you restart (either Historian or the node) after running "aahSecurity.exe"?
Reply
  • Normally there isn't any interaction between "InSQLIndexing" (a local Virtual Service Account used by the "aahIndexSvc.exe" service) and PCS components. Several questions about this:

    1. Have you manually changed the identity of any of the Historian services (e.g. through the Windows Services console) or kept the default?
    2. What other AVEVA software is running on the Historian node (e.g. Application Server, InTouch, etc.)?
    3. What other AVEV A software is running remotely and using the same SMS configuration?
    4. What triggers the "not registered" message (e.g. attempting to start Historian)?
    5. Where does this "not registered" message appear (e.g. in the SMC Log)?
    6. Does it make any difference if you restart (either Historian or the node) after running "aahSecurity.exe"?
Children
No Data