[Vstudio] - Unable to Access Server Admin

[Russ Tyndall]

On 5/1/06 2:41 PM, "Ruslan Zasukhin" <sunshine at public.kherson.ua> wrote:

> On 5/1/06 7:39 PM, "Russ Tyndall" <fitzbew at nc.rr.com> wrote:
> 
>>>> (I also observe rather erratic behaviour using Vstudio in X.4.6, but this
>>>> is
>>>> likey to Mach-o Vcomponents/ Vserver interaction problems.  Already bugged
>>>> in Mantis ID 001565 and discussed with Ruslan at length.)
>>> 
>>> They cannot interact. 100%. Evne 200%
>>> 
>>> Vstudio + Vserver. Each keep dlls in own folder.
>>> And each dll has own @exactuable_path.
>>> 
>>> So what problems you see ?
>>> 
>> 
>> This is the problem(?) that you and I worked on via IM early last month for
>> several hours.  That when I interacted with Vserver using RB app with Mach-O
>> vcomponents, Vserver would act strangely, creating "phantom" master.vdb
>> entries and also V4RB app would have experience strange exceptions.
>> 
>> When we used exact same PEF-format RB app with carbon-version of
>> vcomponents, no problems!
>> 
>> If I recall correctly, you were able to duplicate bug on your machine but
>> you were unsure of exact cause.
>> 
>> Later, we discussed problem via email and you thought Vstudio was also
>> involved. I *assumed* that the problem was Mach-O vcomponents since they are
>> also used by Vstudio (correct?).
>> 
>> Forgive me if I have misunderstood something.  I have not had any problems
>> with vserver since I began only touching Vserver with carbon vcomponents RB
>> apps.
> 
> 1) I believe that this is Vstudio fault in phantom masterdbs.
>   but our developer was not able reproduce this.
>   other our developer(s) should try
> 
> This is the only problem you mention now with 2.3.1 ?
> 
> Or anything else?
> 

On that day, I (we?) was experiencing problems with Vserver after only
"touching" vserver with Mach-O V4RB apps, not with Vstudio.

We would run V4RB Mach-O app against Vserver and suddenly get validation
exceptions and Master.vdb would suddenly have problems.  It did not happen
every time, just suddenly it would happen after some period of use.

When we built same app using Carbon format Vcomponents, we could *never* get
problem to occur.  And I have not seen problem since I stopped using Mach-O
RB apps against Vserver and I have only rarely used Vstudio with Vserver
since that day so *if* it was Mach-O related, I would not have seen it
lately.

But, you have not apparently been able to reproduce. I misunderstood, I
thought you had reproduced it.  Sorry.

Ok!  I will try and see if I can figure out more about this.  The bad thing
is (even if this only happens on my machine) that Vserver becomes unusable
after the problems occur, even from Win32 client.  I had to reinstall
Vserver to get back up. Merely trashing Master.vdb did not seem to fix it.

I believe it is related to RegisterDatabase(), AddUser() functions since I
was using those heavily in first few days of practice with Vserver. Just
guessing, though.

Simply, though, if you cannot reproduce, you cannot fix.

-- 
Russ Tyndall
Wake Forest, NC