Page Index Toggle Pages: [1] 2  Send Topic Send Topic Print Print
Hot Topic (More than 10 Replies) Database xx failed to open. (Read 6281 times)
Janko
Member
*
Offline


No personal text

Posts: 15
Joined: Apr 14th, 2005
Database xx failed to open.
Feb 17th, 2006 at 5:06pm
Print Post Print Post  
Dear Lantica and fellow users,

Unfortunately we had a server lock up, and upon rebooting, Sesame now is having trouble loading a database.  Only one database was running at the time, which is the most important.  I tried unlocking it, and the error now receiving after unlocking is:

Database D:\xxx\xxx.db failed to open.
Error: failure while loading application: D:\xx\xxx.db.

I did a search on the forums, and found nothing.  If anyone has any experience with this, we would appreciate it.  This database is pretty important, and for it to be corrupted would be a disaster!

Thank you for any and all help!
  
Back to top
 
IP Logged
 
Ray the Reaper
Global Moderator
Members
Lantica Support
*****
Offline


The One & The Only

Posts: 2482
Joined: Aug 20th, 2003
Re: Database xx failed to open.
Reply #1 - Feb 17th, 2006 at 5:11pm
Print Post Print Post  
Hello Janko,

You will need to send the .DB and .DAT files of the application that is failing to load to Support@Lantica.com

Roughly what percent of loading does it get to before that message appears?

-Ray
  

Raymond Yoxall Consulting
ray.yoxall@gmail.com
ryoxall@lantica.com
Sesame Applications, Design and Support
Back to top
IP Logged
 
Janko
Member
*
Offline


No personal text

Posts: 15
Joined: Apr 14th, 2005
Re: Database xx failed to open.
Reply #2 - Feb 17th, 2006 at 5:20pm
Print Post Print Post  
In preparation of sending the e-mail with the attachment, I now notice that the .db is 1 kb, and the .dat is 0 kb.

I will check with our backups, and see what we have.

Is it possible that Sesame stores the information elsewhere?

Thank you!


  
Back to top
 
IP Logged
 
Ray the Reaper
Global Moderator
Members
Lantica Support
*****
Offline


The One & The Only

Posts: 2482
Joined: Aug 20th, 2003
Re: Database xx failed to open.
Reply #3 - Feb 17th, 2006 at 6:10pm
Print Post Print Post  
Hello Janko,

Sesame does not save the files anywhere else.

-Ray
  

Raymond Yoxall Consulting
ray.yoxall@gmail.com
ryoxall@lantica.com
Sesame Applications, Design and Support
Back to top
IP Logged
 
Janko
Member
*
Offline


No personal text

Posts: 15
Joined: Apr 14th, 2005
Re: Database xx failed to open.
Reply #4 - Feb 17th, 2006 at 7:32pm
Print Post Print Post  
Well,

I have lost more than a month's work, which is our fault of course, but what reason would cause the database to collapse so? 

The database was overwritten, or its entire contents deleted, and replaced with 1 KB files.

Thanks for your help so far!

  
Back to top
 
IP Logged
 
Ray the Reaper
Global Moderator
Members
Lantica Support
*****
Offline


The One & The Only

Posts: 2482
Joined: Aug 20th, 2003
Re: Database xx failed to open.
Reply #5 - Feb 17th, 2006 at 8:58pm
Print Post Print Post  
Hello Janko,

Before we can accurately say what happened, we need some more information about what happened to the server computer.

What version of Sesame are you running?
What all does "server lock up" mean to you? In other words what locked up?
What was Sesame doing when the server locked up?
What was the last thing done in Sesame before the computer was rebooted.

-Ray
  

Raymond Yoxall Consulting
ray.yoxall@gmail.com
ryoxall@lantica.com
Sesame Applications, Design and Support
Back to top
IP Logged
 
Janko
Member
*
Offline


No personal text

Posts: 15
Joined: Apr 14th, 2005
Re: Database xx failed to open.
Reply #6 - Feb 17th, 2006 at 9:30pm
Print Post Print Post  
Thank you for your response!

We are using Sesame version 1.1.3.

Our server houses two applications, Sesame, and our accounting software.

