adTempus Knowledge Base

K00000213: All programs fail to run with error "A required privilege is not held by the client" when adTempus service set to run under user account

Thu, 22 Mar 2012 15:34:00 GMT

Symptoms

Whenever adTempus tries to run a program, the job fails, and the job log contains one of the following messages:

Logon failed for user 'username': A required privilege is not held by the client.

The program could not be started: A required privilege is not held by the client. (1314)

Cause

These errors occur if the adTempus service has been configured to run under a user account that does not have the necessary permissions or privileges.

Resolution

See article K00000215 for information on configuring the user account properly.

You may instead prefer to reconfigure adTempus to run under the Local System account. If you are using a remote SQL Server instance to host the adTempus database, you will in this case need to configure SQL Server to grant permission for the adTempus computer, as discussed in article K00000397.

K00000397: Granting adTempus access to a remote database when running under the Local System account

Fri, 30 Mar 2012 16:09:26 GMT

Summary

This artcle describes how to grant adTempus access to a remote SQL Server database when adTempus is running under the Local System account.

Background

The adTempus service by default runs under the Local System account, and this is the preferred account for the service.

However, the Local System account by default cannot connect to a database hosted on a different computer. In such a configuration, the adTempus database configuration documentation recommends that you either change your database and adTempus to use explicit SQL Server authentication, or reconfigure the adTempus service to run under a user account that has the necessary database permissions (see article K00000215).

However, both of these approaches have drawbacks:

Many administrators prefer to avoid enabling explicit SQL Server authentication on the database server.
Running adTempus under a user account requires extra steps to enable account rights for the user account.

A third approach is to add access to SQL Server for the Local System account on the adTempus computer, as described in the following section.

Configuring SQL Server

Note: This procedure is only necessary if adTempus is running on a different computer than SQL Server. If they are on the same computer, no further configuration is needed.

To grant adTempus access to a remote SQL Server, you must add a machine login to SQL Server. To do so, connect to SQL Server using SQL Server Management Studio or another management tool.

In the database script below, make the following replacements:

Change "domain" to the name of your domain.
Change "computername" to the name of the computer where the adTempus service is running. Be sure to leave the "$" after the name as shown below.
Change "databasename" to the name of the adTempus database.

CREATE LOGIN [domain\computername$] FROM WINDOWS with DEFAULT_DATABASE=[databasename]
go

use [databasename]
go

EXEC sp_grantdbaccess N'domain\computername$', N'domain\computername$'
go

exec sp_addrolemember N'db_accessadmin', N'domain\computername$'
GO

exec sp_addrolemember N'db_backupoperator', N'domain\computername$'
GO

exec sp_addrolemember N'db_datareader', N'domain\computername$'
GO

exec sp_addrolemember N'db_datawriter', N'domain\computername$'
GO

exec sp_addrolemember N'db_ddladmin', N'domain\computername$'
GO

exec sp_addrolemember N'db_owner', N'domain\computername$'
GO

exec sp_addrolemember N'db_securityadmin', N'domain\computername$'
GO

Run the modified script and make sure that all statements succeeded.

adTempus should now be able to connect to the database while running under the Local System account.

K00000309: Error when saving Script or ScriptLibrary on 64-bit platforms

Tue, 20 Mar 2012 19:56:39 GMT

Symptoms

When you edit a script that uses a Windows Script Host language such as VBScript or JScript, the adTempus Console gives the following error when you try to save or test the script:

Retrieving the COM class factory for component with CLSID {0E59F1D5-1FBE-11D0-8FF2-00A0D10038BC} failed due to the following error: 80040154.

