"Not enough storage is available to complete this operation" ?

K

Kelvin Beaton

I'm trying to run "Resultant Set of Policy" and am getting this error, "Not
enough storage is available to complete this operation". I have plenty of HD
space and RAM.



Anyone know what it's looking for, or how to resolve this?



Thanks



Kelvin
 
T

Tim Springston [MS]

This could be an error from a different source. Are you getting this error
on a domain controller, or domain member?
 
K

Kelvin Beaton

On a domain controller....


Tim Springston said:
This could be an error from a different source. Are you getting this
error on a domain controller, or domain member?

--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.
Click to expand...
 
T

Tim Springston [MS]

If you run a DCDIAG /V (DCDIAG.EXE is a Support Tool) does the DC fail any
tests? If it does, what tests are failing and what are the error codes?
 
K

Kelvin Beaton

Looks pretty clean to me.

This is about all I see.
* Checking Service: NtFrs
NtFrs Service is stopped on [MONSTER]
and I'm aware of that.

Do you see something more then this?

Thanks

Kelvin

+++++++++++++++++++

Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine monster, is a DC.
* Connecting to directory service on server monster.
* Collecting site info.
* Identifying all servers.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\MONSTER
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... MONSTER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\MONSTER
Starting test: Replications
* Replications Check
......................... MONSTER passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=mccsa,DC=local
* Security Permissions Check for
CN=Configuration,DC=mccsa,DC=local
* Security Permissions Check for
DC=mccsa,DC=local
......................... MONSTER passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... MONSTER passed test NetLogons
Starting test: Advertising
The DC MONSTER is advertising itself as a DC and having a DS.
The DC MONSTER is advertising as an LDAP server
The DC MONSTER is advertising as having a writeable directory
The DC MONSTER is advertising as a Key Distribution Center
The DC MONSTER is advertising as a time server
The DS MONSTER is advertising as a GC.
......................... MONSTER passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Domain Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role PDC Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Rid Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
......................... MONSTER passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 1608 to 1073741823
* monster.mccsa.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1108 to 1607
* rIDNextRID: 1292
* rIDPreviousAllocationPool is 1108 to 1607
......................... MONSTER passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/monster.mccsa.local/mccsa.local
* SPN found :LDAP/monster.mccsa.local
* SPN found :LDAP/MONSTER
* SPN found :LDAP/monster.mccsa.local/MCCSA
* SPN found
:LDAP/2d24b734-9bfa-4095-9557-3261caefa4a5._msdcs.mccsa.local
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/2d24b734-9bfa-4095-9557-3261caefa4a5/mccsa.local
* SPN found :HOST/monster.mccsa.local/mccsa.local
* SPN found :HOST/monster.mccsa.local
* SPN found :HOST/MONSTER
* SPN found :HOST/monster.mccsa.local/MCCSA
* SPN found :GC/monster.mccsa.local/mccsa.local
......................... MONSTER passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
NtFrs Service is stopped on [MONSTER]
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: RPCLOCATOR
* Checking Service: w32time
* Checking Service: TrkWks
* Checking Service: TrkSvr
* Checking Service: NETLOGON
* Checking Service: Dnscache
* Checking Service: NtFrs
......................... MONSTER failed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
MONSTER is in domain DC=mccsa,DC=local
Checking for CN=MONSTER,OU=Domain Controllers,DC=mccsa,DC=local in
domain DC=mccsa,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
in domain CN=Configuration,DC=mccsa,DC=local on 1 servers
Object is up-to-date on all servers.
......................... MONSTER passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service Event log test
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... MONSTER passed test frssysvol
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15
minutes.
......................... MONSTER passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... MONSTER passed test systemlog

Running enterprise tests on : mccsa.local
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the
scope

provided by the command line arguments provided.
......................... mccsa.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
PDC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
Time Server Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
KDC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
......................... mccsa.local passed test FsmoCheck

+++++++++++++++++++
 
T

Tim Springston [MS]

Having the File Replication Service stopped could cause this behavior. What
happens if you start NTFRS?

--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.


Kelvin Beaton said:
Looks pretty clean to me.

This is about all I see.
* Checking Service: NtFrs
NtFrs Service is stopped on [MONSTER]
and I'm aware of that.

Do you see something more then this?

Thanks

Kelvin

