Hopefully someone can help.

I have loaded D3, successfully, and licensed it but when I reboot the system
and try to start the D3 service, it stops immediately and MS returns an
error that says:

"RPC Locator has encountered a problem and needs to close. We are sorry for
the inconvenience."

I have checked the RPC Locator service and it says started.

I have tried repeatedly to get D3 the run correctly. It seems to be on the
latest version that this happens as I had everything working well with a
previous release on W2K.

I have also tried this on two separate systems, both with XP-Pro.

I must be doing something wrong but I have spoken with RD support and they
say that they have experienced this problem but do not have a recorded
solution for it.

Thanks for your time.

Regards,

Neil

Neil Charrington

C.A. Software Systems

T: +44 1564 777011

F: +44 1564 777454

W: www.casoftware.co.uk

Neil,

Have you started the service manually - in the debug mode to see what's
happening?

Find the directory that contains the program D3VME.EXE. In a DOS window,
change to that directory and then enter:

D3VME /DEBUG

This will start d3 in a debug mode. One of the first things it will do is
tell you that
you have to enter "G" to start the service. Enter "G" and see what happens.

You will probably get no additional information from this, and it will
likely be
a fruitless exercise, but you never know.

Larry Hazel

Have you upgraded to XP-Pro/SP2? I had the same problem. I bought a brand
new Sony laptop with XP-Home. Then I bought the XP-Pro/sp2 upgrade and had
CompUSA do the upgrade and test it. Then I loaded D3 and it wouldn't work.
I spent two days at RD trying to get it to work.

Finally, in desperation, I restored the laptop "to factory settings"
(xp-home), re-installed Pick and it's been working fine ever since.

They told me there's a DLL with a dependent DLL in XP sp1. The dependent
DLL has been replaced in sp2 and so the DLL RD depends on isn't there.

Mark Brown


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

Hi
I doubt that it is a service pack problem as I have D3 running on the latest
XP-PRO Service Pack 2. Also it is extremely unlikely that RD a Microsoft
partner would use something that vanished from the later release. I suspect
help desk laziness with that sort of comment. Quite possibly CompUSA,
whoever they are, did it incorrectly.
Peter McMurray

"Mark Brown" <mbrown (AT) drexelmgt (DOT) com> wrote

Sheesh. Questioning Mark Brown is like questioning G_d. Watch out for
lightening.

"Peter McMurray" <excalibur21 (AT) bigpond (DOT) com> wrote

Jeffrey Kaufman wrote:
Or, even more scary: lightning!

--
frosty (resisting the Michael Jackson joke, for once.)

Thank you for the correction, Larry. Much funnier your way.

"frosty" <frostyj (AT) bogus (DOT) tld> wrote

Hi
To me Mark is the MAZDA (Bob Marley followers will understand) of D3 I treat
all his info as gospel so one slip is not an issue. In fact his exposition
of the Pick interface on a course in Sydney remains one of the best I have
ever attended.
Peter McMurray
"Jeffrey Kaufman" <jkaufman (AT) keydata (DOT) us> wrote

"Peter McMurray" <excalibur21 (AT) bigpond (DOT) com> wrote:
Peter, you don't know RD like we do. This is very likely.

The political, not technical Microsoft partnership is only for their
PDP.NET product, lot of good that does. The relationship doesn't
extend to D3, which has never been MS certified.

T

Neil, I am running D3NT 7.4.3 and have chosen to not upgrade because
I've heard there are various issues with 7.4.4 and 7.4.5. I'm not
trying to avoid anything specific and catastrophic, I just need to
stick with what works.

I suggest you completely uninstall D3, reinstall the base platform,
then upgrade to 7.4.3, and try to run that. If it works then the
problem is probably specific to a newer D3 release. There's nothing
critically wrong with 7.4.3 that I know of and it should be a stable
platform for your continued development.

If that doesn't work (and you DID say you were running on a prior
release but we don't know which one yet) then I'm guessing the problem
has to do with something else that you're loading on your systems - or
not loading on your systems, and a related incompatibility with the
newer D3.

Did you do the nt_upgrade procedure in the VME after installing? You
might be trying to run a new monitor with an old dataset. That
shouldn't stop the software from booting, but we need to check all
angles here.

Please try to post some more info and maybe someone here will be able
to help.

Regards and good luck,
Tony



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