I found that the problem was simply due to registration errors. I
unregistered the server and then registered the app server again and all was
fine. Previously I had simply registered the new version of the app server
without unregistering the previous.
Before using MIDAS we tried using MTS, but had problems with database
handles not staying valid between calls. We ise informix via the BDE.
Have you ever set up a Midas 2 app as a service? I am having trouble doing
this.
Thanks
Stacey
> -----Original Message-----
> From: Peter G Jones [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 6 July 2000 11:10 p.m.
> To: Multiple recipients of list delphi
> Subject: Re: [DUG]: Midas problems
>
>
>
> Multiple RDM's in the same server is probably asking for
> trouble, I've never
> done that - but if it worked well once, then I suppose
> there's no reason to
> change.
>
> It sounds like the 4th client is using DCOM...? The socket
> server provides
> the inter-machine connection but COM is still used to create
> the server
> instance. You should check you DCOM settings on the server
> objects. What
> account is the socket server running under? If it's system,
> does the system
> account have access to all the resources it needs? Is the
> server logged in
> under a specific account? If so then has the account
> permissions changed
> lately?
>
>
> We find that we must have the server logged-in as a specific
> user (with
> partial admin rights). If we tru to log out while users are
> connected -
> even with the socket server running as a system user service,
> the client
> connections must be terminated and the Midas server instances
> get killed.
>
> We have started to use MTS which is a lot cleaner in shutting
> down and the
> setup of server and client is a lot simpler.
>
>
>
>
> >From: Stacey Verner <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
> >Subject: [DUG]: Midas problems
> >Date: Fri, 30 Jun 2000 11:11:36 +1200
> >
> >I have a midas AppServer and several clients.
> >
> >Previously this is what I had:
> >- 1 Server with 3 remote datamodules.
> > - 1 Remote datamodule contains the database connection
> > which is shared between the other 2 RDM's.
> > - The other 2 RDM contain queries, providers and procedures.
> >- 4 different clients which connect to both
> > of the remote data modules via Socket Connections
> >
> >What I have now:
> >- 1 Server with 4 remote data modules.
> > - 1 Remote datamodule contains the database connection
> > which is shared between the other 3 RDM's.
> > - The other 3 RDM contain queries, providers and procedures.
> >- The 4 existing clients which connect to RDM's 2 and 3
> > via Socket Connections
> >- 1 New Client which connects to RDM 4.
> >
> >Basically I have added a new RDM, and created a new client
> to connect to
> >it.
> >On my machine (W2K professional) this works fine. On the
> main server (W2k
> >server with terminal services and citrix) we get the error:
> >
> >EX. EOLESysEror
> >The class is configured to run as a security id different
> from the caller.
> >
> >Any suggestions?
> >
> >Thanks
> >
> >stacey
> >
> >
> >Stacey Verner Ph: +64-9-4154790
> >Software Developer Fax: +64-9-4154791
> >CJN Technologies Ltd. Email: [EMAIL PROTECTED]
> >PO Box 302-278, North Harbour, Auckland, New Zealand
> >12 Piermark Drive, North Harbour Estate, Auckland, NZ
> >Visit our website at http://www.cjntech.co.nz/
> >
>
> ______________________________________________________________
> __________
> Get Your Private, Free E-mail from MSN Hotmail at
http://www.hotmail.com
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
