double trouble - part 2 - potential consultation fee

[Ryan Powers]

This concerns the customer who previously had double records through VMWare.
They replaced the virtual server with a standard file server this morning.
Some indexes could be fixed, but not all.

Now, when building indexes on a large transaction file it creates something
he has never seen before i.e. index.A, index.A1, INDEX.B, INDEX.B1, etc.
Their sizes vary from about 12 MB to 25 MB, and the secondaries such as
"index.A1", are almost but never exactly the same size. In any case, this is
a source of confusion.

The next issue is much more serious. When building some indexes he receives
a Window page fault: "The instruction at 0040a1e9 referenced memory at
20202020. The memory could not be read from."

Once this happens, his only recourse is to delete all of the indexes from
the command prompt and rebuild them one at a time. Only by excluding the
problem indexes is he able to successfully build the others.

This is a HUGE problem for a large client. Any ideas would be greatly
appreciated. If you have experience resolving this type of issue and can fix
it remotely through a virtual terminal (such as WebEx etc.), the client is
willing to pay a reasonable consulting fee.


---
Ryan Powers
Bulldog Software, Inc.
http://www.bulldogsoftware.com