Upgrade Concerns

  • Thread starter Thread starter JDH
  • Start date Start date
J

JDH

I am hoping someone can assist me soon with my issues. I am preparing to
upgrade to Exchange 2003 and Windows 2003 tomorrow (2/5) so any help is
greatly appreciated.

I have two domain controllers, FILE and MAIL.

When I run DCDIAG on both, I receive errors. However, the errors are
different. MAIL reports the following:

Starting test: FsmoCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
......................... preferredsourcing.com failed test FsmoCheck

FILE reports the following:
Starting test: FsmoCheck
Error: The server returned by DsGetDcName() did not match
DsListRoles()
for the PDC
......................... domainxxx.com passed test FsmoCheck

I have done serveral hours worth of research and cant finde a solution.

I am concerned about these errors. When I check REPLMON, everything seems
fine. When I run NETDOM QUERY FSMO on both servers, both report correctly
that FILE holds all 5 FSMO roles.

Should I be worried about my upgrade?

Thanks,
Josh
 
Always hate to go into upgrades with any errors, but if your event logs are
clean, dcdiag and netdiag look good (with the below exceptions), netdom
reports properly, and you're not seeing any replication problems or domain
function loss that you're aware of, may be ok.
Couple of things that I might try though would be to move the pdc role from
file to mail and see if netdom query fsmo picks that up from both and if the
dcdiag log is fixed too, then you can move it back to file if wanted.
Also take a look at the rpc locater service and if it isn't set to auto
start (from manual) change that and reboot to see if that helps pick it up
too.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
Thanks. I am going to try that. After further investigation, I found a
couple more things out.

We also have an old SBS 4.5 server on the network. It isnt doing anything
that I know of, but my FILE server is throwing out an IP conflict with it.
This sounds obvious, but the 2 servers have different IP's. I am goign to
do some investigation into decomissioning that old box today. I would
rather just be rid of it than try to figure out what is screwing up this
week.

My upgrade window starts in about 4 hours, so you may hear from me again.
Thanks for the advice David.

Josh.
 
After taking my old SBS down, and doing the FSMO PDC transfter back and
forth, the errors went away. I now have a happy AD running Win 2k3 and
EX2k3. Thanks for the assist.

Josh
 
Back
Top