Error publishing databases with not-server's default collation

Hello.
While trying to publish any database that uses a collation different from
server's default, I get this error in the step after selecting the articles
to be published:
Error 21423: You do not have sufficient privileges to view the publication
information. Your administrator may need to fix the PAL role on the publisher
for publication 'database_name'.
I've being trying to track down this error for a while now, and I've just
noticed it's related to the collation...
Any ideas about this?
Not sure if it's relevant here, but when I had a case-sensitive server
collation I noticed that passwords of logins became case sensitive on
authentication. I wonder if there is somehow a login/user case sensitivity
issue at work here also? Are the 2 collations the same in this regard or
different (a mixture of _CS and _CI)? Please can you post up the entire
collation names for the circumstance that doesn't work.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||The collations are:
Chinese_Taiwan_Stroke_BIN for the dbs that fails
and:
SQL_Latin1_General_CP1_CI_AS for the dbs that are sucessfuly published.
In any case, the passwords for the accounts are all lowercase...
Thanks for your support,
RODOLFO
"Paul Ibison" wrote:

> Not sure if it's relevant here, but when I had a case-sensitive server
> collation I noticed that passwords of logins became case sensitive on
> authentication. I wonder if there is somehow a login/user case sensitivity
> issue at work here also? Are the 2 collations the same in this regard or
> different (a mixture of _CS and _CI)? Please can you post up the entire
> collation names for the circumstance that doesn't work.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>