From fitzbew at nc.rr.com Mon May 1 11:25:27 2006 From: fitzbew at nc.rr.com (Russ Tyndall) Date: Mon May 1 10:25:34 2006 Subject: [Vstudio] - Unable to Access Server Admin Message-ID: Using Vstudio 2.3.1 DEMO, from Win XP. Connecting to Vserver 2.3 on X.4.6 I'm unable to access Vserver "Server Admin" (formerly "Monitor"), even though my login ID is Admin in the Master.vdb Sysuser table. I get an error message saying that the function is only available to Admins. I'll put this in Mantis. (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.) -- Russ Tyndall Wake Forest, NC From sunshine at public.kherson.ua Mon May 1 19:03:40 2006 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Mon May 1 11:03:44 2006 Subject: [Vstudio] - Unable to Access Server Admin In-Reply-To: Message-ID: On 5/1/06 6:25 PM, "Russ Tyndall" wrote: Hi Russ, > (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 ? -- Best regards, Ruslan Zasukhin VP Engineering and New Technology Paradigma Software, Inc Valentina - Joining Worlds of Information http://www.paradigmasoft.com [I feel the need: the need for speed] From fitzbew at nc.rr.com Mon May 1 12:39:34 2006 From: fitzbew at nc.rr.com (Russ Tyndall) Date: Mon May 1 11:39:40 2006 Subject: [Vstudio] - Unable to Access Server Admin In-Reply-To: Message-ID: On 5/1/06 12:03 PM, "Ruslan Zasukhin" wrote: > On 5/1/06 6:25 PM, "Russ Tyndall" wrote: > > Hi Russ, > >> (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. Russ From sunshine at public.kherson.ua Mon May 1 21:41:58 2006 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Mon May 1 13:42:05 2006 Subject: [Vstudio] - Unable to Access Server Admin In-Reply-To: Message-ID: On 5/1/06 7:39 PM, "Russ Tyndall" 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? -- Best regards, Ruslan Zasukhin VP Engineering and New Technology Paradigma Software, Inc Valentina - Joining Worlds of Information http://www.paradigmasoft.com [I feel the need: the need for speed] From fitzbew at nc.rr.com Mon May 1 15:19:19 2006 From: fitzbew at nc.rr.com (Russ Tyndall) Date: Mon May 1 14:19:25 2006 Subject: [Vstudio] - Unable to Access Server Admin In-Reply-To: Message-ID: On 5/1/06 2:41 PM, "Ruslan Zasukhin" wrote: > On 5/1/06 7:39 PM, "Russ Tyndall" 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 From sunshine at public.kherson.ua Sat May 6 13:35:01 2006 From: sunshine at public.kherson.ua (Ruslan Zasukhin) Date: Sat May 6 05:35:09 2006 Subject: [ANN] Valentina Studio 2.3.2 uploaded. OS X 10.3 Supported! Message-ID: Hi All, This minor build fix * WIN - no help files. Mistake was in installer script * MAC - few glitches in the Create Field dialog and in strange failure to open db files. MAC USERS. Attention !!! Vstudio 2.3.1 and 2.3.2 is able to run on MAC OS X 10.3 !! -- Best regards, Ruslan Zasukhin VP Engineering and New Technology Paradigma Software, Inc Valentina - Joining Worlds of Information http://www.paradigmasoft.com [I feel the need: the need for speed]