DBPROCESS is dead - still

I have posted recently regarding one workstation that
receives the error message:
DBPROCESS is dead or not enabled. A database error has
occurred.
Database error code 10025.
Database error message: Select error: Possible network
error: Write to server failed. General network error.
Check your documentation.
This error isn't happening on any other workstations
running the same application. I have even moved the pc to
the same location where it's running successfully and it
still receives the same message. I have reinstalled the
client application and have re-installed Connectivity
only as the application uses DB-Library. Still the same
error. Anyone have any other ways of troubleshooting this
problem, or possible resolution?
Thanks,
HillaireHave you tried the dbsetavail command ?
J
>--Original Message--
>I have posted recently regarding one workstation that
>receives the error message:
>DBPROCESS is dead or not enabled. A database error has
>occurred.
>Database error code 10025.
>Database error message: Select error: Possible network
>error: Write to server failed. General network error.
>Check your documentation.
>This error isn't happening on any other workstations
>running the same application. I have even moved the pc to
>the same location where it's running successfully and it
>still receives the same message. I have reinstalled the
>client application and have re-installed Connectivity
>only as the application uses DB-Library. Still the same
>error. Anyone have any other ways of troubleshooting this
>problem, or possible resolution?
>Thanks,
>Hillaire
>.
>|||No I haven't. I'm wondering why would I need to, as the
application works correctly on all other pc's. Any idea
how it would solve the problem?
Thanks!!!
>--Original Message--
>Have you tried the dbsetavail command ?
>J
>>--Original Message--
>>I have posted recently regarding one workstation that
>>receives the error message:
>>DBPROCESS is dead or not enabled. A database error has
>>occurred.
>>Database error code 10025.
>>Database error message: Select error: Possible network
>>error: Write to server failed. General network error.
>>Check your documentation.
>>This error isn't happening on any other workstations
>>running the same application. I have even moved the pc
to
>>the same location where it's running successfully and
it
>>still receives the same message. I have reinstalled the
>>client application and have re-installed Connectivity
>>only as the application uses DB-Library. Still the same
>>error. Anyone have any other ways of troubleshooting
this
>>problem, or possible resolution?
>>Thanks,
>>Hillaire
>>.
>.
>|||To be perfectly honest, I have no idea why it would fail
on one but work on others.
The only thing I can think of is there is something on
that particular machine thats disabling it, i.e firewalls
and the like.
J
>--Original Message--
>No I haven't. I'm wondering why would I need to, as the
>application works correctly on all other pc's. Any idea
>how it would solve the problem?
>Thanks!!!
>>--Original Message--
>>Have you tried the dbsetavail command ?
>>J
>>--Original Message--
>>I have posted recently regarding one workstation that
>>receives the error message:
>>DBPROCESS is dead or not enabled. A database error has
>>occurred.
>>Database error code 10025.
>>Database error message: Select error: Possible network
>>error: Write to server failed. General network error.
>>Check your documentation.
>>This error isn't happening on any other workstations
>>running the same application. I have even moved the pc
>to
>>the same location where it's running successfully and
>it
>>still receives the same message. I have reinstalled the
>>client application and have re-installed Connectivity
>>only as the application uses DB-Library. Still the same
>>error. Anyone have any other ways of troubleshooting
>this
>>problem, or possible resolution?
>>Thanks,
>>Hillaire
>>.
>>.
>.
>