microsoft / microsoft/sql-server-samples
Re-linking data source problem
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 11.2k
- Forks
- 9.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 14
Description
I have used scripts like that (Migrated from SSRS2016 tp SSRS2019:
$SourceServer = "http://OldServer/ReportServer"
$TargetServer = "http://NewServer/ReportServer"
$SourceFolder = "/Prototypes/MS"
$TargetFolder = $SourceFolder
rs.exe -i "C:\RSS\ssrs_migration.rss" -e Mgmt2010 -s $SourceServer -v f=$SourceFolder -v ts=$TargetServer -v tf=$TargetFolder
I get message error:
Re-linking data source for item Payment report ... SUCCESS
Re-linking references for item Payment report ... FAILURE:
The item '/Prototypes/MSFinance/SQL_PEPCO_Connector_DAX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/Prototypes/MSFinance/SQL_PEPC
O_Connector_DAX' cannot be found.
Migrating parameters for report Payment liabilities report ... SUCCESS
Migrating subscriptions for report Payment liabilities report: 2 items found.
Migrating subscription sub2_disable ... FAILURE:
The report server cannot process the report or shared dataset. The shared data source 'SQL_PEPCO_Connector_DAX' for the report server is not valid.
The problem Is that my report is in path /Prototypes/MS
but my DataSource is in Finance/SQL_PEPCO_Connector_DAX
and script generate wrong path to the DataSource
'/Prototypes/MSFinance/SQL_PEPCO_Connector_DAX'

Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ssrs_migration.rss script invoked by rs.exe and trace how the report path /Prototypes/MS is combined with the Finance data-source path. Reproduce the migration using the OldServer and NewServer example, then verify that the generated reference points to the data source without merging the folder names and that re-linking and subscription migration succeed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100