Viewing 15 posts - 1 through 15 (of 25 total)
logged this with microsoft a while ago:
not sure what the solution is as the replicated machine is clustered using SteelEye Lifekeeper and the network name is the machinename.
April 1, 2014 at 8:13 am
Hi Can some one assist,
I managed to find a few spare mins today looking into this problem.
I zoned in that the problem is relating to the sp_helpqreader_agent SP, and is...
March 25, 2014 at 10:50 am
SQL version is 10.50.4279 for the publisher
The distributer is 10.50.4000.
The SQL Database that is replicated is running in SQL 2000 Compatibility Mode and was upgraded recently from SQL 2000(replication was...
January 27, 2014 at 5:11 am
I setup replication on a test server with the same settings as live and found no error generating the scripts but did find that the link server error also occurred...
January 22, 2014 at 7:25 am
Hi Andreas,
I've checked the Servernames they are all correct. We do use aliases on our clustered environments etc but that shouldn't cause this problem as replication is working correctly. It's...
January 21, 2014 at 9:05 am
I think my problem is linked to the linked server DATA ACCESS, if we can get to the bottom of that then it should work as the generate scripts tries...
January 21, 2014 at 8:59 am
Hi Andreas, Thanks for the post, I ran the proc mentioned and it returns the name of the distribution server on the publisher, on the distribution server every thing is...
January 21, 2014 at 7:54 am
The second problem, when I go to test the connection of the linked server call repl_distributor which is setup by the distributer it is failing to connect properly ie ...
January 21, 2014 at 7:28 am
Does this have to be uploaded as an Excel file?, why not try .csv or .txt and then it should pull through?
January 21, 2014 at 5:48 am
FIXED!!!
Perseverance and we get there!.
The fix was as follows in my case:
Could connect using the [servername]\instancename but not using its alias.
SQL 2008 R2 Standard Edition x64 version
1) Open SQL...
July 4, 2013 at 4:53 am
You will need to read data from the COM+ Catalog:
http://msdn.microsoft.com/en-gb/library/windows/desktop/ms679168(v=vs.85).aspx
"The COM+ catalog provides a layer of abstraction over the actual details of where and how COM+ configuration data...
July 3, 2013 at 3:08 am
I encountered a similar problem and had some fun and thought it may help others.
When checking the endpoints check the names on both servers(or add the witness or any other...
December 7, 2012 at 3:15 am
after monitoring the above server for several weeks and with the addition of the monitoring i placed, this problem wasnt as easy or as straight forward as simply saying upgrade...
December 4, 2012 at 8:20 am
to follow up the data file for the database is 8.6GB but the log file is 2 MB as it is in Bulk-Logged mode and the Torn page detection and...
November 14, 2012 at 2:23 am
Fair points, Thanks for the responses.
I'll have to rework the proposals and see whether the customers are happy to stump up extra cash, the money parts usually the stumbler for...
October 19, 2012 at 5:43 am
Viewing 15 posts - 1 through 15 (of 25 total)