search

assasafras / git_tutorial

Tutorial
0 stars 0 forks source link

Job Failed: NZReports - EOM - Monthly 1st (4am) | Step 7 | CommissionReportGenerator #16

Closed assasafras closed 8 years ago

assasafras commented 8 years ago

Message

Executed as user: FLEXIRENT\SysSQLSit. Microsoft (R) SQL Server Execute Package Utility Version 10.0.6000.29 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 8:39:47 a.m.
Error: 2016-10-03 08:39:51.16
Code: 0xC00291CB
Source: Send Mail Task Send Mail Task
Description: Either the file "\SITAKL016V\WebReports\Sales\Sales Budget Reports\Salesperson\Commission Reports\Akaash Sharma\Akaash Sharma- September 2016.html" does not exist or you do not have permissions to access the file. End Error

Error: 2016-10-03 08:39:51.16
Code: 0xC0024107
Source: Send Mail Task
Description: There were errors during task validation. End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 8:39:47 a.m.
Finished: 8:39:51 a.m.
Elapsed: 3.666 seconds. The package execution failed. The step failed.

assasafras commented 8 years ago

Issue 1

User sysSQLSIT has not been granted any permissions for the folder "\SITAKL016V\WebReports\Sales\Sales Budget Reports\Salesperson\Commission Reports\" and it's subfolders.

Solution 1

Granted the following permissions to the user sysSQLSIT to the directory all sub directories of "\SITAKL016V\WebReports\Sales\Sales Budget Reports\Salesperson\Commission Reports":

This task is to be done by Jasper across all environments (for the specific environment's syssql user profile).

assasafras commented 8 years ago

Issue 2

In SIT the reports needed do not exist in SIT Report Server (http://sitakl006v/Reports/Pages/Folder.aspx).

Solution 2

Reports should be deployed to SIT. THIS HAS NOT BEEN DONE IN SIT

assasafras commented 8 years ago

Issue 3

In SIT the report Data Sources needed are not correctly configured on the SIT Report Server (http://sitakl006v/Reports/Pages/Folder.aspx).

Solution 3

Data Sources configured correctly. THIS HAS NOT BEEN DONE IN SIT AS WE DON'T HAVE THE PASSWORD

assasafras commented 8 years ago

Solution

The above issues needed to be resolved. In addition the wrong server connection was being used to get to the reports server (e.g. "http://DEVAKL**016V/..." instead of "http://DEVAKL006V**/...")

THIS WAS TESTED IN DEV ENVIRONMENT