The server locked up, which made me pull the plug -- it would not respond to anything, whether it be Task Manager, or Start-->Shutdown.  It was given ample time to respond, but merely sat unresponsive.

Sesame on the user's computer was idle when the server locked up.  Sesame was open, but with nothing being currently accessed.  Sesame was open from the previous night, which is a common occurence here.

Sesame was just viewing a random record.

Fortunately the accounting was not damaged, and thankfully we do have, at the least, a month-old backup.

Thank you!
  
Back to top
 
IP Logged
 
The Cow
YaBB Administrator
*****
Offline



Posts: 2530
Joined: Nov 22nd, 2002
Re: Database xx failed to open.
Reply #7 - Feb 18th, 2006 at 1:17am
Print Post Print Post  
Quote:
Sesame on the user's computer was idle when the server locked up.  Sesame was open, but with nothing being currently accessed.


If there was only one connected client and that client was idle, I would suspect some external program "reached out" and touched the files. Sesame only opens the files immediately after a change in the data, and then closes the file as soon as the change has been written. If no user was making changes, the files would be closed and completely inert.

Sesame only very rarely rewrites an entire existing file - after structural changes, like a reconcile, a merge, or a trim. Usually it writes the changed data to a specific portion of the file(s) and does not change or rewrite any other portion of the file, except to update the total number of records on a delete or add.

Even if you pull the plug on an active server, you would have to time it so that Sesame is writing at that precise moment, which is fairly unlikely given the speed of modern harddrives.

Do you have any ideas as to what happened to cause your computer to lock up in the first place?

Before you pulled the plug, did you get a chance to look at the Sesame server's status window?

Were any of the memory numbers very very low?

Have you had any trouble with the network hardware on either of these two machines?

Any problem with the server's memory or harddrive?

Do you have sufficient swap space setup?

Are there any log file entries on the server (either OS or Sesame) that might be illuminating?

Is there any access to this server from the outside world?

Is it possible that these files were truncated before the server was reset?

Were there any notable oddities or misbehaviors the last time these applications were in use?

When you "pulled the plug" on the computer was there any activity on the screen? Was the Sesame server status window still updating? Could you move the mouse?

Was the network card still operational? Could you ping the computer from another computer?

Was the accounting software being actively used at the time?

How was it noted that the server computer was down? Was someone sitting at the computer? Did the Sesame client attempt to access the server?

Has this computer locked up before?

On Monday, Ray will probably ask to see the .db and the .dat file and the log files from the server and the client computer. Please save them.

Sorry to ask so many questions.
  

Mark Lasersohn&&Programmer&&Lantica Software, LLC
Back to top
IP Logged
 
NICEBERG
Full Member
Members
***
Offline


I came, I saw, I'm still
trying to figure it out!

Posts: 208
Location: Green Bay, WI
Joined: Dec 17th, 2003
Re: Database xx failed to open.
Reply #8 - May 12th, 2006 at 1:20pm
Print Post Print Post  
We've begun to experience the "..*.db failed to open" problem with increasing frequency in the past few weeks.

A few questions I have:
1. I've found our *.log file on the server in the Sesame folder - how do I view it? What program can open this file? I've tried MSWord, Notepad, Wordpad, all to no avail.

