Error Pull replication

I have two Win2000 that are in a domain. SQL1(SQL server) acts as the
distributor and publisher. SQL2(MSDE2000) acts as the subscriber. Push merge
replication is running well.
I want to PULL the db from SQL1 to the db on SQL2, failed :The process could
not connect to Distributor. Cannot generate SSPI context.
I changed Merge Agent location from Subsciber to Distributor, message :
Server 'SQLTEST1" is not prepared to run the offloaded agent
Error Unable to activate the agent on the specified remote server because of
security restrictions. Use dcomcnfg on the remote server to allow the local
SQL Server Agent account to activate the agent
1. Where the best location for the Merge Agent
2. What I have to do next
the SSPI error should be addressed first - consult these kb articles for
more info on it.
http://support.microsoft.com/search/...alse&x=11&y=14
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
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:CA8EB6A7-F554-4A18-B817-6CE8F3B9A2C6@.microsoft.com...
> I have two Win2000 that are in a domain. SQL1(SQL server) acts as the
> distributor and publisher. SQL2(MSDE2000) acts as the subscriber. Push
merge
> replication is running well.
> I want to PULL the db from SQL1 to the db on SQL2, failed :The process
could
> not connect to Distributor. Cannot generate SSPI context.
> I changed Merge Agent location from Subsciber to Distributor, message :
> Server 'SQLTEST1" is not prepared to run the offloaded agent
> Error Unable to activate the agent on the specified remote server because
of
> security restrictions. Use dcomcnfg on the remote server to allow the
local
> SQL Server Agent account to activate the agent
> 1. Where the best location for the Merge Agent
> 2. What I have to do next
>
|||Thank you for the reply. Now it is running well.
One more question. I want to use dinamic filter, different database name for
each subscriber:
... WHERE CityCode = DB_NAME()
but no record in the subscriber table. Plese advice.
"Hilary Cotter" wrote:

> the SSPI error should be addressed first - consult these kb articles for
> more info on it.
> http://support.microsoft.com/search/...alse&x=11&y=14
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:CA8EB6A7-F554-4A18-B817-6CE8F3B9A2C6@.microsoft.com...
> merge
> could
> of
> local
>
>
|||I think that db_name will always resolve to msdb - as that is the database
that the job is run in. In this case I think you will need to change your
filtering criteria.
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
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> Thank you for the reply. Now it is running well.
> One more question. I want to use dinamic filter, different database name
for[vbcol=seagreen]
> each subscriber:
> ... WHERE CityCode = DB_NAME()
> but no record in the subscriber table. Plese advice.
>
> "Hilary Cotter" wrote:
http://support.microsoft.com/search/...alse&x=11&y=14[vbcol=seagreen]
Push[vbcol=seagreen]
:[vbcol=seagreen]
because[vbcol=seagreen]
|||what should be the filter?
Please advise.
Thank you.
"Hilary Cotter" wrote:

> I think that db_name will always resolve to msdb - as that is the database
> that the job is run in. In this case I think you will need to change your
> filtering criteria.
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> for
> http://support.microsoft.com/search/...alse&x=11&y=14
> Push
> :
> because
>
>
|||I would like to use instance name as the filtering criteria, it is posible ?
Please advice.
Thank you.
"Hilary Cotter" wrote:

> I think that db_name will always resolve to msdb - as that is the database
> that the job is run in. In this case I think you will need to change your
> filtering criteria.
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> for
> http://support.microsoft.com/search/...alse&x=11&y=14
> Push
> :
> because
>
>

Error on replication

Hi,
when i try to run an push-replication on MS SQL 2000
i get the error "Log file is full" on the subscriber.
I tried to make this grow VERY much, but it doesnt help.
The table that fails has over 75000 posts, so maybe that is an issue.

The error occurs when i for the first time tries to sync it...

Any ideas?

// PeterTry breaking your task into smaller units of work.

You would normally be using "BeginTrans" and "CommitTrans" to free up the log space in a program after a unit of work has been completed.

Good Luck,|||Well, the thing is... i only want to replicate this to a server, and not
run any scripts. Shouldnt MS-SQL handle this?

I tried the push-operation without the LARGE-table (75000 posts)
and it worked. So it has something to do with that.
Any more suggestions?

Please?!!

// Peter

Originally posted by Bruce A. Baasch
Try breaking your task into smaller units of work.

You would normally be using "BeginTrans" and "CommitTrans" to free up the log space in a program after a unit of work has been completed.

Good Luck,sql

Error number: 1105 the primary group is full

Hi i am Oscar,
I have a problem with database Subscriber. I've created this database with
2 datafile (*.mdf). the first datafile has static size and second datafile
is define with unrestrictec file growth option . the replication have been
worked all time, until the disc has fulled. How is possible that database
Published has 1928 Mb size and Subscriber database grows up a lot of?
Have i configured something in Suscriber database?
Could you help me , please?
Best Regards
Message posted via http://www.sqlmonster.com
Very odd . On the subscriber are there any other tables which are not part
of the publication?
Also, please use sp_spaceused on the publisher and subscriber and post up
the results.
HTH,
Paul Ibison SQL Server MVP,
www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||well paul,
I have executed this storage procedure in Publisher and Suscriber y this
the results
Publishers.
BDIntranet8577.38 MB51.54 MB
1921176 KB973024 KB281384 KB666768 KB
Suscriber.
BDIntranet 55386.75 MB2567.94 MB
52550464 KB52194688 KB230888 KB124888 KB
There is datafile that it?s growing too much. i do not understand Why?
Best Regards,
oscar
Message posted via http://www.sqlmonster.com
|||I was expecting that most of the extra space would be unallocated, but that
is simply not the case. You have 44GB more space used on the subscriber.
Perhaps it is being used for other things apart from this subscription? Or
else you are not replicating deletes, and the subscriber holds all the
original data, much of which has been removed from the publisher?
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

'Error Message

Hi All
I have the 3 servers, A, B & C. A is the publisher, B is the distributor and
C is the subscriber. I have enabled these servers with their roles. I created
a publication which i try to do a transactional replication and i get an
error like this:
'Error Message:
The process could not create file '\\B\SNAPSHOT\unc'.
Error Details:
The network path was not found.
(Source: (OS); Error number: 53)
I don't know what to do and i need some help. Thank you in advance.
Mitty,
can you log on to the publisher as the sql server agent's login and see if
you can browse to the distribution working folder (\\B\SNAPSHOT\). If you
can, see if you can create a file there. This'll test the existance of the
share, your rights to add a file and also see if there is enough space
there.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)