Emerson Exchange 365

Data base connection

Dear all,

     in my plant the ups failed so we resorted to using our blackstart gen as ups to power our pro plus server while work is going on to get the ups going. but eventually the black start gen developed problems too and we started having on and off erratic power supply to the system which shutdown the pro plus and controllers without going through the normal shutdown process this happened a couple of times before our power was restored to normalcy. when power was normalized, we powered the system the pro plus, app station and operator stations all came on and deltav operate runs fine on all. but when we tried to lunch explorer from the pro plus we got this message

"Connected with the database server but failed to open a database connection. please read read specific message below and take appropriate action.

Reason:

failed to open the database. please check the event log on the pro plus for details.

we checked the event log but all it says was error with time and date

it is a version 7.2 

thanks

molly

• 23 Feb 2017 10:26 PM
• Cancel

21 Replies

• molly

  

  • 12 Mar 2017 8:09 AM

  In reply to victor:

  folks,
  i did two experiments on the above issue with a deltav standalone, first i tried the suggestions of wharrnet as explained but the result turns as this, the areas and logic all were imported but the controllers, proplus, App station and operator stations were not imported from the .fhx files.
  
  a second trial was using Roman kostuniak suggestions on the same standalone station after the import, all areas and logic, controllers, proplus, app station and operator stations were imported as it was in my plant config. my problem here is am not sure if all communication config is imported as the check box in creating a new database in Roman Kosttuniak case did not include the preserve network definition . also one more thing
  while importing this dialog box comes up
  
  The data base already contains an existing object " thesite' would you like to update the existing object in the database.
  it has options of
  YES, NO, NO TO ALL, CANCEL . here which is the option to choose
  thanks once again for your time

  • Cancel
• victor

  

  • 15 Mar 2017 4:59 PM

  In reply to AdrianOffield:

  We performed the procedure and we are still on it.it was successful except for a particular segment we cannot down any device.It keeps stopping with hardware or comms problem.What do we do to download on this hi channel.

  • Cancel
• victor

  

  • 15 Mar 2017 5:12 PM

  In reply to victor:

  we need some help here!

  • Cancel
• molly

  

  • 15 Mar 2017 9:12 PM

  In reply to victor:

  those segments or cards are they enabled? right click on p01 or p02 see if the card is enabled or drop down the particular controller from I/O riht click and do an I/O auto sense good luck

  • Cancel
• Andre Dicaire

  

  • 15 Mar 2017 9:51 PM

  In reply to victor:

  Victor. I reviewed all these calls and it is not clear what was done, and where exactly you are in your recovery. Adrian suggested you call the GSC, and I agree. Although everyone on the thread is trying to be helpful, there is a significant lack of detail that may have led to some loss of Data.
  
  Having said that, you now have a download issue with a "segment". From that, can we assume that your Pro Plus is fully recovered and is operational? Have you downloaded your entire configuration from this new database, and the only issue is this segment? or is this the first segment you download?
  
  Is this a Foundation field bus card. You message above states "hi channel". did you mean H1 Card? Or is it a DeviceNet, Profibus, A-si card.
  
  If everything else is working and you have only this single download issue to an H1 segment, you might start by ensuring the segment power supply and wiring connections are good. especially if you cannot communicate with any device on that segment. Are both segments affected on the card, or just one. What do the H1 card diagnostics say? It would be easy to replace the H1 card to eliminate or confirm the issue is or is not with the card. If you have a physical layer diagnostic tool, confirm the physical layer is good. With the Segment power good, H1 and physical layer checked, next confirm if you can simplify the segment and get at least one device working. Disconnect devices at the Segment brick/hub to see if you are able to restore connection of one or more devices. If that enables communication, reconnect devices one at a time until the issue returns. This is assuming the issue is due to a device.
  
  If you need quick response, you need to engage the GSC so they can help identify the underlying issue. Posts on this forum are not necessarily going to be responded to quickly, or correctly. And if my suggestions above are completely unrelated to your issue, I could be wasting your valuable time. If your plant is down, please call your local Emerson or LBP service provider.

  Andre Dicaire

  • Cancel
• victor

  

  • 16 Mar 2017 9:37 AM

  In reply to Andre Dicaire:

  Thanks.We worked thru your suggestions and got it solved.we cleared our comms isssues by replacing most the devises on the segment but found the problem in the control studio for a particular unassigned fb for the device.we did the assignment and the download was successful.our plant is up and running again though not yet fully commissioned.we are downloading every fb device and this is taking time.is there a fasterway of doing this?

  • Cancel