+++++++++++++++++++

Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine monster, is a DC.
* Connecting to directory service on server monster.
* Collecting site info.
* Identifying all servers.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\MONSTER
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... MONSTER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\MONSTER
Starting test: Replications
* Replications Check
......................... MONSTER passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=mccsa,DC=local
* Security Permissions Check for
CN=Configuration,DC=mccsa,DC=local
* Security Permissions Check for
DC=mccsa,DC=local
......................... MONSTER passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... MONSTER passed test NetLogons
Starting test: Advertising
The DC MONSTER is advertising itself as a DC and having a DS.
The DC MONSTER is advertising as an LDAP server
The DC MONSTER is advertising as having a writeable directory
The DC MONSTER is advertising as a Key Distribution Center
The DC MONSTER is advertising as a time server
The DS MONSTER is advertising as a GC.
......................... MONSTER passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Domain Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role PDC Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Rid Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
......................... MONSTER passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 1608 to 1073741823
* monster.mccsa.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1108 to 1607
* rIDNextRID: 1292
* rIDPreviousAllocationPool is 1108 to 1607
......................... MONSTER passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/monster.mccsa.local/mccsa.local
* SPN found :LDAP/monster.mccsa.local
* SPN found :LDAP/MONSTER
* SPN found :LDAP/monster.mccsa.local/MCCSA
* SPN found
:LDAP/2d24b734-9bfa-4095-9557-3261caefa4a5._msdcs.mccsa.local
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/2d24b734-9bfa-4095-9557-3261caefa4a5/mccsa.local
* SPN found :HOST/monster.mccsa.local/mccsa.local
* SPN found :HOST/monster.mccsa.local
* SPN found :HOST/MONSTER
* SPN found :HOST/monster.mccsa.local/MCCSA
* SPN found :GC/monster.mccsa.local/mccsa.local
......................... MONSTER passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
NtFrs Service is stopped on [MONSTER]
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: RPCLOCATOR
* Checking Service: w32time
* Checking Service: TrkWks
* Checking Service: TrkSvr
* Checking Service: NETLOGON
* Checking Service: Dnscache
* Checking Service: NtFrs
......................... MONSTER failed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
MONSTER is in domain DC=mccsa,DC=local
Checking for CN=MONSTER,OU=Domain Controllers,DC=mccsa,DC=local in
domain DC=mccsa,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
in domain CN=Configuration,DC=mccsa,DC=local on 1 servers
Object is up-to-date on all servers.
......................... MONSTER passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service Event log test
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... MONSTER passed test frssysvol
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15
minutes.
......................... MONSTER passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... MONSTER passed test systemlog

Running enterprise tests on : mccsa.local
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the
scope

provided by the command line arguments provided.
......................... mccsa.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
PDC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
Time Server Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
KDC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
......................... mccsa.local passed test FsmoCheck

+++++++++++++++++++

Tim Springston said:
If you run a DCDIAG /V (DCDIAG.EXE is a Support Tool) does the DC fail
any tests? If it does, what tests are failing and what are the error
codes?

--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.
Click to expand...
Click to expand...
 
K

Kelvin Beaton

Thanks Tim for your time...

The messages I got in Event Viewer are listed below.
The last one looks like NTRFS may have corrected its self.

The only odd thing I can see at this point is the name of the folder,
C:\WINNT\SYSVOL\sysvol\mccsa.local\DO_NOT_REMOVE_NtFrs_PreInstall_Directory"
I'm assuming this is the folder it is using, is that correct?
I guess if it's working, who am I to argue...

----------------------

The File Replication Service is starting.
++++++++++++++++
The File Replication Service has detected that the replica set "DOMAIN
SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to
read from the NTFS USN journal is not found. This can occur because of one
of the following reasons.
++++++++++++++++
The File Replication Service is deleting this computer from the replica set
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" as an attempt to recover from the
error state,
Error status = FrsErrorSuccess
At the next poll, which will occur in 5 minutes, this computer will be
re-added to the replica set. The re-addition will trigger a full tree sync
for the replica set.
++++++++++++++++
The File Replication Service successfully added this computer to the
following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

Information related to this event is shown below:
Computer DNS name is "monster.mccsa.local"
Replica set member name is "MONSTER"
Replica set root path is "c:\winnt\sysvol\domain"
Replica staging directory path is "c:\winnt\sysvol\staging\domain"
Replica working directory path is "c:\winnt\ntfrs\jet"
++++++++++++++++
The File Replication Service is no longer preventing the computer MONSTER
from becoming a domain controller. The system volume has been successfully
initialized and the Netlogon service has been notified that the system
volume is now ready to be shared as SYSVOL.


Tim Springston said:
Having the File Replication Service stopped could cause this behavior.
What happens if you start NTFRS?

--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.


Kelvin Beaton said:
Looks pretty clean to me.

This is about all I see.
* Checking Service: NtFrs
NtFrs Service is stopped on [MONSTER]
and I'm aware of that.

Do you see something more then this?

Thanks

Kelvin

