Topic: corrupt data

[M Alden]

Hello,

We have a client that we've been slowly moving all of their servers over to SME boxes from Win2k boxes. Everythings been going well until the last server.  

When we try to bring up the data files for their last app, the database is corrupted on the client side.  It's not really a database; it's just their data files.  The actually program does not work off the server; we just have it store its data files there.  It's a mortgage app called POINT. If we move the data files back to a Win2k box, everything is fine. We tried bringing up the data on a 5.6 box, and a 6.3 box. Both have same results. We tried creating a whole new data file, same results. The names and addresses are all messed up when you bring up the client software every time.

I was just curious if anyone had every experienced something similar, and if anyone can offer a solution.  We would really like to bring down this last Win2k box...

Thanks,
M Alden

[Brad D.]

Have you tried copying the files via "FTP" and setting the mode to "Binary"?  I had a similar problem with MYOB Accounting .PLS files over FTP links.

You could also perform a MD5 signature test. That would let you know the file is not being damaged during transit. See: http://www.flux.org/pipermail/linux/2002-March/007716.html

[bob]

I have 2 systems running SME 5.6U5, and using Point software with no corruption problems. I jsut set up an I-bay, caled it Calyx, and coppied all the pntdata and template folders to it. It works like a champ

Bob

[M Alden]

Interesting...  I guess its good news that other people are using POINT on SME boxes and it works...

We were on the phone with Calyx about this. They said they don't support Linux, but that they've never heard of this issue.  What happens is that the person's name that you pull up does not correspond to the correct information. It's like its somehow getting crossed up, if that makes any sense.

Now that we know that it will work, we can keep trying other options.

Thanks!

[Paul]

I have also been using Point for almost a year on with SME 5.6.  I have never had data problems and we have 8 clients accessing the same data.  Make sure you do all the updates on the server because there is a samba update that helps with file locking.

As a matter of fact, the same hardware with SME 5.6 installed is about 1.5 times faster than Win2k was.

I installed the client software and network database together from the start.  This creates all the necessary files and folders on the server.  The data files are all seperate and there is a db file that syncs the searches to the actual data files.  This is where you might be running into problems.  Try the following:

FIRST OF ALL, BACKUP ALL THE DATA ON THE ORIGINAL W2K SERVER THEN:

1-Copy all of the original files using the "copy" utility within point from the original W2K server to one of the clients "local directory".

2-Delete ALL files from the new SME server as if you were starting from scratch.

3-Map the directory (on the client) where the network files will be.  I think I had to actually MAP the directory under windows for it to work properly.
 
3-Re-install Point on one of the clients (or Install on another machine that does not have point installed yet) and tell the install where the local data files are and tell it where network files are mapped.  This will create a new db file from scratch on the server and all the other necessarry files and folders.  If you get an error during install (this has happened to me) then you don't have permissions on the server set properly.

4-Copy the files from the local directory back to the network using the "copy" utility within point.  This will update the db file on the server and everything should sync properly.

If you are not sure what all this means, email me and I will give you my phone number so you can call me.  It would be a lot easier to explain this in person.

Good Luck

Paul

[Paul]

M Alden

Scratch the original post of mine.

I have found your problem (I think)

There are 2 files in the PNTDATA directory that are the db files that I talk about in my first post.  They are actually indexing files and are named BORROWER.IDX and PROSPECT.IDX.

These 2 files are the indexes for the borrowers and prospects.  If you rename these files (eg: BORROWERS_OLD.IDX) and try to do a search then you will receive an error from point.

To fix this, go to the right of the startup screen and click on the "Rebuild List" tab and then either the "Prospect" or "Borrower" button and it will rebuild the list properly.

I would try this first.

Sorry if I confused you.

Paul

[M Alden]

Paul,

Very cool!!!  Thanks so much!!  We'll try to rebuild first, and see what happens.

Ever think about working for Calyx?? You seem to know tons more then they do...

[Paul]

