Re: MF Runtime Error 077

On Jun 27, 8:27 pm, Michael Russell <Michael.Russ...@xxxxxxx> wrote:
MicroFocus documentation:
077 Internal ISAM module error (Fatal)

* This is the result of an internal system error.

Contact Technical Support who will help you discover
the cause of your error and how it can be rectified.

Looks as though you have to contact MF, then.

Regards

Michael

razor wrote:
I am running MF Netexpress 3.1. System is very stable, no upgrades for
years. I am getting a runtime error 077 when attempting to perform a
particular job. When I transferred the data back to my own machine,
the error does not occur. Normally, when there is a corrupt file I
would expect to experience it as well.

The MF help says contact tech support and they will help discover the
source of the problem.

Problem is, I am a sub-contractor maintaining a system for another
party. They are the ones who can contact tech support (they only have
one copy of N/E 3.1 under maintenance) and they are not very proactive
about it, preferring to try this and that (rebuild, etc).

Has anybody had this error before? I have been doing M/F 20 years+ and
I don't recall it.

Any clues what it may be?

I'm starting to clutch at straws now. I have an alternate key where
there are probably many hundreds of records with the same value.
Theory says this is ok, but hmmmm...

Many thanks

Ian R


Thanks for taking the time Michael but all you did was repeat what I
had written.

As I stated, I can't get hold of MF directly so I needed to fix it
myself, which I did....

I performed index reorg and rebuild of file. Previously, this on its
own did not fix it as the error always came back later in the day. As
I stated, I had an alternate key where many 100's of records would
have had the same value. This is an obsolete key that is not used any
more and so does not generate any unique data. I wrote a small prog to
read these records and 'unique ise' them with an incrementing value.
This seems to have done the job (fingers still crossed).

I think maybe the internal ISAM error reflects the fact that maybe the
system could not cope with so many non-unique keys. Maybe?

Thanks


.

Relevant Pages

  • Re: Windows shuts down or restarts on its own
    ... Technical support at this point is useless. ... I installed a fix from HP that I thought would fix the problem. ... repairs several times but I'm still having the problem. ... You have a laptop, right? ...
    (microsoft.public.windowsxp.general)
  • Re: Moving house
    ... I can second a recommendation for Newnet - that's who I use at home. ... I've never had to speak to their technical support, ... area and giving an estimated time for a fix, ...
    (uk.net.web.authoring)
  • Re: Linux is KING - Couldnt be hacked - Mac, Vista went down in flames
    ... Yeah, technical support lines, anti-virus companies, spam... ... I view being asked to fix someone's PC like they'd just asked me to ...
    (Fedora)
  • Re: KB942615 December IE Cumulative Update - Crashing IE
    ... Microsoft said they are working on a fix for the problem with URLMON.DLL ... The technical support ... Please let the critical update install again and apply the workaround. ...
    (microsoft.public.windowsupdate)