Exchange 2003 down due to SYSVOL not being shared

Hi friends,

In a bit of trouble. The Exchange 2003 information store and system attendant services won't start due to the SYSVOL not being mounted on our Windows 2000 server. This is due to replication problems apparently. But I'm open to suggestions!

The event log error codes are very sparse and have strange error codes like %c00.

Is there any way to get these services started so the network clients can use their email?

High points due to urgency!

Thanks,

Lee.
LeeGoldingAsked:
Who is Participating?
 
DarthModConnect With a Mentor Commented:
PAQd, 500 points refunded.

DarthMod
CS Moderator
0
 
trenesCommented:
Hi LeeGolding,

First make sure you have setup your DNS correctly, that is likely to be the root cause here.


Cheers!
0
 
trenesCommented:
LeeGolding,

Also have a look here
http://support.microsoft.com/kb/315457/
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
LeeGoldingAuthor Commented:
What could be wrong with the DNS in particular?

Lee.
0
 
LeeGoldingAuthor Commented:
I have 2 DCs. Both have hosts in the DNS. Their network adapters point to the main DC which has the DNS server on it. Global Catalogue is on this main server. Exhcnage 2003 is installed on this main server.

Lee.
0
 
trenesCommented:
This will get you on the way.
We need first to get rid of this replicaiton errors.

Full ms link http://technet2.microsoft.com/WindowsServer/en/library/22764cb5-9860-4f8f-95e7-337df24edf741033.mspx?mfr=true

Repadmin is a command-line tool that report failures on a replication link between two replication partners. The following repadmin example displays the replication partners and any replication link failures for Server1 on the microsoft.com domain:

repadmin /showrepl server1.microsoft.com

For a complete list of repadmin options, use the ? option:

repadmin /?

Dcdiag is a command-line tool that can check the DNS registration of a domain controller, check to see that the security descriptors (SIDs) on the naming context heads have appropriate permissions for replication, analyze the state of domain controllers in a forest or enterprise, and more. The following dcdiag example checks for any replication errors between domain controllers:

dcdiag /test:replications
0
 
LeeGoldingAuthor Commented:
Should I post the results of these here so that you can help me fix them?

Thanks,

Lee.
0
 
trenesCommented:
Yes if you could?
0
 
LeeGoldingAuthor Commented:
  Testing server: Default-First-Site-Name\PDC
      Starting test: Replications
         [Replications Check,PDC] A recent replication attempt failed:
            From BDC to PDC
            Naming Context: CN=Schema,CN=Configuration,DC=ourdomain,DC=com
            The replication generated an error (8456):
            The source server is currently rejecting replication requests.
            The failure occurred at 2006-11-09 09:53.19.
            The last success occurred at 2006-11-07 20:13.57.
            43 failures have occurred since the last success.
            Replication has been explicitly disabled through the server options.

         [Replications Check,PDC] A recent replication attempt failed:
            From BDC to PDC
            Naming Context: CN=Configuration,DC=ourdomain,DC=com
            The replication generated an error (8456):
            The source server is currently rejecting replication requests.
            The failure occurred at 2006-11-09 09:53.19.
            The last success occurred at 2006-11-07 20:13.57.
            43 failures have occurred since the last success.
            Replication has been explicitly disabled through the server options.

         [Replications Check,PDC] A recent replication attempt failed:
            From BDC to PDC
            Naming Context: DC=ourdomain,DC=com
            The replication generated an error (8456):
            The source server is currently rejecting replication requests.
            The failure occurred at 2006-11-09 09:53.19.
            The last success occurred at 2006-11-07 20:13.57.
            44 failures have occurred since the last success.
            Replication has been explicitly disabled through the server options.

         ......................... PDC passed test Replications

I have since enabled outbound and inbound replication using repadmin. Restarted FRS. But we are still stuck with the above error.

What now?

Lee.
0
 
redseatechnologiesCommented:
0
 
LeeGoldingAuthor Commented:
Solved it with the help of Chris-dent and Netman66, and a lot of internet searching. I had to do a dcdiag /fix and D4 authorative restore. Once done everything came to life.

Thanks for the help guys anyway.

Lee.

0
 
redseatechnologiesCommented:
Want to post a link to that question for clarity?

Also, post a question in CS to have this PAQd

-red
0
 
trenesCommented:
I dont see any posts of Cris-dent or Netman66 if they would post in this thread then you could give them the points.
0
 
LeeGoldingAuthor Commented:
I posted a question specifically about the DNS problems around the same time as this. My main aim of this question was to find a way to start Exchange without sysvol being mounted. And there isn't.

The other questions solved some other vital problems which had the benefit of allowing Exchange to start as AD came up and the server became a domain controller.

http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_22052689.html
http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_22053040.html

Where I have awarded points to them for solving the specific problems posted there.

Lee.



0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.