We are having two or three problems; potentially related.

Background. A Windows2000 server (BDC), which was recently upgraded to a
dual-boot configuration (other image is W2kPRO) then both added to the
domain, server as an additional domain controller, had some problems with
MSMQ and MSDE. To rectify this, we removed MQ and reinstalled it, as well
as re-mapped volumes for MSDE/SQL2000. Subsequently some other artifacts
have emerged, including now the PDC, which was recovered from a hardware
crash not long ago. It has current service levels, as does the BDC.

Note: A baseline server installation, used as our observational 'control'
does not appear to share these maliase; a member of the domain yet as a
server only.

Symptoms: (1) MQ thinks the BDC server is still believes it is
operating in a WORKGROUP configuration.
(2) A message that MQSEC.DLL cannot be found occurs
on restart on the PDC.
(3) Both NETLOGON evts. 5774 and 5775 are showing
up, as well other DNS errors.
(4) The MSMQ MMC snap-in fails to initialize.

Questions: i. What would be a good problem determination/short-term
operational stability approach?
ii. Is there a way to reset both configurations
(component and security)
iii. As we plan for upgrading, how can these be avoided
in the future.

Best;

JgE sends.

Attn: Moderators and Group

If there aren't any thoughts forthcoming, please advise.


"Joseph G. Earl" <(E-Mail Removed)> wrote in message
news:79R6f.17$(E-Mail Removed)...
> We are having two or three problems; potentially related.
>
> Background. A Windows2000 server (BDC), which was recently upgraded to a
> dual-boot configuration (other image is W2kPRO) then both added to the
> domain, server as an additional domain controller, had some problems with
> MSMQ and MSDE. To rectify this, we removed MQ and reinstalled it, as well
> as re-mapped volumes for MSDE/SQL2000. Subsequently some other artifacts
> have emerged, including now the PDC, which was recovered from a hardware
> crash not long ago. It has current service levels, as does the BDC.
>
> Note: A baseline server installation, used as our observational 'control'
> does not appear to share these maliase; a member of the domain yet as a
> server only.
>
> Symptoms: (1) MQ thinks the BDC server is still believes it is
> operating in a WORKGROUP configuration.
> (2) A message that MQSEC.DLL cannot be found
occurs
> on restart on the PDC.
> (3) Both NETLOGON evts. 5774 and 5775 are showing
> up, as well other DNS errors.
> (4) The MSMQ MMC snap-in fails to initialize.
>
> Questions: i. What would be a good problem determination/short-term
> operational stability approach?
> ii. Is there a way to reset both configurations
> (component and security)
> iii. As we plan for upgrading, how can these be
avoided
> in the future.
>
> Best;
>
> JgE sends.
>
>
>