Re: database security
- From: "Bill Bach" <goldstar@xxxxxxxxxxxxx>
- Date: Wed, 19 Oct 2005 17:37:03 -0500
Dave wrote:
> Thanks Bill.
> I found the cause of the problem today in fact. I installed the SP3
> (8.7) client on my workstation and that appears to have fixed the
> problem. If I fire up PCC from an SP1 workstation, the problem
> appears .. so looks like a bug in the client itself !
>
> On a side note, i'm just trying out your killuser utility.
> I am using the following command line on my test box:
>
> killuser /Sdanshape_test /UMaster /P123456 /D /KS
>
> However, it doesn't seem to work. The output from killuser is as
> follows:
>
> Status from pvStart = 0
> status from pvConnectServer = 7004
>
> Any clue as to what that error code means? The connections are still
> visable in Monitor.
>
> Cheers, thanks heaps
> Dave
The 7004 indicates a generic connection error. Perhaps the Username or
password was incorrect? This user/pass combination is NOT the "Master"
password to the database, but rather the same admin-level password that
you use to connect to the Monitor remotely.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - November, 2005 ***
*** Chicago: Pervasive DataExchange Class - November, 2005 ***
.
- Follow-Ups:
- Re: database security
- From: Dave
- Re: database security
- References:
- database security
- From: Dave
- Re: database security
- From: Bill Bach
- Re: database security
- From: Dave
- database security
- Prev by Date: Re: Psql .NET Provider bug list
- Next by Date: Re: Does Pervasive SQL.2000 Workgroup run under Windows Server 2003?
- Previous by thread: Re: database security
- Next by thread: Re: database security
- Index(es):
Relevant Pages
|
|