Thursday, March 29, 2012

cannot rename instance of analysis server.missing reg key

when i use the rename instance tool i get this error saying it cannot find the regestry key

hkey_local_Machine\wow6432Node\Microsoft\Microsoft Sql Server\90

When i look for this key, it doesnt exist. My installation went perfectly. what is going wrong

There are 2 versions of ASInstanceRename utility. Make sure you use one that is installed with 64bit version of Analysis Server.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||but i am using the 32 bit version of sql server 2005, and its on a 32 bit pc. theres no way i can install the 64 bit version as my machine wont even run the setup file|||

You should use 64 bit version of asinstancerename utility on 64 bit machine to rename 32bit instances. It is intended to be able to handle 32bit instances.

To get 64bit version of asinstancerename, uninstall 32bit version SQL Tools from your machine and install them back using 64ibt CD.

That should get you going.

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

Cannot remove table from Publication

I am trying to remove a table from a Publication because I want to modify it.
I am going to the Articles tab in the Publication Properties dialog.
However, the checkbox is disabled, probably because the snapshot has run.
How can I modify the table or remove it from the Publication so that it can
be modified?
Environment:
Win2k3
Sql Server 2000
Merge Replication with ce devices
try sp_dropmergearticle
"Thirsh" <Thirsh@.discussions.microsoft.com> wrote in message
news:32274340-B26D-4534-A2F3-FBF6A9B49989@.microsoft.com...
>I am trying to remove a table from a Publication because I want to modify
>it.
> I am going to the Articles tab in the Publication Properties dialog.
> However, the checkbox is disabled, probably because the snapshot has run.
> How can I modify the table or remove it from the Publication so that it
> can
> be modified?
> Environment:
> Win2k3
> Sql Server 2000
> Merge Replication with ce devices
|||I gave it a try. Here's the result from the query analyzer:
Cannot drop article 'AppRoles' from publication 'TB_Tracker' because its
snapshot has been run and this publication could have active subscriptions.
"Hilary Cotter" wrote:

> try sp_dropmergearticle
> "Thirsh" <Thirsh@.discussions.microsoft.com> wrote in message
> news:32274340-B26D-4534-A2F3-FBF6A9B49989@.microsoft.com...
>
>

cannot remove subscription from subscriber!

