I have read many of the postings on the 18483 error, but I must be
missing something because I can't get it to work and I have been trying
for days. I have also read about this topic in BOL which says the same
thing as the postings.
Local replication has been working for almost a year, but I ran into
problems when I wanted to add a remote site to the process. I
therefore decided to disable replication and reenable it to both sites.
I decided to get it working properly to the local server and felt that
I could then setup it up for the remote.
The problem that I am having is the old 'Error 18483
'distributor_admin' is not setup for remote access. I don't understand
why I am receiving this error since I just disabled replication and
immediately tried to reenable it. (NOTE: I have changed the alias
names for easier recognition since the original setup, although I still
point to the ip addesses of the boxes both local and remote.) I have
since read a posting which suggest to alias to the computer name which
I have done.
BOL says that I need to add 'distributor_admin' as a remote login even
though the publisher and the distributor are the same box. I have run
the 'sp_addremotelogin' stored procedure with several permutations i.e.
Local and Remote user 'distributor_admin', Local user
'distributor_admin' Remote user an admin account on the server and vice
versa. If I use 'distributor_admin' as both the Local and Remote user
I still received the 18483 error. When I used 'distributor_admin' as
Local and an admin account for remote, I receive an error that I am
using the wrong password. I know the password of the admin account
because it is mine. I have also set the 'distributor_admin' account
password to match mine via the 'sp_changedistributor_password' stored
procedure. The same happens if 'distributor_admin' is remote and an
admin account is local.
Does anyone have an idea of what I am missing?
Are you running SQL 2000? If so, I think you have misread BOL. BOL states
"The connection between a Publisher and a remote Distributor is a hybrid of
a linked server and remote server. The connection uses the login
distributor_admin. At the remote Distributor, the Publisher can be
configured to be either trusted (no password is required for the
distributor_admin login) or non-trusted (a password is required). It is
recommended that you use a non-trusted connection for the Publisher
connection to the Distributor, requiring a distributor_admin password."
They are referring to the Administrative Link password here - not the
distributor_admin account.
If I were you I would disable replication, if the distributor_admin account
remains, delete it, if repl_distributor remails as a remote server, delete
it.
Then try to enable replication again.
Hilary Cotter
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
<pw@.indii.com> wrote in message
news:1108397908.962930.70700@.g14g2000cwa.googlegro ups.com...
> I have read many of the postings on the 18483 error, but I must be
> missing something because I can't get it to work and I have been trying
> for days. I have also read about this topic in BOL which says the same
> thing as the postings.
> Local replication has been working for almost a year, but I ran into
> problems when I wanted to add a remote site to the process. I
> therefore decided to disable replication and reenable it to both sites.
> I decided to get it working properly to the local server and felt that
> I could then setup it up for the remote.
> The problem that I am having is the old 'Error 18483
> 'distributor_admin' is not setup for remote access. I don't understand
> why I am receiving this error since I just disabled replication and
> immediately tried to reenable it. (NOTE: I have changed the alias
> names for easier recognition since the original setup, although I still
> point to the ip addesses of the boxes both local and remote.) I have
> since read a posting which suggest to alias to the computer name which
> I have done.
> BOL says that I need to add 'distributor_admin' as a remote login even
> though the publisher and the distributor are the same box. I have run
> the 'sp_addremotelogin' stored procedure with several permutations i.e.
> Local and Remote user 'distributor_admin', Local user
> 'distributor_admin' Remote user an admin account on the server and vice
> versa. If I use 'distributor_admin' as both the Local and Remote user
> I still received the 18483 error. When I used 'distributor_admin' as
> Local and an admin account for remote, I receive an error that I am
> using the wrong password. I know the password of the admin account
> because it is mine. I have also set the 'distributor_admin' account
> password to match mine via the 'sp_changedistributor_password' stored
> procedure. The same happens if 'distributor_admin' is remote and an
> admin account is local.
> Does anyone have an idea of what I am missing?
>
|||Hilary,
Thanks for your response it was very helpful. Also I did read the BOL
about linked servers, but with my limited knowledge I didn't understand
it the way that a more experienced person might. I was going to delete
the linked server and recreate it, but I didn't know what the affect
would be on my production environment.
I followed your advice and deleted the distributor_admin login and the
repl_distributor remote server. I also ran sp_removedbreplication and
then tried to reestablish it. I again got the 18483 remote login
error. DO I NEED TO RESTART THE SERVICE IN ORDER FOR MY CHANGES TO
FULLY TAKE AFFECT?
Thanks,
Peter
|||I re-read BOL, and it is confusing. Now I am not sure if they were referring
to the administrative link password after all. I am going to try to research
this.
I would try the restart - but I am not sure if this is going to fix it.
Someone in the past had similar problems to you and he/she deleted this
account, and then recreated it as a standard SQL Server login, assigned it a
password and then put it in the System Administrator group. It worked for
them. I tried this myself and it also worked.
You might want to try this as a last resort. I would advise you to call PSS
for their help on this one.
Hilary Cotter
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
<pw@.indii.com> wrote in message
news:1108477637.970068.101100@.o13g2000cwo.googlegr oups.com...
> Hilary,
> Thanks for your response it was very helpful. Also I did read the BOL
> about linked servers, but with my limited knowledge I didn't understand
> it the way that a more experienced person might. I was going to delete
> the linked server and recreate it, but I didn't know what the affect
> would be on my production environment.
> I followed your advice and deleted the distributor_admin login and the
> repl_distributor remote server. I also ran sp_removedbreplication and
> then tried to reestablish it. I again got the 18483 remote login
> error. DO I NEED TO RESTART THE SERVICE IN ORDER FOR MY CHANGES TO
> FULLY TAKE AFFECT?
> Thanks,
> Peter
>
|||Hilary,
I appreciate your comments about BOL. With my limited experience I
felt that I was chasing my tail.
Also I did restart the SQL Server service which cleared up some
problems, but in the end I received the imfamous 'Error 18483'. I will
try your suggestion and manually delete and recreate the
'distributor_admin' login and add it to the SA group.
I will let you know if this works.
Peter
|||Peter,
Yo tena el mismo problema...
Solucin:
http://support.microsoft.com/default...b;en-us;818334
y exec sp_helpserver
Recuerdos
<pw@.indii.com> escribi en el mensaje
news:1108560299.305220.159700@.l41g2000cwc.googlegr oups.com...
> Hilary,
> I appreciate your comments about BOL. With my limited experience I
> felt that I was chasing my tail.
> Also I did restart the SQL Server service which cleared up some
> problems, but in the end I received the imfamous 'Error 18483'. I will
> try your suggestion and manually delete and recreate the
> 'distributor_admin' login and add it to the SA group.
> I will let you know if this works.
> Peter
>
|||Hilary,
I am sorry that I missed you at the last NYC SQL Server User Group
meeting. I just became a member.
On another note, I would like to tell you the outcome of my problem. I
was having problems with my replication setup and decided to redue it.
Lucky for me that I made a copy of the original replication script.
All of the attempts described in this posting didn't work for me, but I
learned a lot about Transact-SQL and using stored procedures. As a
last resort, I edit the oringinal script and managed to get replication
setup again. It took me a few iterations, but it worked.
I don't know why I could setup replication via Enterprise Manager, but
I wanted to let you know this because you assist many people.
Thanks.
Showing posts with label distributor_admin. Show all posts
Showing posts with label distributor_admin. Show all posts
Wednesday, March 7, 2012
distributor_admin not a local user?
The distribution server for my publisher is a live server, and the publisher is a test server that I wish to make it's own distributor. Whenever I try to select it as it's own distributor, I get an error that "distributor_admin" is not a local user. How
do I go about fixing this?
Thanks for your help,
Stephen
Where is your Distributor? Is it on the Publisher?
Is the Subscriber in the same domain as the Publisher?
How did you configure your Subscriber? Can you go to
Tools-Replication-Configure Publishers, Subscribers, Distributors, click on
the Subscribers tab, and click on the browse button (the three ellipses) to
the right of your server name?
Make sure you are using Impersonate the SQL Server Agent account on the
Publisher if you are in the same domain.
"Stephen A." <stephen.accetta@.honeywell.com> wrote in message
news:B6D49A36-D4D7-4D51-85B5-0BDFEA948056@.microsoft.com...
> The distribution server for my publisher is a live server, and the
publisher is a test server that I wish to make it's own distributor.
Whenever I try to select it as it's own distributor, I get an error that
"distributor_admin" is not a local user. How do I go about fixing this?
> Thanks for your help,
> Stephen
|||>>Where is your Distributor? Is it on the Publisher?
No. The distributor is machine A, the publisher is machine B, I wish to
make machine B it's own distributor
Same segment, but the subscriber (Machine C) is not on any domain, I
registered it by IP address. I'm not having any problems with the
subscriber, merely with making the publisher it's own distributor.
click on
ellipses) to
I'll check, but I think so.
the
I already set up a replication account, I merely wish to make the
publisher it's own distributor.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||The solution is easy!!! Register servers to SQL by using their names
or aliasses. Do not use ip numbers.
do I go about fixing this?
Thanks for your help,
Stephen
Where is your Distributor? Is it on the Publisher?
Is the Subscriber in the same domain as the Publisher?
How did you configure your Subscriber? Can you go to
Tools-Replication-Configure Publishers, Subscribers, Distributors, click on
the Subscribers tab, and click on the browse button (the three ellipses) to
the right of your server name?
Make sure you are using Impersonate the SQL Server Agent account on the
Publisher if you are in the same domain.
"Stephen A." <stephen.accetta@.honeywell.com> wrote in message
news:B6D49A36-D4D7-4D51-85B5-0BDFEA948056@.microsoft.com...
> The distribution server for my publisher is a live server, and the
publisher is a test server that I wish to make it's own distributor.
Whenever I try to select it as it's own distributor, I get an error that
"distributor_admin" is not a local user. How do I go about fixing this?
> Thanks for your help,
> Stephen
|||>>Where is your Distributor? Is it on the Publisher?
No. The distributor is machine A, the publisher is machine B, I wish to
make machine B it's own distributor
Same segment, but the subscriber (Machine C) is not on any domain, I
registered it by IP address. I'm not having any problems with the
subscriber, merely with making the publisher it's own distributor.
click on
ellipses) to
I'll check, but I think so.
the
I already set up a replication account, I merely wish to make the
publisher it's own distributor.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||The solution is easy!!! Register servers to SQL by using their names
or aliasses. Do not use ip numbers.
distributor_admin Issue....But different than normal
I am having the common "distributor_admin does not exist" error when
trying to set up a machine as its own distributor. (First time after
setting up about 200 distributors). I get this whether I'm doing it
remotely, or on the machine itself.
The wrinkle is that the login "distributor_admin" does not exist at all
on the potential publisher (who, again, is going to be its own
distributor).
Do I need to reinstall MS-SQL to get that login created? Or can I do
it by hand somehow?
Or am I barking up the wrong tree?
Thank you!
-Joseph
What happens when you do a select @.@.servername?
Does it match what you get when you issue a xp_cmdshell 'hostname'?
if not you need to do the following
sp_dropserver @.server='oldServername'
sp_addserver @.server='NewServerName', @.local='LOCAL'
Then restart SQL Server.
Hilary Cotter
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
"Joseph" <josephsheppard@.gmail.com> wrote in message
news:1168894392.883101.309200@.v45g2000cwv.googlegr oups.com...
>I am having the common "distributor_admin does not exist" error when
> trying to set up a machine as its own distributor. (First time after
> setting up about 200 distributors). I get this whether I'm doing it
> remotely, or on the machine itself.
> The wrinkle is that the login "distributor_admin" does not exist at all
> on the potential publisher (who, again, is going to be its own
> distributor).
> Do I need to reinstall MS-SQL to get that login created? Or can I do
> it by hand somehow?
> Or am I barking up the wrong tree?
> Thank you!
> -Joseph
>
|||Thanks, Hilary...There certainly was a difference...
I followed your instructions, and I'm going to take another stab at
setting distribution up.
You are the man! I'm going to have my boss order your book...
-Joseph
Hilary Cotter wrote:[vbcol=seagreen]
> What happens when you do a select @.@.servername?
> Does it match what you get when you issue a xp_cmdshell 'hostname'?
> if not you need to do the following
> sp_dropserver @.server='oldServername'
> sp_addserver @.server='NewServerName', @.local='LOCAL'
> Then restart SQL Server.
> --
> Hilary Cotter
> 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
>
> "Joseph" <josephsheppard@.gmail.com> wrote in message
> news:1168894392.883101.309200@.v45g2000cwv.googlegr oups.com...
trying to set up a machine as its own distributor. (First time after
setting up about 200 distributors). I get this whether I'm doing it
remotely, or on the machine itself.
The wrinkle is that the login "distributor_admin" does not exist at all
on the potential publisher (who, again, is going to be its own
distributor).
Do I need to reinstall MS-SQL to get that login created? Or can I do
it by hand somehow?
Or am I barking up the wrong tree?
Thank you!
-Joseph
What happens when you do a select @.@.servername?
Does it match what you get when you issue a xp_cmdshell 'hostname'?
if not you need to do the following
sp_dropserver @.server='oldServername'
sp_addserver @.server='NewServerName', @.local='LOCAL'
Then restart SQL Server.
Hilary Cotter
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
"Joseph" <josephsheppard@.gmail.com> wrote in message
news:1168894392.883101.309200@.v45g2000cwv.googlegr oups.com...
>I am having the common "distributor_admin does not exist" error when
> trying to set up a machine as its own distributor. (First time after
> setting up about 200 distributors). I get this whether I'm doing it
> remotely, or on the machine itself.
> The wrinkle is that the login "distributor_admin" does not exist at all
> on the potential publisher (who, again, is going to be its own
> distributor).
> Do I need to reinstall MS-SQL to get that login created? Or can I do
> it by hand somehow?
> Or am I barking up the wrong tree?
> Thank you!
> -Joseph
>
|||Thanks, Hilary...There certainly was a difference...
I followed your instructions, and I'm going to take another stab at
setting distribution up.
You are the man! I'm going to have my boss order your book...
-Joseph
Hilary Cotter wrote:[vbcol=seagreen]
> What happens when you do a select @.@.servername?
> Does it match what you get when you issue a xp_cmdshell 'hostname'?
> if not you need to do the following
> sp_dropserver @.server='oldServername'
> sp_addserver @.server='NewServerName', @.local='LOCAL'
> Then restart SQL Server.
> --
> Hilary Cotter
> 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
>
> "Joseph" <josephsheppard@.gmail.com> wrote in message
> news:1168894392.883101.309200@.v45g2000cwv.googlegr oups.com...
'distributor_admin' is not defined as a remote login at the server
We have set up one of the clustered instance as a remote distributor and
replication has been working properly. However, on the event log of the
active node, I saw the following error appeared every few minutes:
Could not connect to server 'REPLICATIONSQL\DISTRIBUTOR' because
'distributor_admin' is not defined as a remote login at the server. Verify
that you have specified the correct login name. [CLIENT: 10.1.1.28].
REPLICATIONSQL\DISTRIBUTOR is the name of the clustered instance configured
as a remote distributor and it is running on active node; the client
(10.1.1.28) is the passive node of the cluster. our environment is windows
2003 and sql server 2005 with sp2.
I wonder if anyone has any idea how to get rid of this error from my server.
Thanks in advance.
Zack.
I wonder if it is a managed news group by Microsoft, if not, someone knows
the managed news group since I was told that it is a managed group and
Microsoft will reply every post?
thanks for your kind reply because I really need to fix this error and don't
want to pay MS for this kind of error. We have paid too much to MS already
for support.
Zack.
m
"dp" wrote:
> We have set up one of the clustered instance as a remote distributor and
> replication has been working properly. However, on the event log of the
> active node, I saw the following error appeared every few minutes:
> Could not connect to server 'REPLICATIONSQL\DISTRIBUTOR' because
> 'distributor_admin' is not defined as a remote login at the server. Verify
> that you have specified the correct login name. [CLIENT: 10.1.1.28].
> REPLICATIONSQL\DISTRIBUTOR is the name of the clustered instance configured
> as a remote distributor and it is running on active node; the client
> (10.1.1.28) is the passive node of the cluster. our environment is windows
> 2003 and sql server 2005 with sp2.
> I wonder if anyone has any idea how to get rid of this error from my server.
> Thanks in advance.
> Zack.
>
replication has been working properly. However, on the event log of the
active node, I saw the following error appeared every few minutes:
Could not connect to server 'REPLICATIONSQL\DISTRIBUTOR' because
'distributor_admin' is not defined as a remote login at the server. Verify
that you have specified the correct login name. [CLIENT: 10.1.1.28].
REPLICATIONSQL\DISTRIBUTOR is the name of the clustered instance configured
as a remote distributor and it is running on active node; the client
(10.1.1.28) is the passive node of the cluster. our environment is windows
2003 and sql server 2005 with sp2.
I wonder if anyone has any idea how to get rid of this error from my server.
Thanks in advance.
Zack.
I wonder if it is a managed news group by Microsoft, if not, someone knows
the managed news group since I was told that it is a managed group and
Microsoft will reply every post?
thanks for your kind reply because I really need to fix this error and don't
want to pay MS for this kind of error. We have paid too much to MS already
for support.
Zack.
m
"dp" wrote:
> We have set up one of the clustered instance as a remote distributor and
> replication has been working properly. However, on the event log of the
> active node, I saw the following error appeared every few minutes:
> Could not connect to server 'REPLICATIONSQL\DISTRIBUTOR' because
> 'distributor_admin' is not defined as a remote login at the server. Verify
> that you have specified the correct login name. [CLIENT: 10.1.1.28].
> REPLICATIONSQL\DISTRIBUTOR is the name of the clustered instance configured
> as a remote distributor and it is running on active node; the client
> (10.1.1.28) is the passive node of the cluster. our environment is windows
> 2003 and sql server 2005 with sp2.
> I wonder if anyone has any idea how to get rid of this error from my server.
> Thanks in advance.
> Zack.
>
distributor_admin error
Hi,
When i try to configure publisher, distributor, subscriber on the same remote server, i am getting the following error:
SQL Server Enterprise Manager could not configure '90.168.XX.XXX' as the distributor for '90.168.xx.xxx'
Error: 18483: could not connect to server 'different name' beacuse 'distributor_admin' isn ot defined as a remote login at the server
I changed the MSSQLSERVER and the SQL Server Agent and a dependant file to run froma domain account, i gave that domain account all the privileges on the database and the master database aswell. but i keep getting the error.
Also why is the error showing diffetent server name than the '90.168...' name?
Will i have problems later if i donot set up alias names rather than ip address. If so, how can i set up alias names for SQL Server's
I am quite new to all this, any detailed answer could really help.
thanks
stummalaGot that fixed by re registering the server name to the result of @.@.SERVERNAME
When i try to configure publisher, distributor, subscriber on the same remote server, i am getting the following error:
SQL Server Enterprise Manager could not configure '90.168.XX.XXX' as the distributor for '90.168.xx.xxx'
Error: 18483: could not connect to server 'different name' beacuse 'distributor_admin' isn ot defined as a remote login at the server
I changed the MSSQLSERVER and the SQL Server Agent and a dependant file to run froma domain account, i gave that domain account all the privileges on the database and the master database aswell. but i keep getting the error.
Also why is the error showing diffetent server name than the '90.168...' name?
Will i have problems later if i donot set up alias names rather than ip address. If so, how can i set up alias names for SQL Server's
I am quite new to all this, any detailed answer could really help.
thanks
stummalaGot that fixed by re registering the server name to the result of @.@.SERVERNAME
distributor_admin
Hi ,
In my connection string as below , i have specified to use the user "sa"
but i am not sure why the error msg says login fail for distributor_admin
the server that i am connecting to is set up as a distirbutor on a local
publisher
strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
=master;uid=sa;pwd=XXXX"
appreciate any advice
tks & rdgs
Hi,
is there such a so called default password for this distributor_admin user ?
i can see that in the remote login , the sa is being mapped to the
distributor_admin when i tried to change it , it can be changed but once i
come it again it's still being mapped to distributor_admin
appreciate if someone could help
tks & rdgs
"maxzsim" wrote:
> Hi ,
> In my connection string as below , i have specified to use the user "sa"
> but i am not sure why the error msg says login fail for distributor_admin
> the server that i am connecting to is set up as a distirbutor on a local
> publisher
> strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
> =master;uid=sa;pwd=XXXX"
> appreciate any advice
> tks & rdgs
In my connection string as below , i have specified to use the user "sa"
but i am not sure why the error msg says login fail for distributor_admin
the server that i am connecting to is set up as a distirbutor on a local
publisher
strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
=master;uid=sa;pwd=XXXX"
appreciate any advice
tks & rdgs
Hi,
is there such a so called default password for this distributor_admin user ?
i can see that in the remote login , the sa is being mapped to the
distributor_admin when i tried to change it , it can be changed but once i
come it again it's still being mapped to distributor_admin
appreciate if someone could help
tks & rdgs
"maxzsim" wrote:
> Hi ,
> In my connection string as below , i have specified to use the user "sa"
> but i am not sure why the error msg says login fail for distributor_admin
> the server that i am connecting to is set up as a distirbutor on a local
> publisher
> strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
> =master;uid=sa;pwd=XXXX"
> appreciate any advice
> tks & rdgs
distributor_admin
Runing SQL 2k, Win 2k
We had to rebuild a server and when I attepmt to configure replication I
receive the error...
Could not connect to server 'newSERVERNAME' because 'distributor_admin' is
not defined as a remote login at the server.
When I look at the Logins, 'distributor_admin' login is not there. The only
logins there are BULITIN\Administrators & domainname\Administrator.
So the question is, how do I create this login or all the system created
logins? Is there an SP to create them from another server?
TIA,
Larry...
Your best bet is to remove replication and reinstall it.
"Larry" <Larry@.discussions.microsoft.com> wrote in message
news:C40E4D07-7D98-4CFF-8160-26B072C6E3F2@.microsoft.com...
> Runing SQL 2k, Win 2k
> We had to rebuild a server and when I attepmt to configure replication I
> receive the error...
> Could not connect to server 'newSERVERNAME' because 'distributor_admin' is
> not defined as a remote login at the server.
> When I look at the Logins, 'distributor_admin' login is not there. The
> only
> logins there are BULITIN\Administrators & domainname\Administrator.
> So the question is, how do I create this login or all the system created
> logins? Is there an SP to create them from another server?
>
> TIA,
> Larry...
>
We had to rebuild a server and when I attepmt to configure replication I
receive the error...
Could not connect to server 'newSERVERNAME' because 'distributor_admin' is
not defined as a remote login at the server.
When I look at the Logins, 'distributor_admin' login is not there. The only
logins there are BULITIN\Administrators & domainname\Administrator.
So the question is, how do I create this login or all the system created
logins? Is there an SP to create them from another server?
TIA,
Larry...
Your best bet is to remove replication and reinstall it.
"Larry" <Larry@.discussions.microsoft.com> wrote in message
news:C40E4D07-7D98-4CFF-8160-26B072C6E3F2@.microsoft.com...
> Runing SQL 2k, Win 2k
> We had to rebuild a server and when I attepmt to configure replication I
> receive the error...
> Could not connect to server 'newSERVERNAME' because 'distributor_admin' is
> not defined as a remote login at the server.
> When I look at the Logins, 'distributor_admin' login is not there. The
> only
> logins there are BULITIN\Administrators & domainname\Administrator.
> So the question is, how do I create this login or all the system created
> logins? Is there an SP to create them from another server?
>
> TIA,
> Larry...
>
distributor_admin
Hi ,
In my connection string as below , i have specified to use the user "sa"
but i am not sure why the error msg says login fail for distributor_admin
the server that i am connecting to is set up as a distirbutor on a local
publisher
strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
=master;uid=sa;pwd=XXXX"
appreciate any advice
tks & rdgsHi,
is there such a so called default password for this distributor_admin user ?
i can see that in the remote login , the sa is being mapped to the
distributor_admin when i tried to change it , it can be changed but once i
come it again it's still being mapped to distributor_admin
appreciate if someone could help
tks & rdgs
"maxzsim" wrote:
> Hi ,
> In my connection string as below , i have specified to use the user "sa"
> but i am not sure why the error msg says login fail for distributor_admin
> the server that i am connecting to is set up as a distirbutor on a local
> publisher
> strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
> =master;uid=sa;pwd=XXXX"
> appreciate any advice
> tks & rdgs
In my connection string as below , i have specified to use the user "sa"
but i am not sure why the error msg says login fail for distributor_admin
the server that i am connecting to is set up as a distirbutor on a local
publisher
strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
=master;uid=sa;pwd=XXXX"
appreciate any advice
tks & rdgsHi,
is there such a so called default password for this distributor_admin user ?
i can see that in the remote login , the sa is being mapped to the
distributor_admin when i tried to change it , it can be changed but once i
come it again it's still being mapped to distributor_admin
appreciate if someone could help
tks & rdgs
"maxzsim" wrote:
> Hi ,
> In my connection string as below , i have specified to use the user "sa"
> but i am not sure why the error msg says login fail for distributor_admin
> the server that i am connecting to is set up as a distirbutor on a local
> publisher
> strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
> =master;uid=sa;pwd=XXXX"
> appreciate any advice
> tks & rdgs
distributor_admin
Hi ,
In my connection string as below , i have specified to use the user "sa"
but i am not sure why the error msg says login fail for distributor_admin
the server that i am connecting to is set up as a distirbutor on a local
publisher
strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
=master;uid=sa;pwd=XXXX"
appreciate any advice
tks & rdgsHi,
is there such a so called default password for this distributor_admin user ?
i can see that in the remote login , the sa is being mapped to the
distributor_admin when i tried to change it , it can be changed but once i
come it again it's still being mapped to distributor_admin
appreciate if someone could help
tks & rdgs
"maxzsim" wrote:
> Hi ,
> In my connection string as below , i have specified to use the user "sa"
> but i am not sure why the error msg says login fail for distributor_admin
> the server that i am connecting to is set up as a distirbutor on a local
> publisher
> strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
> =master;uid=sa;pwd=XXXX"
> appreciate any advice
> tks & rdgs
In my connection string as below , i have specified to use the user "sa"
but i am not sure why the error msg says login fail for distributor_admin
the server that i am connecting to is set up as a distirbutor on a local
publisher
strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
=master;uid=sa;pwd=XXXX"
appreciate any advice
tks & rdgsHi,
is there such a so called default password for this distributor_admin user ?
i can see that in the remote login , the sa is being mapped to the
distributor_admin when i tried to change it , it can be changed but once i
come it again it's still being mapped to distributor_admin
appreciate if someone could help
tks & rdgs
"maxzsim" wrote:
> Hi ,
> In my connection string as below , i have specified to use the user "sa"
> but i am not sure why the error msg says login fail for distributor_admin
> the server that i am connecting to is set up as a distirbutor on a local
> publisher
> strConn = "Provider=SQLOLEDB;Data Source=AAA;InititalCatalog
> =master;uid=sa;pwd=XXXX"
> appreciate any advice
> tks & rdgs
Subscribe to:
Posts (Atom)