Distributor Properties Error

[Al]

I am currently trying to set up my development machine as a Distributor and I
am encountering the following error when viewing the Distributor Properties.

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS"
and "Latin1_General_CI_AS" in the equal to operation. (.Net SqlClient Data
Provider)

I have been able to go through the Configuration Wizard without any problems
as it seems to create my Distribution database correctly. I have checked the
collation for the Distribution database and it is the same as the database
server (Latin1_General_CI_AS). I have also tried Disabling and reconfiguring
distribution on my machine but without any success.

I am running SQL Server 2005 Developer Edition (SP1) on a Windows 2003 R2
Standard Server. Does anyone have any idea what the cause or solution is to
this problem?

Thank you.

[Hilary Cotter]

What is the collation for the model db and tempdb. There were some problems
in the past with mismatched collations between the user database and tempdb.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

Post by Al
I am currently trying to set up my development machine as a Distributor and I
am encountering the following error when viewing the Distributor Properties.
Cannot resolve the collation conflict between
"SQL_Latin1_General_CP1_CI_AS"
and "Latin1_General_CI_AS" in the equal to operation. (.Net SqlClient Data
Provider)
I have been able to go through the Configuration Wizard without any problems
as it seems to create my Distribution database correctly. I have checked the
collation for the Distribution database and it is the same as the database
server (Latin1_General_CI_AS). I have also tried Disabling and
reconfiguring
distribution on my machine but without any success.
I am running SQL Server 2005 Developer Edition (SP1) on a Windows 2003 R2
Standard Server. Does anyone have any idea what the cause or solution is to
this problem?
Thank you.