replication timeout

I have 3 production machines which are replicated to a dr site, all
machines are using a central distributor machine. I have created a
separate distributor database for each system.
My problem is that one of my systems will not replicate I am doing
snapshot and transactional, it just keeps timing out I have put sql
profiler on the dr box and can see that the data gets to the box but
it just times out. All boxes publisher, distributor, subscriber can
see each other so why is it timing out?
what is the exact error message you are getting?
"stephen" <twolf@.icon.co.za> wrote in message
news:75c81dee.0404170439.22bbd18d@.posting.google.c om...
> I have 3 production machines which are replicated to a dr site, all
> machines are using a central distributor machine. I have created a
> separate distributor database for each system.
> My problem is that one of my systems will not replicate I am doing
> snapshot and transactional, it just keeps timing out I have put sql
> profiler on the dr box and can see that the data gets to the box but
> it just times out. All boxes publisher, distributor, subscriber can
> see each other so why is it timing out?
|||Have you looked into creating a different snapshot profile?
If you go into Publisher/Distributor Properties, Agent Profiles, and
then Snapshot Tab, If you look at the existing "Default profile" the
Query time-out is set to 300; you might want to increase that number
to maybe 1000 or so.
Here is something that I have found interesting though that you might
want to know ahead of time so you DON'T CANCEL the replication
process:
Depending on how high you increase this number to, there is always the
potential of getting a somewhat bizare error message while the
replication is running stating that no response has been received from
the snapshot agent, and the Replication monitor will display the red X
symbols (like if it had failed). However, the process is still alive
and well (you can check it under jobs to see if it is still in fact
running), so once it goes past the table that may be causing it to
time-out, the Replication monitor will refresh and the Xs will be
removed.
Try this on a test environment first as every environment reacts
diferently, and always remember to keep a current backup just in case.
Hope this helps.
Jose
twolf@.icon.co.za (stephen) wrote in message news:<75c81dee.0404170439.22bbd18d@.posting.google. com>...
> I have 3 production machines which are replicated to a dr site, all
> machines are using a central distributor machine. I have created a
> separate distributor database for each system.
> My problem is that one of my systems will not replicate I am doing
> snapshot and transactional, it just keeps timing out I have put sql
> profiler on the dr box and can see that the data gets to the box but
> it just times out. All boxes publisher, distributor, subscriber can
> see each other so why is it timing out?

Replication Sync on Windows Vista

On windows XP there is a Synchronize program in Accessories. When I run our replication scripts on a SQL Server Express on the XP machine and start the Synchronize program there are items there that allow me to replicate as well as set a schedule, etc.

On Windows Vista there is a Sync Center, but replication doesn't show up here.

I've searched high and low on Google and am not coming up with anything useful, which leads me to believe this is something very simple that I'm overlooking...

Does anyone know how to make your replication show up on the Sync Center in vista, or is there another application that I should download?

Thanks,

Brian

I could be wrong, but I do not believe those are the same. I think Sync Manager in Vista is a built-in tool for synchronizing PDA's and thing like that. However, so I do not mis-speak, I am testing that now because we are also at the point of testing synchronization with Vista.

I will let you know what i find.

Scott

|||To add files to Sync Center, on the (Vista) machine you want to have the offline copy on, open explorer and navigate to the network share the original file or directory is on. Right-click and on the context menu select "Always Available Online." The SyncCenter icon will be superimposed on the icon to show it is being copied.

Replication Sync on Windows Vista

On windows XP there is a Synchronize program in Accessories. When I run our replication scripts on a SQL Server Express on the XP machine and start the Synchronize program there are items there that allow me to replicate as well as set a schedule, etc.

On Windows Vista there is a Sync Center, but replication doesn't show up here.

I've searched high and low on Google and am not coming up with anything useful, which leads me to believe this is something very simple that I'm overlooking...

Does anyone know how to make your replication show up on the Sync Center in vista, or is there another application that I should download?

Thanks,

Brian

I could be wrong, but I do not believe those are the same. I think Sync Manager in Vista is a built-in tool for synchronizing PDA's and thing like that. However, so I do not mis-speak, I am testing that now because we are also at the point of testing synchronization with Vista.

