SQL Anywhere database - Adaptive Server Anywhere 9.0.2.2551 service

Author

Adaptive Server Anywhere 9.0.2.2551 service

Robert

2005-08-16, 8:23 pm

I have a client who's Adaptive Server Anywhere service is hanging up and
cannot be stopped from Sybase Central or Windows service management console.
We have tried to stop the dbsrv9.exe process through task manager, but he is
getting an error that access is denied. The server has been restarted, but
the service is set to automatic and cannot be modified to manual. Does
anyone have a suggestion on how to force the service to stop or have an idea
as to why the database service will not end.

Thanks in advance,

Robert

Joshua Savill

2005-08-17, 9:27 am

Is the customer logging into the server with a User that has Administrative
Permission to stop the service? What OS is your customer using?

--
Joshua Savill
iAnywhere Solutions - Product Support Analyst

"Robert" <rpruski@esc20.net> wrote in message
news:4302407c$1@foru
ms-1-dub...
>I have a client who's Adaptive Server Anywhere service is hanging up and
>cannot be stopped from Sybase Central or Windows service management
>console. We have tried to stop the dbsrv9.exe process through task manager,
>but he is getting an error that access is denied. The server has been
>restarted, but the service is set to automatic and cannot be modified to
>manual. Does anyone have a suggestion on how to force the service to stop
>or have an idea as to why the database service will not end.
>
> Thanks in advance,
>
> Robert
>

Erik Anderson

2005-08-17, 1:23 pm

I must say that I have experienced these symptoms many times in the past.
On operating systems prior to Windows XP the system administrator does not
have the authority to task-manager closed services owned by the SYSTEM user.
If the dbsrv application has frozen or otherwise stopped responding on a
Win2k system there may be no other alternative than to reboot the machine.

The big issue at this point is to track down and prevent the server from
getting into a "jammed" state to begin with...

"Joshua Savill" <jsavill@ianywhere.com> wrote in message
news:43032bc2$1@foru
ms-1-dub...
> Is the customer logging into the server with a User that has
> Administrative Permission to stop the service? What OS is your customer
> using?
>
> --
> Joshua Savill
> iAnywhere Solutions - Product Support Analyst
>
> "Robert" <rpruski@esc20.net> wrote in message
> news:4302407c$1@foru
ms-1-dub...
>
>

Jeremy Swift

2005-08-23, 7:24 am

Hi, I have just discovered this problem in Windows Server 2003 SP1 as
well.

I have a setup that runs several dbsrv9 and dbremote tasks as
services and Sybase Central won't stop the replication services.
Looking at the replication logs though, they show that replication has
ended.

The task is shown as stopping and Central hangs until you use task
manager to kill the task.

I'm guessing its a rights issue - it worked fine on W2K before we
upgraded - but even with the service runnning under the system
administrator account and logging in with the same account to run
Central the problem persists. Any suggestions about what rights
settings to look for?

We are running ASA 9.0.2.3131.

Thanks

On 17 Aug 2005 09:35:45 -0700, "Erik Anderson"
< erikba@teamworkgroup
.com> wrote:

>I must say that I have experienced these symptoms many times in the past.
>On operating systems prior to Windows XP the system administrator does not
>have the authority to task-manager closed services owned by the SYSTEM user.
>If the dbsrv application has frozen or otherwise stopped responding on a
>Win2k system there may be no other alternative than to reboot the machine.
>
>The big issue at this point is to track down and prevent the server from
>getting into a "jammed" state to begin with...
>
>"Joshua Savill" <jsavill@ianywhere.com> wrote in message
> news:43032bc2$1@foru
ms-1-dub...
>

Thomas Shouse

2005-08-25, 8:23 pm

I have this problem but only when attempting to run multiple database
engines and multiple remote message agents on the same machine. It never
occurred until after 9.0.2 2451, that is after I applied a later patch.

This never occurs in production environments for me, but the production
machines only run one engine and one remote message agent. I am running
9.0.2 3769 at this time.

This also never occurs on faster servers, just on my slower servers.

I use KILL.EXE to stop a rogue service. But, again, only do this on our
development servers, never on production.

"Jeremy Swift" <jeremy.swift@wmann.com> wrote in message
news:srrlg1pctsd9cdu
haq6j1md0qja0rnboub@
4ax.com...
> Hi, I have just discovered this problem in Windows Server 2003 SP1 as
> well.
>
> I have a setup that runs several dbsrv9 and dbremote tasks as
> services and Sybase Central won't stop the replication services.
> Looking at the replication logs though, they show that replication has
> ended.
>
> The task is shown as stopping and Central hangs until you use task
> manager to kill the task.
>
> I'm guessing its a rights issue - it worked fine on W2K before we
> upgraded - but even with the service runnning under the system
> administrator account and logging in with the same account to run
> Central the problem persists. Any suggestions about what rights
> settings to look for?
>
> We are running ASA 9.0.2.3131.
>
> Thanks
>
> On 17 Aug 2005 09:35:45 -0700, "Erik Anderson"
> < erikba@teamworkgroup
.com> wrote:
>
>

Jeremy Swift

2005-08-26, 7:23 am

I'v posted a bug report to Sybase.

On 25 Aug 2005 14:37:54 -0700, "Thomas Shouse" <tshouse@epicsol.com>
wrote:

>I have this problem but only when attempting to run multiple database
>engines and multiple remote message agents on the same machine. It never
>occurred until after 9.0.2 2451, that is after I applied a later patch.
>
>This never occurs in production environments for me, but the production
>machines only run one engine and one remote message agent. I am running
>9.0.2 3769 at this time.
>
>This also never occurs on faster servers, just on my slower servers.
>
>I use KILL.EXE to stop a rogue service. But, again, only do this on our
>development servers, never on production.
>
>
>"Jeremy Swift" <jeremy.swift@wmann.com> wrote in message
> news:srrlg1pctsd9cdu
haq6j1md0qja0rnboub@
4ax.com...
>

Sponsored Links