Microsoft Access Dr Watson Issues

[Mike Kriiger]

In a multi user environment how can you find user or machine that caused the
Dr Watson error . Or is there some other way to delete the LDB file

Thanks

Mike

 

[Cheryl Fischer]

The following has worked for me in the past on a Windows 2000 server:

On the server (logged on with Administrator permissions), open a DOS window
(Run cmd) and navigate to the folder where the database is located. Type:

net file Then, press Enter

You should see a listing of all Open files, each of which will have a number
(probably 6-digit) assigned to it. In the listing, you should also see the
login id of the user that opened the file. Write down the numbers
associated with each of the "orphaned" ldb files you need to delete.

Then, Type:

net file 987654 /delete

where 987654 is the number associated with an LDB file to be deleted.

hth,

 

[Tony Toews]

In a multi user environment how can you find user or machine that caused the
Dr Watson error

Determining the workstation which caused the Microsoft Access MDB
corruption
http://www.granite.ab.ca/access/corruptmdbworkstation.htm

Tony


--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Tony Toews]

The following has worked for me in the past on a Windows 2000 server:

Interesting technique I've never seen before.

However I'd add that you should make sure everyone is out of the .mdb
file before using this approach. Or real strange things can start
happening.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Cheryl Fischer]

This is the kind of thing that you may have to do when you show up at the
office at 6 am or so to do a back-end update and find that (contrary to
company policy and your nice request the from day before) users have left
databases open and/or the ldb file will not delete by normal means. It
seems to be a better option than bouncing the server. A network admin told
me how to do this as an alternative to his having to roll out of bed 3 hours
early.

The user(s) get a nice email telling them that they will have to reboot
their systems.

 

[Tom Wickerath]

Hi Cheryl,

This sounds like a very interesting method to use, but I must be doing something wrong. I
have Windows 2000 Server (SP-4). I opened a .mdb file, and I can see its associated .ldb
file by issuing a DIR command. I also opened a text file in the same folder using
Notepad. When I issue the command

net file

using the command prompt (cmd.exe), the only thing it returns is "There are no entries in
the list", even though I have at least two files open. I am logged in as the
administrator. Any idea why this command is not returning a list of open files with the
numbers as you described?

Congratulations on your (recent?) Access-MVP award.

Tom Wickerath
___________________________________

The following has worked for me in the past on a Windows 2000 server:

On the server (logged on with Administrator permissions), open a DOS window
(Run cmd) and navigate to the folder where the database is located. Type:

net file Then, press Enter

You should see a listing of all Open files, each of which will have a number
(probably 6-digit) assigned to it. In the listing, you should also see the
login id of the user that opened the file. Write down the numbers
associated with each of the "orphaned" ldb files you need to delete.

Then, Type:

net file 987654 /delete

where 987654 is the number associated with an LDB file to be deleted.

hth,

 

[Cheryl Fischer]

Hi Tom,

As I mentioned in a earlier response in this thread, the technique was given
to me by a network admin, pretty much a "do this - do that" primer with no
explanation of the background, etc., so I do not have the knowledge to
troubleshoot the problem (nor a server to do it on). The only possibility
that I can think of for the files not appearing is that they were not opened
from a workstation but on the server??? That is, of course, a total w.a.g.

I think what I'm going to do is get more information by asking about it in a
newsgroup for Windows 2000 Server. Upon reflection, I think this is a
situation where "it worked for me" is not enough to warrant posting.

(Thank you! Yes, very recent award.)
--

Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX

 

[Tony Toews]

find that (contrary to
company policy and your nice request the from day before) users have left
databases open

I'm sure you've seen my standard blurb on this topic.

HOW TO: Detect User Idle Time or Inactivity in Access 2000 (Q210297)
http://support.microsoft.com/?kbid=210297
ACC: How to Detect User Idle Time or Inactivity (Q128814)
http://support.microsoft.com/?kbid=128814

However we found that the code which runs on the timer event must be
disabled for the programmers. Otherwise weird things start happening
when you're editing code.

Also print preview would sometimes not allow the users to run a menu
item to export the report to Excel or others. So you had to right
click on the Previewed report to get some type of internal focus back
on the report so they could then export it. This was also helped by
extending the timer to five minutes.

The downside to extending the timer to five minutes was if a person
stays in the same form and at the same control for considerable parts
of the day, ie someone doing the same inquiries, the routine didn't
realize that they had actually done something. I'll be putting in
some logic sometime to reset this timer whenever they do something in
the program.

and/or the ldb file will not delete by normal means.

Well, that's different then.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm