oh. thanks for the info.
"Michael Hotek" <mike@solidqualitylearning.com> wrote in message
news:Odmydl1cGHA.4932@TK2MSFTNGP03.phx.gbl...
> You can set the partnership at the mirror, because this is a passive
> relationship. All you are doing is changing a setting. It did not work
> at the principal, because the principal is the active part of mirroring
> that is required to initiate the connection. Since the principal has to
> initiate the connection and transfer data immediately upon initiation, the
> connection is created as part of the action of setting the partnership, so
> the security issue would be encountered at the principal only.
>
> --
> Mike
>
http://www.solidqualitylearning.com > Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
>
> "adam" <hartmann@thestar.com.my> wrote in message
> news:O2dhIGycGHA.3952@TK2MSFTNGP04.phx.gbl...
>> thanks Mike.
>> de 1st quest answer it.
>>
>> had discovered dat earlier - the service account (principal) has no
>> access rights on de other (mirror) server.
>>
>> thus, has created a domain user (cos in AD environment) and changed to
>> both servers' service account starter - de sqlserver and sqlagent.
>> -solved-
>>
>> but de weird part is, why mirror server able to set partnership with de
>> principal at de first place??
>> -still no answer-
>>
>> anyway, thanks a lot.
>>
>> Adam.
>>
>>
>> "Michael Hotek" <mike@solidqualitylearning.com> wrote in message
>> news:%23rej74ucGHA.3888@TK2MSFTNGP02.phx.gbl...
>>> First question is are the service accounts the same for both instances
>>> and if they aren't, did you get the certificates exchanged and access
>>> granted. Second question is do you have a local firewall on the machine
>>> that is blocking ports. Third question is there a firewall on the
>>> network that is blocking ports.
>>>
>>> --
>>> Mike
>>>
http://www.solidqualitylearning.com >>> Disclaimer: This communication is an original work and represents my
>>> sole views on the subject. It does not represent the views of any other
>>> person or entity either by inference or direct reference.
>>>
>>>
>>> "adam" <hartmann@thestar.com.my> wrote in message
>>> news:u%23Q4bEBcGHA.3364@TK2MSFTNGP05.phx.gbl...
>>>> hi,
>>>>
>>>> i'm new to this group.
>>>> i wonder if i can get answers to my question here, cos i cant find a
>>>> newsgroup with database mirroring.
>>>>
>>>> i have two servers :
>>>> pSQL - principal
>>>> mSQL - mirror
>>>>
>>>> Have successfully create the endpoints at both servers.
>>>> Have checked on the port 5021 listening at both servers.
>>>> Have successfully ping and see each other in network.
>>>>
>>>> *
>>>> but can only set the partner from the mirror server ( mSQL to pSQL ),
>>>> and
>>>> not the other way round.
>>>> in short unable to set partner from the principal server - pSQL.
>>>>
>>>> below is the error msg:-
>>>> Msg 1418, Level 16, State 1, Line 1
>>>> The server network address "tcp://mSQL:5021" can not be reached or does
>>>> not
>>>> exist. Check the network address name and that the ports for the local
>>>> and
>>>> remote endpoints are operational.
>>>>
>>>>
>>>> anyone successfully solved this issue?
>>>>
>>>> Thanks in advance,
>>>> Adam
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>