Dino,
If you are using SQL Server 7.0, try either of the following:
a.. Configure the publisher as a trusted publisher to the distributor so
that a password is not required to establish the administrative link between
the publisher and the distributor. To change the security settings for the
publisher, follow these steps:
1.. On the Tools menu, select Replication.
2.. On the Publisher tab, highlight your publisher in the list, and then
click the ellipsis (...) next to that publisher.
3.. In the Replication Agents on the Distribution Log into the Publisher
section, select the By impersonating the SQL Server Agent account on
'{ServerName}' (trusted connection) check box.
-or-
b.. Do not use a login that has a NULL password for establishing the
administrative link between the publisher and the distributor. The
administrative link password can be set in Enterprise Manager. To do this,
follow these steps:
1.. On the Tools menu, select Replication.
2.. On the Distributor tab, under the Administrative link password
section, enter your password in the password and confirm password fields.
If you are not using SQL Server 7.0, please provide more specifics.
Regards,
--
Keith Wilson
This posting is provided "AS IS" without express or implied warranty,
guarantee, or rights.
[quoted text, click to view] "Dino M. Buljubasic" <dino.buljubasic@rivusglobal.com> wrote in message
news:Ovn5b.48851$_5.876089@news1.telusplanet.net...
> I am fetching encrypted password from registry and building a
> connectionString from it but my Open method throws error 18456.
>
> When I fetch an encrypted password from database, everything is fine, the
> problem is when I fetch it from registry. I am using MD5 to encrypte
> passwords.
>
> Any help will be appreciated,
>
> --
> Dino Buljubasic
> Software Developer
>
http://rivusglobal.com >
>