Hi there,

We are having a problem installing Reporting Services to an existing SQL
Server 2005 standard edition installation. The original installation was
pre-SP1, then SP1 was applied. Now when I try to install Reporting Services
there is a warning for the Edition Change Check even though I am installing
from the original media.

I would really prefer to install Reporting Services without having to
uninstall and reinstall SQL Server altogether. Any ideas?

Hello,

I Iunderstand that you are not able to installed RS 2005 properly since
other components were upgraded to SP1. If I'm off-base, please let me know.

Based on my experience, this issue may occur since other components are in
SP1. You need to install RS 2005 SP1 after installing RS 2005, and then try
to configure RS 2005 with "reporting service configuation" tools

If the issue persists, please get the following log files and send it to
me. You could remove "online" from my displayed email address.
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Please compress the log file before sending them.

The SP1 setup log is under c:\windows\hotfix\rs9\

I look forward to your reply. Thanks.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Peter,

Sorry I didn't explain fully. Reporting services will not install. After the
warning comes up, the installation attempts to continue but then errors out.
I will send the logs to you via email.

Thanks.

Hello Geeseman,

From the setup files, the errors occurs when install Backward compatibility
component:

==================================

In Summary:

Machine : ECRIMON2
Product : SQL Server Backward-Compatibility Files
Error : An installation package for the product Microsoft SQL
Server 2005 Backward compatibility cannot be found. Try the installation
again using a valid copy of the installation package 'sqlserver2005_bc.msi'.
----------------------------------------------------------------------------
----
Machine : ECRIMON2
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1704
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0012_ECRIMON2_Backward sCompat_1.log
Last Action : InstallFinalize
Error String : An installation package for the product Microsoft SQL
Server 2005 Backward compatibility cannot be found. Try the installation
again using a valid copy of the installation package
'sqlserver2005_bc.msi'.
Error Number : 1706

in Backwardcompat log:

MSI (s) (1C:84) [11:13:00:264]: Executing op:
ProgressTotal(Total=84992,Type=0,ByteEquivalent=1)
MSI (s) (1C:84) [11:13:00:264]: Executing op:
SetTargetFolder(Folder=C:\Program Files\Microsoft SQL Server\80\Tools\Binn\)
MSI (s) (1C:84) [11:13:00:264]: Executing op:
SetSourceFolder(Folder=1\PFiles\MICROS~1\80\Tools\ Binn\|Program
Files\Microsoft SQL Server\80\Tools\Binn\)
MSI (s) (1C:84) [11:13:00:264]: Executing op:
ChangeMedia(MediaVolumeLabel=SQLServerBC,MediaProm pt=Please insert the
disk:
,MediaCabinet=SqlBC.cab,BytesPerTick=32768,CopierT ype=2,ModuleFileName=1\sql
server2005_bc.msi,,,,,IsFirstPhysicalMedia=1)
MSI (s) (1C:84) [11:13:00:264]: Executing op:
FileCopy(SourceName=semmap.dll,SourceCabKey=semmap .dll.TB.8FA31C88_6E16_4DC6
_AEC7_BB557E7CAB59,DestName=semmap.dll,Attributes= 0,FileSize=52224,PerTick=3
2768,,VerifyMedia=1,,,,,CheckCRC=0,Version=2000.80 .2039.0,Language=1033,Inst
allMode=58982400,,,,,,,)
MSI (s) (1C:84) [11:13:00:264]: File: C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\semmap.dll; To be installed; Won't patch; No existing
file



MSI (s) (1C:84) [11:13:01:420]: Note: 1: 1706 2: 3: sqlserver2005_bc.msi
MSI (s) (1C:84) [11:13:01:420]: SOURCEMGMT: Failed to resolve source
MSI (s) (1C:84) [11:13:20:389]: Product: Microsoft SQL Server 2005 Backward
compatibility -- Error 1706. An installation package for the product
Microsoft SQL Server 2005 Backward compatibility cannot be found. Try the
installation again using a valid copy of the installation package
'sqlserver2005_bc.msi'.

===================================

It seems there are some issues on instlled Backward compatibility
componnet. I suggest that you go to Add/Remove program to remove "SQL
Server 2005 Backward compatibility componnet", and they try to install RS
2005 and SP1 again.

If that works, you could try to install SQL Server 2005 Backward
compatibility componnet again and apply sp1 to the component.


If you encounter other errors, please let me know, and send me the newly
copy of setup log files for reviewing. I look forward to your update. Thank
you.
Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Thanks for the . It appears that the backward compatibility component was
installed from a different source than the rest and it couldn't find the
installation source. I was able to resolve the problem by doing what you
suggested.