.NET scripts (VB.NET, C#) are not affected.

The problem occurs only on 64-bit versions of Windows.

Cause

When you save the script, adTempus tries to validate the script.

To execute or validate VBScript or JScript scripts, adTempus uses a scripting engine component that is part of the Windows operating system. Microsoft has not created a 64-bit version of this component, and the adTempus Console (which runs as a 64-bit process) is not able to load the 32-bit scripting component and therefore fails with the error above.

At execution time, adTempus avoids this issue by hosting the script within a 32-bit process.

Workaround

You may ignore the error. The script will save and execute correctly. If the script contains syntax or logic errors, the script will fail when the job is run, and the error details will be reported in the Job Log.

Status

adTempus
This issue has been corrected and the fix will be included in the next maintenance update or software release. Customers affected by the problem may contact us to obtain the fix now.

K00000366: adTempus reports database errors after server hosting database is renamed

Thu, 26 Jan 2012 15:04:15 GMT

Symptoms

If you are using the default SQL Server Express database for adTempus, and you rename the computer after the software has been installed, adTempus may report the following database error:

Could not find server 'servername\ADTEMPUS' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers. (source=Microsoft OLE DB Provider for SQL Server; native error=7202; SQL state=42000)

Where servername is the new name of the computer.

This problem may prevent adTempus from starting, or it may only appear occasionally, causing adTempus to report a catastrophic database failure.

Cause

This problem occurs because of problems caused in SQL Server when the host computer is renamed.

Resolution

This problem can be updated by making a system update to SQL Server.

To do this, run the "adtdbutil.exe" utility found in the adTempus program directory. When started, adtdbutil will connect to the adTempus database and display an empty command-entry window. Enter the following commands, pressing F5 to execute each one:

sp_dropserver 'oldname\adtempus'

sp_addserver 'newname\adtempus',local

EXEC sp_serveroption 'newname\adtempus', 'DATA ACCESS', TRUE

where oldname is the old name for the computer, and newname is the new name.

After you have performed this operation, restart the adTempus service.

Note: If you do not know what the previous name of the computer was, enter the following command after starting adtdbutil, and press F5 to execute it:

select name from sys.servers

Use the name returned by this query in place of "oldname\adtempus" in the commands shown above.

K00000395: SQL Server Express frequently logs message 17137 ("Starting up database")

Thu, 01 Dec 2011 21:07:17 GMT

Symptoms

When adTempus is installed using the default SQL Server Express database engine, you may see frequent informational messages in the Application log in the Event Viewer with source MSSQL$ADTEMPUS and event ID 17137, reading "Starting up database 'adtempus_computername'."

Cause

This occurs if the adTempus database has the auto-close option set, which causes SQL Server to close the database whenever adTempus is not actively using it, and then reopen the database each when adTempus requests a new connection. Each time this happens, SQL Server logs the message. This situation may also reduce the performance of adTempus.

Resolution

To resolve this problem, update the adTempus database to turn off the auto-close option.

To do this, start the adtdbutil tool found in the adTempus program directory (see article K00000385 for more information). After the tool starts and connects to the database, enter the following command into the query panel:

alter database [databasename] set auto_close off

Replace databasename with the name of the adTempus database, which is shown in the Event Log message.

Press F5 to execute the command.

K00000393: E-mail notification fails when trying to use a mail server that requires SSL or TLS

Wed, 23 Nov 2011 15:44:10 GMT

Symptoms

When you configure adTempus to use an SMTP server that requires SSL or TLS connections (any server, such as Google Mail, that requires you to connect to port 465 or 587), notification tests and notification messages will fail with error "Failed to connect to SMTP server." If you display the details for the error message, the details will contain the following message:

530 5.7.0 Must issue a STARTTLS command first

Cause

adTempus does not currently support SSL or TLS connections for e-mail.

Status

adTempus
This issue has been corrected and the fix will be included in the next maintenance update or software release. Customers affected by the problem may contact us to obtain the fix now.

K00000392: Selecting a job in the adTempus Console results in error message "Arithmetic operation resulted in an overflow"

Mon, 21 Nov 2011 22:09:02 GMT

Symptoms

When you select a job in the adTempus Console, adTempus displays the following error message:

Arithmetic operation resulted in an overflow

After you acknowledge this message, you can still work with the job normally, though the information shown on the Statistics tab for the job may be incomplete.

Cause

This error is caused by a math overflow when adTempus attempts to display statistics for the job.

Status

adTempus
This issue has been corrected and the fix will be included in the next maintenance update or software release. Customers affected by the problem may contact us to obtain the fix now.

K00000391: Recipients of notification messages cannot determine who else received the message

Mon, 21 Nov 2011 17:55:01 GMT

Symptoms

When adTempus sends a notification message the results of the Notification Task or a Notification Action, each recipient of that notification message receives a separate copy of the message addressed only to them. The recipient is not able to see which other recipients received the message.

Cause

This behavior is by design, and stems from the ability of adTempus to customize the way each recipient receives a message, for example, by limiting the length of the message.

Status

In the next major release of adTempus, the notification framework will be updated so that a single message can be sent listing all notification recipients. Unfortunately, no workaround is currently available for this behavior.

K00000390: Using .NET Framework version 4.0 for scripts

Fri, 04 Nov 2011 17:57:21 GMT

Summary

This article describes how to configure adTempus so that user scripts written in the .NET languages (such as VB.NET and C#) can use language features and assemblies from version 4.0 of the Microsoft .NET Framework.

More Information

adTempus version 3.x and earlier is built using version 2.0 of the .NET Framework, and any .NET scripts run by adTempus therefore also use version 2.0. If you want to run scripts that use features from later versions of the .NET Framework, you must update the adTempus runtime configuration files so that the newer version of the Framework will be loaded.

First make sure that version 4.0 of the .NET Framework is installed on the computer where the adTempus service is running, and on any remote computers where you are running the adTempus Console.

Next you must configure the adtjobhost program, which is responsible for executing the scripts. Edit the file "adtjobhost.exe.config" found in the adTempus program directory on the adTempus server (the computer where the adTempus service is installed and where jobs run). You can edit this file using a text editor such as Notepad.

In this file, locate the line at the end of the file that reads

</configuration>

Immediately above this line, insert the following text:

Save and close the file.

Next you must configure the adTempus Console so that the correct version of the .NET Framework will be used for the script editor in the Console. Edit the "adtconsole.exe.config" file, also found in the adTempus program directory, and make the same change. After saving the file, you will need to close and restart the adTempus Console if it was running, in order for the change to take effect.

Note: If you are running the adTempus Console on any remote computers, you will need to update adtconsole.exe.config on those computers as well.

It is not necessary to restart the adTempus service for the configuration changes to take effect.

K00000288: Configuring the automatic database backup

Tue, 04 Oct 2011 15:28:20 GMT

Summary

If you are using the default SQL Server Express database engine for adTempus, adTempus creates a database backup automatically each day around 1:30 AM. This article explains how to change the settings for the automatic backup.

More Information

The automatic backup cannot be configured through the adTempus Console, but some settings can be changed by setting options in the Registry on the computer where the adTempus service is running. Note that any changes you make will not take effect until the adTempus service is restarted.

The following settings are stored under Registry key "HKEY_LOCAL_MACHINE\Software\Arcana Development\adTempus\options". If the "options" key does not exist, you will need to create it.

Each setting is controlled by a string (REG_SZ) value created under the options key. You will need to create each value, as they are not present by default. Be sure to create each value as a STRING value. For example, to set the "Maintenance:DoDatabaseBackup" option, create (or modify if it already exists) the "Maintenance:DoDatabaseBackup" value.

Option Name	Description
Maintenance:DoDatabaseBackup	Controls whether the backup is performed. Set to "0" to disable backups. Set to "1" to enable backups. If no value is present, the backup will be performed.
Maintenance:BackupTime	Sets the time at which the backup will occur. Specify the time in the form "HH:mm". For example, "02:45" to run the backup at 2:45 AM, or "16:30" to run it at 4:30 PM.
Maintenance:LogBackupSuccess	Determines whether adTempus will log a message when the backup succeeds. If the value is set to "1", adTempus will log an informational message to the computer's Event Log and also to the Alerts log in adTempus indicating that the backup ran successfully. If this value is set to "0", adTempus will log a message only if the backup fails. Default value: "0".

You can change where the automatic backup is stored by setting the DatabaseBackupPath option.

Note: This option is set in a different location than the options described above.

The following settings are stored under Registry key "HKEY_LOCAL_MACHINE\Software\Arcana Development\adTempus".

Each setting is controlled by a string (REG_SZ) value created under the key. You will need to create the value, as is is not present by default.

Option Name	Description
DatabaseBackupPath	Sets the path where the backup file will be written. This must be on a local drive (mapped network drives and UNC paths are not allowed) because the backup is performed by SQL Server, which is running under the Local System account and does not have access to remote resources. If no value is specified, the backup is written to the "data\backup" directory under the adTempus program directory.

K00000388: Predefined Job Variables variables for adTempus 3.x

Mon, 12 Sep 2011 14:26:19 GMT

Summary

When adTempus runs a program or script, it defines Job Variablesthat the program or script can use. These variables are discussed in the Predefined Variables topic in the adTempus 3.x help document.

Some new variables have been added to adTempus since the last update of the documentation. This article provides the current list of variables.

More Information

The list below includes all of the predefined variables as of adTempus version 3.0.8.1.

Variable Name	Description
ADJobInstance	A GUID identifying this instance of the job. This value is used by the adtchkpt utility program.
ADTExecutionReason	A message indicating why the job is being run, e.g., "scheduled execution".
ADTExecutionAttempt	The execution attempt number. This value will be 1 for the first attempt and is incremented each time the job is restarted by a Job Control Action.
ADTJobDescription	The name of the job.
ADTInstanceID	The instance number for this instance.
ADTJobOID	The unique identifier for this job.
ADTTriggerClass	The name of the trigger that started the job.
ServerName	The name of the computer where the job is running.
ADTQueueName	The name of the Job Queue that the job is assigned to.
ADTGroupName	The full name of the Job Group that contains the job.
ADTJobStep	The unique identifier for this job step.
ADTStepNumber	The step number.
ADTJobCheckpoint	The checkpoint being passed to the program.
ADTStepRestartCount	The restart count. This value will be 0 for the first attempt and is incremented each time the step is restarted by a Job Control Action.
ADTStepDescription	The system-generated description of the step. Use ADTStepName to get the user-supplied name of the step.
ADTFullyQualifiedJobName	The fully-qualified name of the job, including the names of its ancestor groups, e.g., "Group 1\Group 1a\My Job".
ADTJobNotes	The contents of the Description/Notes field from the job properties.
ADTStepNotes	The contents of the Description/Notes field from the job step properties.
ADTStepName	The name of the step, if specified.
ADTTaskResult	The exit code of the most recent Program Execution Task to be executed.
ScriptResult	The Result value provided by the most recent script to be executed.
ConsoleOutputFileName	The name of the file containing the captured console output from the most recent step that captured console output.

Various triggers may also add additional variables. See the documentation for the individual triggers for more information.

K00000376: Web Request task and SQL Server Job task fail with error "The task could not be executed because a required software component is not installed on this computer"

Fri, 22 Jul 2011 15:14:49 GMT

Symptoms

After installing adTempus version 3.0.8 on a computer running a 64-bit version of Windows, jobs that use the Web Request task or the SQL Server Job task fail, and the following error message is reported in the job log:

The task could not be executed because a required software component is not installed on this computer.

Cause

This problem occurs because of a problem in the task hosting component of adTempus.

Resolution

This problem was resolved in version 3.0.8.1 of adTempus. If you are running version 3.0.8, download the latest release from the adTempus download page and run it to update your installation.

If you are running version 3.0.8.1 or later and still experiencing the problem, submit as support request for assistance with this issue. Include with your support request the log files from the "logs" directory under the adTempus program directory.

K00000387: Allowing remote access to the adTempus SQL Server Express database

Tue, 03 Jan 2012 19:11:37 GMT

Summary

This article describes how to configure the adTempus SQL Server Express installation to allow connections from remote computers.

More Information

When you use the default SQL Server Express installation to host the adTempus database, the database server is by default configured so that only local connections are allowed (no connections are allowed from other computers). In some cases you may wish to allow remote access (for example, to query the database from another computer).

This change will enable users from other computers to query the adTempus database directly. Consider the security implications of this before making the change. In the default configuration, only members of the Administrators group will have access.

To make this change:

Log in as an Administrator to the computer where the adTempus service is installed.
Go to the Start menu, then Microsoft SQL Server 2005, then Configuration Tools, then SQL Server Surface Area Configuration.
In the Surface Area Configuration tool, click the Surface Area Configuration for Services and Connections link.
Expand ADTEMPUS, then Database Engine, and select Remote Connections.
Check the option for Local and Remote Connections and Using TCP/IP Only.
Click OK.
Using the Windows Services tool, restart the "SQL Server (ADTEMPUS)" service. This will require restarting adTempus as well.

Designating System Administrators

Depending on the version of Windows running on the computer, members of the Administrators group may automatically have access to SQL Server. On newer versions of Windows, only the user who installed adTempus and SQL Server will have access by default, and other users will need to be added.

To add an additional user as a System Administrator for SQL Server:

Log in as an Administrator to the computer where the adTempus service is installed.
Go to the Start menu, then Microsoft SQL Server 2005, then Configuration Tools, then SQL Server Surface Area Configuration.
In the Surface Area Configuration tool, click the Add New Administrator link.
Enter the appropriate user ID in the User to provision box.
Select the "Member of SQL Server SysAdmin role on ADTEMPUS" privilege and click the right arrow button to add the privilege for the user.
Click OK to complete the configuration.

This will grant the selected user full permissions for the adTempus instance of SQL Server. To grant a lower level of access (such as read-only) use SQL Server Management Studio (see article K00000385) and refer to SQL Server documentation on user and security management.

K00000385: How to query the adTempus database

Tue, 03 Jan 2012 19:01:26 GMT

Summary

This article explains how to query the adTempus database.

More Information

Note: Direct updates to the adTempus database are not supported and may result in unrecoverable data corruption. Do not execute any updates against the adTempus database unless you are instructed to do so by a support engineer.

adTempus data is stored in a SQL Server database, which can be queried using standard SQL Server client tools.

Standalone SQL Server Instance

If you are using your own SQL Server instance to host the adTempus database, you can use SQL Server Management Studio or any other SQL Server query tool to query the database.

SQL Server Express

If you are using the default SQL Server Express installation to host the database, no tools are provided as part of the SQL Server installation. Instead you can use the adtdbutil.exe tool found in the adTempus program directory.

When you start adtdbutil it will automatically connect to the adTempus database and display a query panel. Enter your SQL query into the box and press F5 to execute it. Note that you can paste text into the query box using CTRL-V.

If you prefer to use a more robust query tool you can download and install the free SQL Server Management Studio Express from Microsoft.

Alternatively, if you already have Management Studio or another query tool installed on another computer, you can run that tool and connect to the adTempus database. You will first need to enable remote access to the adTempus database, as described in article K00000387.

When connecting to the adTempus database from a remote computer, specify the server to connect to as "computername\adtempus", where computername is the name of the computer where adTempus is installed.

K00000354: "Cannot connect to database" error when running adTempus reports from Console

Thu, 05 May 2011 16:52:03 GMT

Symptoms

When you attempt to run one of the reports listed below from the adTempus Console, you receive the following error message:

Cannot connect to database

The problem occurs with the following reports:

Job Accounting Report
Job History Report

The problem may occur in the following scenarios:

The user running the report is not a member of the Administrators group; or
adTempus is using the default SQL Server Express database, and the Console from which you are attempting to run the report is a remote Console (that is, it is running on a different computer than the adTempus service).

Cause

The adTempus Console does not ordinarily communicate directly with the database (it communicates only with the adTempus service), so users using the Console do not need permission to access the adTempus database directly. However, these two reports do make a direct connection to the adTempus database, bypassing the Console and the service. As a result, the user running the reports must have read permission for the adTempus database.

In addition, by default, SQL Server Express is configured to allow only local connections. Therefore the connection will fail if the report is being run from a remote computer.

Resolution

To resolve this issue you must reconfigure SQL Server to allow remote connections and/or to allow access to the user attempting to run the report.

Allow Remote Access to SQL Server Express

Follow the instructions in article K00000387 to allow remote access to SQL Server Express.

The reports should now run correctly from the remote Console.

Grant Read Permission to Affected Users

The user who is running the Console must have read permissions for the adTempus database. This permission requirement is separate from any permissions that have already been configured within adTempus itself, and must be configured within SQL Server.

Follow these instructions to make the changes.

Determine whom you will grant access to, based on your security policies and on who needs access to the reports. You may choose to grant access to only a single user, or to a group of users. In the example below, we assume that a Windows domain security group called "adTempus users" has already been created, and we grant access to members of that group.
Log in as an Administrator to the computer where the adTempus service is installed.
Run the "adtdbutil" program found in the adTempus program directory (e.g., "c:\program files\arcana development\adTempus\adtdbutil.exe"). This utility will connect to the adTempus database and display an empty query-entry box.
Enter the following text into the query box:

CREATE LOGIN [MYDOMAIN\adTempus users] FROM WINDOWS; 
CREATE USER [MYDOMAIN\adTempus users] FOR LOGIN [MYDOMAIN\adTempus users]; 
EXEC sp_addrolemember N'db_datareader', N'MYDOMAIN\adTempus users';
Note: Replace "MYDOMAIN\adTempus users" with the user name or group (including domain name, if appropriate) that you want to grant access to.

Press the F5 key to execute the command.
The Messages panel at the bottom of the window should display the message "Command completed successfully".

The designated user(s) will now be able to run the reports.

Note: If you are using your own SQL Server instance to host the adTempus database, you or your database administrator can use SQL Server Management Studio to make the necessary changes, and any changes should be made in accordance with your organization's security policies.

K00000386: Querying the adTempus database to obtain a list of notification recipients for each job

Thu, 05 May 2011 16:40:10 GMT

Summary

This article provides a database query that can be used to get a list of all jobs that send notification messages and the recipients that each job notifies.

More Information

See article K00000385 for instructions on how to execute a database query.

The following SQL query returns a list of all jobs that contain Notification Tasks or Notification Actions in Responses, and lists all of the notification recipients who receive notification for the job. The query reports on job-level and step-level Responses.

select j.name as JobName,
0 as StepNumber,
cast(event as varchar(50)) as Event,
'Individual' as RecipientType,
nr.name as RecipientName
from job j join response r on j.oid=r.owner
join actions a on r.oid=a.owner
join notificationaction na on a.actionoid=na.oid
join notificationrecipients nrs on nrs.owner=na.oid
join notificationindividual nr on nr.oid=nrs.recipientoid
join events es on es.owner=r.oid
join jobeventfilter e on es.eventoid=e.oid
where j.instanceparent is null

union

select j.name as JobName,
0 as StepNumber,
cast(event as varchar(50)) as Event,
'Group' as RecipientType,
nr.name as RecipientName
from job j join response r on j.oid=r.owner
join actions a on r.oid=a.owner
join notificationaction na on a.actionoid=na.oid
join notificationrecipients nrs on nrs.owner=na.oid
join notificationgroup nr on nr.oid=nrs.recipientoid
join events es on es.owner=r.oid
join jobeventfilter e on es.eventoid=e.oid
where j.instanceparent is null

union

select j.name as JobName,
StepNumber,
cast(event as varchar(50)) as Event,
'Individual' as RecipientType,
nr.name as RecipientName
from job j join jobstep js on j.oid=js.owner
join response r on js.oid=r.owner
join actions a on r.oid=a.owner
join notificationaction na on a.actionoid=na.oid
join notificationrecipients nrs on nrs.owner=na.oid
join notificationindividual nr on nr.oid=nrs.recipientoid
join events es on es.owner=r.oid
join jobeventfilter e on es.eventoid=e.oid
where j.instanceparent is null

union

select j.name as JobName,
StepNumber,
cast(event as varchar(50)) as Event,
'Group' as RecipientType,
nr.name as RecipientName
from job j join jobstep js on j.oid=js.owner
join response r on js.oid=r.owner
join actions a on r.oid=a.owner
join notificationaction na on a.actionoid=na.oid
join notificationrecipients nrs on nrs.owner=na.oid
join notificationgroup nr on nr.oid=nrs.recipientoid
join events es on es.owner=r.oid
join jobeventfilter e on es.eventoid=e.oid
where j.instanceparent is null

union 
select j.name as JobName,StepNumber,'Notification Task' as Event,
'Individual' as RecipientType,
nr.name as RecipientName
from job j join jobstep js on j.oid=js.owner
join notificationtask nt on js.task=nt.oid
join notificationrecipients nrs on nrs.owner=nt.oid
join notificationindividual nr on nr.oid=nrs.recipientoid
where j.instanceparent is null

union 
select j.name as JobName,StepNumber,'Notification Task' as Event,
'Group' as RecipientType,
nr.name as RecipientName
from job j join jobstep js on j.oid=js.owner
join notificationtask nt on js.task=nt.oid
join notificationrecipients nrs on nrs.owner=nt.oid
join notificationgroup nr on nr.oid=nrs.recipientoid
where j.instanceparent is null


order by jobname,stepnumber,event,recipientname

K00000384: Diagnosing e-mail notification failures

Wed, 04 May 2011 20:58:40 GMT

Summary

When e-mail notification fails during a job, adTempus logs a message to the Job Log reporting the failure, along with an error message. In some cases this information will be enough to determine the cause of the problem, such as an invalid server address or password.

In some cases, however, the error message may be a generic "Send failed" error message:

SMTP notification to "someone@example.com" failed: Send failed.

In this case, the adTempus diagnostic log will contain more detailed information about the failure.

More Information

To locate the the error information, find the most recent "adtempussrv.*.log" file in the "logs" directory under the adTempus program directory (on the computer where the adTempus service is running). Open this log file in a text editor such as Notepad and search for the string "Send failed: ChilkatLog:". Following this line in the log will be a detailed transcript of the mail session, including more detailed error information.

If you are not able to determine the cause of the problem from the information in the log file, contact us for assistance.

K00000383: Scheduled executions are missed if a Schedule Trigger uses a "wraparound" scheduling scenario

Tue, 12 Apr 2011 17:37:37 GMT

Symptoms

If a schedule is configured using a "wraparound" scenario, where the effective time period for the schedule crosses midnight, adTempus will fail to run jobs during a portion of the schedule period.

Example

A Schedule Trigger is configured to run at a specified interval, with a start time that is later in the day than the end time (for example, between 6:00 am and 4:00 am). The intended behavior is for the job to execute except during the period from 4:00 am to 6:00 am. Instead, adTempus will miss executions from 12:00 am to 4:00 am, and will only execute the job from 6:00 am to 11:59 pm.

Workaround

This scheduling scenario can be accommodated by using two separate schedules on the Schedule Trigger:

The first Schedule is configured to execute the job at the desired interval between 12:00 am and 4:00 am.
The second Schedule is configured to execute the job at the desired interval between 6:00 am and 11:59 pm.

Status

adTempus
This issue has been corrected and the fix will be included in the next maintenance update or software release. Customers affected by the problem may contact us to obtain the fix now.

K00000382: Using a script to interpret a process exit code

Fri, 01 Apr 2011 20:32:29 GMT

Summary

This article describes how to use a script to interpret exit codes from a process run by adTempus.

Background

When you run a process using a Program Execution Task in adTempus, the Success Criteria rules on the Advanced page of the step properties determine how adTempus knows whether the program succeeded. In most cases, you will be able to use one of the simple exit code rules. For example, most programs will return "0" for success and some value greater than 0 for a failure. Some programs may return "0" for success, "4" for a warning, or "8" for an error.

However, some programs may use an exit code scheme that cannot be accommodated by a simple rule. For example, consider a program that has possible exit codes of 1, 2, 3, 23, 45, and 67, with exit codes 23 and 67 indicating success, and all others indicating failure. For such a scheme you can use a simple script to interpret the exit code and tell adTempus whether the program succeeded or failed.

Procedure

On the Advanced page of the step properties, select the "Use a script" option in the Success Criteria section. Click Select... then New... to create a new script.

Make sure that "VB.NET" is selected as the script Language, then replace the default script code with the following:

Imports System
Imports System.Collections
Imports ArcanaDevelopment.adTempus.Server

Public Class UserScript
    Inherits ArcanaDevelopment.adTempus.ScriptEngine.UserScriptBase

    Public Overrides Function Run() As Object
    'The ProcessExitCode variable contains the exit code from the program that was just run
    'The script must examine the exit code and return a True value if the step should be reported as successful
    'or False if it should be reported as failed.
		Select Case CInt(adTempus.JobVariables("ProcessExitCode"))
			Case 23,67
				Return True
			Case Else
				Return False
        End Select
    End Function
End Class

Modify the "Case" line as necessary to specify the exit codes that represent successful execution (in this example, 23 and 67). Note that all

After adTempus runs the program, it stores the program's exit code in a Job Variable named ProcessExitCode and then runs the script.

The script retrieves the ProcessExitCode variable and returns a result based on its value. The script returns True if the exit code represents success, or False if it represents failure. In this example, the script returns True (success) for exit codes 23 and 67, and False (failure) for anything else.

Based on the result of the script, adTempus reports the step as either successful or failed.

K00000381: Using a script to control a service on a remote computer

Thu, 24 Mar 2011 21:37:17 GMT

Summary

The Service Control Task in adTempus allows you to start or stop a service running on the same computer as adTempus, but does not allow you to control a service on a remote computer.

Using a script it is possible to control a service on a remote computer.

Procedure

You will first create a Script Library that contains supporting code.You will then create jobs that runs the script code.

Create the Script Library

1. In the adTempus Console, expand the Scripts folder, then right-click Script Libraries and choose New Script Library....

2. In the Script Library Properties window:

a. Name the library "ServiceControl"

b. Select "VB.NET" for the Language

c. In the Referenced Assemblies section, click the Add... button. In the Add Assembly Reference window select "System.ServiceProcess.dll" and click OK.

d. Erase the default script code and paste in the following code:

Imports System.Collections.Generic 
Imports System 
Imports ArcanaDevelopment.adTempus.Server
Imports System.ServiceProcess

'Contains methods for controlling Windows services. See www.arcanadev.com/support/kb/K00000381.aspx for more information

Public Module ServiceControl
    Public Function StartService(serviceName As String,Optional computerName As String="") As Boolean 
		Try
			Dim controller As ServiceController
			
			controller=GetService(serviceName,computerName)
			If ServiceControllerStatus.Running=controller.Status Then
				adTempus.LogMessage(MessageTypeEnum.Informational,0,"Service " & ServiceDescription(serviceName,computerName) & " was already running")
			Else
				controller.Start()
				adTempus.LogMessage(MessageTypeEnum.Informational,0,"Started service " & ServiceDescription(serviceName,computerName))
			End If
			Return True
		Catch ex As Exception
			adTempus.LogMessage(MessageTypeEnum.Error,0,"An error occurred while starting service " & ServiceDescription(serviceName,computerName) & ": " & ex.Message)
			Return False
		End Try
    End Function

    Public Function StopService(serviceName As String,Optional computerName As String="") As Boolean 
		Try
			Dim controller As ServiceController
			
			controller=GetService(serviceName,computerName)
			If ServiceControllerStatus.Stopped=controller.Status Then
				adTempus.LogMessage(MessageTypeEnum.Informational,0,"Service " & ServiceDescription(serviceName,computerName) & " was already stopped")
			Else
				controller.Stop()
				adTempus.LogMessage(MessageTypeEnum.Informational,0,"Stopped service " & ServiceDescription(serviceName,computerName))
			End If
			Return True
		Catch ex As Exception
			adTempus.LogMessage(MessageTypeEnum.Error,0,"An error occurred while stopping service " & ServiceDescription(serviceName,computerName) & ": " & ex.Message)
			Return False
		End Try
    End Function

	Private Function GetService(serviceName As String,computerName As String) As ServiceController
		Dim controller As New ServiceController(serviceName)
		If Not String.IsNullOrEmpty(computerName) Then
			controller.MachineName=computerName
		End If
		Return controller
	End Function

	Private Function ServiceDescription(serviceName As String,computerName As String) As String
		If String.IsNullOrEmpty(computerName) Then
			Return """" & serviceName & """"
		Else
			Return """" & serviceName & """ on computer """ & computerName & """"
		End If
	End Function

End Module

e. Click OK to save the Script Library.

Start a Service from a Script

Once the Script Library has been created you can call the StartService method from an adTempus script to start a service.

To use the code defined in the Script Library:

1. Create a new job, or edit an existing job.

2. On the Steps page of the Job Properties, add a new step, selecting the "Execute a script" option in the Select Task window.

3. In the Script Execution Task Properties window, select the "Execute a script stored in adTempus" option, then click the Select... button.

4. In the Select Script window, click New... to create a new script.

5. In the Script Properties window, select "VB.NET" as the script Language.

6. Under Included Script Libraries, check the "ServiceControl" library.

7. To start service serviceName on remote computer computerName, use the following code:

Imports System
Imports System.Collections
Imports ArcanaDevelopment.adTempus.Server

Public Class UserScript
    Inherits ArcanaDevelopment.adTempus.ScriptEngine.UserScriptBase

    Public Overrides Function Run() As Object
        If StartService("serviceName","computerName") Then
                Return 0
        Else
                Return 8
        End If
    End Function
End Class

Stop a Service from a Script

Once the Script Library has been created you can call the StopService method from an adTempus script to stop a service.

To use the code defined in the Script Library:

1. Create a new job, or edit an existing job.

2. On the Steps page of the Job Properties, add a new step, selecting the "Execute a script" option in the Select Task window.

3. In the Script Execution Task Properties window, select the "Execute a script stored in adTempus" option, then click the Select... button.

4. In the Select Script window, click New... to create a new script.

5. In the Script Properties window, select "VB.NET" as the script Language.

6. Under Included Script Libraries, check the "ServiceControl" library.

7. To stop service serviceName on remote computer computerName, use the following code:

Imports System
Imports System.Collections
Imports ArcanaDevelopment.adTempus.Server

Public Class UserScript
    Inherits ArcanaDevelopment.adTempus.ScriptEngine.UserScriptBase

    Public Overrides Function Run() As Object
        If StopService("serviceName","computerName") Then
                Return 0
        Else
                Return 8
        End If
    End Function
End Class

Notes

The adTempus job must be run under the User Account of a user who has permission to control the specified service.

The script will not try to start a service that is already running, or stop a service that is already stopped.

The script will log an informational message in the job log if the service is successfully started or stopped, or an error message if an error occurs. If an error occurs, the script will also cause the step to fail.

The serviceName required by the scripts above is the internal service name for the service, which is not always the same as the display name shown in the Services tool in Windows. To find the internal name, run the Registry Editor and go to key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services. Under this key, locate the key for the service you want to control. The serviceName is the key name. For example, the "Automatic Updates" service can be found under key "wuauserv". If you were controlling this service, you would use "wuauserv" as the serviceName in the script.

adTempus Knowledge Base

K00000213: All programs fail to run with error "A required privilege is not held by the client" when adTempus service set to run under user account

Symptoms

Cause

Resolution

K00000397: Granting adTempus access to a remote database when running under the Local System account

Summary

Background

Configuring SQL Server

K00000309: Error when saving Script or ScriptLibrary on 64-bit platforms

Symptoms

Cause

Workaround

Status

K00000366: adTempus reports database errors after server hosting database is renamed

Symptoms

Cause

Resolution

K00000395: SQL Server Express frequently logs message 17137 ("Starting up database")

Symptoms

Cause

Resolution

K00000393: E-mail notification fails when trying to use a mail server that requires SSL or TLS

Symptoms

Cause

Status

K00000392: Selecting a job in the adTempus Console results in error message "Arithmetic operation resulted in an overflow"

Symptoms

Cause

Status

K00000391: Recipients of notification messages cannot determine who else received the message

Symptoms

Cause

Status

K00000390: Using .NET Framework version 4.0 for scripts

Summary

More Information

K00000288: Configuring the automatic database backup

Summary

More Information

See Also

K00000388: Predefined Job Variables variables for adTempus 3.x

Summary

More Information

K00000376: Web Request task and SQL Server Job task fail with error "The task could not be executed because a required software component is not installed on this computer"

Symptoms

Cause

Resolution

K00000387: Allowing remote access to the adTempus SQL Server Express database

Summary

More Information

Designating System Administrators

K00000385: How to query the adTempus database

Summary

More Information

Standalone SQL Server Instance

SQL Server Express

K00000354: "Cannot connect to database" error when running adTempus reports from Console

Symptoms

Cause

Resolution

Allow Remote Access to SQL Server Express

Grant Read Permission to Affected Users

K00000386: Querying the adTempus database to obtain a list of notification recipients for each job

Summary

More Information

K00000384: Diagnosing e-mail notification failures

Summary

More Information

K00000383: Scheduled executions are missed if a Schedule Trigger uses a "wraparound" scheduling scenario

Symptoms

Example

Workaround

Status

K00000382: Using a script to interpret a process exit code

Summary

Background

Procedure

K00000381: Using a script to control a service on a remote computer

Summary