Followup weirdness:  I've used SDesigner on a post-import dsr on my C: drive.  Since I'm not sure if my latest reprogramming will work the way I want it to, instead of reconciling I used "Save As New Application" to create a db, also on my C drive.  I've opened the db and everything looks fine, but of course none of my lookups will work because all those files are on the F drive.

So I copied the db to the F drive.  Then I fired up Sesame as a client with my usual client icon, and tried to open the db.  Failure.  All the logs tell me is that it failed to open.  I unlocked it in case it was locked.  Failure.  Copied it back to the C drive, opened with a Sesame standalone, success.

In case it is my connection or something related to my own computer, I've tried opening it from the fileserver's own client.  That was 40 minutes ago.  The screen shows "working" in the upper right.  Hung?

While the server's client was flipping me the hourglass, I copied a known good pre-import db to the fileserver and tried to open it with my workstation's client icon.  After a few minutes I got the message "Failure to connect to server - too many clients".  That's a surprise.  I have a 10 user license, and this would only be the second connection to this server.

Back to the fileserver.  I tried to access the Sesame Server interface, but it was not responding, totally white.  I eventually used Task Manager to kill it.  The server's client then told me the server was no longer responding, so I shut it down too.  Started Sesame Server up again, and the client.  Tried to access the problem db with the server's client, but "It may be in use" - locked.  Unlocked it, tried again.  "Failure to open".

Used the server's client to open the pre-import db: success.    Used my workstation's client to open it: success.

So clearly there's a problem with my post-import db.  I get a Failure when I try to open the F drive copy with Sesame as a client, but Success when I open it on my C drive with Sesame as a standalone.  Could it be the filesize?  Pre-import filesize is 47,852 KB, post import filesize is 118,772 KB, is that unusually large?  Could it be bad data?  But why would it open with no problem with the standalone?  A problem with Sesame Server?  "Too many clients" has me worried.

Any help would be appreciated.

Quote:


Everything here is 2.0.2.  I used the client's Server Administration to unlock.  The only messages related to the failure is "Failed to open".

I plan to work with the good copy tomorrow, and retry the import, see if it happens again.  It's probably bad data, though I don't know why the standalone runtime would succeed, but the -client would fail.

Thanks for the support Bob, Robert, it is much appreciated.  I'll take you up on it if I haven't nailed this down by midday.

I plan to go on the assumption that corrupt data is the problem.  I have a working app that contains my Customer and Invoice records, and a problem app that contains all that plus my Workorder records.  So I'll start by stripping out Workorders that I think may be bad, see what happens.  If I can get it to work I'll do a brand new import using just those records that passed the test.

In any event, Customer and Invoice alone along with a working Workorder form that can create new Workorders, will get my users to a functional state.  I've done no testing as yet (today will be a loooong day) with the imported data, except for a few Invoice reports (found a few that crashed Sesame - for some reason the program doesn't like to perform mathematics on value elements that are not bound to any value type, who woulda thunk it?)

Anyhoo, I'll proceed on that assumption, and hope that the Lanticans will check in, as they may have additional suggestions.  Thanks again.

Infinity wrote on Sep 3^rd, 2007 at 11:24am:

We've been here, Scott, but you're getting good advice from the folks, so we didn't want to muddy the waters. You've got a lot of configurations and files going back and forth. It's likely that, at some point, you weren't where you thought you were.

Infinity wrote on Sep 3^rd, 2007 at 3:16pm:

Usually it means that either you are bouncing the file through the network several times due to file sharing or that some piece of anti-spy/mal/ad/virus-ware is examining each bit as it goes by.

Quote:

Thanks.  I've turned off the AV on my workstation and the server; the process is moving noticeably faster now.

The problem lies somewhere between 6-1-2003 and 9-1-2003.  The file with Workorders from 6-1-2003 to present will not open.  The file with records between 9-1-2003 to present will.

Infinity wrote on Sep 3^rd, 2007 at 5:38pm:

Scott,

I don't think you are hitting a file size limit. We are doing some stress-testing right now on an app that is over 300MB. It makes no sense that the file opens standalone, but not client-server unless there is some sort of resource limit being imposed by your network. Can you send it into Support so that Ray can see if he can open it?

At any rate, I strongly recommend you get with Ray tomorrow and have him check out your configuration. It still sounds like there is some file sharing in the mix. You should not be needing to move the whole of your apps through your network if your client-server environment is set up properly.