Windows Forum

Ask something
Discussion Locked

forest prep errors

0 helpful
5 replies

by seadogs

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am getting the error that "either you do not have permission to update the active directory schema or active directory service is currently too busy". I got this error on the dc when trying to run it. Our network consists of the dc which is the forest root, and a member server which will be the exchange server. I get a similar error on the exchange server. I found some suggestions to look for, but none have worked so far. Remote registry is running, my user is the same one we used to install windows and has schema and enterprise level permissions. I did run dcdiag and get an error that the rpc server is unavailable. Could that be the cause? Any help is appreciated!

5 replies

by bazz00

It sounds like your PDC is requesting a service from the member server because the member server beleives that it is the master even though it is not the PDC. Hence the RPC error, the PDC is requesting something from the member server that it cannot provide.

Have the machines been rebooted recently? Or has there been an instance of a power cut and no UPS?

If it is convenient you could try a complete shutdown and power them up in the order of, PDC first and wait until it is fully booted with all services started before switching the member server back on. This should help the servers get their roles corrected and stop them from fighting each other for the role of master.

by ojt

My best bet is that this is a DNS problem. Start by verifying that all servers have access to the DNS zone that contains the appropriate records for your forest - without this it wont work!

by seadogs

So far I've tried everything but answer #3 with no luck. I've even set the future exchange server as a dc with no difference in results. Can anyone tell me how to verify that the dns server is setup correctly? The future exchange server has been added as a new host under the forward look up zone. Unfortunately I know very little about DNS and it looks like this problem is only going to be figured out by me with lots of help from you guys, hopefully sooner than later. Thanks again!

This discussion is closed to new replies.