Recent Control & Safety Systems Discussions
Similar Posts
Status: OPC Server init failed: hr=8008005. Error Msg: Server execution failed
Why am I getting "Write Failed" for quality?
Question regarding historical data access 'Login Failed'
Batch Exec failed to verify due to transition rather than termination in an operation. Possible impact?
Batch Executive - Bad Phases when Disabled?
Share

Execute Batch and Failed “Write to REQUEST attribute Failed” when try to access request.cv. (I.g 3404)

Hi, Emerson Exchange 365 users. 

Problem in Batch execution that  “Write to REQUEST attribute Failed” when try to access request.cv. (I.g 3404) for displaying prompt message for operation. 
is any way to solve it? 

chanwoopark
  • Youssef.El-Bahtimy
    I believe this happens when a previous attempt to request a prompt was not completed. In other words setting the request twice without waiting for it to get cleared out by the batch executive in between requests. Check your phase logic and make sure you have a confirmation for each request to be reset before transitioning.
  • Matt Stoner
    This failure occurs when your logic writes to REQUEST while a REQUEST code is already active (non zero value). It could be previous prompt but it can be any other request code (i.e. download parameters, acquire device, etc).

    Make sure all your REQUEST writes have a confirm that the REQUEST is 0 before proceeding. If you have some timeout feature then you need to abort the REQUEST by writing a 6000 as this is the only value supported to overwrite a previous REQUEST.
  • greenst1

    In reply to Matt Stoner:

    Is this the case just within a given phase ? What if there were multiple phases (not even on the same unit or within the same batch) requesting ownership of a shared resource ?
  • chanwoopark

    In reply to Matt Stoner:

    Hi Matt thanks for reply. it's correct what you mentioned that request was being activated and what causing that error message!
  • chanwoopark

    In reply to Youssef.El-Bahtimy:

    set transition not to move next step unless request=0. thanks !
  • chanwoopark

    In reply to greenst1:

    i believe differentiate by number of message. ig 3401/3402....(depends on message number assigned)
  • greenst1

    In reply to chanwoopark:

    That could be a solution for message requests but for other requests e.g. phases in different batches make a 40xx request to take ownership of a shared resource (xx = Equipment ID) - can have the same error?
  • Matt Stoner

    In reply to greenst1:

    The phases have their own request parameter, so it is only for the same phases that writes to it's own REQUEST parameter while it is non-zero with the exception of 6000 which aborts the current request. Parallel phases on the same unit can write to REQUEST parameter without failure.

This is the official online community site of the Emerson Global Users Exchange, a forum for the free exchange of non-proprietary information among the global user community of all Emerson Automation Solution's products and services. Our goal is to improve the efficiency and use of automation systems and solutions employed at members’ facilities by sharing our knowledge, experiences, and application information.

User Groups | World Areas | Community Guidelines | Legal Information | Privacy Policy | Contact Community Manager

Website translation provided by Website Translator

© 2015-2022 Emerson Global Users Exchange. All rights reserved.