I had a list of scheduled reports running in Pentaho bi server. every time I restart Pentaho server all the scheduled job are deleted.
When I check in Catalina here in what I got:
Caused by: org.pentaho.platform.api.scheduler2.SchedulerException: Quartz failed to list jobs.
at org.pentaho.platform.scheduler2.quartz.QuartzScheduler.getJobs(QuartzScheduler.java:481)
at org.pentaho.platform.web.http.api.resources.services.SchedulerService.getJobs(SchedulerService.java:503)
at org.pentaho.platform.web.http.api.resources.SchedulerResource.getJobs(SchedulerResource.java:415)
Related
I am running SQL Server Standard (linux) in a docker container and the Agent is not working to any schedule (recurring, one time).
The agent itself works, I have programmed a couple jobs which are completing successfully. However, the jobs do not even start when I activate the schedule meaning there isn't even an error message to review or record in the job activity monitor. Below is my configuration:
sql server job properties
I corrected the timezone issue by passing the proper environment variable, America/Toronto did not not pass properly, so I used America/New_York.
Scheduled a SSIS package on my Sql Server Agent, when i go to the Job History it says the Job succeded for the time it was scheduled to run, but im noticing the Job does nothing, i mean the Package is running but it's not doing what it is supossed to do.
I know the Package works because when i go to the BI Studio and rightclick>Execute Package it works.
Could be a security issue. Agent jobs run as the Agent Service Account, so you want to make sure that account has correct permissions in the database or else you will need to create an SSIS proxy to run the job.
Can I set up a SQL Server agent job to run the same job continuously as soon as the previous instance is completed or after 5 minutes (whichever is higher)? I'm using SQL Server 2012.
we have some cloud Services hosted in Windows Azure and also some Azure SQL database. At night (during 4:00 - 6:00 utc) there are running some Jobs to import data into database. Since some weeks all the Jobs fails with an timeout expired exception of the database. If I run the Jobs later (during 7:00 - 9:00 utc) on my local machine within the Emulator, all Jobs work without any Problems on the same database.
At the mport time is no much traffic from our site on the database server. The monitoring of the manage portal shows that there are not many open Connections, no throttled ones and no connection errors. There are much more traffic during my local runs.
The sys.event_log do not contains any errors or other possible issues.
Are there any logs or other Options to get more Information about why the Jobs failed at night?
Update
It seems, that the SQL Azure Server ignores the command timeout property. The Jobs start at 4:30 UTC and stops with an timeout exception at 4:37. But the query, which gets an timeout, has an command timeout of 1200 (20 minutes). And before starting the command, there are some downloads from an ftp-server, file parsing and other SQL queries.
Just to note that SQL Azure isn't a full version of MS SQL and does have some limitations. Most notable limitation is the infrastructure that its built on. Your SQL Azure DB will be hosted on a Small Instance server that has shared resource with hundreds of other users. Although there is a fair use policy on the machines it does take time for the servers to kick in.
My suggestion would be to have some way of determining if the Job is actually starting or if the connection pool is timing out prior to starting the job. I.E. create a jobs table that is inserted into to say its started and have this as the first action on your job.
Alternatively you could think about migrating to a VM setup in Azure. This is where you have a Small or Medium instance VM with a fully fledged version of MS SQL Server running on it. That way you can run your jobs against the server correctly and control you connection pooling more appropriately.
Im installing TFS 2012 on a windows Server 2012 VM. Im using a single server configuration and have SQL server standard installed. When I go through the TFS setup wizard it hangs on creating the database and after an hour or so I get the error below.
TF255356: The following error occurred when configuring the Team Foundation databases: TF400711: Error occurred while executing servicing step Update Servicing Resources for component UpdateTfsServicingResources during Install: TF246018: The database operation exceeded the timeout limit and has been cancelled. Verify that the parameters of the operation are correct.. For more information, see the configuration log.
You can view my log here:
https://docs.google.com/file/d/0B8ioN5Ats0NlY1AzYjRJR19wck0/edit?usp=sharing&pli=1