+++++++++++++++++++

Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine monster, is a DC.
* Connecting to directory service on server monster.
* Collecting site info.
* Identifying all servers.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\MONSTER
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... MONSTER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\MONSTER
Starting test: Replications
* Replications Check
......................... MONSTER passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=mccsa,DC=local
* Security Permissions Check for
CN=Configuration,DC=mccsa,DC=local
* Security Permissions Check for
DC=mccsa,DC=local
......................... MONSTER passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... MONSTER passed test NetLogons
Starting test: Advertising
The DC MONSTER is advertising itself as a DC and having a DS.
The DC MONSTER is advertising as an LDAP server
The DC MONSTER is advertising as having a writeable directory
The DC MONSTER is advertising as a Key Distribution Center
The DC MONSTER is advertising as a time server
The DS MONSTER is advertising as a GC.
......................... MONSTER passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Domain Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role PDC Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Rid Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
......................... MONSTER passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 1608 to 1073741823
* monster.mccsa.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1108 to 1607
* rIDNextRID: 1292
* rIDPreviousAllocationPool is 1108 to 1607
......................... MONSTER passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/monster.mccsa.local/mccsa.local
* SPN found :LDAP/monster.mccsa.local
* SPN found :LDAP/MONSTER
* SPN found :LDAP/monster.mccsa.local/MCCSA
* SPN found
:LDAP/2d24b734-9bfa-4095-9557-3261caefa4a5._msdcs.mccsa.local
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/2d24b734-9bfa-4095-9557-3261caefa4a5/mccsa.local
* SPN found :HOST/monster.mccsa.local/mccsa.local
* SPN found :HOST/monster.mccsa.local
* SPN found :HOST/MONSTER
* SPN found :HOST/monster.mccsa.local/MCCSA
* SPN found :GC/monster.mccsa.local/mccsa.local
......................... MONSTER passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
NtFrs Service is stopped on [MONSTER]
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: RPCLOCATOR
* Checking Service: w32time
* Checking Service: TrkWks
* Checking Service: TrkSvr
* Checking Service: NETLOGON
* Checking Service: Dnscache
* Checking Service: NtFrs
......................... MONSTER failed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
MONSTER is in domain DC=mccsa,DC=local
Checking for CN=MONSTER,OU=Domain Controllers,DC=mccsa,DC=local
in domain DC=mccsa,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
in domain CN=Configuration,DC=mccsa,DC=local on 1 servers
Object is up-to-date on all servers.
......................... MONSTER passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service Event log test
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... MONSTER passed test frssysvol
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15
minutes.
......................... MONSTER passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... MONSTER passed test systemlog

Running enterprise tests on : mccsa.local
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the
scope

provided by the command line arguments provided.
......................... mccsa.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
PDC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
Time Server Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
KDC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
......................... mccsa.local passed test FsmoCheck

+++++++++++++++++++

Tim Springston said:
If you run a DCDIAG /V (DCDIAG.EXE is a Support Tool) does the DC fail
any tests? If it does, what tests are failing and what are the error
codes?

--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
On a domain controller....


This could be an error from a different source. Are you getting this
error on a domain controller, or domain member?

--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
I'm trying to run "Resultant Set of Policy" and am getting this
error, "Not enough storage is available to complete this operation".
I have plenty of HD space and RAM.



Anyone know what it's looking for, or how to resolve this?



Thanks



Kelvin
Click to expand...
Click to expand...
Click to expand...
 
T

Tim Springston [MS]

Hi Kelvin-

If the server is no longer in journal wrap (you can basically tell by
whether the SYSVOL and NETLOGON shares are present-if they are all is well)
then does the original 'not enough storage' error still occur?

--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.


Kelvin Beaton said:
Thanks Tim for your time...

The messages I got in Event Viewer are listed below.
The last one looks like NTRFS may have corrected its self.

The only odd thing I can see at this point is the name of the folder,
C:\WINNT\SYSVOL\sysvol\mccsa.local\DO_NOT_REMOVE_NtFrs_PreInstall_Directory"
I'm assuming this is the folder it is using, is that correct?
I guess if it's working, who am I to argue...

----------------------

The File Replication Service is starting.
++++++++++++++++
The File Replication Service has detected that the replica set "DOMAIN
SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to
read from the NTFS USN journal is not found. This can occur because of one
of the following reasons.
++++++++++++++++
The File Replication Service is deleting this computer from the replica
set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" as an attempt to recover from
the error state,
Error status = FrsErrorSuccess
At the next poll, which will occur in 5 minutes, this computer will be
re-added to the replica set. The re-addition will trigger a full tree sync
for the replica set.
++++++++++++++++
The File Replication Service successfully added this computer to the
following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

Information related to this event is shown below:
Computer DNS name is "monster.mccsa.local"
Replica set member name is "MONSTER"
Replica set root path is "c:\winnt\sysvol\domain"
Replica staging directory path is "c:\winnt\sysvol\staging\domain"
Replica working directory path is "c:\winnt\ntfrs\jet"
++++++++++++++++
The File Replication Service is no longer preventing the computer MONSTER
from becoming a domain controller. The system volume has been successfully
initialized and the Netlogon service has been notified that the system
volume is now ready to be shared as SYSVOL.


