Hello, I was wondering if any of the long-time WebFOCUS developers remember a problem they may have encountered in the past - namely the control file, Domainname.htm, sometimes getting zapped to zero bytes.

Do any of you know the reason why this happens?

I tried digging around in FocalPoint but couldn't find anything.

I know I've encountered this in the past and it happened yesterday on the antique system I'm supporting.

Thanks,

This message has been edited. Last edited by: Francis Mariani,

Remember it happening, but don't remember a solution.

Hope you have backups

I found two troubleshooting documents related to this bug.

The first describes what I already remember doing in the past - restoring the domain.htm file from a backup.

80452520 – Not able to access reports in one Managed Reporting domain

It seems I'll have to do what the second describes - I can't view that domain via Dev Studio.

52172518 – Cannot associate domain with WFRS node in Managed Reporting

I remember in some releases, when trying to open a file from an outside text editor and saving changes, it would revert the file to 0 bytes and everything would be gone after. The code was deleted somehow by saving the file from Notepad++. Not sure if that is related or not.

Oh man - I remember that one. I always had to restore from a backup. It got to the point where I saved off a copy before I started an edit.

Our External editor was always set to backup on save.

Its just safer that way

quote:

mes

We found that it was the way the software saved when a change was being made; it deletes the file and then saves the new one. This is great when it works, but zeros out the file if it glitches mid-process.
Never found a fix, just set up an hourly backup process to recover files and a zero-byte scan to find them when it happened

Yes, this is the infamous FILE zero-byte problem. EditPlus has a life-saving option to backup the file being edited. I have backups of files I edited in 2005!

The bigger problem is the MRE Domain "control" (as the documentation calls it) file, domain-id.htm. I've experienced this file getting zapped at least a couple of times in my career. We restored the file, things worked for a day, then things got unstable, so a server reboot (WebSphere, WebFOCUS) seems to have fixed it for now.

My current job is to babysit a dying (v7.7.05) star.

LOL Sooo true... Our's was a 7.6.11 red giant. We barely got the last application off of it before it went super nova on us... *moment of silence/takes hat off*

quote:

7705

As if millions of voices suddenly cried out in terror and were suddenly silenced