Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OFO not available until reboot

Status
Not open for further replies.

Lightspeed1

Technical User
Mar 27, 2002
58
US
Hi all,
Running BE8.6 on new NT4.0 SP6a + Exchange5.5 SP4 server
I am continually getting
OFO: Open file option not available until system has been restarted
OFO: Initialization failed on C:

OFO: Open file option not available until system has been restarted
OFO: Initialization failed on E:

Even though I have rebooted multiple times. When I uninstall OFO I get the message that the uninstall failed to remove the "Open File Option uninstall string" registry entry and to remove it manually. However, when I look in the designated registry section the directory referenced in the message is not present. I have done a search in the registry for anything referencing Open File Option and have come up empty. I have installed and uninstalled the main BE component multiple times and this does not seem to resolve the problem either. I also have noticed that I am getting an error in the event log - Event ID 7000 - that indicates that the "Open Transaction Cooridinator" has failed to start because the file cannot be found. When I try to start the service (which is set to start on boot - but is not started)I get the same message about the file not being found. If I try to start the service manually I get the message indicating that "the system may become unuseable, am I sure that I want to continue?" I have already done one 12 hour emergency rebuild on a crashed server for these folks six months ago and am not anxious to do that again. I have noticed that when I uninstall the OFO, the Open Transaction Coordinator service is gone, so they must be related? I have searched the Veritas knowledge base as well as Microsofts and came up with nothing. SO.. sorry for the long winded post but I am at my wits end!!! PLEASE HELP!! Not only is the "Backup Failed" message embarrassing, but this is one of my largest clients and I ( and my kids!!) can't afford to lose them.
Regards,
Lightspeed1
 
Tough one. I would try again to unistall OFO, including the Serialnumber, reboot. Before you install OFO again, reapply the SP6a and MDAC the machine with MDAC 2.6 and the Jet Engine. You find both on the Microsoft download site.
Reboot and install OFO. If this still don't work, then I would consider to phone Veritas Support.
 
Thanks Tilo - I have gotten a day or so away from the problem (and had a stiff drink!) and reloading the service pack had occurred to me. hmmm... MDAC component re-load also.. have to try that too. I have removed the serial numbers on the main BE component as well as the OFO serial on uninstall, think I should try a search on the registry to verify NO BE components left over.
Thanks for taking the time to reply, It's nice to just have someone else scratching their head too!! I am going to get on the horn with Veritas. I'll run the the BEDIAG, maybe there is a system config conflict.
Regards,
Lightspeed1
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top