I don't rely much on any customer support.  I usually figure out problems before CS picks up my call off of hold.

CS at most companies seem to be glorifies sales people that know slightly more than just how to sell their products.  

I have basically given up on CS departments.  I get better and faster answers on forums and web boards.  Just look at your example: You will probably solve your problem before Calyx calls you back next week some time

If you have any more questions, email me and I will be glad to help.

Good Luck and post back with results,

Paul

[M Alden]

Paul,

Well, more news to report - despite your best effort, neither of your suggestions helped...

Your second suggestion was the one actually recommended by Calyx, and already tried by our tech - though he did go through your steps just to make sure.  Your first suggestion was hopeful in the beginning, but the old problem resurfaced after a bit of the data was copied over.

We are now thinking that the problem may be that the database is too large. Calyx had said something about not having any more than 400 or so entries per folder.  Ours has over a 1000. So, we broke it down into separate folders - still same problem.

Armed with this new information, we are going to try again with their support and see if any headway can be made.  The most promising news we can tell them is that it is not a file system or OS issue, but a Calyx issue - as it works on other systems (yours).

Any other ideas would be greatly appreciated!!!

M Alden

[Paul]

M Alden,

I have been around Calyx Point for about 12 years (back when it was still DOS based) and I am having flashbacks of a problem similar to yours.  It was on a Novel Network with old coax cables (remember those?).  I'm going to have to see if I can contact the original IT guy but I think it was actually a hardware related item like a cable or network card.

Let me see if I can contact him, it's been about 5 years since I saw him last.

Just a couple of questions:

1-Is the index just out of sync or are the actual data files messed up?

2-What OS is on the client?

You may also want to try to connect a client directly to the server with a "cross-over cable" to eliminate any possible hardware/cable problems and start from scratch with a new I-bay (named something completly different) as follows:

Let's make sure you create the I-Bay properly.

a-In the server manager choose "Information Bays"
b-Click "Click here to create a new information bay.
c-In the "Information Bay Name" put calyx (or pntdata or point - all LOWER CASE and keep it short with NO SPACES)
d-In the "Description" put Point Data
e-Pick the correct group
f-User access via file sharing or user ftp  "Write = group, Read = group"
g-Public access via web or anonymous ftp "None"
h-Execution of dynamic content (CGI, PHP, SSI): "disabled"

This method will disable the web server on this share and will create a samba share that when accessed through "My Network Places" (WXP) or "Network Neighborhood" (earlier Windows versions) will show an empty directory on the client.  If you see directories like "cgi-bin, files and html" then you have created a different type of ibay and I don't know if it will work properly that way.  

SME will always create the cgi-bin, files and html directory on the server but when the ibay is used as a smaba share (as created above) it will put you directly into the "files" directory through "My network places" and you won't even be able to get to the cgi-bin or html directories.

Now you can "Map" this share on you windows client as lets say "F: calyx on Mitel SME network server"

Now try to install Point and tell it during install the the network path is just F:\

I know this is getting a bit complicated so if you would rather call me, just email me and I will give you my number.

Paul

[M Alden]

Paul,

Thanks again for your continued help.

I pretty sure the problem is not network/hardware related, as all the servers are in the same rack, and we've tried putting the POINT files on several SME boxes (5.6 & 6). We are actually doing all of this testing on a separate, none critical box.

1) All of the clients are Win2K.

2) The problem that is exhibited is that when you click on somebody's name, an entirely different person's info comes up.

And, actually, everything works fine on the SME box UNTIL you go to rebuild the list, then it all craps out.

Now, I'm pretty sure that this is NOT and SME issue, as you and a couple other people use it successfully.  Weird thing is why the heck does it work on a Windows box and not be all weird on it???

We are using RAID, though. Could that be the problem??? Just thought of that. Maybe it can't handle the drives??  One box is hardware RAID 5, and the other is software RAID 1.  We will try it on a single drive and see what happens.

M Alden