2. Can a Sesame file become corrupted like Q&A could (funny characters in table view - I've found none, but just curious).

I'll be meeting with our Sys Admin person in a bit, so I'm sure there will be a few more questions. I've printed out this thread as a starting point for us.

Thanks,
Fred
  
Back to top
 
IP Logged
 
NICEBERG
Full Member
Members
***
Offline


I came, I saw, I'm still
trying to figure it out!

Posts: 208
Location: Green Bay, WI
Joined: Dec 17th, 2003
Re: Database xx failed to open.
Reply #9 - May 12th, 2006 at 1:41pm
Print Post Print Post  
Olay, we've opened the log file. Naturally, a lot of it doesn't make sense. Can we send it to Support for a quick peak and see if anything stands out?

Also, we're still on 1.1.2. Would going to 1.1.3 have any impact in this area?

Thanks again.
  
Back to top
 
IP Logged
 
Ray the Reaper
Global Moderator
Members
Lantica Support
*****
Offline


The One & The Only

Posts: 2482
Joined: Aug 20th, 2003
Re: Database xx failed to open.
Reply #10 - May 12th, 2006 at 1:45pm
Print Post Print Post  
Hello Fred,

1. The log file opens with Sesame's Log Viewer.
Click File->Server Administration
Login: admin
Password: hello
Click the Local Logs tab.

There are two different "failed to open" messages, both are caused by different things. The first one is minor, the second one is not.

The first one just says
"Database C:\Sesame\Data\Name.db failed to open".
This means that the file is locked. This can happen if another sesame process has that file open, or if the last sesame process that had that file open was improperly shutdown.

The Second one says
"Database C:\Sesame\Data\Name.db failed to open
Error: failure while loading application C:\Sesame\Data\Name.db."
This means that between the DB and DAT files something is wrong. This can be caused by mismatched files, one of the files being overwritten, two separate Sesame Processes accessing the same application, part of one file missing due to Hard Drive errors, or other causes.

Which error you are getting is key to where to look for the problem. Which Error are you getting?

Note: When I say separate Sesame Processes I do not mean two clients in the same file. I mean either two Standalone copies of Sesame in the same file, or two Sesame Servers in the same file, or Sdesigner Reconciling to an application that is loaded by a Sesame Server or a Standalone copy of Sesame. 

-Ray
  

Raymond Yoxall Consulting
ray.yoxall@gmail.com
ryoxall@lantica.com
Sesame Applications, Design and Support
Back to top
IP Logged
 
Ray the Reaper
Global Moderator
Members
Lantica Support
*****
Offline


The One & The Only

Posts: 2482
Joined: Aug 20th, 2003
Re: Database xx failed to open.
Reply #11 - May 12th, 2006 at 1:48pm
Print Post Print Post  
Quote:
Olay, we've opened the log file. Naturally, a lot of it doesn't make sense. Can we send it to Support for a quick peak and see if anything stands out?


Send it to support@lantica.com and mark the E-mail "Attention Raymond Log File from NICEBERG"

-Ray
  

Raymond Yoxall Consulting
ray.yoxall@gmail.com
ryoxall@lantica.com
Sesame Applications, Design and Support
Back to top
IP Logged
 
NICEBERG
Full Member
Members
***
Offline


I came, I saw, I'm still
trying to figure it out!

Posts: 208
Location: Green Bay, WI
Joined: Dec 17th, 2003
Re: Database xx failed to open.
Reply #12 - May 12th, 2006 at 2:25pm
Print Post Print Post  
Thanks Ray, it's on the way. It does appear in the log that we are attempting to open the same database twice on the same computer. This is NOT the case.
  
Back to top
 
IP Logged
 
Ray the Reaper
Global Moderator
Members
Lantica Support
*****
Offline


The One & The Only

Posts: 2482
Joined: Aug 20th, 2003
Re: Database xx failed to open.
Reply #13 - May 12th, 2006 at 2:49pm
Print Post Print Post  
Hello Fred,

How many computers do you have that are running Sesame?
Client/Server or Standalone?

-Ray
  

Raymond Yoxall Consulting
ray.yoxall@gmail.com
ryoxall@lantica.com
Sesame Applications, Design and Support
Back to top
IP Logged
 
NICEBERG
Full Member
Members
***
Offline


I came, I saw, I'm still
trying to figure it out!

Posts: 208
Location: Green Bay, WI
Joined: Dec 17th, 2003
Re: Database xx failed to open.
Reply #14 - May 12th, 2006 at 3:30pm
Print Post Print Post  
Nine computers - six licenses (folks have been trained to log off when finished, not an issue)- client/server.

Additional info: I only work Fri-Sat-Sun with a very small crew - max two other computers running. Even though I KNOW that Sesame is not up and running on those machines, I will sometimes get the error message on my machine - and I know there is not another copy of the db running.

I suspect the issue may be related to my pc, it sometimes locks up when I've been on the net and try to run another program. I had to reboot several times last weekend. My pc will be replaced in the near future, but I want to explore all avenues and not "assume" that this is the entire problem.
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: [1] 2 
Send Topic Send Topic Print Print