Re: Database cannot be opened
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 63508
interpreted = N
texte = This occurrence happened again this morning, to a totally different DB. I tried to close the database as you suggested and it still would not allow the DB to be opened. For a quick fix we have to rename the DB and that clears up the problem. (i.e. Database1.db to Database2.db). It is like WebCatalog locks the DB and will not allow any access to it for a period of time. Then a day or two later it will be accessible again. This is by far the strangest think I have seen WebCatalog do. Any help would be greatly appreciated. Thanks. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of devaulw@onebox.com Sent: Monday, November 28, 2005 3:20 PM To: WebDNA Talk Subject: Re: Database cannot be opened Can you close the database and re-open it? I would also check ErrorLog.txt using: tail ErrorLog.txt To see what is being noted there. Bill -----Original Message----- From: Eric Miller
Sent: Mon, 28 Nov 2005 15:05:03 -0500 To: "WebDNA Talk" Subject: Database cannot be opened Hello all, Since moving to a new OSX.3 server system, we are experiencing some strange problems with WebDNA. The strangest being that it seems to not be able to find databases that exist and that were working in previous minutes. All data is still in there and all permissions/ownership are unchanged. In order to get access to it again, we have to change the DB name and thus all our search statements. Usually a day or two later we can change it back to the original name and it will work fine. Has anyone else seen this and does anyone have any idea what may be causing it? Thanks, Eric Miller The GoTriCities Network ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
This occurrence happened again this morning, to a totally different DB. I tried to close the database as you suggested and it still would not allow the DB to be opened. For a quick fix we have to rename the DB and that clears up the problem. (i.e. Database1.db to Database2.db). It is like WebCatalog locks the DB and will not allow any access to it for a period of time. Then a day or two later it will be accessible again. This is by far the strangest think I have seen WebCatalog do. Any help would be greatly appreciated. Thanks. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of devaulw@onebox.com Sent: Monday, November 28, 2005 3:20 PM To: WebDNA Talk Subject: Re: Database cannot be opened Can you close the database and re-open it? I would also check ErrorLog.txt using: tail ErrorLog.txt To see what is being noted there. Bill -----Original Message----- From: Eric Miller Sent: Mon, 28 Nov 2005 15:05:03 -0500 To: "WebDNA Talk" Subject: Database cannot be opened Hello all, Since moving to a new OSX.3 server system, we are experiencing some strange problems with WebDNA. The strangest being that it seems to not be able to find databases that exist and that were working in previous minutes. All data is still in there and all permissions/ownership are unchanged. In order to get access to it again, we have to change the DB name and thus all our search statements. Usually a day or two later we can change it back to the original name and it will work fine. Has anyone else seen this and does anyone have any idea what may be causing it? Thanks, Eric Miller The GoTriCities Network ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
"Eric Miller"
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Make sure I understand this??? (1997)
Date fun with MySQL (2004)
Upgrade to 3.07 problems (2000)
Bug Report, maybe (1997)
Now, Now (2000)
db security on NT (1997)
[OT] Am I an Idiot? (2004)
TCPCONNECT ---- POST? (2004)
Error:Too many nested [xxx] contexts (1997)
encrypt but with normal characters for result? (2005)
WebCatalog for guestbook ? (1997)
Just a thought (1998)
WebCat & WebTen (1997)
Mac: LModelDirector bug fix (1997)
WebCatalog 2.0 & WebDNA docs in HTML ... (1997)
taxrate - off by 1 cent (1997)
Associative lookup style? (1997)
WebDNA-Talk Digests (1997)
Case sensitivity and [showif] (1999)
using showpage and showcart commands (1996)