Cannot delete merge publication

Hello...
I had a merge publication that I thought was removed...at least it does not
appear in Ent. Mgr under the list of Publications. However, in the
Replication Monitor the publication still exists. When I click on the
publication to delete or check its properties I get the mesage:
SQL Server could not retrieve information about publication 'My_Publication'
Error 21776: [SQL-DMO] The name 'My_Publication' was not found in the
MergePublications collection. If the name is a qualified name...'
I searched for that error code...but could not find anything that would help
me solve this problem.
if anyone has any ideas, it would be appreciated.
thanks
- dw
check sysmergepublications in the publications database. Do you find the
publication there?
If so you will need to delete it and the matching sysmergearticles columns.
Also delete the rows for this publication from
distribution.dbo.MSpublications
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"dw" <dw@.discussions.microsoft.com> wrote in message
news:85F329D5-E863-41A5-8AB3-8BB008C98EC7@.microsoft.com...
> Hello...
> I had a merge publication that I thought was removed...at least it does
not
> appear in Ent. Mgr under the list of Publications. However, in the
> Replication Monitor the publication still exists. When I click on the
> publication to delete or check its properties I get the mesage:
> SQL Server could not retrieve information about publication
'My_Publication'
> Error 21776: [SQL-DMO] The name 'My_Publication' was not found in the
> MergePublications collection. If the name is a qualified name...'
> I searched for that error code...but could not find anything that would
help
> me solve this problem.
> if anyone has any ideas, it would be appreciated.
> thanks
> - dw

Cannot connect to the Report Mgr.

Hi All,
I'm experiencing the error referenced in the following link to MS
Support
http://support.microsoft.com/Default.aspx?kbid=922656
I implemented the workaround but I'm still getting the error. Actually
when I started I was receiving "error message 1" and then when I
updated my RSWebApplication.config file to use the fully qualified URL
using the IP Address that is assigned to the Default Web Site's "IP
Address" property.
My config file now looks like this...
<ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
The server is a Windows 2003 server and the Reporting Services was
installed with SQL2005 but not configured. I was able to configure the
Reports server (from what I can tell) using the "Reporting Services
Configuration" tool).
Any idea as to what may still be causing the problem?
Thanks in advance for any help you can offer.
Mike Gorgone
Senior Software Engineer
PictureU PromotionsOn Aug 21, 2:06 pm, Mike <m_gorg...@.hotmail.com> wrote:
> Hi All,
> I'm experiencing the error referenced in the following link to MS
> Support
> http://support.microsoft.com/Default.aspx?kbid=922656
> I implemented the workaround but I'm still getting the error. Actually
> when I started I was receiving "error message 1" and then when I
> updated my RSWebApplication.config file to use the fully qualified URL
> using the IP Address that is assigned to the Default Web Site's "IP
> Address" property.
> My config file now looks like this...
> <ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
> <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> The server is a Windows 2003 server and the Reporting Services was
> installed with SQL2005 but not configured. I was able to configure the
> Reports server (from what I can tell) using the "Reporting Services
> Configuration" tool).
> Any idea as to what may still be causing the problem?
> Thanks in advance for any help you can offer.
> Mike Gorgone
> Senior Software Engineer
> PictureU Promotions
The last response in this link might be helpful.
http://www.sqlreportingservices.net/Ask/1730.aspx
Regards,
Enrique Martinez
Sr. Software Consultant|||On Aug 21, 9:55 pm, EMartinez <emartinez...@.gmail.com> wrote:
> On Aug 21, 2:06 pm, Mike <m_gorg...@.hotmail.com> wrote:
>
> > Hi All,
> > I'm experiencing the error referenced in the following link to MS
> > Support
> >http://support.microsoft.com/Default.aspx?kbid=922656
> > I implemented the workaround but I'm still getting the error. Actually
> > when I started I was receiving "error message 1" and then when I
> > updated my RSWebApplication.config file to use the fully qualified URL
> > using the IP Address that is assigned to the Default Web Site's "IP
> > Address" property.
> > My config file now looks like this...
> > <ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
> > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > The server is a Windows 2003 server and the Reporting Services was
> > installed with SQL2005 but not configured. I was able to configure the
> > Reports server (from what I can tell) using the "Reporting Services
> > Configuration" tool).
> > Any idea as to what may still be causing the problem?
> > Thanks in advance for any help you can offer.
> > Mike Gorgone
> > Senior Software Engineer
> > PictureU Promotions
> The last response in this link might be helpful.http://www.sqlreportingservices.net/Ask/1730.aspx
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Hi Enrique,
Thanks for the link. I've seen some information along those same lines
but I can't set the IP Address property to "All Addresses" the IP
needs to be set to the specific address we have in there.
Is there any war around that?
Mike

Cannot connect to remote server with enterprise mgr

Hi I am a newbie so I will try to describe my situation below.
I purchased a Server running Windows 2003 and installed SQL 2000 with SP4.
The server is hosted in a co-location building at my ISP. I have terminal
Server access. I have a application that I will use to connect thru the
interent to that server to the database. When I tried to connect using
Enterprise manager using the public Ip i get "invalid connection,
connectionOpen(parse correctparme. What am I not doing correctly?
I can connect once I'm connected thru Terminal server, but not when I try
to connect from my local box.
I had a similar problem occur when I changed hosting companies. At some
point, my firewall closed port 1433 and it needs to be open and allow
traffic. Also, I have to specify the port number with my server. I connect
with the server IP address, <111.333.555.666,1433>. mssql,mydomain.com,1433
works as well. Try that.
This does assume that you are using the default port for SQL Server which is
1433.
Dan
"francis" wrote:

> Hi I am a newbie so I will try to describe my situation below.
> I purchased a Server running Windows 2003 and installed SQL 2000 with SP4.
> The server is hosted in a co-location building at my ISP. I have terminal
> Server access. I have a application that I will use to connect thru the
> interent to that server to the database. When I tried to connect using
> Enterprise manager using the public Ip i get "invalid connection,
> connectionOpen(parse correctparme. What am I not doing correctly?
> I can connect once I'm connected thru Terminal server, but not when I try
> to connect from my local box.

Cannot connect to remote server with enterprise mgr

Hi I am a newbie so I will try to describe my situation below.
I purchased a Server running Windows 2003 and installed SQL 2000 with SP4.
The server is hosted in a co-location building at my ISP. I have terminal
Server access. I have a application that I will use to connect thru the
interent to that server to the database. When I tried to connect using
Enterprise manager using the public Ip i get "invalid connection,
connectionOpen(parse correctparme. What am I not doing correctly?
I can connect once I'm connected thru Terminal server, but not when I try
to connect from my local box.I had a similar problem occur when I changed hosting companies. At some
point, my firewall closed port 1433 and it needs to be open and allow
traffic. Also, I have to specify the port number with my server. I connect
with the server IP address, <111.333.555.666,1433>. mssql,mydomain.com,1433
works as well. Try that.
This does assume that you are using the default port for SQL Server which is
1433.
Dan
"francis" wrote:

> Hi I am a newbie so I will try to describe my situation below.
> I purchased a Server running Windows 2003 and installed SQL 2000 with SP4.
> The server is hosted in a co-location building at my ISP. I have terminal
> Server access. I have a application that I will use to connect thru the
> interent to that server to the database. When I tried to connect using
> Enterprise manager using the public Ip i get "invalid connection,
> connectionOpen(parse correctparme. What am I not doing correctly?
> I can connect once I'm connected thru Terminal server, but not when I try
> to connect from my local box.