Migrating SSRS ReportsServices from SQL 2005 to 2008

By -
In the process of consolidating two servers, a task emerged to move a 2005 SQL backend and its SSRS instance to a box running SQL Server 2008.

At first I considered installing SQL side by side to avoid any upgrade issues. But as it turned out, installing SSRS was quite straight forward but getting IIS to serve the virtual directory was not. After several attempts I kept getting a WMI error and errors regarding failure to load assemblies, this was due to a clash between the 32bit and new 64bit environment.

After a few hours it became obvious it would be much simpler to simply migrate the actual reports across to SSRS 2008. So to that end I performed the following steps. Fortunately it didn't turn out to be too much work thanks to Reporting Services Scripter.

But this tool was designed to migrate between two 2005 servers and a newer platform so that script didn't work straight away.
 I opened the generated ‘RS Scripter Load All Items.cmd’ and set the RS variable so it referenced the 100 hive and set the url of the local report server, as shown in the following lines:

SET REPORTSERVER=http://localhost/ReportServer
SET RS=”C:\Program Files (x86)\Microsoft SQL Server\100\Tools\binn\rs.exe”

I still had issues with data sources, I found the best way to resolve this was to reconfigure the data sources through the report manager.  Use the report manager, open each report manually and modify its datasource property and point to a new shared datasource. This allowed my reports to access the database.

Comments

Post a Comment

Popular posts from this blog

WinDBG on 32Bit Applications

By -
On a 64-bit Windows installation is it possible to make both 32-bit and 64-bit dumps of 32-bit processes. The task manager will create a 64-bit dump, which therefore is often what you end up with users sending you. This is not a problem for native executeables since you can still load it in windbg and use the !wow64exts.sw extension to switch into the 32-bit view. However if your process is a .NET process and you want to use SoS to investigate it then you are out of luck, you'll just get the message "SOS does not support the current target architecture." This extension gets around this by hooking/patching functions in dbgeng.dll so that SoS thinks it's working with a 32-bit dump. ** Usage ** Copy soswow64.dll into the "winxp" subfolder of windbg. Then after loading a 64-bit memory dump of a 32-bit process you can simply load the extension: 0:000> .load soswow64 Successfully hooked IDebugControl::GetExecutingProcessorType. Successfully patched DbgEng!X...
Read more

EXCEL Macro - Compare Column A to Column B

By -
Recently a friend asked me to fix a macro that she was working on to compare two columns in Excel and if the cell in Column A did not exist in any cell of Column B, then add it to Column C. You can make check both columns for miss matches by copy/pasting Column B to Column A and vice versa to check both lists and maybe someone will find it handy =) Sub Subset() Dim Acell As Range 'Acell is a range of 1 or more cells Dim Bcell As Range 'Bcell is a range of 1 or more cells Dim Ccell As Range 'Ccell is a range of 1 or more cells Dim Index As Integer 'Index is the current row we are saving to in the Ccell Index = 1 'Start the Index at 1 Dim found As Boolean    'Remove the hidden space 160    Range("A1:A1000").Replace What:=Chr(160), Replacement:="", LookAt:=xlPart    Range("B1:B1000").Replace What:=Chr(160), Replacement:="", LookAt:=xlPart    For Each Acell In Range("A1:A1000")     Acell...
Read more

Powershell Script to Automatically Deploy Sharepoint WSP Packages

By -
Recently I wanted to automate the retraction, removal and deployment of WSP packages in a folder. So I wrote this powershell script. NOTE: There is a bug in the script that returns a false positive. The property $solution.Deployed returns true even though the object is not finished deploying or is locked! I will update this code or if you do then please send your updated code and I will update my post. $packages = (dir *.wsp | Select-Object name) $currentDir = (Get-Location).Path Add-PSSnapin Microsoft.Sharepoint.PowerShell -ErrorAction "SilentlyContinue" Write-Host "Started package installation" foreach ($i in $packages) { Write-Host "Retracting: " + $i $solution = (Get-SPSolution | where-object {$_.Name -eq $i.Name}) Write-Host $solution.Name if ($solution -ne $null) { Write-Host "Solution Found..." if ($solution.Deployed -eq $true) { Write-Host "Uninstalling..." Uninstall-SPSolution -Identity ...
Read more