marrowyung
asked on
Error when creating SQL server 2005 Endpoint
Dear all,
Right now I just move all Db from an old DB, which is mirrored before, to a new server.
When I try to create the new mirror relation I find I need to drop the existing master key and recreate.
but when I try to recreate the end point using this script:
CREATE ENDPOINT Endpoint_Mirroring
STATE = STARTED
AS TCP (
LISTENER_PORT=7024
, LISTENER_IP = ALL
)
FOR DATABASE_MIRRORING (
AUTHENTICATION = CERTIFICATE ccc
, ENCRYPTION = REQUIRED ALGORITHM AES
, ROLE = ALL
);
GO
I get this error:
"The certificate 'ccc' is not valid for endpoint authentication. The certificate must have a private key encrypted with the database master key and current UTC date has to be between the certificate start date and the certificate expiration date.
"
Any reason on this and how to fix this ?
What we need to do is just to recreate the mirror ASAP.
DBA100.
Right now I just move all Db from an old DB, which is mirrored before, to a new server.
When I try to create the new mirror relation I find I need to drop the existing master key and recreate.
but when I try to recreate the end point using this script:
CREATE ENDPOINT Endpoint_Mirroring
STATE = STARTED
AS TCP (
LISTENER_PORT=7024
, LISTENER_IP = ALL
)
FOR DATABASE_MIRRORING (
AUTHENTICATION = CERTIFICATE ccc
, ENCRYPTION = REQUIRED ALGORITHM AES
, ROLE = ALL
);
GO
I get this error:
"The certificate 'ccc' is not valid for endpoint authentication. The certificate must have a private key encrypted with the database master key and current UTC date has to be between the certificate start date and the certificate expiration date.
"
Any reason on this and how to fix this ?
What we need to do is just to recreate the mirror ASAP.
DBA100.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We forget about that and we use the wizard to generate the end point and keep all existing first.
ASKER
we only need cert. to setup mirror if and only if both primary and DR SQL server don't trust each other ? like the start account of both server is not hte same and not under the same domain ?