October 3, 2007 at 7:04 pm
I have a sql server 2005 machine. .When i am accessing replication folder it says that"Replication component is not installed on this sever.Try to install it".When i am tryin to install it from setup ,i am unable to install repication components.could any one help me out
October 4, 2007 at 7:30 am
What edition of SQL Server 2005 are you running (Enterprise, Standard, Workgroup, Express)?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 11, 2009 at 1:35 pm
I just spent the better part of a day researching this. Here's my scenario and what I fear is the outcome.
- My development server is SQL 2005 Standard Edition with SP2 installed.
- I tried to install the Replication component in the manner that BOL describes it, using the Setup disk. (ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/c50ad078-060b-4a8d-ad45-9e31a8d85729.htm)
- I got an error stating "Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove." This wasn't too much of a surprise since the setup disk was from the RTM release. (I also tried the Add/Remove Program and command line options to no avail.)
- I tried downloading the SP2 install package and installing the Replication component from there. Unfortunately there is no option to do so, nor did it contain the MSI (SQLRun_SQL.msi, I think) required to do it from the command line.
The conclusion that I've come to, as pretty much every other person that I've seen report this problem on various boards, is that you cannot install Replication on a SQL Server 2005 machine that's already had a Service Pack applied. The options seem to be:
1. Uninstall SQL Server and reinstall it with Replication, then apply whichever Service Packs you had previously applied.
2. Install a new instance of SQL Server with Replication included.
I'm also researching this with Microsoft and will update if I hear anything. If you find anything better, please let me know.
Thanks.
Jim
P.S. - A couple of relevant links that summarize my situation pretty well:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=293490
http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SQL-Server-2005/Q_23675614.html
~~ Everything in moderation, including moderation. ~~
March 23, 2009 at 12:59 pm
I think I've found a workaround that might be useful to some of you. After deciding I didn't want to completely uninstall my SQL Server to get replication working, I went ahead and created a second SQL instance on the same machine. After doing so, I was able to go to the Control Panel - Add/Remove Programs and select the option to Change my installation. I was prompted to select which SQL instance to modify and I chose the default MSSQLSERVER instance, the one without Replication Components installed. Somewhat pessimistically, I followed the wizard up to the point where I could choose to add Replication. To my surprise the installation completed without errors.
I was then able to access Replication components, i.e., set up a sample Transactional publication, on my default instance. But.... it still didn't quite work. When the Snapshot Agent ran, I got an error like this, "job cannot be run because the Snapshot subsystem failed to load". A little bit more internet scouring* led me to this code:
use msdb
go
delete from msdb.dbo.syssubsystems
exec msdb.dbo.sp_verify_subsystems 1
go
After running that and restarting SQL Server Agent, voila!, Replication is now working on my default instance. Finally.
The only thing left for me to test is to uninstall the named instance and see if replication is still happy on the default. Can't get to that today, but will update post again if/when I do. At worst, I am stuck with an extraneous instance that I can either leave in a stopped state or put in Draconian lockdown mode.
~~ Everything in moderation, including moderation. ~~
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply