I set up the transationsal replication on SQL7.0. It did not work. Here are the messages
1 on Snapshot Agent: The process could not create file Server_namec$MSSQL7REPLdATAFTPServer_namefile_nam e. Error: Access is denied
2. On Log Reader Agent: bi replication transaction are available
3. Disribution Agent: The initial snapshot for publication "DB_Name" is not yet available.
Thank you for your help
My shop is thinking of migrating from NT4 to Win2K. Is anyone running SQL7 on Windows 2000 (which edition?)? How's you're experience been? Anyone hear any anecdotes of particular things that don't work (well)?
Thanks for your input.
Hi,
Need to set up replication between a server in our corporate network and another outside our network. Both are NT 4 servers running SQL7 and I am instructed to configure merge replication on both ends. My questions are: Is it possible to achieve this by running tcpip(read somewhere that I would need to run MPR to load the net libraries) and configuring the firewall to allow tcp/ip on the ports we are running SQL on between the two servers?
Please help as this is very urgent.
Regards
Kunta
Hi, guys
I have an urgent problem in replication.
Yesterday I set up a Transaction replication with 1 publication
Server A (publisher)(push)(SQL 7)
Server B (distributor and subscriber)(SQL 7)
The replication was succesful and the suscriber can get correct data.
This morning I found the Red sigh in replication mornitor/miscellaneous agents.The error message is:
"The job failed. Unable to determine if the owner (domain nameuser ID) of job Agent history clean up: distribution has server access (reason: Could not obtain information about Windows NT group/user 'domain name'. [SQLSTATE 42000] (Error 8198))."
I tried to use the 'disable publishing and distribution wizard' to disable this replication, but it did not finish and the screen jusr freeze. I used the task manager to end the task.
then I check the replication monitor, the publication was gone but the RED sigh still there.
I tried to use sp_dropdistpublisher to drop a Publisher
but it said "the server A is not a distributor"
I tried to use sp_dropdistributiondb to delete the distribution database.
but it said "Could not drop the distribution database 'distribution'.
This distributor database is associated with a Publisher."
I tried to use sp_dropdistributor to remove the Distributor .
but it said "Could not drop the Distributor 'Server B'.
This Distributor has associated distribution databases."
Any suggestion? Thank you in advance.
Theresa
I would like to set up one way Merge replication. The only way I was able to do this was to remove the triggers off the tables manually. There seems like there should be a better way.
View 2 Replies View RelatedTrying to remove replication i get the error message..
Error 2812: Could not find stored procedure 'distribution.dbo.MSdrop_snapshot_dirs
Any idea ?
Thanks.
Andrew Ratley MCDBA.
Hi there SQLTEAM
I have a situation; one of our clients requested us to start investigating SQL replication.
The Publisher would be the client's server running SQL7
And we would be the subscriber running SQL 2005
Can this be done?
Are there any pro's and con's on even trying replications between SQL 2005 and SQL7
If this is possible could someone be so kind as to point me to a step by step guide and how to achieve this.
I'm attemting to replicate from a SQL7 box to SQL2000.
The snapshot works fine, but it fails when it tries to push the subscription to the SQL2000 box with a trust error (I don't recall the exact message). I noticed that it fails when Enterprise Mgr is configured as: "Tools/Replication/Configure Publishing, Subscribers and Distribution", Subscriber Tab, "Impersonating SQL Service Agent". It works if I change to "SA".
This is only the case when we replicate from SQL7 to SQL2K. SQL7 to SQL7 works fine with "Impersonating". Has anybody seen this behavior? Any workarounds, other than using SA?
I'm attemting to replicate from a SQL7 box to SQL2000.
The snapshot works fine, but it fails when it tries to push the subscription to the SQL2000 box with a trust error (I don't recall the exact message). I noticed that it fails when Enterprise Mgr is configured as: "Tools/Replication/Configure Publishing, Subscribers and Distribution", Subscriber Tab, "Impersonating SQL Service Agent". It works if I change to "SA".
This is only the case when we replicate from SQL7 to SQL2K. SQL7 to SQL7 works fine with "Impersonating". Has anybody seen this behavior? Any workarounds, other than using SA?
Hi all,
i think i have serious problem. i have almost 20,000 rows with the following conflict on a table (generated by merge replication over a period of around 3 weeks) :
'The row was updated at 'SubscriberServer3.DatabaseA' but could not be updated 'at 'PublicationServer1.DatabaseA'. Metadata mismatch'
i have 20 remote subscribers & 1 publisher. The above message originates from practically everywhere.
Besides dropping(not practical at the moment) & recreating replication to get rid of them, what else can i do to resolve this problem?? Do i have to resolve this problem row by row?? i'm at my wit's end. Please help!!
Thanx in advance.
I have a database, whose size is 1600MG. That database needs to be copied to the other server. But, the server does not have enough space (1600MB) for the database since the other databases also share the space. Therefore, I transfered the database to a database in that server whose size was set up 700MB the server. The table schema and data were transered successfully. But, when I tried to replicate the tranfered data to another database. The transfered database did not show all of the tables which were shown when I had queried them against that transfered database.
My question is that why it did not show alll of the tables for me to pick up for replication. Does that have something to do with the transfered database? In other word, if I set up the same size of database for the transfered database, it would have worked. Right?
I'm pretty new to the whole replication method. I've been making c++ programs to replicate the databases using manual odbc classes. I'm ready to try something new if it would work for me.
I have multiple databases. Basically I have a bunch of computers, each with a SQL server. These databases are the "publishers" due to the fact they are the databases that receiving new data. All of the publishers then upload their new information to the main SQL server. This seems not an issue but the trick is when the publisher uploads the information to the new SQL server, it then deletes the uploaded information from itself. This is basically the same model for everything I do. I was hoping someone might be able to tell me how to do this with replication/triggers and what versions of SQL Server 2005 that I would need to put on each of the publishers and subscriber (main).
Thank you,
Jeremy
hi guys :( ive searched on all the topics here about replication. but now i am wondering what windows xp settings do i have to edit? i read something about dcom settings and changing permissions. what is the RIGHT way to share a file or whatever because the schema cannot be accessed for some reason. i need a whole list of things to do because things are not working out after i read the tutorials on other sites. please someone help me.
basically i need to have two servers that need to be replicating each other. i realized that the instances have to be named so i am just totally confused. ill even let anyone connect remotely to help me out if they want. or explaining will do fine. please! thanks guys!
happy holidays!
Hi there, the subject says it all.
I have two databases on one server. I want to replicate 1 table from one Dbase to the other. Can it be done? Am running SQL 6.5 on NT 4
Gordon
I want to get notice by netsend, email or any other methods
when replication doesn't work or malfunction.
Does anyone know how to do this or any other solution you use for this kind of issue?
Thank you..
I have maually deleted the Database.LDF file by stopping the SQL Server. When i start the SQL Server, merge replication which was configured for the database does not work. How do i fix this problem.
Thanks in advance.
Regards,
Venu.
Hi
I'm developing a scientific appliation - to forecast the spread of disease. The algorithm has been designed such that different subpopulations reside on separate computers.
The model uses the same set of data repeatedly, and only returns a small signature that reflects the appropriateness of a particular set of parameters.
The model does however change, and I'm looking for a way to roll out this model (which only contains T-SQL, CLR assemblies and service broker code).
I have considered setting up a database on each computer which has the 'data' files which are static, and a separate database which contains the algorithm which can be amended.
Could one then detach the algorithm database making the new version that can then be rolled out (by attaching it to each computer used)?
Is this the best practice? Does anyone have a suggestion as to how to do this?
Go well
Greg
Hello!
I have a problem with creating Merge replication between two instances of MSDE 2000. In the article http://support.microsoft.com/kb/324992/, published by Microsoft, described, that it is possible.
I am creating Merge Publication at MSDE 2000, with Distributor and Publisher configured at same machine, with options "Allow Pull Subscriptions" and "Allow Anonymous Subscriptions". There is no problem with creating of Publication. Even snapshot generation finishes successfully. Also I create a login with SQL Server Authentication and "System Administrators" database role at the publisher in order to connect to it from Subscriber.
The problem occurs, when creating anonymous pull subscription to this publication at another instance of MSDE. During initial synchronization an error occurs:
The process could not connect to Distributor '<publisher_server_name>'. Login failed for user '<login_created_at_publisher>'. Reason: Not associated with a trusted SQL Server connection. The step failed.
Although I didn't use Windows Authentication at all, so Subscriber doesn't need to connect to Distributor using trusted SQL Server connection.
What is a problem and how can I workaround?
Note: The same works correctly, if MS SQL Server used as a Publisher instead of MSDE.
Please, help!
I can provide publication and subscription creation scripts, if required.
Hi,
we have developped an application on pdaphone. we try to use merge replication between our sql server 2000 sp4 and sql Ce 3.0 via GPRS . Sometime that works very fine . Sometime it's a nightmare !!! nothing work . we have multiple error....
can someone tell me, what are the rules to make it work ?
can someone tell me, if it really works fine ?
thanks
I have been evaluating merge replication, 'push' subscription on SQL Server 2014. If the default resolver is used (I refer to @article_resolver parameter of sp_addmergearticle), all seems to work as expected. However if I use "Microsoft SQL Server Subscriber Always Wins Conflict Resolver" (or any other MS standard resolver for that matter), if the Subscriber is on a different machine, the merge agent invariably gives the following error: "The process could not initialize <resolver_name>. Verify that the component is registered correctly."
This does not happen if the Subscriber is on the same machine as the Publisher and Distributor.
The problem seemed to exist in SQL Server 2008 according to some posts but it has been apparently fixed since then. I've tried the following:
- @partition_options = 0, as was suggested somewhere.
- Copied ssrpub.dll (the resolver dll) to the Subscriber machine (should not really matter as this is 'push' subscription?)
- Registered ssrpub.dll with regsvr32 on the Publisher/Distributor machine.
I've also run sp_enumcustomresolvers on the Publisher machine, and it happily showed all standard resolver, including the "Microsoft SQL Server Subscriber Always Wins Conflict Resolver".
Another thought is, I'm using SQL Server Express as the Subscriber (on the remote machine). Perhaps it does not support custom resolvers? (I'm using the full SQL Server in the 'local subscriber' variant, which does work OK as I mentioned before).
Note also that if I create a new publication via SSMS, the Resolver tab of the Article Properties dialog is empty, i.e. it does not list any resolver. The same tab contains the full list of resolvers though, if opened for an existing publication.
I have a mobile device application using mobile sql 2005 replicating with sql 2000 in a x86 environment. This works fine!
I'm having issues getting this to work under Windows Server 2003 X64.
I've got all the components installed under the X64 environment including CLR 2.0 X64 and the mobile sql tools. the but when I run the Configure Web Synchronization Wizard I get the following error. SQL Server 2005 Mobile Edition Server Tools were not found on the IIS server. Run the SQL Server 2005 Mobile Edition Server Tools installer....
My question is: Were do I get the X64 version of these tools?
sqlce30setupen.msi
sql2Ken@P4.msi
The SQL environment is X86 as follows: SQL2000 SP4
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Any help would be much appreciated!
How can I copy a SQL 7 database from one server to another? Please tell me all the ways because I've tried the obvious and it doesn't work. (backup and restore - won't go from one server to another, DTS transfer object Wizard - does a whole pile of errors and doesn't do stored proceedures and trigures). Thanks for help in advance. Also, what is the email address to post to the listserv and where is the FAQ for SQL7? Most of my listserv's tell you where to post right at the bottom of the digest I get - any chance you guys would do that with this list? Thanks again.
View 6 Replies View RelatedHi there,
After installing SP2 we encounter a problem with MMC. When selecting a DB we recieve a RunTime error? And the DB items/properties are not shown.
Is there anyone with the same problem and knows how to fix this? I search the MS site for more information but there is nothing on it.
Danny
Is MS SQL 7.0 have any difference/incompatibility problem with the BackOffice's SQL 7.0?
anybody can clarify this to me please... tq!
I am going to install SQL7.0 on the current NT4.0 with SQL6.5 on it by uninstalling SQL6.5 first and then installing (not upgrading through Wizard) SQL7.0.
Here are the questions I need help with:
1. Should I convert the database after the installation of SQL7.0 or directly restore the SQL6.5 databases backup?
2. If I need to convert the databases, How and in what way?
3. Which way is better upgrade or installation?
Thank you ahead of time
John
I am looking for documentation/information on how to configure SQL7 so that I
can use SMTP for delivering e-mail.
I have other applications which use SMTP for delivering our e-mail.
I don't have Exchange. Internally we use GroupWise for our mail system.
Thanks in advance!!!
Current system 2 x 500mhz pIII 512MB ram, System mirrored and data raid 5 30GB made from 3 disks. All server is running in CA TNG. an Asset management DB and Software Delivery database. But the poor server runns most of the time at 100% 65% being used by SqlServer process. Does/Can anyone recommend any tweaks upgrades that may let the server take a breath in and out ie will more memory speed thing up faster processors or more disk.
Thanks
Nigel
Hi,
i'm brand new in the sql server world so maby this is an easy problem.
I have to get data from AS/400 to SQL7. I've created a package with a client acces odbc driver and an sql driver which transfers the data of an entire table. When i execute this it works fine.
Now i want to shedule this (shedule package). When i start this job it doesn't work.
This is the error i get:
DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSDataPumpTask_1 DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147008507 (80074005) Error string: Unspecified error Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts.hlp Help context: 1100 Error Detail Records: Error: -2147008507 (80074005); Provider Error: 0 (0) Error string: Unspecified error Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts.hlp Help context: 1100 Error: -2147467259 (80004005); Provider Error: 5 (5) Error string: [IBM][Client Access ODBC Driver (32-bit)][DB2/400 SQL]Communication link failure. COMM RC=0x5 Error source: Microsoft OLE DB Provider for ODBC Drivers Help file: Help context: 0 DTSRun OnFinish: DTSStep_DTSDataPumpTask_1 DTSRun: Package execution complete. Process Exit Code 1. The step failed.
on the server i've installed client access as well and created the same odbc driver (with the same name). But it still doesn't work.
Can anybody help me please??
I have a database on a 6.5 server but wish to upgrade this database to a sql 7 database. But I would like to test this first on another server which is a sql 7 server. Is it possible to restore a 6.5 backup to a SQL server 7.0 server?
Thanks in advance..
Is there a way to list all the tables in each of the filegroup
in a database. I have a database with 7 filegroups and would like
to have a list of tables in each filegroup
Sp_helpfilegroup gives you list of filegroups and the names of files
hai,
i unable to import/export from sql7.0 database to text file in windows 98 system . can anybody help me ?
I recall seeing something about an extra / additional / enhanced / second version of Help that is available after installing SQL7 SP2. Does anyone know anything about it, such as where to find it? Thanks.
View 1 Replies View RelatedI need some documentation on how to trouble shoot clustering SQL7EE. I have setup the cluster and looks like it is working but I missed somthing. When I test a failover by pulling the Network cable to the main network not the heartbeat network both boxes lock up. I can failover by powering down one box and using the MSCluster Admin. I am using NT40 6a on Dell PowerEdge 2400 and PowerValut 211s
View 3 Replies View Related