Closed cbonezzi closed 5 years ago
By seeing your config file on an administrative share, I think that your agent account is not authorized to access that file. Try copying it in one of the build/release well-known folders like Build.ArtifactStagingDirectory and then point to it's path.
Thanks mmajcica! I moved that configuration file to the Build.ArtifactStagingDirectory, pointed the definition to it, and it worked like a charm.
Here is my configuration for the task. All I get when I execute the release is ##[Error]Access is denied. Any help/ideas would be greatly appreciated. Thanks in advance.![image](https://user-images.githubusercontent.com/8673768/51010706-1446df00-151b-11e9-8440-b0687bb7ceb6.png)
Here is the error I get on the logs 2019-01-11T02:45:39.8351702Z ============================================================================== 2019-01-11T02:45:39.8351702Z Task : Deploy MS SQL SSRS Reports 2019-01-11T02:45:39.8351702Z Description : Deploy items on MS SQL SSRS server based on a configuration file. 2019-01-11T02:45:39.8351702Z Version : 3.1.3 2019-01-11T02:45:39.8351702Z Author : Mario Majcica 2019-01-11T02:45:39.8351702Z Help : 2019-01-11T02:45:39.8351702Z ============================================================================== 2019-01-11T02:45:45.8508839Z ##[error]Access is denied 2019-01-11T02:45:45.8665094Z ##[section]Finishing: Deploy reports 2019-01-11T02:45:45.8821200Z ##[section]Finishing: Release
Here is my configuration file
SSRS destination folder![image](https://user-images.githubusercontent.com/8673768/51010944-1493aa00-151c-11e9-89c3-85462c2c2914.png)
A few more pieces of information. The configuration file lives in the destination server where reports will be deployed to. I am not sure if this could be causing the problem.
Error from SSRS Log library!ReportServer_0-8!1be8!01/10/2019-21:16:50:: i INFO: Call to GetItemTypeAction(wsdl/ReportService2010.asmx). User: UPEXCHANGE-DEV\SSRSUser. library!ReportServer_0-8!1be8!01/10/2019-21:16:50:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: , Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item 'wsdl/ReportService2010.asmx' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash.; library!WindowsService_44!1fa0!01/10/2019-21:23:52:: i INFO: Call to CleanBatch() library!WindowsService_44!1fa0!01/10/2019-21:23:52:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams, 0 segments, 0 segment mappings, 0 edit sessions. library!WindowsService_44!1fa0!01/10/2019-21:23:52:: i INFO: Call to CleanBatch() ends