IB Server window name

Thread View: borland.public.interbase.opensource

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Gheorghe Mon, 28 Nov 2005 11:22

#209

Author: Gheorghe
Date: Mon, 28 Nov 2005 11:22

21 lines
1524 bytes

Hi,

I start IBServer as an application, and, upon starting up, use this code for
testing if server is already running:

            AnsiString s = "full path to ibserver.exe";

            HWND hPrevApp = FindWindow("IB_SERVER", NULL);
            if(!hPrevApp)
            {
                    // start ibserver
            }

Everithing works fine, except that some customers who use Win Terminal
Services report that code is trying to start IB even if it is already
started. They have to shut down ibserver.exe from Task Manager and then it
is OK.

It seems that on Terminal Services, the window name is not "IB_SERVER" but
smth. else.
Any ideas?

Re: IB Server window name

#210

Author: Bill Todd
Date: Mon, 28 Nov 2005 12:02

6 lines
1206 bytes

This is just a guess but I suspect that on Terminal Server if user A
starts IB as an application I doubt that  user B can see the window
handle since IB is running in user A's memory.

-- 
Bill Todd (TeamB)

Re: IB Server window name

#212

Author: Dan Palley
Date: Mon, 28 Nov 2005 16:50

34 lines
2031 bytes

"Gheorghe" <gmusca@dnt.ro> wrote in message 
news:438ae817@newsgroups.borland.com...
> Hi,
>
> I start IBServer as an application, and, upon starting up, use this code 
> for
> testing if server is already running:
>
>            AnsiString s = "full path to ibserver.exe";
>
>            HWND hPrevApp = FindWindow("IB_SERVER", NULL);
>            if(!hPrevApp)
>            {
>                    // start ibserver
>            }
>
> Everithing works fine, except that some customers who use Win Terminal
> Services report that code is trying to start IB even if it is already
> started. They have to shut down ibserver.exe from Task Manager and then it
> is OK.
>
> It seems that on Terminal Services, the window name is not "IB_SERVER" but
> smth. else.
> Any ideas?

The hidden window that IB uses for local connections is only available on 
the console session when running on Terminal Server.  Other sessions will 
need to connect to the server using TCP/IP and a loopback connection 
(localhost).  What you can do is connect to the server using the API to see 
if it's running.

Why not simply have IB run as a service instead?

Dan

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads