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.
Not sure if this is the right place, but ill give it a try.. Everytime i try to make a websync for my replications i get this error and then it rolls back everything:
===================================
The operation completed successfully. (Exception from HRESULT: 0x80070000) (mscorlib)
I need to replicate a database which will be updated both sides.Table doesn't have the primary key,and already has data.Please advice which replication will suit and what are the limitations.URGENT!! Thanks!
I did setup to have a Desktop SQL Server running on Windows NT workstation in a different domain across the internet create a pull subscription to a transaction publication that is immediate updating that I have published on my NT SERVER in my domain. It never got any further than creating the subscription -- I got the following error on the pull:shared agent job history:
The job failed unable to determine if the owner (domainusername) of job SQLServername-databasename-pubname-SQLServername2-databasename2 - 0 has server access (reason: Could not obtain information about Windows NT group/user 'othernameIdon'tunderstand'(SQLState 4200000) (Error 8198)
I want to be able to do bi-directional transaction based replication between a 7.0 SQL server running on Windows NT 4.0 server SP5 and an NT Workstation 4.0 SP5. Can this be done or would it require that both machines to be NT Server based? The reason I asked is because previously under 6.5 I was able to install the SQL operating system on Windows NT Workstation and now it looks like I can only install the Desktop version under 7.0. Will this give me the type of replication I am looking for?
Hello, I'm newbie in replication field. At the moment, I am able to setup replication on LAN (1 distributor to few subcribers). However, I found some difficulties on setting-up the replication on WAN. Is there any guidelines, setup documents or examples (like print screen) for me to refer to ? Hope able to get any assistance at here.
I am setting up 2005 Transacational Replication on a database that was created on SQL 2000. There are 1400 articles (tables, views, sp and functions). It takes 2.5 hours to create the snapshot. Then, once the distribution errors gets its first error, it keeps retrying and getting the same error. Q1: Can I tell it to record the error but keep going? Q2: How do I stop the distribution agent once it gets in the this state? I have been deleting the publication but that seems like overkill.
I am trying to figure out a more efficient way to identify all the articles that are going to get errors. Is there any way to test the articles to see which ones will get an error? My current process takes a long time just to identify one error (since I have to create the snapshot each time).
Sorry for the previous mail.. Didnt mean to send it like that..
I have a question about replication. I have created the destination machine as the subscriber, where I created a pull subscribtion and tried to replicate I got this error. "Subscriber must be running in perseat license moe to use this."
The cd I used to install MSSQL 7.0 is the msdn back office test platform. Where am I going wrong??/ because I never got to specify the per seat license anywhere.. The documentation says that If I can have it installed on a 95/98 box then it means I have a perseat licesne, which I was able to do..
We are working on mssql 6.5, sp 4 and are beginning to test replication between two servers containing the same databases.
In EM, we added a distribution database on the publisher machine and through EM added each server as a local on each separate server and installed mssql 65 and sp4 on each machine and created the same database on each repsective machine.
In EM , through replication configuration, we added a subscriber database on one machine. On the publisher machine ,in EM through replication configuration, we went to add a publisher and when we clicked on the subscriber and then clicked on the publisher database and then clicked 'O.K.", we got the following message:
'Error 21271 : the name 'xyz-01' is not a vlaid object identifier, oe is not a valid format for this proprty or method'
This error message is not in BOL.
Has any one received this message in this situation?
What do we do to resolve it?
Any assistance that can be provided will be greatly appreciated. THanks.
Steps I made: 1) Created Publications by script - using Manual Sync. (Transacat Repl) 2) Created Subscriptions by script 3) Started Distribution Agent THEN THIS ERROR MSG:
I have a Windows Mobile aplication that uses merge replication to synchronize between sql compact and full sql Enterprise edition and It works great. Instantiating the SqlCeReplication object setting it's properties and calling Synchronize on it is pretty simple assuming everything is setup properly at the publisher.
For the life of me I can't figure out how to do this on the desktop (Programatically setup a subscription and create a database using objects in the System.Replication Namespace and hopefully call Synchronize on it).
We have a setup with one Publisher Server and 15 Subscribers with merge replication configured for all subscribers. The current Database size is approximately 3 GB expected to grow to 10 GB in next 1 year. We wanted to know what benefits would we incur if we add an additional seperate distributor server (hardware box). Also, what is the approx. size of a database where a seperate distributor server (hardware box) is recommended.
When trying to create a publication or subsubscription running under a Windows Domain account the following error message appears:
Replication-Replication Distribution Subsystem: agent ECHOECHO-InsDB-INS_CMS_PUB-HARPO-58 failed. Unable to start execution of step 2 (reason: Error authenticating proxy DETINIsrvRep_user, system error: Logon failure: unknown user name or bad password.). The step failed.
Further in the SQL logs we find that the above message is due to:
[298] SQLServer Error: 22046, Encryption error using CryptProtectData. [SQLSTATE 42000]
It appears that when Credentials for the agent proxy are being created that this message occurs. So when the SP that tries to run the agent (snapshot or distrobution) is called it always returns incorrect password details.
The Credentials do appear to be created, they are visible via SQL Studio, but you can't see the password. Changing the password via SQL Studio does not work as the Credentials are recreated every time.
I have checked the following:
MSDTC is running correctly The Domain Account has the correct privileges to run these services Regenerated the Service Master Key Created Master Keys in each database effected by replication Ensure SQL Service accounts have access to decrypt the Service Master Key I can create a Publication and Subscription using the local system account on the cluster
I am using two windows 2000(SP4) server box for Sql server 2000(SP3a) replication wit following methods-
1.ISDN Dialup line with NT1 terminator at both end. 2.Create Dialup from one computer. 3.Create RAS with static IP Address at second computer (Dial in) for acceptance of dialing. 4.Dialing from one place to another computer and get connection by dialup. 5.I can ping only Remote IP (RAS STATIC) Address at both end.
Try to registered SQL Server 2000 from dial place or dial in place got following errors- Specify Sql server not found, Connection Open Connected()
What I am missing in setup of windows or Sql server 2000 or any hard component, let me help. Is the any need of physical router.
I am using two windows 2000(SP4) server box for Sql server 2000(SP3a) replication wit following methods-
1. ISDN Dialup line with NT1 terminator at both end. 2. Create Dialup from one computer. 3. Create RAS with static IP Address at second computer (Dial in) for acceptance of dialing. 4. Dialing from one place to another computer and get connection by dialup. 5. I can ping only Remote IP (RAS STATIC) Address at both end.
Try to registered SQL Server 2000 from dial place or dial in place got following errors- Specify Sql server not found, Connection Open Connected()
What I am missing in setup of windows or Sql server 2000 or any hard component, let me help. Is the any need of physical router.
Dear Pat Phelan Sir Resident Curmudgeon
Lot of thanks to you for your valuable suggesion, I did do whatever you suggested prior to his emal but not yet got solution
I am using port 1430 for a server and 1440 for b server.
How I can open my case with MS-PSS (Microsoft Professional Support Services), I didn't find any rool for unregistered users.
I am new to Sql server and had just finished the MErge Replication setup on one of the PRoduction server. Today I got the request to change one of the Datatype of one the Published Article. Please help as what are the correct step to make it happen. Is there any production downtime required and if yes , then how much.
We have a vendor that is exposing our database via a High Availability replica. They are geographically far away from us though so we would like to extract portions of the database over to our side for our reporting /warehousing purposes. I was curious if it is possible to setup snapshot replication on a high availability group?
I have a setup of transaction replication between one publisher and subscriber in the Same server.Now, I need to add a new subscriber to the existing publisher. So publisher database name is DB_A and Subscriber 1 name is DB_B. So the new subscriber will be DB_C. Is this kind of setup possible on one server?
If yes then at the time of reinitialization is it going to apply the snapshot on DB_B as well as DB_C?Also let say if due to disk error DB_B gets corrupted then will data be still replicated between DB_A and DB_C? (Assuming publisher, subscriber 1 and 2 are sitting on individual disks).
I am setting up the replication with the scripts which used to setup in MSSQL2005 (non-cluster server). After I run the script and start the snapshot agent, log agent or distributed agent, it prompts,
Unable to start execution of step 2 (reason: Error authenticating proxy abc.comadmin9, system error: Logon failure: unknown user name or bad password.). The step failed.
abc.comadmin9 is the administrator for all cluster, mssql service and I am sure that the username and password is correct.
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
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.
I recently installed SQL 2005. During the setup, I didn't get the option that makes me add the licensing module I'm using. I don't want to be slapped in the wrist by microsoft. After setup, how can I check the licensing used?
I am trying get a database setup in my new install of VS 2005. I have a project on one PC where I just have VS2005 installed and i am able create a website, go to the APP_DATA folder and add a database. On another PC I have VS 2005 installed and then I installed SQL server 2005. Now I fail to connect to ??? when I try and enter the sercuity page of webconfig or try to add a database when I open the APP_DATA folder. There have been many things done on this PC between the install of the two mentioned packages and trying this database creation. However, I feel that something related to the install of SQL Server 2005 after VS 2005 has done something unexpected. Or, I need to manage something between the SQL Express version that got loaded with VS 2005 and the subsequent install of SQL Server. I just don't know what to look for at this point.
I have a SQL 2k5 log shipping setup and all copy jobs as well as restore jobs are running properly but the LS_Alert job that the wizard auto creates fails every two minutes has anyone experienced this before. After going through the wizard it creates a LS_Alert job and schedules it every two minutes and it fails constantly.
I'm a Network Administrator that has to do everything from desktop to server, to routing, and DBA so I need a bit of advice. Stretched thin for time and knowledge in the SQL area and trying to do the best I can.
I currently have a MS SQL 2000 database that is 60GB in size for MS Dynamics 8.0 and one that is 2GB that I want to move to a new server.
I've setup and tested it and it all works, now I'm looking for some Best Practices information for best performance. Currently doing about 3,000 transactions a day.
Server is HP ML350-G5 2 Xeon Dual Core 2.0GHz CPUs w/16GB RAM w/external drive bays running 72GB 15K SAS drives with SMART ARRAY P800. OS is Windows Server 2003 Enterprise w/SP2 - MS SQL 2005 Standard I have the following drive configurations setup.
C:(RAID1+0)OS - SQL 2005 D:(RAID1+0)Dynamics Application Shared dictionary files for clients G:(RAID0)BACKUPS (see note below about TEMPDB) I also have a 25GB swap file on this drive maybe better to put in on the D: volume if I put TEMPDB here H:(RAID1+0)LOGS (2 user db logs and the tempdb log) I:(RAID1+0)DATA (2 user db - [model, msdb, master]
Recently found that my G: drive (RAID0) only has space for 2 backups (poor space planning on my part) before I need to move the files. Normally I backup the DB with BackupExec 10.1d just fine in about 2 hours over the wire at night since no one is in the DB at night. Was wondering if putting my TEMPDB there on (RAID0) would be advisable or not. In SQL 2005 it gets rebuilt each time SQL is restarted so it would seem that ensuring it's on a RAID1 or RAID1+0 might not be as necessary as say the DATA files. Then if I really wanted to I could actually do backups on the I:DATA drive at night and then use TAPE to back that up, and use an automated script to move them off to offline storage once the TAPE backup is done.
For the [model, msdb, master] should they need to be on the I:DATA drive or just leave them on C:OS ? Not sure how much they're actually used.
Also doing some brief testing the Microsoft Dynamics was much slower on the new Server than it was on the original. Odd to me since the new Server is like a McLaren F1 racing a Ford Pinto. The old server is running a single P4 CPU and 6GB RAM
I've set MS SQL 2005 to use 12GB of RAM on the new server so as to leave 4GB for other Server tasks.
I ran the Maintenance Wizard and had it do checks and defrag and index rebuild etc... so not really sure why the speed would be noticeably slower. One thing I did notice is that once a screen query was ran then the next time it was a bit faster but overall I was expecting to see the screens fly by on this new hardware and SQL 2005 but it doesn't really do that.
I've read some of the white papers etc for tuning, but wow I just don't have unlimited hours to do all this analysis, there seem to be hundreds of pages to read on that type of stuff.
