At 09:23 AM 11/12/2005 +0000, you wrote:

>Hi,
>
>We have a win2003 with 4 x Opteron CPU and a Firebird 1.5.2 SS on it.
>Often, the clients cannot connect on \\SERVER1\Files\MyFDB.FDB because
>(we presume) a file named PIPE\interbas\server\gds_db remains open
>from yesterday session. What's odd is that sometimes some clients can
>connect, others don't.

\\SERVER1\Files\MyFDB.FDB is not a legal connection string. This looks
like a shared resource - its path should not be available to a Firebird client.

>In this situation we cannot stop the fbserver service from the
>'services' window.
>
>Then we press Ctrl+Alt+Del and kill the fbguard and fbserver. Then
>start the fbserver service and everything is ok.

..except or any work that users lost from doing this. It is NOT a good
thing to do.

>This happens in the morning, when the first user tries to log in.
>
>Can you help us? (we can provide any other info on request)

Do not try to access any database through a shared or mapped resource. You
must use the server MACHINE's actual network host name (not a virtual
server name) and provide either the absolute file path to the database or
an alias that point to the absolute path.

For example, if the host machine is named Socrates and your Files directory
is on drive c:

Using Named Pipes protocol:

\\Socrates\c:\FilesMyFDB.FDB

or if using TCP/IP (recommended):

Socrates:c:\Files\MyFDB.FDB

Also, on an SMP machine, the CPUAffinityMask must be set to one and only
one CPU. By default it is set to "1" (for CPU 0). To calculate the mask
setting for a different CPU, see the release notes for instructions.

./heLen