We are having a symmetry issue between rep over a LAN and over the WAN. I want to know the roll of the MSDTC and possible two-phase commits (2PC) that may be occurring with certain subscription types. It didn't seem the replication stream scales well over the WAN and 2PC are not the thing to do over longer distances due to the excessive amount of handshaking needed in 2PCs (reflectivity issues).
If 2PCs and the MSDTC are used, are certain setups or types of replication in SQL 2005 available that would be more efficient over a long distance WAN? Can 2PCs be avoided?
The setup that was built with the issues is not a typically built replication topology (by my book). By my own rule, I never place the distributor on the publisher, ever. Apparently, when setup this way, I didn't have any issue replicating over a similar WAN. Does the distributor work differently when running on a dedicated server?
What's the best replication topology when attempting to replicate over a long distance WAN?
I'm getting this, after upgrading from 2000 to 2005.Replication-Replication Distribution Subsystem: agent (null) failed.The subscription to publication '(null)' has expired or does notexist.The only suggestions I've seen are to dump all subscriptions. Sincewe have several dozen publications to several servers, is there adecent way to script it all out, if that's the only suggestion?Thanks in advance.
We have a large number of clients attempting to replicate two publications on 2005 Express databases (2 publications subscribed to the one subscriber database) with our 2005 Server (9.00.3042.00 SP2 Standard Edition) and experiencing two significant problems:
1) Users experience the following message:
The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Subscriber for changes not yet sent to the Publisher. You must reinitialize the subscription (without upload).
This problem should not apparently occur with SQL Server 2005 (or 2005 Express) instances with SP2 applied. All clients experiencing this problem have SP2 installed as does our Server and the retention period is 30 days. The subscribers have been replicating well under that.
2) Replications never succeed after appearing to replicate/loop around for hours
This issue is the most critical as we have clients who have been installed and re-installed with new instances of SQL Server 2005 Express, new empty databases (on subscriber before snapshot extraction), and using fresh snapshots (less than an few hours old) which cannot successfully replicate.
Interestingly there is at least 1 instance where several computers are subscribed and successfully replicating the same database as another where replication refuses to succeed.
To test we have taken a republished database from another 2005 Server which is working fine and restored it to the same server as the one holding the database with which we are experiencing problems and subscribed to it. This test worked fine and replication of both publications went through fast and repeatedly without showing any signs of problem.
This indicates that the problem is perhaps data related as it appears localised to that database.
Below are two screenshots which may assist.
Screenshot 1 Shows that on the server side the replication attempts look like they are succeeding despite the fact that the subscriber end does not indicate success. Also the history indicates the the subscription has spent all it's time initialising and not merging any changes.
Screenshot 2 Shows a rogue process which has appears on many of the problem child subscribers. It shows a process running with no end time even though the job indicates failure in the message and even though other replication attempts appear to have succeeded after it. This process stays in the history showing that it is running even when I can find no corresponding process for it.
Can anyone suggest a further course of action/further testing/further information required which may assist?
This is extremely urgent and any assistance would be greatly appreciated!
Is there any way to measure bandwith usage during merge replication between sql server 2005 and sql server mobile 2005 running on a cradled wm5 mobile device.
Attaching the windows performance monitor to the network connection established over usb would work although I was wondering if there was something specific for this case integrated into Sql server 2005 / sql server mobile 2005 / Sql server management studio / third party tools that i could use ?
I have a problem when i start sincronyzing with the emulator of MSVS2005 to SQL2005 in Windows Vista. I have the same program in the emulator, but sincronyzing with windows XP Pro and no problem...
"Failure to connect to SQLServer with provided connection information. SQL Server does not exist, access is denied because the IIS user is not a valid user on the SQL Server, or the password is incorrect"
I just want to display all the data of a Single table into a Data Grid, I know that we can drag and drop the table on to a form and datagrid is generated, but here I want to retrive those values through my code, how should i do that
I am getting following errors while running the program Error 1) Error No. 28037, MS SQL Server 2005 Evrywhere Edition Error: A request to send data to the computer running IIS has failed. For more information see HRESULT Error 2) Error No. 0, SQL Server 2005 Evrywhere Edition ADO.Net Data Provider Error: The specified table does not exist [ JobLists ].
Can anybody please tell me, where I went wrong ??? In this code anywhere else????
Note: While adding a Data Source of SQL Server 2005 Mobile Edition, I have added that .sdf file into my project, thats why I have written the Data Source as : .DbFile.sdf
@"Data Source = .DbDotNetCF.sdf";
The code is as follows:
using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Text; using System.Windows.Forms; using System.Data.SqlServerCe;
namespace DeviceApplication1 { public partial class Form1 : Form { string filename = @".DbDotNetCF.sdf";
private DataSet dsJobLists;
public Form1() { InitializeComponent(); }
private void DeleteDB() { if (System.IO.File.Exists(filename)) { System.IO.File.Delete(filename); } }
private void Sync() { SqlCeReplication repl = new SqlCeReplication();
if (DbDotNetCFDataSetUtil.DesignerUtil.IsRunTime()) { // TODO: Delete this line of code to remove the default AutoFill for 'dbDotNetCFDataSet.JobLists'. this.jobListsTableAdapter.Fill(this.dbDotNetCFDataSet.JobLists); } } } }
I have created a merge replication correctlly( I suppose, there were no errros) Please help
If we changed the sort order from BIN to BIN2 but kept everything else the same will it have any effect on replication? So in SQL 2005 if I were to change my default collation from Latin1_General_Bin to Latin1_General_Bin2, would that cause replication to break? I suspect that it will not be an issue since it is just sort order that is changing and the code page stays the same.
BTW, this is transactional replication. Sorry, I left that out of my original post.
I am having trouble with getting Merge Replication up with a new SQL 2005 x64 Server. I already have it running smoothly with SQL 2005 Mobile and SQL 2000, but I want to migrate the backend to SQL 2005.
There is a front end server running IIS 6.0 on Windows 2003 x86 Standard (Server A) with SSL required and Basic Authentication set as the only authentication method (default Domain and Realm are also set). The backend server is running SQL 2005 x64 Standard on Windows 2003 x64 Standard (Server B). The mobile devices are running Windows Mobile 5.0 with SQL 2005 Mobile (Client).
From both a standard Windows XP workstation (IE) and the Client (PIE) I can browse to the HTTPS site on port 444 for the sqlcesa30.dll on Server A and get a response in normal and ?diag modes. The ?diag gives success in all but the 8.0 Database Reconciler (I didn't install the SQL 2000 replication components on Server A, my understanding is they should not be needed). Sql Server Module Versions are as follows: sqloledb.dll - 2000.86.1830.0, 9.0 replrec.dll - 2005.90.1399.0, 9.0 replprov.dll - 2005.90.1399.0, 9.0 msgprox.dll - 2005.90.1399.0.
The publication on Server B is enabled for Web Synchronization and the Snapshop Agent has run. There are no reported errors on that side.
Since I ran into issues getting synchronization to run I have opened up permissions fairly wide in this test environment. The PAL and the Database both have the user I am attempting to sync with listed (I am using the Administrator account in the test domain). I have opened full rights on the Snapshot share on Server B to Everyone (both NTFS ACL on the directory and the Share permissions). The virtual directory on Server A containing the sqlcesa30.dll has also been opened very wide, and the Application Pool does have access to it.
The Client is running a custom C#.NET 2005 application. With the exception of changes to set the application to sync with the Server A/B duo instead of the production servers, this application is identical to the code currently being used in production with SQL 2000 Standard.
The persistent error that I am getting from the Client being thrown by SQL 2005 Mobile when I attempt to sync is "An instance of the SQL Server Reconciler error object cannot be created. Try reinstalling the replication components."
SQL 2005 Mobile components on Server A are set to Logging Level 3 but not returning any errors that I can see to troubleshoot with. All replication components appear to be installed and operational, although I have re-installed them.
Besides the obvious question of how to solve the error listed above, is there an issue with am x85 front end IIS 6.0 server talking to an x64 back end SQL 2005 server for merge replication over HTTPS with Windows Mobile 5.0 clients running SQL 2005 Mobile?
Based on everything I have read off the MSDN Forums, MSDN articles, BOL, log files, and web searches it seems like I should have an operational synching topology, however clearly I have missed something because I have yet to get a successful subscription through to the publication.
Any insight/enlightenment would be greatly appreciated, this seems to be a very narrow and specific area of replication and mobility and information is relatively sparse from my experience so far.
We have upgraded our distribution servers to SQL Server 2005 from 2000 2 days ago. All our replication is transactional. Some replication is running through without any hassles, but others are just not doing anything. The logreader agent is running and succeeding, but not bringing any transacions through to the distribution, even though I can see there is about 9 hours worth of data sitting in on the publication that needs to be replicated. The tables on the publisher is still marked for replication, but when I run MSlogreader_history for the specific agent, it gives me the message: "Executed as user: DOMAINSERVICEACCOUNT. The step succeeded.", but it delivers no transactions and commands. It has been doing this for the last 8 hours.
What can I possibly still check to see what the problem is? Any suggestions are MORE that welcome! P.S. Our replication has been running very stable in 2000 for the last 3 years and I have never come accross this before.
I needed a ROM on a SQL 2005 replication requirement. Would really appreciate any help on this.
We have a SQL 2005 database with about 4 GB data, 46 tables to be replicated. For users to run queries and generate reports, we need a replica of this database. We are thinking of using replication wizard to generate a separate instance of the database on a different box. Also thinking that the replication wizard could be used here.
Based on this information would it be possible to get a ROM estimate for the Development tasks involved in setting up the replication?
I am new on this forum and this is my first Thread on this forum, I want to know how to replicate in SQL Server 2005, I have seven servers, five on them contains Sql server 2000 version and two of them contain sql server 2005. I want to replicate on two servers where SQL Server 2005 installed.
I am trying to configure Transactional replication with updatable subscription sql server 2005 with service pack 2.
Creating distributor and publisher on the same box, but subscriber on a different server.
Distributor and publisher are configured without any problem but when I try configuring subscriber, it throws below warning.
TITLE: New Subscription Wizard ------------------------------
Unable to set the Publisher login for the updatable subscription. You may have to set this up directly on the Subscriber machine using sp_link_publication.
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "REPLLINK_QA-WIN2K3-1413475264_ADVENTUREW1643387368_WELLCORE-542849619_ADVENTUREW1643387368" was unable to begin a distributed transaction. Changed database context to 'AdventureWorks'. OLE DB provider "SQLNCLI" for linked server "REPLLINK_QA-WIN2K3-1413475264_ADVENTUREW1643387368_WELLCORE-542849619_ADVENTUREW1643387368" returned message "The transaction manager has disabled its support for remote/network transactions.". (Microsoft SQL Server, Error: 7391)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3152&EvtSrc=MSSQLServer&EvtID=7391&LinkId=20476
------------------------------ BUTTONS:
OK ------------------------------
I tried setting this up directly on the Subscriber machine using sp_link_publication but the same error.
Any help or suggestion are welcome.
Thanks Sachin
Don't sit back because of failure. It will come back to check if you still available. -- Binu
Hello: I tried to set up a pull transctional replication on SQL Express 2005. The publisher is SQL 2000 which has tables that have primary keys. However, only tables I see in my SQL express (Subscriber) are the system tables. What did I do wrong?
I can't find the right answer on the web. Thanks GCP
Can someone provide some troubleshooting for the following error I have during the replication setup on SQL 2005??
Thanks,
Frank
System Engineer
===================================
Cannot connect to LASC06.
===================================
Failed to connect to server LASC06. (Microsoft.SqlServer.ConnectionInfo)
------------------------------ Program Location:
at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect() at Microsoft.SqlServer.Management.UI.ReplicationSqlConnection.ValidateConnection(UIConnectionInfo connInfo, IServerType server) at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)
------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
does any know of any plans to support publications in Sql 2005 Express? I want to start moving away from MSDE but we use replication (one MSDE database is the publisher and several client PC's use MSDE as the subscribers.).
Is there any way to configure repl. monitor in 2005 to view all the publications that go via a distributor in one place? (as opposed to having to link to each publisher to see the replictaion status).
we have 7 publishers going throigh one distributor and in 2000 could see them all on the distributor...now have to connect to each publisher & look on each...
I'm working on developing a software solution using Mobile Client Software Factory. Let me start off by saying that this package is such a dream come true, and I can't thank the guys who put this together enough. The problem is, we're having some trouble getting the components setup for the Framework to work, in particular with SQL Server 2005.
We have SQL Server 2005 running on a machine, and we have our entire database setup what I believe to be correctly. Last night, we tried for hours to get the PPC Emulator running our version of the Framework to connect to the SQL Server (On another machine on the same LAN) to no avail.
We published just one table to test with, we have the snapshot created, the web service is running, and yet it won't let us connect. The most common error we're getting from the webservice log is: Hr=80004005 ERR:OpenDB failed getting pub version 28627.
I was just wondering if someone out there had a guide for correctly setting up SQL Server 2005 for merge replication so that remote clients can access the server through the webservice over the internet. If there is anything specifically special that needs to be done to work with the Mobile Client Software Factory, that would be great to know too.
I'd really appreciate some help, and thanks in advance to anyone who can lend some advice.
Hi, We are looking into implementing SQL 2005 on one box and have SQL 2005 Reporting Services run on another box with its own replicated database. Mirrioring would not work in this scenario as the primary box has to be down for the secondary box to accept any incoming request.
My questions here is Microsoft website states that Transactional replication is supported for SQL 2005 Standard Edition, but I did watch some presentation on microsoft website that states that you need to have the Enterprise Edition to enable replication.
Can anyone tell me this is possible or not with the Standard Edition ?
I have two servers with sql server 2005, one is in the main office and the other in a store...
I would like that the items table from the main office send new data to the server at store, and the sales data from the store to be send to the main office, can anyone help me to do that?!
I am trying to create a new transactional publication between two Sql 2005 servers. This is my first attempt with replication in 2005, so i have obviously missed something in the setup. Each time i try to create the new puplication i receive the following error.
Any help is greatly appreciated
TITLE: New Publication Wizard ------------------------------
SQL Server could not configure 'DTS-70P40LT2Y0A' as a Distributor.
I have tried to setup Web replication following the instructions in the articles in SQL Books Online, using RMO. I am able to create the subscription, but when I try to sync it I get the following error.
The process could not create file 'C:DOCUME~1lsimpsonLOCALS~1TempHNTBW115D$B_borings_BoringsAll_C:BORINGSBORINGDB.MDF' due to OS error 123.
Is anyone familiar with this error? If I can solve it, I think the replication will work.
I was trying to set up a replication process to move data from SQL 2005 to DB2/AS400.
To get it started, I have create a simplest table (say, PERSON) on SQL 2005 server, and the same table (PERSON) on DB2/AS400. I have only one column SSN (of type int). I have journaled the table on DB2 end. I was able to have successfully configured publisher (on SQL 2005) and subscriber (i.e. a pushed subscription). I used transactional replication. And I also installed HIS 2004 to have DB2OLEDB ready. I was able to use query/insert/delete against table on DB2 based the linked server (that I created for testing purpose).
I did a lot of reading on this and my impression is that replicating to DB2/AS400 is supported from SQL 2005. But I always have this error from replication monitor. Can anyone enlighten me what was wrong.
A SQL error has occurred. Please consult the documentation for your specific DB2 version for a description of the associated Native Error and SQL State. SQLSTATE: 42710, SQLCODE: -601 (Source: MSSQL_REPL_DB2, Error number: -601) Get help: http://help/-601
A SQL error has occurred. Please consult the documentation for your specific DB2 version for a description of the associated Native Error and SQL State. SQLSTATE: 42710, SQLCODE: -601 (Source: MSSQL_REPL_DB2, Error number: -601) Get help: http://help/-601
Web Replication Enabled IIS Configured as documented, except DB server is an AD Domain Controller so can't assign Local User to Application Pool
SQL 2005 Express
Using RMO to create subscription Using Basic Authentication of HTTPS Calling the replisapi.dll?diag works fine
When I attempt to do a web synchronization with the Publisher, I get the following error:
The Merge Agent could not connect to the URL 'https://test.abc.com/TestWebReplication/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable.
Does anyone have any suggestions. I am sure it has something to do with the security setup on the Publisher, but I can't think of anything else to try.
Ok here is the deal...We have our current dev box running SQL 2000 SP3We have two new desktop boxes that we are using as a test, they are both running SQL 2005 SP1The Dev Box = PUBLISHERDesktop #1 = DISTRIBUTORDesktop #2 = SUBSCRIBERAll three SQL Servers are using the same Domain Account to run SQL Agent and SQL Server processes.When I try to create a publication from the publisher, while running the sp_addpublication step through the UI (or thru SQL Query Analyzer) I get the following error message:Msg 15404, Level 16, State 10, Procedure sp_grant_publication_access, Line 136Could not obtain information about Windows NT group/user 'crumpte', error code 0xffff0002.So as a test I tried using our subscriber box as the publisher and had it point to the same distributor box to act as a distributor - and the publication was created fine.It seems to be an issue using SQL 2k as the Publisher and SQL 2005 as the distributor. From the research that I have done, I found this KB article:http://support.microsoft.com/default.aspx?kbid=830596Which essentially says to install the latest SP for SQL 2k, which would be SP4, in the past I know there were issues with AWE memory allocation.Q1. Has SP4 been hotfixed to resolve this AWE issue?Q2. Has anyone here successfully setup replication from SQL 2k -> SQL 2005 using SQL 2005 as the distributor?Thanks!
I have been following the MS on-line tutorials to get replication setup between SQL Server 2005 and SQL Server Compact Edition. I get to the point where I run the Configure Web Synchronization and it is running through the process where it is doing the automated configuration of the shared directory - assigning users etc.
I have attempted this step with a user account that I expressly created for snapshots and with the Administrator account and get the following error message:
* The operation completed successfully. (Exception from HRESULT: 0x80070000)
At first, I thought this was a rights issue due to the fact that I was using an account that I manually created. However, by using the Administrator account (test only until I can figure this out) that should have removed any rights issues associated with accessing the shared directory where the snapshot will reside.
Any help in getting this figured out will be greatly appreciated.
David L. Collison Any day above ground is a good day!
