Hi Again
I believe that we need more information urgently. In particular the version
of D3 as this could affect all of us. I am afraid that I still do not trust
a third party to properly install XP as they usually leave that to the goofy
kid on school break.
I am amazed that the RD/MS relationship does not include D3 which I have
always found to be an excellent product.
Peter McMurray
"Tony Gravagno" <g6q3x9lu53001 (AT) sneakemail (DOT) com.invalid> wrote

Hi Neil,

This is like "teaching Grandma to suck eggs", but here goes. Is the D3VME
service starting with system priveledges, or have you created an
administrative user and running the service as that user.

I have had a similar problem with the SQL debugger within Visual Studio,
which was solved by creating the administrative user and starting the SQL
service under those priveledges.

Something to do with a couple of DLL files being installed when the computer
was registered to another network.

Regards

Jon


"Neil Charrington" <neil (AT) casoftware (DOT) co.uk> wrote

"Peter McMurray" wrote:

I'll send Neil a nudge to check this thread. We have other business
dealings so I'm interested in seeing him resolve this as well.

I dunno if they are working with OEM systems, I don't think so, but
that's a good idea. He did say they had a prior release of D3
running, but he didn't say if it was on the same box.

Nevertheless, that is the case. I was employed at RD for many years,
last position was DBMS Product Manager, and I know some of the issues
in this area. I try to keep up with their current initiatives,
including whatever aspects of their relationship with Microsoft that
they make public, and to my knowledge there is no business link
between D3 development and Microsoft.

While my company is now a jBASE Distributor, my primary development
environment is still D3. Our focus (I and those who provide services
through Nebula R&D) is changing but I'll continue to support D3 for as
long as it seems appropriate, technically and in a business sense.
Yes, it is an excellent product, but there have been a lot of
technical and business issues that stand in the way of our pursuing a
future with it anymore. A lot of companies run with D3NT, including
many of my clients here in CDP, but many large D3NT end-users have
dropped it over the years too. That's mostly due to growing pains in
the platform, not issues with D3 itself, if one can make such a
distinction. From a business perspective I'm hoping that upcoming
releases address the problems, and that RD can take some leadership to
get new VARs and motivate existing VARs to sell more apps. In the
mean time I've needed to make some major strategic changes here.
C'est la vie.

T

Hi Jon,

I tried all of that with Mark at RD support a little while ago and it came
back with exactly the same message - RPC Locator error.

I have decided to try D3 on a new Win 2003 Server system that we now have in
our office. I will update the group when I have (un)successfully loaded and
run it on 2003 Server.

Best regards,

Neil.
"Jon Dempsey" <jon.dempsey (AT) mines_a_beer (DOT) com> wrote

Hi Tony,

Sorry for the lack of response/appreciation for the replies to my original
email, my news system seems to have given up the ghost and I have just
reinstalled it.

Further developments and expansion of the original mail:

1: I was using a D3 version 7.2.x on Win 2000 on my laptop and it worked
fine. I then came to upgrade as I had to reload D3. RD said 7.2 was not a
supported release as well as me being an undesirable (politically speaking)
as I was developing software and they stopped their policy of free software
for developers.

2: I was eventually given an evaluation copy of D3 (version 7.4.5), which
was the version I have been trying to load unsuccessfully on WinXP-Pro.

3: I changed Win 2K to Win XP-Pro/SP2 for various internal reasons and
loaded D3 - it came up with RPC Locator errors. I called RD support and
Mark Morley spent some time with me trying to resolve the problem, to no
avail.

4: I loaded a new system with a "virgin" XP-Pro with SP2 and then tried
loading D3 again and I had the same problem RPC Locator error.

5: Mark then spent some more time with me trying to resolve this and came up
with it being an authentication error on our Domain. I tried everything I
could think of to resolve it and decided to ask the group for their input.

That is where we were until this morning.

6: I have now loaded D3 on our 2003 Server and " hey presto" everything
works (or is working so far).

So I now have 4 weeks evaluation to get OSMOSiS updated on D3 - which does
not present a problem.

Thanks for everyone's input. I would also like to say that the support I
have had from RD UK (Mark and Mandi in particular) has been superb, even if
the support from those above has not.

When are the people at the top of RD (including Mario and Keith - in the UK)
going to learn that the more software is developed on their products (D3
included) then the more of their software will be sold - it's not rocket
science. How much does it cost them to supply developers with a 5-User
version of D3 free-of-charge? How much will they gain if products like ours
are available on their platforms?

Anyway, thanks again.

Best regards,

Neil.

"Tony Gravagno" <g6q3x9lu53001 (AT) sneakemail (DOT) com.invalid> wrote

Neil:

I just installed a new Penguin server running Win2K3. I installed D3 v7.4.4
and I got all kinds of RPC errors in the application event logs. RDUS
indicated there were some hardware issues with the SATA RAID controller, so
I had to send back the Penguin and buy a Dell.

Their PDP.NET product and D3 weren't working properly so I'll have to wait
and see what happens with the new certified Dell server. Of course, one
still has to worry about the gigabit NICs, as RDUS hasn't resolved that
problem in several years.

Best of luck. :-(

Bill

"Neil Charrington" <neil (AT) casoftware (DOT) co.uk> wrote

PDP.NET isn't working with 7.4.4 either?
The marketing bulletin said PDP 3.0 is certified for 7.4.5 so I
ordered a new D3 developer license with a new PDP SDK and an upgrade
for my current D3 and PDP. (Yes, Nebula R&D is a distributor for
mv.NET but I've said here many times in the past that I'd support
PDP.NET and was going to get another developer familiar with it.)
When I was told 3.0 wouldn't work with 7.4.5, I no longer had a reason
to upgrade or buy new software so I just cancelled the orders. It was
suggested that I take the software anyway and when I reiterated that
the software doesn't work, so I have no reason to buy it, I was told
that was a matter of choice on my part. Well, yeah, I choose to not
buy software when Support says it doesn't work, sorry. Oh yeah, and
each day that I don't upgrade PDP.NET the pro-rated cost from my
current version goes up. We're sticking with mv.NET and I don't think
at this point that I'll be looking back.

T

"Bill H" <notme (AT) bogus (DOT) com> wrote: