Hi,

i dont't unterstand this settings:

Initial Size to 10.000 MB

Autogrowth to By 1 MB

restricted to 10.000 MB

You need no autogrowht, because you have defined the size with 10.000 MB. If the...

Hi,

the previous post was from 2012. Are you sure, you have the same error, an Microsoft will fix it soon?

Kind regards,

Andreas

Hi,

I can only see these green arrow, if I start the SSMS within the right domain.

I have two domains, and if I start SSMS just for DOMAIN1, all green arrows...

Hi,

you can use dbWarden to get an email when there are blockings:

http://sourceforge.net/projects/dbwarden/

regards,

Andreas

Hi,

can you give us more details about your setup, SQL version, instances, user for replication, etc...

Hi,

could you please check all servernames of publisher, distributor and subscriber:

SELECT @@SERVERNAME

how do you connect to the server, local with SSMS or remote from distributor. Are there everywhere the same...

Hi,

please check if there is a wrong DISTRIBUTOR connected:

sp_get_distributor

I had the same error a few days before, i don't know how, but my "Distributor" was something else, but not an...

Hi,

my reason not to take a new snapshot is the size of my database. It is about 450 GB and it takes over 24 hours to create, deliver and restore...

Hi

i think it is possible to add new article to a replication without creating a new snapshot for all article:

http://www.mssqltips.com/sqlservertip/2502/limit-snapshot-size-when-adding-new-article-to-sql-server-replication/

regards,

Andreas

Hi,

did the user use the same SID? If you use local sql-user, they must use the same SID.

First you can test, if you have orphaned user:

http://www.fileformat.info/tip/microsoft/sql_orphan_user.htm

I hope it will fix...

Hi,

but you are able to take a snapshot only of the article that was changed.

http://www.mssqltips.com/sqlservertip/2502/limit-snapshot-size-when-adding-new-article-to-sql-server-replication/

regards,

Andreas

Hi,

can you take a look on this link:

http://grumpydba.blogspot.de/2012/09/sql-2008-r2-reporting-services-wont.html

There might be a problem in the time a services needs for starting.

regards,

Andreas

Hi,

have you tested the latency with the "insert token" in the replication monitor?

Hi,

What is your setup of the replication

How many publisher

How many subscriber do you use

Did you use a distributor-server, or is the distributor on one of the publishers?

Do you use...

The problem is solved.

The Subscriber had massive problems with the hard disk.