after deleting a publication from the publisher (which gave a message that
it would also delete all subscriptions to it) the subscription remains on
the subscriber. There is no reference to it on the publisher anymore. It
also looks strange on the subscriber, for example the name format listed in
the subscriptions container on the subscriber was something like
serverName:DatabaseName:PublicationName, and is now only
ServerName:DatabaseName, no publication name. I should also note the name of
the sql server alias used to register it with enterprise manager was change
from that of what it was during the original setup of this replication (was
snapshot, by the way). This was a fix I found for an earlier problem when
trying to setup a new merge replication topology... the alias had to be
changed to match the actual server netbios name. I believe I deleted the
publication from the publisher AFTER I edited the subscriber server's alias
name. Could this have something to do with it?
other info: I cannot delete the tables (articles) from the subscriber
because it thinks its still part of the replication (that was deleted). I
also cannot create the new merge replication, or at least I can create it
but it fails since I need to use the same tables which it thinks are
unavailable due to the previously deleted replication scheme.
any guidance is greatly appreciated. I'm in quite the bind here.
thanks.
answered in the post marked urgent problem
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"djc" <dcopenhaver@.megapathdsl.net> wrote in message
news:%23GZNEuaUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> after deleting a publication from the publisher (which gave a message that
> it would also delete all subscriptions to it) the subscription remains on
> the subscriber. There is no reference to it on the publisher anymore. It
> also looks strange on the subscriber, for example the name format listed
in
> the subscriptions container on the subscriber was something like
> serverName:DatabaseName:PublicationName, and is now only
> ServerName:DatabaseName, no publication name. I should also note the name
of
> the sql server alias used to register it with enterprise manager was
change
> from that of what it was during the original setup of this replication
(was
> snapshot, by the way). This was a fix I found for an earlier problem when
> trying to setup a new merge replication topology... the alias had to be
> changed to match the actual server netbios name. I believe I deleted the
> publication from the publisher AFTER I edited the subscriber server's
alias
> name. Could this have something to do with it?
> other info: I cannot delete the tables (articles) from the subscriber
> because it thinks its still part of the replication (that was deleted). I
> also cannot create the new merge replication, or at least I can create it
> but it fails since I need to use the same tables which it thinks are
> unavailable due to the previously deleted replication scheme.
> any guidance is greatly appreciated. I'm in quite the bind here.
> thanks.
>
|||Running sp_removedbreplication can be used to remove all(ish) traces of
replication in the subscriber database, but obviously must only be done if
this database is not also configured as a publisher. There is also a stored
procedure to tell SQL Server a table is no longer involved in replication
that might be useful: sp_MSunmarkreplinfo which takes the tablename as a
parameter.
Regards,
Paul Ibison
|||thank you! i'll check it out.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:uNDdsubUEHA.1764@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> answered in the post marked urgent problem
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "djc" <dcopenhaver@.megapathdsl.net> wrote in message
> news:%23GZNEuaUEHA.1012@.TK2MSFTNGP09.phx.gbl...
that[vbcol=seagreen]
on[vbcol=seagreen]
> in
name[vbcol=seagreen]
> of
> change
> (was
when[vbcol=seagreen]
> alias
I[vbcol=seagreen]
it
>
|||great. thank you.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23TQbhNeUEHA.1012@.TK2MSFTNGP09.phx.gbl...
> Running sp_removedbreplication can be used to remove all(ish) traces of
> replication in the subscriber database, but obviously must only be done if
> this database is not also configured as a publisher. There is also a
stored
> procedure to tell SQL Server a table is no longer involved in replication
> that might be useful: sp_MSunmarkreplinfo which takes the tablename as a
> parameter.
> Regards,
> Paul Ibison
>
sql

Cannot Remove SQL 2005 June CTP

I have SQL 2005 June CTP installed and running. I previously had VS 2005 CTP installed as well. I removed VS with the beta removal tool and installed the release version. I am now trying to remove SQL and cannot do it.

First I tried Add / Remove programs. I chose remove for SQL 2005 and it removed the entry from Add / Remove programs but did nothing else. I then tried the beta removal tool sqlbuw.exe on the CD which detectes 3 instances of SQL 2005 but when it tries to remove them it says "There are no SQL Server 2005 or .NET Framework components to uninstall. You may now run the setup wizard to install new instances."

When I run the setup wizard it says i must uninstall the previous incompatible beta versions first.

Talk about catch 22. Are there instructions for manually removing SQL 2005 June CTP?

Thanks
MartinMartin,

It sounds like you got yourself into trouble by removing VS prior to SQL Server. The SQL Server uninstall requires that .Net Framework 2.0 still be present on the machine. The reason for this is some assemblies are placed in the GAC (Global Assembly Cache) and the only way to clean up the GAC is through the .Net Framework.

We have an uninstall script that I can send you. You should know that this script is not supported and is not tested to a full release level. We've been using it internally and I've given it out to some folks - we've had no reports of the script causing any machine corruption, however, this is a run at your own risk deal. If you're interested in the script email me at dan.jones@.microsoft.com.

Cheers,
Dan|||Unfortuantly the script did not work and a rebuild was required. At least my computer is faster now :o)

Martin

Cannot remove replication

