Well - At least I'm getting more information on the failed task (though it is still failing).
After installing the new version, I created a new job that runs a "test" SSIS package. The package contains one database connection (named "Lawson") and a SQL task that performs a record count on a single table.
The VisualCron job is using the same credential that is required by the database connection within the SSIS package. This credential consists of a domain user ID and password.
Here is the error I am getting when the VC task fails:
The SSIS Execution failed
Number of warnings: 1
Warning (0):SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
Number of errors: 2
Error (0):SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.".
Error (1):Failed to acquire connection "LAWSON". Connection may not be configured correctly or you may not have the right permissions on this connection.
From, GetErrorValues (0)
Exception in Task: Non zero exit code
Exception in Task: Based on the error, it seems like VisualCron is not passing the credential to the SSIS package.
Edited by user
2010-04-07T15:14:34Z
|
Reason: Not specified