pull subscription, subscriber configuration

Hi,
I was trying a pull subscription and I got all kinds of error messages
all suggesting that the merge agent isn't being run or it isn't
accessible. But, the moment I did a push subscription, it ran and
replication happened without an error message. I don't understand why.
My subscriber is an ordinary windows 2000 OS and is not of a server
configuration. Could that be a reason, since, in a pull subscription,
the agent is supposed to run on the subscriber(which isn't a server)?
Any suggestions or thoughts are welcome!
Also, is there a way a subscriber can tell the publisher to push a
subscription?
Thanks,
PS.
By definition a pull subscriber "pulls" the subscription on its own schedule - it doesn't tell the publisher push now.
Its hard to figure out exactly what the error is from your description. Please provide the complete error messages you are getting.
In general when you have pull subscription problems.
1) check that the SQL Server agent account has rights to read the snapshot share and the underlying path on the publisher, likely to be \\publisherName\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\unc
2) check on your publisher that you have enabled your subscriber to impersonate the Server agent account on the Publisher. Go to Tools, point to replication, click configure publishers, subscribers, and distributors, click on the browse button to the righ
t of your subscriber and select the impersonate option.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ps" wrote:

> Hi,
> I was trying a pull subscription and I got all kinds of error messages
> all suggesting that the merge agent isn't being run or it isn't
> accessible. But, the moment I did a push subscription, it ran and
> replication happened without an error message. I don't understand why.
> My subscriber is an ordinary windows 2000 OS and is not of a server
> configuration. Could that be a reason, since, in a pull subscription,
> the agent is supposed to run on the subscriber(which isn't a server)?
> Any suggestions or thoughts are welcome!
> Also, is there a way a subscriber can tell the publisher to push a
> subscription?
> Thanks,
> PS.
>

Publisher configuration problem

I am trying to configure a MS SQL Server 2000 named \\MSSQL_NEW as a
publisher but I keep getting this
error:
SQL Server Enterprise Manager can not configure 'MSSQL_NEW' as the
distributor for 'MSSQL_NEW'
Error 18483:
Could not connect to server 'MSSQL_NEW' because 'distributor_admin' is not
defined as a remote login at
the server.
I've verified that 'distributor_admin' exists and has sysadmin rights on the
server (MSSQL_NEW).
I noticed that when I execute, 'select @.@.servername', in QA, I get,
'MSSQL_OLD'. But my machine name is, 'MSSQL_NEW'
and name registered in EM is 'MSSQL_NEW'. Tried replacing the registration
'MSSQL_NEW' to 'MSSQL_OLD' but I get a
server does not exist or access denied error.
Will updating @.@.servername to 'MSSQL_NEW' solve my problem? How?
Any comments or suggestions will be highly appreciated. Thanks in advance.
...
Carlo,
please try this...
Use Master
go
Sp_DropServer 'MSSQL_OLD'
GO
Use Master
go
Sp_Addserver 'MSSQL_NEW', 'local'
GO
Stop and Start SQL Services
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||This is a tricky problem to solve.
I normally solve it by issuing a
sp_adddistributor and an sp_adddistributiondb procs.
These should work. Then when you go to replicate it will bomb. So disable
replication, and then re-enable it. It should work this time.
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
"CarloVino" <CarloVino@.discussions.microsoft.com> wrote in message
news:77815079-C1A6-477C-9794-391828479E38@.microsoft.com...
> I am trying to configure a MS SQL Server 2000 named \\MSSQL_NEW as a
> publisher but I keep getting this
> error:
> SQL Server Enterprise Manager can not configure 'MSSQL_NEW' as the
> distributor for 'MSSQL_NEW'
> Error 18483:
> Could not connect to server 'MSSQL_NEW' because 'distributor_admin' is not
> defined as a remote login at
> the server.
> I've verified that 'distributor_admin' exists and has sysadmin rights on
the
> server (MSSQL_NEW).
> I noticed that when I execute, 'select @.@.servername', in QA, I get,
> 'MSSQL_OLD'. But my machine name is, 'MSSQL_NEW'
> and name registered in EM is 'MSSQL_NEW'. Tried replacing the
registration
> 'MSSQL_NEW' to 'MSSQL_OLD' but I get a
> server does not exist or access denied error.
> Will updating @.@.servername to 'MSSQL_NEW' solve my problem? How?
> Any comments or suggestions will be highly appreciated. Thanks in
advance.
> --
> ...

Publication Configuration Error

Hey Everyone,

I am trying to setup publishing on SQL Server 2000 Enterprise. I will be subscribing from a SQL Mobile 2005 database so I have installed the SQL Server 2000 SP3a Replication Components, .NET Framework 2.0, and the SQL Server 2005 Mobile Edition Server Tools.

I was able to go through the 2005 Mobile Web Synchronization Wizard with no problems. However, when I try to run the Configure Publishing and Distribution Wizard, I get the following message at the end:

SQL Server Enterprise Manager could not configure 'GISSERV' as the Distributor for 'GISSERV'
Error 14114: '(null)' is not configured as a Distributor.

The first option I choose is Make 'GISSERV' it's own Distributor. Then, I select the snapshot folder that I shared. And on the third screen, I've tried going with the standard default settings and customizing those settings.

Has anyone else come across this error? Is there anyone else out there replicating from SQL Server 2000 to SQL Server 2005 Mobile?

Thanks in advance,

Lee

Is this merge replication? If so, this configuration is not supported, you cannot have a SQL 2005 subscriber with a SQL 2000 publisher/distributor.

http://msdn2.microsoft.com/ms143241(en-US,SQL.90).aspx

|||

Thanks for the link. I'm going to have to find another way of doing this. I was led to believe that it was possible by this article:

http://www.microsoft.com/sql/editions/sqlmobile/connectivity-tools.mspx

But regardless of what my subscriber is running, I still should not be getting this error, should I?

Thanks,

Lee

|||hold on, i wasn't paying attention when you said SQL Server Mobile 2005. Let me double-check.|||

Yes, SQL 2005 Mobile is supported for a SQL 2000 publisher/distributor, I was incorrect.

Regarding the error message, have you renamed your machine along the way, or restored master database from a backup of another machine? Regardless, here's the KB article that most like fixes the situation:

http://support.microsoft.com/default.aspx?scid=kb;en-us;302223