[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1508
  • Last Modified:

Scheduled jobs run, but don't seem to do anything

Hi - i had a previous question about getting tasks to run but this time it's about having the code in side the task actually run.  Despite trying to get code to run from the JS i just don't seem to be able to manage to get it to run.

I know i'm SA and the install was dbo so i'm working around that but would that really be the issue? surely SA can run the procs that the dbo installed?

Then i tried giving dbo all the JS permissions and that didn't work.

NARG.  This is so fickle.

Can anyone help?
0
edhe
Asked:
edhe
  • 5
  • 5
1 Solution
 
Joe WoodhousePrincipal ConsultantCommented:
It's not a permissions issue as anyone with sa_role is treated as dbo in every database they connect to.

Is it just this code? Can you make any proc run through the scheduler?
0
 
edheAuthor Commented:
I've tried different procs so.. no.  it works on one instance and i can't determine why that's different from the other instances.
0
 
Joe WoodhousePrincipal ConsultantCommented:
Hmm. Ok, asking the simple questions - have you installed & configured JS per the Job Scheduler User Guide?
0
KuppingerCole Reviews AlgoSec in Executive Report

Leading analyst firm, KuppingerCole reviews AlgoSec's Security Policy Management Solution, and the security challenges faced by companies today in their Executive View report.

 
edheAuthor Commented:
Yes - i had a previous question on here that highlighted that.  As far as i'm aware all the stuff is in place but i guess there must be something missing.  I've updated the interfaces file, i've done the permissions and the schedule's active etc etc.

However i do have a runaway process that i can't seem to see in standard PIDs that's stopping me from activating my JS again.  Currently googling for a way to terminate that properly since i've tried kill commands on all my user's pids.
0
 
Joe WoodhousePrincipal ConsultantCommented:
You may have to bounce the box...
0
 
edheAuthor Commented:
Bounce avoided thanks to pathing issue discovered, so got the JS running again however still not showing that the stuff works.  

I got this message in the JSAGENT log:

00:00001:1450040:2010/04/09 17:17:56.69 jamain  ja_open_jsagent_connection(): hostname is laurs55b.
00:00001:1450040:2010/04/09 17:17:56.75 jamain  SYB_JSAGENT connected with Job Scheduler Task on port 41002
00:00001:1450040:2010/04/09 17:17:56.75 jamain  SYB_JSAGENT waiting for connection
00:00001:1450040:2010/04/09 17:17:57.98 jamain  Initializing SYB_JSAGENT
00:00001:1450040:2010/04/09 17:17:57.98 jamain  Allocating list resources.
00:00001:1450040:2010/04/09 17:17:57.98 jamain  Allocating queue resources.
00:00001:1450040:2010/04/09 17:17:57.98 jamain  Allocating thread resources.
00:00001:1450040:2010/04/09 17:17:57.98 jamain  Initializing connection pool.
00:00001:1450040:2010/04/09 17:17:58.28 jamain  Server message: Changed database context to 'master'.

00:00001:1450040:2010/04/09 17:17:58.35 jamain  Server message: Changed database context to 'sybmgmtdb'.

00:00001:1450040:2010/04/09 17:17:58.36 jamain  Server message: Changed database context to 'master'.

00:00001:1450040:2010/04/09 17:17:58.38 jamain  Server message: Changed database context to 'sybmgmtdb'.

00:00001:1450040:2010/04/09 17:17:58.45 jamain  Server message: Changed database context to 'master'.

00:00001:1450040:2010/04/09 17:17:58.45 jamain  Server message: Changed database context to 'sybmgmtdb'.

00:00001:1450040:2010/04/09 17:17:58.73 jamain  Server message: Changed database context to 'master'.

00:00001:1450040:2010/04/09 17:17:58.76 jamain  Server message: Changed database context to 'sybmgmtdb'.

00:00001:1450040:2010/04/09 17:17:58.76 jamain  SYB_JSAGENT ready.
00:00515:00001:2010/04/09 17:18:01.31 worker  Job SQL failed.
00:00515:00001:2010/04/09 17:18:01.31 worker  callback to fetch results failed
00:00515:00001:2010/04/09 17:18:01.31 worker  jsd_GetResults() failed
00:00515:00001:2010/04/09 17:18:01.31 worker  jsj__RunSQLJob() failed
00:00772:00001:2010/04/09 17:18:36.82 worker  No password found for user sa on server MAIN_440
00:00772:00001:2010/04/09 17:18:36.82 worker  jsj__TargetInfo() failed
00:00772:00001:2010/04/09 17:18:36.85 worker  No job output connection pool provided
00:01286:00001:2010/04/09 17:20:00.92 worker  No password found for user sa on server MAIN_440
00:01286:00001:2010/04/09 17:20:00.92 worker  jsj__TargetInfo() failed
00:01286:00001:2010/04/09 17:20:00.95 worker  No job output connection pool provided
00:01029:00001:2010/04/09 17:20:01.48 worker  Job SQL failed.
00:01029:00001:2010/04/09 17:20:01.48 worker  callback to fetch results failed
00:01029:00001:2010/04/09 17:20:01.48 worker  jsd_GetResults() failed
00:01029:00001:2010/04/09 17:20:01.48 worker  jsj__RunSQLJob() failed
00:00515:00001:2010/04/09 17:22:01.09 worker  Job SQL failed.
00:00515:00001:2010/04/09 17:22:01.09 worker  callback to fetch results failed
00:00515:00001:2010/04/09 17:22:01.09 worker  jsd_GetResults() failed
00:00515:00001:2010/04/09 17:22:01.10 worker  jsj__RunSQLJob() failed


Ok - so it's failing, but i don't quite understand why.. The job was made by the sa
0
 
Joe WoodhousePrincipal ConsultantCommented:
Have you defined the sa password though? There are errors about "no password found for user sa".
0
 
edheAuthor Commented:
Yeah:
sp_addexternlogin MAIN_440, sa, sa, <pass>
go
0
 
Joe WoodhousePrincipal ConsultantCommented:
Hmm! I agree that should totally do the trick... Try comparing the .CFG files of an instance where it works? There may be something there in one of the CIS or security parameters? (Kinda clutching at straws here.)
0
 
edheAuthor Commented:
Ok, whittled it down to this in the log:
00:00772:00001:2010/04/09 17:55:00.42 worker  No job output connection pool provided
00:01286:00001:2010/04/09 17:56:00.73 worker  Job SQL failed.
00:01286:00001:2010/04/09 17:56:00.74 worker  callback to fetch results failed
00:01286:00001:2010/04/09 17:56:00.74 worker  jsd_GetResults() failed
00:01286:00001:2010/04/09 17:56:00.74 worker  jsj__RunSQLJob() failed
00:01029:00001:2010/04/09 17:58:00.83 worker  Job SQL failed.
00:01029:00001:2010/04/09 17:58:00.83 worker  callback to fetch results failed
00:01029:00001:2010/04/09 17:58:00.83 worker  jsd_GetResults() failed
00:01029:00001:2010/04/09 17:58:00.83 worker  jsj__RunSQLJob() failed
00:00772:00001:2010/04/09 18:00:01.35 worker  Job SQL failed.
00:00772:00001:2010/04/09 18:00:01.35 worker  callback to fetch results failed
00:00772:00001:2010/04/09 18:00:01.35 worker  jsd_GetResults() failed
00:00772:00001:2010/04/09 18:00:01.35 worker  jsj__RunSQLJob() failed
00:01286:00001:2010/04/09 18:02:00.53 worker  Job SQL failed.
00:01286:00001:2010/04/09 18:02:00.53 worker  callback to fetch results failed
00:01286:00001:2010/04/09 18:02:00.53 worker  jsd_GetResults() failed
00:01286:00001:2010/04/09 18:02:00.54 worker  jsj__RunSQLJob() failed


So it seems that the login's finally working...but i was getting some issues with some alert saying 'checkUpdate' something or other wasn't going to work for now - i think a process may have gotten stopped or locked.  Anyway Weekend beckons and this is almost done.
0

Featured Post

Managing Security & Risk at the Speed of Business

Gartner Research VP, Neil McDonald & AlgoSec CTO, Prof. Avishai Wool, discuss the business-driven approach to automated security policy management, its benefits and how to align security policy management with business processes to address today's security challenges.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now