Skip to main content

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

What is the version of recover1 ?

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

What is the version of recover1 ?

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

If you're sure the logic of your programs are working fine, then I suggest check the NIC cards on each PCs, router or hub and the cable net.

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

Amy, are you sure that recover1 is doing a complete rebuild in place?  recover1 has a mode where it only resets the 'open for modify count'.

Assuming recover1 is in the rebuild mode, what is the output of the file integrity scan (page 648 in the User's Guide)?  And then, what is displayed at the termination of recover1?

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

I am also interested in this thread. One of our many customers is getting multiple 98,38 erros as well as other 98,xx erros that we never see with other customers. After exhausting all of the solutions we could come up with we have determined it must be network related. Can you elaborate on the hardware issue you suggested and how they would affect the programming?

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

I am also interested in this thread. One of our many customers is getting multiple 98,38 erros as well as other 98,xx erros that we never see with other customers. After exhausting all of the solutions we could come up with we have determined it must be network related. Can you elaborate on the hardware issue you suggested and how they would affect the programming?

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

The biggest networking issue affecting file integrity on Windows networks is opportunistic locking, which must be turned OFF. See page 703 in the User's Guide. (This affects all software that is sharing files in a manner that differs from Microsoft's notion, which allows clients to read ahead, cache and all types of nasty things when files are being shared.)

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

I'm using the Recover1 with Runtime 12.06

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

I'm running Recover1 like this: RECOVER1 UB410000.DAT AMYTEST.TXT

When I run Recover1 it tells me that the file is not marked as needing recovery. My support Rep was the one that first ran the Recover1 when the customer called about the issue, so I have no idea what the screen said when she ran it.

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

Do ls tests of your program by accessing that file on a local machine to confirm that the error is given by the index damage or not.
If this test persists the error request Microfocus the latest version of Recovery to solve this problem.
Replace if with this test the error does not show it in the local area, should review its topology and see which are the blocks that are being generated.

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

By loading the Version 12.12 of Recovery and Running it on my own PC I was able to Recover the File.
So Strange.

One of our customers is having an issue where they are getting a 98,38 error on a specific record.  We run Recover1 on the file, and Recover1 says it fixes the file, but then when I bring that customer back up in our software, I am still getting the 98,38 error.

Is there anything else I can do to fix this error?

 

More than proving the recovery verify that your program can operate with that file. If it works correctly, definitely check your platform and topology.
Terms & ConditionsAccessibility statement