I will let you know what i find.

Scott

|||To add files to Sync Center, on the (Vista) machine you want to have the offline copy on, open explorer and navigate to the network share the original file or directory is on. Right-click and on the context menu select "Always Available Online." The SyncCenter icon will be superimposed on the icon to show it is being copied.

Replication Problem where Distributor & Subcriber on same machine

What I would like to do is set up transactional replication from server1 (Publisher) to server2 (Subscriber), with server2 acting as the (Distributor).

I am successful on server2 in allowing server2 as a distributor for server1. When I try to configure replication on server1 to use server2 as a distributor and subscriber I get this message once

"
SQL Server Enterprise Manager could not enable 'server2' as a Subscriber.

Error 14071: Could not find the Distributor or the distribution database fom the local server. The Distributor may not be installed, or the local server may not be configured as a Publisher at the Distributor.
"

and this mesage for each database I enable for subscription, I get this message.

"
SQL Server Enterprise Manager could not enable database 'x' for snapshot or transactional replications.

Error 20028: The Distributor has not been correctly installed. Could not enable database for publishing. The replication 'publish' of database 'x' has been set to false.
"

The last message I get is

"
SQL Server Enterprise Manager successfully enabled 'server2' as the Distributor for 'server1'.
"

This message is apparently false.

When I try to Configure Publishing, Subscribers and Distributing... on server1, I get the message

"
SQL Server Enterprise Manager could not retrieve information about the Distributor or the distribution database.
"

In an attempt to fix this I:
1. disable publishing on server1,
2. disable publising and distribution on server2.
3. enable publishing and distribution on server2.
4. enable publishing on server1 using server2 as distributor.

Again I get errors on step 4.

I have even tried re-installing SQL Server 2000 on server2 with no improvement.

Can some one please shed some light on this problem?

Thanks in advance.Connect to the SQL Server using Query Analyzer and run the following query: select @.@.servername.

If it returns NULL you will need to run the sp_addserver procedure to get
the internal server name correct. You may need to run sp_dropserver as
well. These are documented in Books on Line.

A NULL server name can cause wierd behavior with replication.|||I do have a NULL server name problem. I have run the sp_dropserver, sp_addserver and have retarted SQL Server.

I have tried again to create the replication & it now WORKS!

Satya, thanks soooo much for you help!

Replication Limiting Subscribers

How can we limit the number of anonymous merge subscribtions to a
given publication? Can we limit it by machine MAC address?
(Bump!)
Guys I really need an answer to this question.
How can we limit the number of anonymous merge subscribtions to a
given publication (assuming i can have only one sql account per
publication and no NT authentication)?
The problem with giving a set of sql accounts is that they can be
reused.
Can we limit it by machine MAC address?
Thanks,
Hananiel
hananiel@.yahoo.com (Hananiel) wrote in message news:<e338e321.0410130607.37e214d5@.posting.google. com>...
> How can we limit the number of anonymous merge subscribtions to a
> given publication? Can we limit it by machine MAC address?

Replication in XP home

Please help!!

I have recently installed ms sql on my system and I am trying to replicate my machine which happens to be a compaq laptop which is running xp home edition. The publisher machine can see my server however gives me an invalid subscription error. I have been told that it might be due to the fact the the laptop is on xp home, would this be a problem???

please get back to me, anyone.,.much appreciated!!!!

JaysunJaysun,
What version of SQL Server did you install? Check http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.asp for version/OS compability.

If your version of SQL Server is compatible with XP home I would also suggest looking at the account that SQL Server is using to login. If it is using the local system account then I will not be able to talk to other servers on the domain.

Regards,|||hi thanks for coming back to me, ive checked the version and its ok. plus i can connect to the publisher and also to other servers. esp to another laptop that is running xp prof, and that does not seem to have a problem replicating. however i cannot connect to other servers running windows 2k. ive checked the sql account and username and password is the same as the other laptop./

the error i get when i try and connect to another server:

login failed for user 'sa' not associated with a trusted sql server

would it be because i this one is not logged into a domain??