Tim Springston said:
Having the File Replication Service stopped could cause this behavior.
What happens if you start NTFRS?

--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.


Kelvin Beaton said:
Looks pretty clean to me.

This is about all I see.
* Checking Service: NtFrs
NtFrs Service is stopped on [MONSTER]
and I'm aware of that.

Do you see something more then this?

Thanks

Kelvin

+++++++++++++++++++

Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine monster, is a DC.
* Connecting to directory service on server monster.
* Collecting site info.
* Identifying all servers.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\MONSTER
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... MONSTER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\MONSTER
Starting test: Replications
* Replications Check
......................... MONSTER passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=mccsa,DC=local
* Security Permissions Check for
CN=Configuration,DC=mccsa,DC=local
* Security Permissions Check for
DC=mccsa,DC=local
......................... MONSTER passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... MONSTER passed test NetLogons
Starting test: Advertising
The DC MONSTER is advertising itself as a DC and having a DS.
The DC MONSTER is advertising as an LDAP server
The DC MONSTER is advertising as having a writeable directory
The DC MONSTER is advertising as a Key Distribution Center
The DC MONSTER is advertising as a time server
The DS MONSTER is advertising as a GC.
......................... MONSTER passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Domain Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role PDC Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Rid Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
......................... MONSTER passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 1608 to 1073741823
* monster.mccsa.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1108 to 1607
* rIDNextRID: 1292
* rIDPreviousAllocationPool is 1108 to 1607
......................... MONSTER passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/monster.mccsa.local/mccsa.local
* SPN found :LDAP/monster.mccsa.local
* SPN found :LDAP/MONSTER
* SPN found :LDAP/monster.mccsa.local/MCCSA
* SPN found
:LDAP/2d24b734-9bfa-4095-9557-3261caefa4a5._msdcs.mccsa.local
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/2d24b734-9bfa-4095-9557-3261caefa4a5/mccsa.local
* SPN found :HOST/monster.mccsa.local/mccsa.local
* SPN found :HOST/monster.mccsa.local
* SPN found :HOST/MONSTER
* SPN found :HOST/monster.mccsa.local/MCCSA
* SPN found :GC/monster.mccsa.local/mccsa.local
......................... MONSTER passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
NtFrs Service is stopped on [MONSTER]
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: RPCLOCATOR
* Checking Service: w32time
* Checking Service: TrkWks
* Checking Service: TrkSvr
* Checking Service: NETLOGON
* Checking Service: Dnscache
* Checking Service: NtFrs
......................... MONSTER failed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
MONSTER is in domain DC=mccsa,DC=local
Checking for CN=MONSTER,OU=Domain Controllers,DC=mccsa,DC=local
in domain DC=mccsa,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=MONSTER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mccsa,DC=local
in domain CN=Configuration,DC=mccsa,DC=local on 1 servers
Object is up-to-date on all servers.
......................... MONSTER passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service Event log test
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... MONSTER passed test frssysvol
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last
15 minutes.
......................... MONSTER passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... MONSTER passed test systemlog

Running enterprise tests on : mccsa.local
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the
scope

provided by the command line arguments provided.
......................... mccsa.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
PDC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
Time Server Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
KDC Name: \\monster.mccsa.local
Locator Flags: 0xe00001fd
......................... mccsa.local passed test FsmoCheck

+++++++++++++++++++

If you run a DCDIAG /V (DCDIAG.EXE is a Support Tool) does the DC fail
any tests? If it does, what tests are failing and what are the error
codes?

--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
On a domain controller....


This could be an error from a different source. Are you getting this
error on a domain controller, or domain member?

--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
I'm trying to run "Resultant Set of Policy" and am getting this
error, "Not enough storage is available to complete this operation".
I have plenty of HD space and RAM.



Anyone know what it's looking for, or how to resolve this?



Thanks



Kelvin
Click to expand...
Click to expand...
Click to expand...
 
W

wweist

Joined
Jun 2, 2012
Messages
1
Reaction score
0
I received this error when the account I was using was a member of nested AD Group Objects.

Kelvin Beaton said:
I'm trying to run "Resultant Set of Policy" and am getting this error, "Not
enough storage is available to complete this operation". I have plenty of HD
space and RAM.



Anyone know what it's looking for, or how to resolve this?



Thanks



Kelvin
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Win 32: Not enough storage is available to complete this operation 4
Not enough storage is available to complete this operation-only onVista 4
Not enough memory available to complete the operation 20
Error message with CAPICOM 2.1.0.2 Not enough storage is available 2
RSoP Tool error message: not enough storage 0
Not enough storage is available to complete this operation 6
Not enough storage is available to complete this operation. 1
There is not enough memory available to complete this operation. 4

Top