|
Home > Archive > Programming with dBASE > November 2005 > Internal or Operating System Error with multiple dBase apps running
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Internal or Operating System Error with multiple dBase apps running
|
|
| Christian K 2005-11-16, 11:23 am |
| A client of ours, who has for a long time been running 4 or 5 dBase
apps at a time on their machines, is now running into errors when they
attempt to run more than 2. The error is "Internal or Operating System
Error", and it happens with a different DBF file each time when the 3rd
instqnce of a dBase program is opening.
The client is using a Novell network data server where the DBF's are
stored, for peer to peer sharing. Recently, more licenses were added to
the Novell server, but the problem didn't start occurring immediately
after the license upgrade, but several weeks to my knowledge.
Any ideas? Is there any way to find out more info about the error
message, since it is so vague?
Thanks,
Christian K.
| |
| *Lysander* 2005-11-16, 11:23 am |
| In article < xn0e9t3x3408f9000@ne
ws.dbase.com>, ChristianK@HeroData.com=20
says...
> The client is using a Novell network data server where the DBF's are
> stored, for peer to peer sharing.=20
This is a contradiction :) Server is Server. Peer to Peer is without=20
"dedicated" server...
Do you have the application (.exe) on the server as well, or only the=20
tables?
There is an option in Novell-Servers (but I can't exactly remember=20
where...) where you can restrict multiple instances of one file from the=20
server. Maybe this option got activated by coincidence?
--=20
ciao,
Andr=E9
| |
| Christian K 2005-11-21, 8:23 pm |
| *Lysander* wrote:
>
> This is a contradiction :) Server is Server. Peer to Peer is without
> "dedicated" server...
To clarify: there is no server backend being used, merely peer-to-peer.
> Do you have the application (.exe) on the server as well, or only the
> tables?
Only the permanent tables reside on the networked Novell machine, all
EXE's & various other temp files reside locally on each workstation.
> There is an option in Novell-Servers (but I can't exactly remember
> where...) where you can restrict multiple instances of one file from
> the server. Maybe this option got activated by coincidence?
I'll look into it, but seems doubtful since I can run any 2 of 5
installs of our program, but no more than 2 without receiving the
aformentioned 'internal or operating system' error with some random
table.
I am researching Novell Licensing issues, since the are notorious for
causing odd errors. Any further info or ideas are appreciated, so
please keep them coming.
Thanks,
Christian K.
| |
| *Lysander* 2005-11-22, 11:23 am |
| In article < xn0ea0edtgn7he001@ne
ws.dbase.com>, ChristianK@HeroData.com=20
says...
are[color=darkred]
[color=darkred]
> To clarify: there is no server backend being used, merely peer-to-peer.
OK... but what did you mean by "client is using a Novell network data=20
server"??
> I am researching Novell Licensing issues, since the are notorious for
> causing odd errors. Any further info or ideas are appreciated, so
> please keep them coming.
On another newsgroup you wrote that you recently installed Terminal=20
Server... I would search there. The "internal OS error" can - for=20
example - occur if datasets are not closed correctly. This can happen=20
when the terminal server denies additional launches.
But all of this does not make sense, when neither your *.exe nor the=20
datafiles are on the terminal server.
*.exe on the local machines, only DBFs on a networked drive, nothing on=20
the terminal server... should be no problem at all. Random crashes...=20
maybe... but every 3rd instance in the network? No...
--=20
ciao,
Andr=E9
| |
| Christian K 2005-11-22, 11:23 am |
| *Lysander* wrote:
> OK... but what did you mean by "client is using a Novell network data
> server"??
Novell Server Version 5 is the OS running the machine where the tables
are stored. These files are shared thru mapped network drives. Sorry
for any confusion.
> On another newsgroup you wrote that you recently installed Terminal
> Server... I would search there. The "internal OS error" can - for
> example - occur if datasets are not closed correctly. This can happen
> when the terminal server denies additional launches.
Yes, I would have supected the Terminal Server too as a likely culprit,
but wading thru the sequence of events, I was told the terminal server
was added after the error messages first started occurring.
|
|
|
|
|