Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

ASE15.0.3 job scheduler question

3 posts in General Discussion Last posting was on 2009-07-05 00:10:43.0Z
CC Posted on 2009-07-02 22:20:58.0Z
Reply-To: "CC" <frankchen66@hotmail.com>
From: "CC" <frankchen66@hotmail.com>
Newsgroups: sybase.public.ase.general
Subject: ASE15.0.3 job scheduler question
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a4d32ca$1@forums-3-dub.sybase.com>
Date: 2 Jul 2009 15:20:58 -0700
X-Trace: forums-3-dub.sybase.com 1246573258 10.22.241.152 (2 Jul 2009 15:20:58 -0700)
X-Original-Trace: 2 Jul 2009 15:20:58 -0700, vip152.sybase.com
Path: forums-1-dub!forums-master!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:27956
Article PK: 77203

Hi,

just installed ASE15.0.3 with latest EBF in windows 2003 server. Everything
works fine except the "Scheduled Jobs" function that I tried to use by
Sybase Central.

It looks like the there's one scheduled job "ID 1" came with the
installation. However, when I tried to run it, this message showed in the
log -
---------------
Login failed.
ct_connect(): protocol specific layer: external error: The attempt to
connect to the server failed.
--------------

Check the status of Job Scheduler through its Administration, it shows -
"The job scheduler task is: running"

Did I miss any simple thing on this?

Thanks in advance,
CC


"Mark A. Parsons" <iron_horse Posted on 2009-07-03 01:52:14.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: ASE15.0.3 job scheduler question
References: <4a4d32ca$1@forums-3-dub.sybase.com>
In-Reply-To: <4a4d32ca$1@forums-3-dub.sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 090702-0, 07/02/2009), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a4d644e@forums-3-dub.sybase.com>
Date: 2 Jul 2009 18:52:14 -0700
X-Trace: forums-3-dub.sybase.com 1246585934 10.22.241.152 (2 Jul 2009 18:52:14 -0700)
X-Original-Trace: 2 Jul 2009 18:52:14 -0700, vip152.sybase.com
Lines: 40
Path: forums-1-dub!forums-master!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:27957
Article PK: 77204

What is job 'ID 1' suppose to do?

If job 'ID 1' is trying to log into a remote dataserver ... does it have the correct login credentials for the remote
dataserver?

--------------

I don't use job scheduler but fwiw ... if I installed the product and saw an unknown job in my queue, I certainly would
*NOT* go running the job without first knowing what it's suppose to do.

What if the job drops (or truncates) tables? What if the job drops databases? What if the job does a shutdown of my
(production?) dataserver?

CC wrote:
> Hi,
>
> just installed ASE15.0.3 with latest EBF in windows 2003 server. Everything
> works fine except the "Scheduled Jobs" function that I tried to use by
> Sybase Central.
>
> It looks like the there's one scheduled job "ID 1" came with the
> installation. However, when I tried to run it, this message showed in the
> log -
> ---------------
> Login failed.
> ct_connect(): protocol specific layer: external error: The attempt to
> connect to the server failed.
> --------------
>
> Check the status of Job Scheduler through its Administration, it shows -
> "The job scheduler task is: running"
>
> Did I miss any simple thing on this?
>
> Thanks in advance,
> CC
>
>


Niksa Jurinovic Posted on 2009-07-05 00:10:43.0Z
Message-ID: <4a4fef82$2@forums-3-dub.sybase.com>
From: Niksa Jurinovic <niksa@jurinovic.de>
Subject: Re: ASE15.0.3 job scheduler question
Newsgroups: sybase.public.ase.general
References: <4a4d32ca$1@forums-3-dub.sybase.com>
Lines: 43
Organization: Independent developer
User-Agent: KNode/0.10.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 4 Jul 2009 17:10:43 -0700
X-Trace: forums-3-dub.sybase.com 1246752643 10.22.241.152 (4 Jul 2009 17:10:43 -0700)
X-Original-Trace: 4 Jul 2009 17:10:43 -0700, vip152.sybase.com
Path: forums-1-dub!forums-master!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:27962
Article PK: 77208


CC wrote:

> Hi,
>
> just installed ASE15.0.3 with latest EBF in windows 2003 server.
> Everything works fine except the "Scheduled Jobs" function that I tried to
> use by Sybase Central.
>
> It looks like the there's one scheduled job "ID 1" came with the
> installation. However, when I tried to run it, this message showed in the
> log -
> ---------------
> Login failed.
> ct_connect(): protocol specific layer: external error: The attempt to
> connect to the server failed.
> --------------
>
> Check the status of Job Scheduler through its Administration, it shows -
> "The job scheduler task is: running"
>
> Did I miss any simple thing on this?
>
> Thanks in advance,
> CC

Most probably it's a password problem. You installed ASE server and Job
Scheduler with null password and then, after installation, changed server
password (with sp_password). That invalidated stored jstask's remote
password.

Start Sybase Central, choose Remote Servers on left pane, select loopback
server on the right pane, press right mouse button and select Properties.
Click on CIS Mapping tab and remove whatever item exists. Click on Add
button and select jstask as Local login, type 'sa' as Remote login and
enter correct Remote password (password for 'sa').

Then try to run predefined scheduled job again.


Niksa Jurinovic