Re: Pervasive doesn't allow any more incoming connections
- From: "Bill Bach" <billbach@xxxxxxxxxxxxxxxxxxxx>
- Date: 19 Jul 2005 22:24:41 EDT
Baseball bats are cheaper, but hooking up their mouse to a 220-line can
provide more shocking results. ;-)))
BTW, another possible cause of the System Error (33 errors): Running
the database application at the same time as backups. I noticed that
these occur in the wee hours of the AM -- most likely to run into
complete virus scans and backup copy jobs. If you are backing up at
these times, be sure to either get all users OUT of the database
(another use for the MickySoft Electro-Mouse), or put the database into
continuous operations mode before backup (taking it out afterwards, of
course).
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - July 19-22 ***
*** Chicago: Pervasive DataExchange Class - July 27-29 ***
mikenospam72@xxxxxxxxxxx wrote:
> I'm thinking that we have someone running manual reports based on the
> times (between 7AM and 10AM), and the frequency (doesn't follow a
> pattern).
>
> Anyone know a solution on how to avoid someone running manual reports
> outside of locking them out (security), or purchasing a baseball bat?
.
- References:
- Pervasive doesn't allow any more incoming connections
- From: mikenospam72
- Re: Pervasive doesn't allow any more incoming connections
- From: Leonard
- Re: Pervasive doesn't allow any more incoming connections
- From: mikenospam72
- Pervasive doesn't allow any more incoming connections
- Prev by Date: Re: Dropped Sessions Pervasive v7
- Next by Date: Sometimes Error E_FAIL(0x80004005) in IErrorInfo.Getdescription
- Previous by thread: Re: Pervasive doesn't allow any more incoming connections
- Next by thread: Sometimes Error E_FAIL(0x80004005) in IErrorInfo.Getdescription
- Index(es):
Relevant Pages
|
