| Author |
Message |
admir
Guest
|
 Posted:
Thu Oct 28, 2004 2:01 pm Post subject:
Why am I being ingnored? |
|
|
I have bean posting msg for help on evet id 13508. No one have ever replayed
to me about it.
I cant figure out what to do about this. I folowed all documentation on this
and yet no change.
Since I am am being ignored about this issue I have no joice but to stop
using DFS.
Thanks for nothing MS |
|
| Back to top |
|
 |
Bob Hollness
Guest
|
| Posted:
Thu Oct 28, 2004 9:02 pm Post subject:
Re: Why am I being ingnored? |
|
|
This is a public group and is not a forum that Microsoft will exclusively
answer. Any help or advice given is by the general public and is often
based on their own experiences. So, maybe if nobody is answering your post,
it is because nobody knows the answer. I have posted many times and have
not been lucky enough to get an answer. This does not mean that you are
being ignored.
A quick google has returned this. Have you tried it? Try using google to
find your answer, or maybe just repost.
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows Server 2003, Datacenter Edition
b.. Microsoft Windows Server 2003, Enterprise Edition
c.. Microsoft Windows 2000 Server
d.. Microsoft Windows 2000 Advanced Server
e.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q285923
SYMPTOMS
You may find that the following error messages are recorded in Event
Viewer every 5 minutes on domain controller computers and every 20
minutes on member server computers:
Userenv 1000
Windows cannot access the registry information at
\\domainname.com\sysvol\domainname.com\Policies\{
file://\\domainname.com\sysvol\domainname.com\Policies\{31B2F340-016D
D-11D2-945F-00C04FB984F9}\Machine\registry.pol with (1398).
SceCli 1001
Security policy cannot be propagated. Cannot access the template. Error
code=3.
Userenv 1000
The Group Policy client-side extension Security was passed flags (17)
and returned a failure status code of (3).
NtFrs 13508
Description: The File Replication Service is having trouble enabling
replication from (computername) to (computername) for
c:\winnt\sysvol\domain; retrying.
RESOLUTION
To resolve this issue, synchronize the computers with the domain
controller clock time. Follow these steps:
1.. Run the following command on all computers to synchronize the
clock time with the domain controller:
net time \\(domain controller name) /set /y
2.. Stop and then restart the File Replication Service on all servers
that are experiencing the problem.
3.. Open Event Viewer to make sure that
*************************************************************************
*****
PSS ID Number: 272279
Article Last Modified on 10/11/2002
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows 2000 Server
b.. Microsoft Windows 2000 Advanced Server
c.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q272279
SUMMARY
This article discusses how to troubleshoot the File Replication service
(FRS) and the Distributed file system (Dfs). The main emphasis, however,
of this article is to discuss a general procedure which can help you to
troubleshoot FRS problems.
MORE INFORMATION
You may observe that FRS has stopped replicating content on your system.
This behavior may occur because of many potential causes.
If your system experiences FRS problems, you can perform the following
general procedure to troubleshoot these problems:
1.. Check for free disk space on Computer A (source directory, staging
directory, and database partition) and Computer B (destination
partition, preinstall partition, and database partition). Look for the
following events in Event Viewer:
Event id:13511
Database is out of disk space.
Event id:13522
Staging directory is full. An outbound partner that has not connected
for a while can cause this. Delete the connection and stop and restart
FRS to force deletion of the staging files.
For additional information about how to move the database to a larger
volume, click the article number below to view the article in the
Microsoft Knowledge Base:
221093 How to Relocate the NTFRS Jet Database and Log Files
2.. Create a test file on Computer B and verify its replication to
Computer A.
3.. Verify that both Computer A and Computer B are available on the
network. Because FRS uses the fully qualified domain name (FQDN) of the
replica members, an appropriate first check is to use a ping command
specifying the fully qualified name of the problem replicas.
From Computer A, send a ping command with Computer B's FQDN. From
Computer B, send a ping command to Computer A's FQDN. Verify that the
addresses returned by the ping command are the same as the addresses
returned by an ipconfig /all command by means of the command line of the
destination computer.
4.. Access the Services administrative console by following these
steps:
1.. Click Start, and then click Run.
2.. In the Open box, type:
services.msc
Confirm that FRS runs on both computers. If the service is not
running, review the FRS container of Event Viewer (located in the
Eventvwr.msc file) on the computer experiencing the problem.
5.. Verify remote procedure call (RPC) connectivity between Computer A
and Computer B. An appropriate test may be to open Event Viewer on
Computer B from Computer A (which uses RPC). Check FRS event logs on
both computers. If Event ID 13508 is present, there may be a problem
with the RPC service on either computer or with creating a secure
connection between Computer A and Computer B.
6.. Use the Active Directory Sites and Services console to verify the
replication schedule on the Connection object. Ensure that replication
is enabled between Computer A and Computer B and that the connection is
enabled. The Connection object is the inbound connection under Computer
A's NTFRS MEMBER object from Computer B. For System Volume (SYSVOL), the
Connection object resides in the
Sites\Site name\Servers\Server name\Ntds Settings\Connection name
folder.
7.. For Dfs, view the connection links in Active Directory (AD) Users
and Computers. Open AD Users and Computer, click View from the menu and
ensure that Advanced Settings are selected. Go to the System container.
The location of the Connection objects are in the System\File
Replication Service\DFS Volumes folder.
8.. Verify whether or not the file on the originating server is locked
(cannot be accessed) on either computer. If the file is locked on
Computer B so that FRS cannot read the file, FRS cannot generate the
staging file, which delays replication. If the file is locked on
Computer A so that FRS cannot update the file, FRS continues to retry
the update until it succeeds. The retry interval is 30 to 60 seconds.
9.. Verify whether or not the source file had been excluded from
replication. Confirm that the file is not Encrypting File System (EFS)
encrypted, a NTFS file system (NTFS) junction, or excluded by a file or
folder filter on the originating replica member. If any of these
situations are true, FRS does not replicate the file or directory.
10.. If all of the previous conditions are met, you may have to
examine the log files that are created for FRS. The log files are
located in the %Systemroot%\Debug folder. The file names are listed from
NtFrs 001.log to NtFrs 005.log.
"admir" <admir@kuub3.nl> wrote in message
news:eiz5DzMvEHA.908@TK2MSFTNGP11.phx.gbl...
| Quote: | I have bean posting msg for help on evet id 13508. No one have ever
replayed
to me about it.
I cant figure out what to do about this. I folowed all documentation on
this
and yet no change.
Since I am am being ignored about this issue I have no joice but to stop
using DFS.
Thanks for nothing MS
|
|
|
| Back to top |
|
|
Glenn L
Guest
|
| Posted:
Fri Oct 29, 2004 7:04 am Post subject:
Re: Why am I being ingnored? |
|
|
You may also consider opening a case with Microsoft PSS. For a nominal fee,
they will fix this error for you.
--
Glenn L
CCNA, MCSE 2000, MCSE 2003 + Security
"Bob Hollness" <bob@blockbuster.com> wrote in message
news:Or675dQvEHA.3908@TK2MSFTNGP12.phx.gbl...
| Quote: | This is a public group and is not a forum that Microsoft will exclusively
answer. Any help or advice given is by the general public and is often
based on their own experiences. So, maybe if nobody is answering your
post,
it is because nobody knows the answer. I have posted many times and have
not been lucky enough to get an answer. This does not mean that you are
being ignored.
A quick google has returned this. Have you tried it? Try using google to
find your answer, or maybe just repost.
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows Server 2003, Datacenter Edition
b.. Microsoft Windows Server 2003, Enterprise Edition
c.. Microsoft Windows 2000 Server
d.. Microsoft Windows 2000 Advanced Server
e.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q285923
SYMPTOMS
You may find that the following error messages are recorded in Event
Viewer every 5 minutes on domain controller computers and every 20
minutes on member server computers:
Userenv 1000
Windows cannot access the registry information at
\\domainname.com\sysvol\domainname.com\Policies\{
file://\\domainname.com\sysvol\domainname.com\Policies\{31B2F340-016D
D-11D2-945F-00C04FB984F9}\Machine\registry.pol with (1398).
SceCli 1001
Security policy cannot be propagated. Cannot access the template. Error
code=3.
Userenv 1000
The Group Policy client-side extension Security was passed flags (17)
and returned a failure status code of (3).
NtFrs 13508
Description: The File Replication Service is having trouble enabling
replication from (computername) to (computername) for
c:\winnt\sysvol\domain; retrying.
RESOLUTION
To resolve this issue, synchronize the computers with the domain
controller clock time. Follow these steps:
1.. Run the following command on all computers to synchronize the
clock time with the domain controller:
net time \\(domain controller name) /set /y
2.. Stop and then restart the File Replication Service on all servers
that are experiencing the problem.
3.. Open Event Viewer to make sure that
*************************************************************************
*****
PSS ID Number: 272279
Article Last Modified on 10/11/2002
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows 2000 Server
b.. Microsoft Windows 2000 Advanced Server
c.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q272279
SUMMARY
This article discusses how to troubleshoot the File Replication service
(FRS) and the Distributed file system (Dfs). The main emphasis, however,
of this article is to discuss a general procedure which can help you to
troubleshoot FRS problems.
MORE INFORMATION
You may observe that FRS has stopped replicating content on your system.
This behavior may occur because of many potential causes.
If your system experiences FRS problems, you can perform the following
general procedure to troubleshoot these problems:
1.. Check for free disk space on Computer A (source directory, staging
directory, and database partition) and Computer B (destination
partition, preinstall partition, and database partition). Look for the
following events in Event Viewer:
Event id:13511
Database is out of disk space.
Event id:13522
Staging directory is full. An outbound partner that has not connected
for a while can cause this. Delete the connection and stop and restart
FRS to force deletion of the staging files.
For additional information about how to move the database to a larger
volume, click the article number below to view the article in the
Microsoft Knowledge Base:
221093 How to Relocate the NTFRS Jet Database and Log Files
2.. Create a test file on Computer B and verify its replication to
Computer A.
3.. Verify that both Computer A and Computer B are available on the
network. Because FRS uses the fully qualified domain name (FQDN) of the
replica members, an appropriate first check is to use a ping command
specifying the fully qualified name of the problem replicas.
From Computer A, send a ping command with Computer B's FQDN. From
Computer B, send a ping command to Computer A's FQDN. Verify that the
addresses returned by the ping command are the same as the addresses
returned by an ipconfig /all command by means of the command line of the
destination computer.
4.. Access the Services administrative console by following these
steps:
1.. Click Start, and then click Run.
2.. In the Open box, type:
services.msc
Confirm that FRS runs on both computers. If the service is not
running, review the FRS container of Event Viewer (located in the
Eventvwr.msc file) on the computer experiencing the problem.
5.. Verify remote procedure call (RPC) connectivity between Computer A
and Computer B. An appropriate test may be to open Event Viewer on
Computer B from Computer A (which uses RPC). Check FRS event logs on
both computers. If Event ID 13508 is present, there may be a problem
with the RPC service on either computer or with creating a secure
connection between Computer A and Computer B.
6.. Use the Active Directory Sites and Services console to verify the
replication schedule on the Connection object. Ensure that replication
is enabled between Computer A and Computer B and that the connection is
enabled. The Connection object is the inbound connection under Computer
A's NTFRS MEMBER object from Computer B. For System Volume (SYSVOL), the
Connection object resides in the
Sites\Site name\Servers\Server name\Ntds Settings\Connection name
folder.
7.. For Dfs, view the connection links in Active Directory (AD) Users
and Computers. Open AD Users and Computer, click View from the menu and
ensure that Advanced Settings are selected. Go to the System container.
The location of the Connection objects are in the System\File
Replication Service\DFS Volumes folder.
8.. Verify whether or not the file on the originating server is locked
(cannot be accessed) on either computer. If the file is locked on
Computer B so that FRS cannot read the file, FRS cannot generate the
staging file, which delays replication. If the file is locked on
Computer A so that FRS cannot update the file, FRS continues to retry
the update until it succeeds. The retry interval is 30 to 60 seconds.
9.. Verify whether or not the source file had been excluded from
replication. Confirm that the file is not Encrypting File System (EFS)
encrypted, a NTFS file system (NTFS) junction, or excluded by a file or
folder filter on the originating replica member. If any of these
situations are true, FRS does not replicate the file or directory.
10.. If all of the previous conditions are met, you may have to
examine the log files that are created for FRS. The log files are
located in the %Systemroot%\Debug folder. The file names are listed from
NtFrs 001.log to NtFrs 005.log.
"admir" <admir@kuub3.nl> wrote in message
news:eiz5DzMvEHA.908@TK2MSFTNGP11.phx.gbl...
I have bean posting msg for help on evet id 13508. No one have ever
replayed
to me about it.
I cant figure out what to do about this. I folowed all documentation on
this
and yet no change.
Since I am am being ignored about this issue I have no joice but to stop
using DFS.
Thanks for nothing MS
|
|
|
| Back to top |
|
|
admir
Guest
|
| Posted:
Fri Oct 29, 2004 4:21 pm Post subject:
Re: Why am I being ingnored? |
|
|
O yeah, that is so bright. You buy something that is suposed to work and
then you have to pay to them to nake it work.
That is stealing.
"Glenn L" <the.only@gmail.com> wrote in message
news:eOMKuuVvEHA.3624@TK2MSFTNGP09.phx.gbl...
| Quote: | You may also consider opening a case with Microsoft PSS. For a nominal
fee,
they will fix this error for you.
--
Glenn L
CCNA, MCSE 2000, MCSE 2003 + Security
"Bob Hollness" <bob@blockbuster.com> wrote in message
news:Or675dQvEHA.3908@TK2MSFTNGP12.phx.gbl...
This is a public group and is not a forum that Microsoft will
exclusively
answer. Any help or advice given is by the general public and is often
based on their own experiences. So, maybe if nobody is answering your
post,
it is because nobody knows the answer. I have posted many times and
have
not been lucky enough to get an answer. This does not mean that you are
being ignored.
A quick google has returned this. Have you tried it? Try using google
to
find your answer, or maybe just repost.
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows Server 2003, Datacenter Edition
b.. Microsoft Windows Server 2003, Enterprise Edition
c.. Microsoft Windows 2000 Server
d.. Microsoft Windows 2000 Advanced Server
e.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q285923
SYMPTOMS
You may find that the following error messages are recorded in Event
Viewer every 5 minutes on domain controller computers and every 20
minutes on member server computers:
Userenv 1000
Windows cannot access the registry information at
\\domainname.com\sysvol\domainname.com\Policies\{
file://\\domainname.com\sysvol\domainname.com\Policies\{31B2F340-016D
D-11D2-945F-00C04FB984F9}\Machine\registry.pol with (1398).
SceCli 1001
Security policy cannot be propagated. Cannot access the template. Error
code=3.
Userenv 1000
The Group Policy client-side extension Security was passed flags (17)
and returned a failure status code of (3).
NtFrs 13508
Description: The File Replication Service is having trouble enabling
replication from (computername) to (computername) for
c:\winnt\sysvol\domain; retrying.
RESOLUTION
To resolve this issue, synchronize the computers with the domain
controller clock time. Follow these steps:
1.. Run the following command on all computers to synchronize the
clock time with the domain controller:
net time \\(domain controller name) /set /y
2.. Stop and then restart the File Replication Service on all servers
that are experiencing the problem.
3.. Open Event Viewer to make sure that
*************************************************************************
*****
PSS ID Number: 272279
Article Last Modified on 10/11/2002
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows 2000 Server
b.. Microsoft Windows 2000 Advanced Server
c.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q272279
SUMMARY
This article discusses how to troubleshoot the File Replication service
(FRS) and the Distributed file system (Dfs). The main emphasis, however,
of this article is to discuss a general procedure which can help you to
troubleshoot FRS problems.
MORE INFORMATION
You may observe that FRS has stopped replicating content on your system.
This behavior may occur because of many potential causes.
If your system experiences FRS problems, you can perform the following
general procedure to troubleshoot these problems:
1.. Check for free disk space on Computer A (source directory, staging
directory, and database partition) and Computer B (destination
partition, preinstall partition, and database partition). Look for the
following events in Event Viewer:
Event id:13511
Database is out of disk space.
Event id:13522
Staging directory is full. An outbound partner that has not connected
for a while can cause this. Delete the connection and stop and restart
FRS to force deletion of the staging files.
For additional information about how to move the database to a larger
volume, click the article number below to view the article in the
Microsoft Knowledge Base:
221093 How to Relocate the NTFRS Jet Database and Log Files
2.. Create a test file on Computer B and verify its replication to
Computer A.
3.. Verify that both Computer A and Computer B are available on the
network. Because FRS uses the fully qualified domain name (FQDN) of the
replica members, an appropriate first check is to use a ping command
specifying the fully qualified name of the problem replicas.
From Computer A, send a ping command with Computer B's FQDN. From
Computer B, send a ping command to Computer A's FQDN. Verify that the
addresses returned by the ping command are the same as the addresses
returned by an ipconfig /all command by means of the command line of the
destination computer.
4.. Access the Services administrative console by following these
steps:
1.. Click Start, and then click Run.
2.. In the Open box, type:
services.msc
Confirm that FRS runs on both computers. If the service is not
running, review the FRS container of Event Viewer (located in the
Eventvwr.msc file) on the computer experiencing the problem.
5.. Verify remote procedure call (RPC) connectivity between Computer A
and Computer B. An appropriate test may be to open Event Viewer on
Computer B from Computer A (which uses RPC). Check FRS event logs on
both computers. If Event ID 13508 is present, there may be a problem
with the RPC service on either computer or with creating a secure
connection between Computer A and Computer B.
6.. Use the Active Directory Sites and Services console to verify the
replication schedule on the Connection object. Ensure that replication
is enabled between Computer A and Computer B and that the connection is
enabled. The Connection object is the inbound connection under Computer
A's NTFRS MEMBER object from Computer B. For System Volume (SYSVOL), the
Connection object resides in the
Sites\Site name\Servers\Server name\Ntds Settings\Connection name
folder.
7.. For Dfs, view the connection links in Active Directory (AD) Users
and Computers. Open AD Users and Computer, click View from the menu and
ensure that Advanced Settings are selected. Go to the System container.
The location of the Connection objects are in the System\File
Replication Service\DFS Volumes folder.
8.. Verify whether or not the file on the originating server is locked
(cannot be accessed) on either computer. If the file is locked on
Computer B so that FRS cannot read the file, FRS cannot generate the
staging file, which delays replication. If the file is locked on
Computer A so that FRS cannot update the file, FRS continues to retry
the update until it succeeds. The retry interval is 30 to 60 seconds.
9.. Verify whether or not the source file had been excluded from
replication. Confirm that the file is not Encrypting File System (EFS)
encrypted, a NTFS file system (NTFS) junction, or excluded by a file or
folder filter on the originating replica member. If any of these
situations are true, FRS does not replicate the file or directory.
10.. If all of the previous conditions are met, you may have to
examine the log files that are created for FRS. The log files are
located in the %Systemroot%\Debug folder. The file names are listed from
NtFrs 001.log to NtFrs 005.log.
"admir" <admir@kuub3.nl> wrote in message
news:eiz5DzMvEHA.908@TK2MSFTNGP11.phx.gbl...
I have bean posting msg for help on evet id 13508. No one have ever
replayed
to me about it.
I cant figure out what to do about this. I folowed all documentation
on
this
and yet no change.
Since I am am being ignored about this issue I have no joice but to
stop
using DFS.
Thanks for nothing MS
|
|
|
| Back to top |
|
|
admir
Guest
|
| Posted:
Fri Oct 29, 2004 4:24 pm Post subject:
Re: Why am I being ingnored? |
|
|
Thank you for your replay. I realy tryed evrything. I folowed all
instructions that I could find but no luck. I just have to stop using DFS.
regards,
Admir
"Bob Hollness" <bob@blockbuster.com> wrote in message
news:Or675dQvEHA.3908@TK2MSFTNGP12.phx.gbl...
| Quote: | This is a public group and is not a forum that Microsoft will exclusively
answer. Any help or advice given is by the general public and is often
based on their own experiences. So, maybe if nobody is answering your
post,
it is because nobody knows the answer. I have posted many times and have
not been lucky enough to get an answer. This does not mean that you are
being ignored.
A quick google has returned this. Have you tried it? Try using google to
find your answer, or maybe just repost.
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows Server 2003, Datacenter Edition
b.. Microsoft Windows Server 2003, Enterprise Edition
c.. Microsoft Windows 2000 Server
d.. Microsoft Windows 2000 Advanced Server
e.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q285923
SYMPTOMS
You may find that the following error messages are recorded in Event
Viewer every 5 minutes on domain controller computers and every 20
minutes on member server computers:
Userenv 1000
Windows cannot access the registry information at
\\domainname.com\sysvol\domainname.com\Policies\{
file://\\domainname.com\sysvol\domainname.com\Policies\{31B2F340-016D
D-11D2-945F-00C04FB984F9}\Machine\registry.pol with (1398).
SceCli 1001
Security policy cannot be propagated. Cannot access the template. Error
code=3.
Userenv 1000
The Group Policy client-side extension Security was passed flags (17)
and returned a failure status code of (3).
NtFrs 13508
Description: The File Replication Service is having trouble enabling
replication from (computername) to (computername) for
c:\winnt\sysvol\domain; retrying.
RESOLUTION
To resolve this issue, synchronize the computers with the domain
controller clock time. Follow these steps:
1.. Run the following command on all computers to synchronize the
clock time with the domain controller:
net time \\(domain controller name) /set /y
2.. Stop and then restart the File Replication Service on all servers
that are experiencing the problem.
3.. Open Event Viewer to make sure that
*************************************************************************
*****
PSS ID Number: 272279
Article Last Modified on 10/11/2002
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows 2000 Server
b.. Microsoft Windows 2000 Advanced Server
c.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q272279
SUMMARY
This article discusses how to troubleshoot the File Replication service
(FRS) and the Distributed file system (Dfs). The main emphasis, however,
of this article is to discuss a general procedure which can help you to
troubleshoot FRS problems.
MORE INFORMATION
You may observe that FRS has stopped replicating content on your system.
This behavior may occur because of many potential causes.
If your system experiences FRS problems, you can perform the following
general procedure to troubleshoot these problems:
1.. Check for free disk space on Computer A (source directory, staging
directory, and database partition) and Computer B (destination
partition, preinstall partition, and database partition). Look for the
following events in Event Viewer:
Event id:13511
Database is out of disk space.
Event id:13522
Staging directory is full. An outbound partner that has not connected
for a while can cause this. Delete the connection and stop and restart
FRS to force deletion of the staging files.
For additional information about how to move the database to a larger
volume, click the article number below to view the article in the
Microsoft Knowledge Base:
221093 How to Relocate the NTFRS Jet Database and Log Files
2.. Create a test file on Computer B and verify its replication to
Computer A.
3.. Verify that both Computer A and Computer B are available on the
network. Because FRS uses the fully qualified domain name (FQDN) of the
replica members, an appropriate first check is to use a ping command
specifying the fully qualified name of the problem replicas.
From Computer A, send a ping command with Computer B's FQDN. From
Computer B, send a ping command to Computer A's FQDN. Verify that the
addresses returned by the ping command are the same as the addresses
returned by an ipconfig /all command by means of the command line of the
destination computer.
4.. Access the Services administrative console by following these
steps:
1.. Click Start, and then click Run.
2.. In the Open box, type:
services.msc
Confirm that FRS runs on both computers. If the service is not
running, review the FRS container of Event Viewer (located in the
Eventvwr.msc file) on the computer experiencing the problem.
5.. Verify remote procedure call (RPC) connectivity between Computer A
and Computer B. An appropriate test may be to open Event Viewer on
Computer B from Computer A (which uses RPC). Check FRS event logs on
both computers. If Event ID 13508 is present, there may be a problem
with the RPC service on either computer or with creating a secure
connection between Computer A and Computer B.
6.. Use the Active Directory Sites and Services console to verify the
replication schedule on the Connection object. Ensure that replication
is enabled between Computer A and Computer B and that the connection is
enabled. The Connection object is the inbound connection under Computer
A's NTFRS MEMBER object from Computer B. For System Volume (SYSVOL), the
Connection object resides in the
Sites\Site name\Servers\Server name\Ntds Settings\Connection name
folder.
7.. For Dfs, view the connection links in Active Directory (AD) Users
and Computers. Open AD Users and Computer, click View from the menu and
ensure that Advanced Settings are selected. Go to the System container.
The location of the Connection objects are in the System\File
Replication Service\DFS Volumes folder.
8.. Verify whether or not the file on the originating server is locked
(cannot be accessed) on either computer. If the file is locked on
Computer B so that FRS cannot read the file, FRS cannot generate the
staging file, which delays replication. If the file is locked on
Computer A so that FRS cannot update the file, FRS continues to retry
the update until it succeeds. The retry interval is 30 to 60 seconds.
9.. Verify whether or not the source file had been excluded from
replication. Confirm that the file is not Encrypting File System (EFS)
encrypted, a NTFS file system (NTFS) junction, or excluded by a file or
folder filter on the originating replica member. If any of these
situations are true, FRS does not replicate the file or directory.
10.. If all of the previous conditions are met, you may have to
examine the log files that are created for FRS. The log files are
located in the %Systemroot%\Debug folder. The file names are listed from
NtFrs 001.log to NtFrs 005.log.
"admir" <admir@kuub3.nl> wrote in message
news:eiz5DzMvEHA.908@TK2MSFTNGP11.phx.gbl...
I have bean posting msg for help on evet id 13508. No one have ever
replayed
to me about it.
I cant figure out what to do about this. I folowed all documentation on
this
and yet no change.
Since I am am being ignored about this issue I have no joice but to stop
using DFS.
Thanks for nothing MS
|
|
|
| Back to top |
|
|
admir
Guest
|
| Posted:
Fri Oct 29, 2004 8:46 pm Post subject:
Re: Why am I being ingnored? |
|
|
Thank you for your replay. I realy tryed evrything. I folowed all
instructions that I could find but no luck. I just have to stop using DFS.
regards,
Admir
"Bob Hollness" <bob@blockbuster.com> wrote in message
news:Or675dQvEHA.3908@TK2MSFTNGP12.phx.gbl...
| Quote: | This is a public group and is not a forum that Microsoft will exclusively
answer. Any help or advice given is by the general public and is often
based on their own experiences. So, maybe if nobody is answering your
post,
it is because nobody knows the answer. I have posted many times and have
not been lucky enough to get an answer. This does not mean that you are
being ignored.
A quick google has returned this. Have you tried it? Try using google to
find your answer, or maybe just repost.
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows Server 2003, Datacenter Edition
b.. Microsoft Windows Server 2003, Enterprise Edition
c.. Microsoft Windows 2000 Server
d.. Microsoft Windows 2000 Advanced Server
e.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q285923
SYMPTOMS
You may find that the following error messages are recorded in Event
Viewer every 5 minutes on domain controller computers and every 20
minutes on member server computers:
Userenv 1000
Windows cannot access the registry information at
\\domainname.com\sysvol\domainname.com\Policies\{
file://\\domainname.com\sysvol\domainname.com\Policies\{31B2F340-016D
D-11D2-945F-00C04FB984F9}\Machine\registry.pol with (1398).
SceCli 1001
Security policy cannot be propagated. Cannot access the template. Error
code=3.
Userenv 1000
The Group Policy client-side extension Security was passed flags (17)
and returned a failure status code of (3).
NtFrs 13508
Description: The File Replication Service is having trouble enabling
replication from (computername) to (computername) for
c:\winnt\sysvol\domain; retrying.
RESOLUTION
To resolve this issue, synchronize the computers with the domain
controller clock time. Follow these steps:
1.. Run the following command on all computers to synchronize the
clock time with the domain controller:
net time \\(domain controller name) /set /y
2.. Stop and then restart the File Replication Service on all servers
that are experiencing the problem.
3.. Open Event Viewer to make sure that
*************************************************************************
*****
PSS ID Number: 272279
Article Last Modified on 10/11/2002
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows 2000 Server
b.. Microsoft Windows 2000 Advanced Server
c.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q272279
SUMMARY
This article discusses how to troubleshoot the File Replication service
(FRS) and the Distributed file system (Dfs). The main emphasis, however,
of this article is to discuss a general procedure which can help you to
troubleshoot FRS problems.
MORE INFORMATION
You may observe that FRS has stopped replicating content on your system.
This behavior may occur because of many potential causes.
If your system experiences FRS problems, you can perform the following
general procedure to troubleshoot these problems:
1.. Check for free disk space on Computer A (source directory, staging
directory, and database partition) and Computer B (destination
partition, preinstall partition, and database partition). Look for the
following events in Event Viewer:
Event id:13511
Database is out of disk space.
Event id:13522
Staging directory is full. An outbound partner that has not connected
for a while can cause this. Delete the connection and stop and restart
FRS to force deletion of the staging files.
For additional information about how to move the database to a larger
volume, click the article number below to view the article in the
Microsoft Knowledge Base:
221093 How to Relocate the NTFRS Jet Database and Log Files
2.. Create a test file on Computer B and verify its replication to
Computer A.
3.. Verify that both Computer A and Computer B are available on the
network. Because FRS uses the fully qualified domain name (FQDN) of the
replica members, an appropriate first check is to use a ping command
specifying the fully qualified name of the problem replicas.
From Computer A, send a ping command with Computer B's FQDN. From
Computer B, send a ping command to Computer A's FQDN. Verify that the
addresses returned by the ping command are the same as the addresses
returned by an ipconfig /all command by means of the command line of the
destination computer.
4.. Access the Services administrative console by following these
steps:
1.. Click Start, and then click Run.
2.. In the Open box, type:
services.msc
Confirm that FRS runs on both computers. If the service is not
running, review the FRS container of Event Viewer (located in the
Eventvwr.msc file) on the computer experiencing the problem.
5.. Verify remote procedure call (RPC) connectivity between Computer A
and Computer B. An appropriate test may be to open Event Viewer on
Computer B from Computer A (which uses RPC). Check FRS event logs on
both computers. If Event ID 13508 is present, there may be a problem
with the RPC service on either computer or with creating a secure
connection between Computer A and Computer B.
6.. Use the Active Directory Sites and Services console to verify the
replication schedule on the Connection object. Ensure that replication
is enabled between Computer A and Computer B and that the connection is
enabled. The Connection object is the inbound connection under Computer
A's NTFRS MEMBER object from Computer B. For System Volume (SYSVOL), the
Connection object resides in the
Sites\Site name\Servers\Server name\Ntds Settings\Connection name
folder.
7.. For Dfs, view the connection links in Active Directory (AD) Users
and Computers. Open AD Users and Computer, click View from the menu and
ensure that Advanced Settings are selected. Go to the System container.
The location of the Connection objects are in the System\File
Replication Service\DFS Volumes folder.
8.. Verify whether or not the file on the originating server is locked
(cannot be accessed) on either computer. If the file is locked on
Computer B so that FRS cannot read the file, FRS cannot generate the
staging file, which delays replication. If the file is locked on
Computer A so that FRS cannot update the file, FRS continues to retry
the update until it succeeds. The retry interval is 30 to 60 seconds.
9.. Verify whether or not the source file had been excluded from
replication. Confirm that the file is not Encrypting File System (EFS)
encrypted, a NTFS file system (NTFS) junction, or excluded by a file or
folder filter on the originating replica member. If any of these
situations are true, FRS does not replicate the file or directory.
10.. If all of the previous conditions are met, you may have to
examine the log files that are created for FRS. The log files are
located in the %Systemroot%\Debug folder. The file names are listed from
NtFrs 001.log to NtFrs 005.log.
"admir" <admir@kuub3.nl> wrote in message
news:eiz5DzMvEHA.908@TK2MSFTNGP11.phx.gbl...
I have bean posting msg for help on evet id 13508. No one have ever
replayed
to me about it.
I cant figure out what to do about this. I folowed all documentation on
this
and yet no change.
Since I am am being ignored about this issue I have no joice but to stop
using DFS.
Thanks for nothing MS
|
|
|
| Back to top |
|
|
admir
Guest
|
| Posted:
Fri Oct 29, 2004 8:46 pm Post subject:
Re: Why am I being ingnored? |
|
|
Thank you for your replay. I realy tryed evrything. I folowed all
instructions that I could find but no luck. I just have to stop using DFS.
regards,
Admir
"Bob Hollness" <bob@blockbuster.com> wrote in message
news:Or675dQvEHA.3908@TK2MSFTNGP12.phx.gbl...
| Quote: | This is a public group and is not a forum that Microsoft will exclusively
answer. Any help or advice given is by the general public and is often
based on their own experiences. So, maybe if nobody is answering your
post,
it is because nobody knows the answer. I have posted many times and have
not been lucky enough to get an answer. This does not mean that you are
being ignored.
A quick google has returned this. Have you tried it? Try using google to
find your answer, or maybe just repost.
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows Server 2003, Datacenter Edition
b.. Microsoft Windows Server 2003, Enterprise Edition
c.. Microsoft Windows 2000 Server
d.. Microsoft Windows 2000 Advanced Server
e.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q285923
SYMPTOMS
You may find that the following error messages are recorded in Event
Viewer every 5 minutes on domain controller computers and every 20
minutes on member server computers:
Userenv 1000
Windows cannot access the registry information at
\\domainname.com\sysvol\domainname.com\Policies\{
file://\\domainname.com\sysvol\domainname.com\Policies\{31B2F340-016D
D-11D2-945F-00C04FB984F9}\Machine\registry.pol with (1398).
SceCli 1001
Security policy cannot be propagated. Cannot access the template. Error
code=3.
Userenv 1000
The Group Policy client-side extension Security was passed flags (17)
and returned a failure status code of (3).
NtFrs 13508
Description: The File Replication Service is having trouble enabling
replication from (computername) to (computername) for
c:\winnt\sysvol\domain; retrying.
RESOLUTION
To resolve this issue, synchronize the computers with the domain
controller clock time. Follow these steps:
1.. Run the following command on all computers to synchronize the
clock time with the domain controller:
net time \\(domain controller name) /set /y
2.. Stop and then restart the File Replication Service on all servers
that are experiencing the problem.
3.. Open Event Viewer to make sure that
*************************************************************************
*****
PSS ID Number: 272279
Article Last Modified on 10/11/2002
-------------------------------------------------------------------------
-------
The information in this article applies to:
a.. Microsoft Windows 2000 Server
b.. Microsoft Windows 2000 Advanced Server
c.. Microsoft Windows 2000 Datacenter Server
-------------------------------------------------------------------------
-------
This article was previously published under Q272279
SUMMARY
This article discusses how to troubleshoot the File Replication service
(FRS) and the Distributed file system (Dfs). The main emphasis, however,
of this article is to discuss a general procedure which can help you to
troubleshoot FRS problems.
MORE INFORMATION
You may observe that FRS has stopped replicating content on your system.
This behavior may occur because of many potential causes.
If your system experiences FRS problems, you can perform the following
general procedure to troubleshoot these problems:
1.. Check for free disk space on Computer A (source directory, staging
directory, and database partition) and Computer B (destination
partition, preinstall partition, and database partition). Look for the
following events in Event Viewer:
Event id:13511
Database is out of disk space.
Event id:13522
Staging directory is full. An outbound partner that has not connected
for a while can cause this. Delete the connection and stop and restart
FRS to force deletion of the staging files.
For additional information about how to move the database to a larger
volume, click the article number below to view the article in the
Microsoft Knowledge Base:
221093 How to Relocate the NTFRS Jet Database and Log Files
2.. Create a test file on Computer B and verify its replication to
Computer A.
3.. Verify that both Computer A and Computer B are available on the
network. Because FRS uses the fully qualified domain name (FQDN) of the
replica members, an appropriate first check is to use a ping command
specifying the fully qualified name of the problem replicas.
From Computer A, send a ping command with Computer B's FQDN. From
Computer B, send a ping command to Computer A's FQDN. Verify that the
addresses returned by the ping command are the same as the addresses
returned by an ipconfig /all command by means of the command line of the
destination computer.
4.. Access the Services administrative console by following these
steps:
1.. Click Start, and then click Run.
2.. In the Open box, type:
services.msc
Confirm that FRS runs on both computers. If the service is not
running, review the FRS container of Event Viewer (located in the
Eventvwr.msc file) on the computer experiencing the problem.
5.. Verify remote procedure call (RPC) connectivity between Computer A
and Computer B. An appropriate test may be to open Event Viewer on
Computer B from Computer A (which uses RPC). Check FRS event logs on
both computers. If Event ID 13508 is present, there may be a problem
with the RPC service on either computer or with creating a secure
connection between Computer A and Computer B.
6.. Use the Active Directory Sites and Services console to verify the
replication schedule on the Connection object. Ensure that replication
is enabled between Computer A and Computer B and that the connection is
enabled. The Connection object is the inbound connection under Computer
A's NTFRS MEMBER object from Computer B. For System Volume (SYSVOL), the
Connection object resides in the
Sites\Site name\Servers\Server name\Ntds Settings\Connection name
folder.
7.. For Dfs, view the connection links in Active Directory (AD) Users
and Computers. Open AD Users and Computer, click View from the menu and
ensure that Advanced Settings are selected. Go to the System container.
The location of the Connection objects are in the System\File
Replication Service\DFS Volumes folder.
8.. Verify whether or not the file on the originating server is locked
(cannot be accessed) on either computer. If the file is locked on
Computer B so that FRS cannot read the file, FRS cannot generate the
staging file, which delays replication. If the file is locked on
Computer A so that FRS cannot update the file, FRS continues to retry
the update until it succeeds. The retry interval is 30 to 60 seconds.
9.. Verify whether or not the source file had been excluded from
replication. Confirm that the file is not Encrypting File System (EFS)
encrypted, a NTFS file system (NTFS) junction, or excluded by a file or
folder filter on the originating replica member. If any of these
situations are true, FRS does not replicate the file or directory.
10.. If all of the previous conditions are met, you may have to
examine the log files that are created for FRS. The log files are
located in the %Systemroot%\Debug folder. The file names are listed from
NtFrs 001.log to NtFrs 005.log.
"admir" <admir@kuub3.nl> wrote in message
news:eiz5DzMvEHA.908@TK2MSFTNGP11.phx.gbl...
I have bean posting msg for help on evet id 13508. No one have ever
replayed
to me about it.
I cant figure out what to do about this. I folowed all documentation on
this
and yet no change.
Since I am am being ignored about this issue I have no joice but to stop
using DFS.
Thanks for nothing MS
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in