Starting RPCServer from the startup script - NEW BIZARRE UPDATE!

[Anony Usenet]

Hi,

I have realized that the startup script WILL WORK *if* (and only if)
Arcview is started on its own, and the project is opened with the
File->Open Project.

If you double click on the .apr file OR start arcview from the command
line with the apr file given as a command line argument, It does *NOT* work.

This is a "BIZARRE" problem (bug?).

As a programmer, clicking on the apr file should be equivalent to
starting arcview and then using file->open .... No?

Any arcview programmer's out there??

Thanks!
- John

Hi,

Short Version:

When I start the RPCServer from the project startup script clients
CAN NOT connect.
If I start it by "hand" (say with a button which runs that same
startup script!) clients CAN connect.

Long Vesrion:

I need to run an RPC Server for my Arcview app.
(Arcview GIS 3.2a on NT4.0 SP6)

I wrote one line scripts called StartProject and EndProject which are
the startup and shutdown scripts respectively of the project.

StartProject:
RPCServer.Start( 0x40000001, 1 )

EndProject:
RPCServer.Stop

I am using the portmapper (NobleNet's)that came with the Arcview
distribution.

When the project is opened it runs the script and registers with the
Portmapper. It appears to have done all the all right things.

When I run my client though it fails with some weird errors.
Sometimes it is just a timeout error other times I get:

Java (remotetea) Client:
Connection reset by peer: JVM_recv in socket input stream read

C (gcc) Client:
RPC: Unable to receive; Routine will place interface out of state

When I try to make an internal arcview RPCClient (in the same app) it
*always* fails with a timeout.

Now for the "WEIRD" part.

If I stop the server by running the EndProject script by hand and
restart
the server by running the StartProject script by hand the clients can
connect
and it works great!

(Well the Java and C clients work, I still can't get the arcview
client
to work. It still times out)

Is there something "special" about how the startup and shutdown
scripts are
run? Could this be some weird bug?

Can anyone think of a way to start the server automatically without
having to run the script by hand?

Thanks!
- John