• Not Answered

Process History View of one of the area not appearing

Hello;

       We have a DeltaV 11.3 on Windows 7 With 01 Engg. Station (EWS) & 02 Operators Station (OWS-1 & 2). Each has 02  different areas assigned to it's historian. From Few days. OWS-1 has stopped giving Historical trends of one of it's Area. & other Area is giving historical  trends. We have downloaded the Cont. Histo. but it wont help.In diagnostics of it's continuous historian it is showing " Continuous Historain Server Stopped -- Yes". I'm unable to understand why this is happening. Kindly Help. 

5 Replies

  • Which diagnostic parameter is showing this message?

    From the article on Continuous Historian Diagnostics, it seems likely to me that you have either run out of space on your drive, or are otherwise unable to record additional data due to permissions:

    http://www3.emersonprocess.com/systems/support/bol1231/c_continuous_historian_diagnostics.html

    Is DCSTOP = YES? 

    DCSTOP

    Boolean

    0=NO, 1=YES. The string value is displayed in Diagnostics.

    YES if real-time data collection has been stopped due to:

    • Data storage (database) could not be opened for writing

    • Data storage disk has too little free space for normal operation 

    NO otherwise. If YES, forces OINTEG to 1 (BAD).

     This wouldn't explain why one area is being historized and the other not, however. 

    Can you provide the value of all diagnostic parameters?

  • In reply to Youssef.El-Bahtimy:

    Thanks!!
    Yes DCS Stop is the message(as Yes) Bad reads are Zero. Bad Writes are 177(the no. of tags in this area) space is not a constrain I have checked it." •Data storage (database) could not be opened for writing" Could be the issue. But how to resolve this. I have tried with deleting this area from the node & reassigned again, but this also wont help.
  • In reply to ghatevinod:

    Have you looked at the Continuous Historian Administration console?  

    Can you check to make sure the DeltaVAdmin account in not locked out?  If using a domain, please check the local deltavadmin account on the historian app station and the domain deltavadmin account.  If using workgroup, just check the local on each node. 

    There are several easy ways to do this. I check accounts quickly by using the command

    • net user deltavadmin
    • net user deltavadmin /domain

    and look for the Account active field.  

    Ensure the passwords on the local and domain accounts match.  Run the following commands and enter the password.  If another command shell opens, then the pw is correct. 

    • runas /user:machine\deltavadmin "cmd"
    • runas /user:domain\deltavadmin "cmd"
    • (where machine is the local machine name and domain is the domain name)
  • In reply to Youssef.El-Bahtimy:

    Thanks Youssef!
    Can you Expali in Simple word & stepwise. I'm unable to understand. Sorry!
  • In reply to ghatevinod:

    Ok, on the app station, check Deltavadmin account status

    1. open cmd.exe

    2. in the command prompt, type

    net user deltavadmin

    3. Observe the value of  Account active.  It should be Yes.

    4. Repeat for 

    net user deltavadmin /domain

    Next check to ensure the local deltavadmin and domain deltavadmin passwords match.  If you did not set the deltavadmin password during installation or you set it to default, disregard this step. On the app station, log in to Windows using the appstation\deltavadmin account and the domain\deltavadmin account.  If you can do so using the same password, you are good.

    Open the Windows event logs on the app station.. You can enter eventvwr.msc in the windows run menu or command prompt, or open it from the control panel-->administrative tools.   Look in the application and system logs for any warnings or errors that pertain to the continuous historian system. Let me know if you find any.