I am trying to "Configure Distributor" prior to setting up the publications. When I go through the wizard, at the very last step I get the following error:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Cannot find the principal 'sa', because it does not exist or you do not have permission.
'distribution' is not configured as a distribution database.
Changed database context to 'master'. (Microsoft SQL Server, Error: 15151)
i'm getting the following error message when i attempt to configure my server as a local distributor:
TITLE: Connect to Server
------------------------------
Cannot connect to 9A6375C3046246B.
------------------------------
ADDITIONAL INFORMATION:
Failed to connect to server 9A6375C3046246B. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
An error has occurred while establishing a connection to the server. 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: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
this error is occuring despite the fact that i have the server configured to allow remote connections. can someone please help me troubleshoot this error? thanks.
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
An error occurred during decryption. There is no remote user 'distributor_admin' mapped to local user '(null)' from the remote server 'repl_distributor'. Changed database context to 'master'. (Microsoft SQL Server, Error: 15466)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2153&EvtSrc=MSSQLServer&EvtID=15466&LinkId=20476
I'm having a problem configuring one of my SQL servers as a distributor. I've done it successfully on another server, so I know that it's nothing procedural and there must be an issue with the way the server is set up. When I click 'finish' on the Configure Publication and Distribution Wizard, I get the following error message:
Enterprise Manager could not configure 'ABEL' as the distributor for 'ABEL'.
Error 20017: Cannot add the remote distributor at this time. Make sure that the local server is configured as a Distribution Publisher at the Distributor.
Can anyone point me in the right direction? I'm fairly new to SQL Server, so feel free to explain things in a condescending manner. ;-)
I am working on setting up our new SQL Server 2005 servers. One ofthem will eventually be our Replication Distributor. However when Iattempt to set this up within the wizard, I get the following error:------------------------------TITLE: New Publication Wizard------------------------------SQL Server could not configure 'ServerInstance' as a Distributor.------------------------------ADDITIONAL INFORMATION:Property LoginSecure cannot be changed or read after a connectionstring has been set. (Microsoft.SqlServer.ConnectionInfo)------------------------------BUTTONS: OK------------------------------In the "Specify the Domain or Machine account under which the Snap ShotAgent will run" page, I designate a Windows Auth. domain user; The sameuser that is used to start SQL Service. Any idea as to why I amgetting this error?
Property LoginSecure cannot be changed or read after a connection string has been set. (Microsoft.SqlServer.ConnectionInfo)
I have had a good look through the forums and have found several ideas about permissions on the DATA folder to no avail. I have also not changed the sa user it is still sa. Unfortunaley all the things I have found haven't worked. Have you got any ideas?
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
An error occurred during the execution of xp_cmdshell. A call to 'CreateProcess' failed with error code: '5'. Invalid destination path C:Program FilesMicrosoft SQL ServerMSSQLData. Changed database context to 'master'. (Microsoft SQL Server, Error: 15121)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15121&LinkId=20476
I often deal with a problem when replicated database is down due to electric outage or any other scheduled type of downtime. Primary database is up but distribution agent is going down 'after 10 attempts to connect to replicated database'. That's the problem I think because not only distribution agent goes in undetermined state and I have to restart sqlagent service, but I need to go through whole process of snapshot and applaying it to replicated db. I would like it to accumulate transactions in distribution database and once replicated db is up - distribute them.
I wonder if anybody can tell me how to configure distribution thread so it does not go down after 10 unsuccessfull attempts but stays for day or two.
1 SERVERNAME SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15 Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
1 SERVERNAMEINSTANCE SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
IIS 5.0
SQL Server CE 2.0 (sp3a)
Merge replication previously working fine. The problem
After migrating MSDE from sp3a to sp4 (in order to fix CE replication bug) I can't sync to MSDE. I got the following error code: [29045]->[Initializing SQL Server Reconciler has failed.] so I've looked into SQL Server CE log file and I've found the following error message:
2006/02/07 19:44:23 Thread=9A8 RSCB=4 Command=SYNC Hr=00000000 The process could not connect to Distributor 'Distributor-name'. 20084
2006/02/07 19:44:23 Thread=9A8 RSCB=4 Command=SYNC Hr=00000000 Data source name not found and no default driver specified
I've already tried without success
Uninstalling all SQL Server 2000 (EE) instances (except for the "no instance") Unistalling and re-install MSDE (sp4) Re-registering sscerp20.dll. Rebooting server. Restarting IIS.
Hey guys. I am creating an app that uses the RMO Merge Replication objects. So far it can subscribe and unsubscribe just fine but when it comes to the syncing process it gets a little weird, here's why.
- If I run the SQL GUI Sync tool, it sinks fine. So that setup is working.
- When I run the C# App it blows up witht the error: "Process cannot connect to Distributor"
- Here's the weird part: When I set a breakpoint on my custom method SyncData (this method sets up the connection info and properties and then calls Syncronize( ) ) and step through the code when it gets to Syncronize( ) it runs perfectly fine, no execeptions.
I thought that maybe the Syncronize( ) method was being called too fast before the connection properties got to fully setup and connect, so I added a Thread.Sleep( ) method for 10 secs after each connection call and just before calling Syncronize( ). It still didn't work. My class is a static class by design, however, I changed it into an ordinary class and then placed the connection info in the constructor hoping it would do it's connection when the object gets initialized, that didn't work either.
If someone could please help me out with this I would greatly appreciate it.
Here's my code:
using System;using System.Collections.Generic;using System.Text;using Microsoft.SqlServer.Replication;using Microsoft.SqlServer.Replication.BusinessLogicSupport;using Microsoft.SqlServer.Management.Common;using System.Windows.Forms;using System.Threading;namespace Emds.Briefcase.BriefcaseSubscriber.BLL{ public class SyncDataClass { #region Members private static string m_statusMessage = string.Empty; private static byte m_percentComplete; public delegate void StatusTextChangeHandler(int percent, string status); public static event StatusTextChangeHandler OnStatusChange; #endregion Members #region Methods public static string SyncData() { //Delay(); // Define the server, publication, and database names. string publicationName = "Chart"; string publisherName = @"JSMITHSQL2005"; string subscriberName = @"JDOESQL2005"; string subscriptionDbName = "DataSubscriber"; string publicationDbName = "DataPublisher"; string message = string.Empty; // Create a connection to the Subscriber. ServerConnection conn = new ServerConnection(subscriberName); MergePullSubscription subscription; try { // Connect to the Subscriber. conn.Connect(); // Delay(); // Define the pull subscription. subscription = new MergePullSubscription(); subscription.ConnectionContext = conn; //Delay(); subscription.DistributorSecurity.WindowsAuthentication = false; subscription.DistributorSecurity.SqlStandardLogin = "sa"; subscription.DistributorSecurity.SqlStandardPassword = "russell"; // Delay(); subscription.PublisherName = publisherName; subscription.PublicationDBName = publicationDbName; subscription.PublicationName = publicationName; subscription.PublisherSecurity.SecurityMode = ReplicationSecurityMode.SqlStandard; subscription.PublisherSecurity.SqlStandardLogin = "sa"; subscription.PublisherSecurity.SqlStandardPassword = "russell"; // Delay(); subscription.DatabaseName = subscriptionDbName; subscription.SubscriberSecurity.WindowsAuthentication = false; subscription.SubscriberSecurity.SqlStandardLogin = "sa"; subscription.SubscriberSecurity.SqlStandardPassword = "russell"; // Delay(); // If the pull subscription exists, then start the synchronization. if (subscription.LoadProperties()) { // Check that we have enough metadata to start the agent. if (subscription.PublisherSecurity != null || subscription.DistributorSecurity != null) { // Synchronously start the Merge Agent for the subscription. subscription.SynchronizationAgent.Status += new AgentCore.StatusEventHandler(SynchronizationAgent_Status); // Delay(); subscription.SynchronizationAgent.Synchronize(); message = "Data Syncronization is a success!"; } else { throw new ApplicationException("There is insufficent metadata to " + "synchronize the subscription. Recreate the subscription with " + "the agent job or supply the required agent properties at run time."); } } else { // Do something here if the pull subscription does not exist. throw new ApplicationException(String.Format( "A subscription to '{0}' does not exist on {1}", publicationName, subscriberName)); } } catch (Exception ex) { // Implement appropriate error handling here. throw new ApplicationException("The subscription could not be " + "synchronized. Verify that the subscription has " + "been defined correctly.", ex); } finally { conn.Disconnect(); } return message; } static void SynchronizationAgent_Status(object sender, StatusEventArgs e) { m_percentComplete = e.PercentCompleted; m_statusMessage = e.Message; //Fire custom event if (OnStatusChange != null) { OnStatusChange(m_percentComplete, m_statusMessage); } } #endregion Methods }}
I have 2 servers: #1 -- SQL 2005 SP1 publisher ; #2 -- SQL 2005 SP2 subscriber
originally I had #1 as pub and dist but dist but killing my CPU so I was in the process of moving the dist to #2... Got it all configured and when I tried to add #2 as a dist for #1 it fails when I get to the administrative password screen... It give me an error about how it cannot connect with the given password but under that is says linked server failed.
Since it mentioned linked server I tried to connect via the previous linked server to #2 and it failed... I cannot connect to #2 anymore from #1. I can login directly to #2 and I can use osql to connect to #2 but linked server does not work. I tried all drivers and many configurations...
Hi every1, I have problem about configuration in Merge Replication. First, I configure for SQL Server 2000, expand Replication> Publication>New Publication>Choose Publication Database, I choose pubs>Select Publication Type, choose Merge Replication>Specify Subscribers Type, choose Servers running SQL Server 2000 and Devices running SQL Server CE>Specify article (ex. authors)€¦>Finish. I configure succeeded (A snapshot of 1 article(s) is generated). Snapshot folder reference to path: \server_nameC$Program FilesMicrosoft SQL Server 2005 Mobile EditionServerReplication Next, I configure for SQL Server Mobile Agent, Subscriber Type, choose SQL Server Mobile Edition>Web server, choose Create a new virtual directory>Alias: Replication (reference to the path: C:Program FilesMicrosoft SQL Server 2005 Mobile EditionServerReplication)..>Client Authentication, choose Client will connect anonymously€¦.>Snapshot share access, enter \server_nameReplication =>error: The share '\server_nameReplication' cannot be accessed. Please specify a new share. Why that? I want to ask u I configure that correctly? If Subscriber is Pocket PC Emulator, what is subscriber €™s property of SqlCeReplication (Windows PocketPC Emulator?)? Plz help me. Thanks so much.
I'm beginning to wonder if replication is worth the trouble I've had to spend on it!
Trying to create a simple peer-to-peer replication topology. I can create the initial publication. I can change the property to allow P2P. I can backup the database and I can create a snapshot. When, however, I try to configure the peer-to-peer topology, I get a 14027 error message telling me that ONE table out of 250, or so, "does not exist in the current database." That's pretty troubling given that I can run a select query against that specific table. I would appreciate any information that would help me to understand what's going on or successfully set up replication.
Hi, In a mapping I have two look up€™s before setting the configure error output €śERROR€? as ignore failure, the job was stopped with an error message €śRow yield no match€?. Now that I had changed the error as ignore failure the job is successful but only concern here is will the destination table get inserted with those records which are not matched in look up.
i want to upload reports in ssrs , when i trying to configure reporting service configuration manager, getting error" there was an error while switching panels. The most likely cause is an error retrieving wmi properties. the exception details are access is denied . You must have an administrator on the report server computer to use this tool".
Error message: Setup failed to configure the server
I'm attempting to install SQL Server 2000 Developer Edition on a 2nd workstation in our area for development and practice with having this 2nd workstation as a "local" (test) SQL Server box. The install fails with the above mentioned message. (We have a database running in production on SQL Server 2000 and we need a place to simply copy the database and run tests on it)
The target PC is running WInXP Pro-SP3 and has IIS installed, along with Visual Studio 2005 & .Net framework, etc.
I downloaded it (via MSDN license) and accepted the defaults on the install.
I installed Micrsoft Server Desktop Engine from the CD I received in my ASP.net book. The installation went fine and then I went to the DOS prompt and did the "setup SAPWD..." and it ran. I restarted my computer and opened ASP Matrix and went to the Data tab and proceed to connect to the server. It gave me an error message it couldn't connect.
So I uninstalled MSDE and made sure the sql2ksp3 folder was gone. So I went ahead and installed the MSDE again from the CD again and then went to DOS to do the setup. It ran through the setup until the very end with 11 seconds remaining and received error message " Setup failed to configure the server. Refer to the server error logs and setup logs for more information. I have tried it several times and it always stops around 11 seconds. I have tried to install the download from microsoft.com instead the CD and that didn't work also. So at this point I am stuck. PLEASE HELP!
I also checked my Registry keys for a file called PendingFileRenameOperations and it wasn't in the registry keys.
If anyone has any suggestions I would appreciate it.
I've tried looking for a solution in other threads but I couldn't find anything that was completely the same as my situation. I got a new pc at work and I've tried installing SQL Server 2005 on it but everytime I try to install it, regardless of services included or excluded with the install, I cannot get through the install without this error. Below is the excerpt from the Summary.txt log file.
Error Code: -2147024894 MSI (s) (74!98) [17:10:55:858]: Product: Microsoft SQL Server 2005 Tools -- Error 29549. Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024894 Error message: The system cannot find the file specified. Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Error 29549. Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024894 Error message: The system cannot find the file specified. Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. <Func Name='GetCAContext'> <EndFunc Name='GetCAContext' Return='T' GetLastError='203'> Doing Action: Do_sqlAssemblyRegSvcs PerfTime Start: Do_sqlAssemblyRegSvcs : Mon Nov 12 17:10:55 2007 <Func Name='Do_sqlAssemblyRegSvcs'> Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: 2147942402 Error message: The system cannot find the file specified. Error descrition: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Error Code: -2147024894 Windows Error Text: The system cannot find the file specified. Source File Name: sqlcasqlassembly.cpp Compiler Timestamp: Thu Aug 11 01:12:01 2005 Function Name: Do_sqlAssemblyRegSvcs Source Line Number: 155
I've searched for and found similar problems that deal with the microsoft.sqlserver.notificationservices.dll not being found but I haven't found a fix that worked for me. These are the fixes I've refered to thus far.
The answer that seems to fix this problem for everyone is to set the MSDTC service login as the NT AUTHORITYNetworkService account. The problem for me is that this is already set to this profile and I've tried resetting the services and rebooting the machine. I did not have a problem with my old machine, which as far as I can tell, is the same configuration, so I know this install should work.
I'm running Windows XP SP2. This is not the upgrade to SQL Server 2005 SP2, this is the original disk that came with Visual Studio 2005.
Has anyone else faced this issue where changing the MSDTC login wasn't the solution? Also, this is my first post, so I apologize if I've left anything out. Just let me know if you want any other information.
After extensive testing I have found that bcp's run almost twice as fast on my dedicated Distributor than on either the Publisher or Subscriber. I was wondering if there is a way to make the bcp's spawned by creating a Snapshot run on the distributor and not the Publisher.
I was wondering if you could set up multiple distributors for one database?For example:Server A needs to publish data to server B so I set up server A's distributor as server B. Later Server A needs to publish data to server C so I want to set up the distributor for this replication to use server C.I don't think this is possible as you need to set up the distributor for the entire DB when its created not for each individual replication job.Any help is appreciated.Nick
I am having problem creating a distributor on my sever, when i do it thru the enterprise manager it defaults to another sever's path and when i put the severs path it dosen't find it. and when i do it thru query analzer this is what i get
Server: Msg 6, Level 16, State 1, Procedure sp_adddistributor, Line 147 Specified SQL server not found. Remote logins for remote server 'repl_distributor' have been dropped. Server dropped. Server added. Server network name set.
and for this it is going to another server sp_adddistributor @distributor = '158.72.80.48' ,@heartbeat_interval = 10 , @password = 'grants831' -- , @from_scripting = from_scripting
error message
Server: Msg 18482, Level 14, State 1, Procedure sp_adddistributor, Line 147 Could not connect to server 'GEMS' because 'vivian' is not defined as a remote server. Remote logins for remote server 'repl_distributor' have been dropped. Server dropped. Server added. Server network name set.
Completed SQL 2000 Transactional Replication from distributor/publisher to Subscriber. (with identity problem solved)
NOW wizard disallows set up subscriber to publish back to the Distributor/Publisher. "Distributor not known" message on Subscriber server when we open configure Publisher-Subscriber tool.
Any experience using this wizard to set this up would be appreciated.
For remote distributor (transactional replication,distribution database 50GB, 3 day retention), what is the most critical resource except disk ? Is it CPU intensive ? does it use lots of memory (i.e. would 4GB be enough) ?
Hello, I have 3 servers sql 7 sp3, 1 editor, a distributor and an subscriber. the base on the editor is removed, how to make to remove all traces of replication on the distributor and the subscriber. thank you. Pascal
I'm reading the MS online docs about replication. there's something not so clear until so far.
I have one central server and 7 client servers. Sometimes new data is entered at one client server. This should be replicated (when client comes online) to the Central Server (merge replication).
Also, the other way, once the central server gets new data (that was replicated from a client), it should be again replicated to all 6 other clients (from the central server).
now, who should i configure as the distributor, publisher and subscriber?
