Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Paradox Topics / September 2008

Tip: Looking for answers? Try searching our database.

Suddenly no tables could be opened ...

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Nils Gustaf Lindgren - 25 Sep 2008 13:51 GMT
... or rather, during the morning the small database distributed over two
work stations from a server malfunctioned more and more.
After claiming that indices were out of date, tables can no longer be opened
and I get the error message
"You have attempted to open a database that is in use by someone else, but
the database cannot be shared. You must set the location for the .NET
control file"
Here is the setup: two workstations with XP Pro, connected through wire to a
SBS Server. No connection to the Internet, and no update nor newly installed
software. The server is not connected to Internet either, nor has it been
updated for several months.
The net drectory is the shared root on the server as it has been for more
than a decade (OK we have changed servers).
We run Pdx 9.
I have never previously had any questions concerning "the .NET control
file".
Where do I start looking?

Cheers

Nils
Jim Moseley - 25 Sep 2008 15:45 GMT
Nils,

Reboot both computers & run the Clear Lock Files utility on both.  That will
probably solve your issues.  Search for REMLOK32.exe.  I found it here:

http://www.diamondsg.com/paradox.htm#Remlok32

HTH,
Jim Moseley
Dennis Santoro - 25 Sep 2008 15:47 GMT
Assuming the data is on the server as it should be (not the
workstations) then get the workstations out. Look for and delete any
.lck and .net files in the data space and on the users working
directories and priv directories.

Tutility or chimney sweep the files to fix any damage.

Check the idapi.cfg file to make sure it is intact and then make sure
all users are pointed to the same .cfg file or copies that are exactly
the same.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

> .... or rather, during the morning the small database distributed over two
> work stations from a server malfunctioned more and more.
[quoted text clipped - 17 lines]
>
> Nils
Nils Gustaf Lindgren - 25 Sep 2008 16:35 GMT
Thanks both of you.
Apparently a crashed index in one of the main files had caused a shut down
on one of the machines, leaving a "live" .lck file. Unfortunately I had to
re-start the server to be able to eradicate it. Hasn't happened for a long
time, now. Wonder how long I can keep this system running ... the oldest
parts are from 1994 ... too late now to shift to something else ...
Fortunately it remains stable, almost all of the time. In a way, it is to
the greater glory of those who developed the original software lo these many
moons ago.
Cheers
Nils
> Assuming the data is on the server as it should be (not the workstations)
> then get the workstations out. Look for and delete any .lck and .net files
[quoted text clipped - 36 lines]
>>
>> Nils
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.