Hi,
I have a box running SQL 7 with replication. I restored one of the
replicated database to another SQL 7 with no replication. A developer needed
to test an upgrade of an application (MS Great Plains) using that database.
The application states that the tables are part of a replication. As far as I
know, when you restore a replicated DB to another server (with no
replication), the replication infomation is lost. I have also ran
sp_removedbreplication successfully but we still have the same problem.
Any ideas?
--
--
I saw it work in a cartoon once so I am pretty sure I can do it.The tables in question are still marked for replication.
I think you may need to manually update some of the system tables to remove
the marking for replication on the object.
I don't have my poster here at the office, so i couldn't tell you which
tables specically to look at.
I would guess sysobjects.xtype....
Rick Sawtell
MCT, MCSD, MCDBA
"Sasan Saidi" <SasanSaidi@.discussions.microsoft.com> wrote in message
news:260846C9-A09A-415A-8028-715D66021376@.microsoft.com...
> Hi,
> I have a box running SQL 7 with replication. I restored one of the
> replicated database to another SQL 7 with no replication. A developer
needed
> to test an upgrade of an application (MS Great Plains) using that
database.
> The application states that the tables are part of a replication. As far
as I
> know, when you restore a replicated DB to another server (with no
> replication), the replication infomation is lost. I have also ran
> sp_removedbreplication successfully but we still have the same problem.
> Any ideas?
> --
> --
> I saw it work in a cartoon once so I am pretty sure I can do it.|||I don't have a SQL 7.0 box at work anymore, but if it
also exists on SQL 7.0, please try using
sp_MSunmarkreplinfo which takes a tablename as a parameter
HTH,
Paul Ibison (SQL Server MVP)
>> (recommended sql server 2000 replication book:
>> http://www.nwsu.com/0974973602p.html)|||Before updatnig system tables, I would recommend making sure you've dropped
the distributor and publisher. In EM from Tools...Replication...configure
publishing subscribers and distributors. Make sure there are no selections
(uncheck all boxes).
Colleen
"Paul Ibison" wrote:
> I don't have a SQL 7.0 box at work anymore, but if it
> also exists on SQL 7.0, please try using
> sp_MSunmarkreplinfo which takes a tablename as a parameter
> HTH,
> Paul Ibison (SQL Server MVP)
> >> (recommended sql server 2000 replication book:
> >> http://www.nwsu.com/0974973602p.html)
>
>

Cannot remove replication

Hi,
I have a box running SQL 7 with replication. I restored one of the
replicated database to another SQL 7 with no replication. A developer needed
to test an upgrade of an application (MS Great Plains) using that database.
The application states that the tables are part of a replication. As far as
I
know, when you restore a replicated DB to another server (with no
replication), the replication infomation is lost. I have also ran
sp_removedbreplication successfully but we still have the same problem.
Any ideas?
--
I saw it work in a cartoon once so I am pretty sure I can do it.The tables in question are still marked for replication.
I think you may need to manually update some of the system tables to remove
the marking for replication on the object.
I don't have my poster here at the office, so i couldn't tell you which
tables specically to look at.
I would guess sysobjects.xtype....
Rick Sawtell
MCT, MCSD, MCDBA
"Sasan Saidi" <SasanSaidi@.discussions.microsoft.com> wrote in message
news:260846C9-A09A-415A-8028-715D66021376@.microsoft.com...
> Hi,
> I have a box running SQL 7 with replication. I restored one of the
> replicated database to another SQL 7 with no replication. A developer
needed
> to test an upgrade of an application (MS Great Plains) using that
database.
> The application states that the tables are part of a replication. As far
as I
> know, when you restore a replicated DB to another server (with no
> replication), the replication infomation is lost. I have also ran
> sp_removedbreplication successfully but we still have the same problem.
> Any ideas?
> --
> --
> I saw it work in a cartoon once so I am pretty sure I can do it.

Cannot remove replication

I don't have a SQL 7.0 box at work anymore, but if it
also exists on SQL 7.0, please try using
sp_MSunmarkreplinfo which takes a tablename as a parameter
HTH,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]Before updatnig system tables, I would recommend making sure you've dropped
the distributor and publisher. In EM from Tools...Replication...configure
publishing subscribers and distributors. Make sure there are no selections
(uncheck all boxes).
Colleen
"Paul Ibison" wrote:

> I don't have a SQL 7.0 box at work anymore, but if it
> also exists on SQL 7.0, please try using
> sp_MSunmarkreplinfo which takes a tablename as a parameter
> HTH,
> Paul Ibison (SQL Server MVP)
>
>
>