| Author |
Message |
Stephen
Guest
|
 Posted:
Wed Jan 19, 2005 2:35 am Post subject:
Ultrasound event errors |
|
|
Have had DFS/FRS and ultrasound running without issue for some time. Last
night I added a new DFS target to an existing link. After some time I got
some errors in Ultrasound and the event log stating that the staging
directory was full. So, I edited the registry to increase the size of the
staging directory on the affected server and restarted ntfrs.
After the large initial synchronisation, the staging directory emptied,
there have not been any new event log entries, and I can physically verify
the the targets are synchronised.
However, ultrasound continues to produce errors that the FRS staging space
is full on this server every few hours, and shows the server as being sick.
I resolve the ultrasound events, but they just keep coming back:
FRS event log (continuous) - FRS staging space full
The File Replication Service has detected that the staging directory is
full. See the "Staging directory is full" topic in the Ultrasound
documentation.
Alert data entries:
Server ReplicaSet EventID Description Severity Timestamp Param1 Param2
TimeSinceEvent ServerID ReplicaSetID MemberID WindowsEventID
ServiceStartTime ServerBootTime IsAfterRestart UpdateID StartTime EndTime
ozzie sysvol [fdn-calpoly] 13522 Service paused because staging area is full
Warning 1/17/2005 3:30:00 PM 1450960 - 18:09:35 2 1 2 50 1/17/2005 7:03:00
PM 1/17/2005 8:39:00 AM 0 37759 1/18/2005 9:39:00 AM <not set>
Looking at the FRS event log (continuous), the alert data entries happened a
day ago. And again, nothing in the event logs, staging directory has
remained empty, and very little synchronisation has needed to take place
since the origonal synchronisation, as only a few files have been updated.
Still, we continue to get Ultrasound FRS staging space full events every few
hours. How can I make them stop?
I'm probably missing something really obvious here, but any help would be
appreciated.
Thank you,
Stephen B. |
|
| Back to top |
|
 |
Maxim Stepin [MSFT]
Guest
|
| Posted:
Wed Jan 19, 2005 5:07 am Post subject:
Re: Ultrasound event errors |
|
|
Stephen,
This error should disapper after 24 hours since the last time event was
reported.
-- Maxim
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.
"Stephen" <sbarash@ns.calpoly.edu> wrote in message
news:OTETI1Z$EHA.3908@TK2MSFTNGP12.phx.gbl...
| Quote: | Have had DFS/FRS and ultrasound running without issue for some time. Last
night I added a new DFS target to an existing link. After some time I got
some errors in Ultrasound and the event log stating that the staging
directory was full. So, I edited the registry to increase the size of the
staging directory on the affected server and restarted ntfrs.
After the large initial synchronisation, the staging directory emptied,
there have not been any new event log entries, and I can physically verify
the the targets are synchronised.
However, ultrasound continues to produce errors that the FRS staging space
is full on this server every few hours, and shows the server as being
sick.
I resolve the ultrasound events, but they just keep coming back:
FRS event log (continuous) - FRS staging space full
The File Replication Service has detected that the staging directory is
full. See the "Staging directory is full" topic in the Ultrasound
documentation.
Alert data entries:
Server ReplicaSet EventID Description Severity Timestamp Param1 Param2
TimeSinceEvent ServerID ReplicaSetID MemberID WindowsEventID
ServiceStartTime ServerBootTime IsAfterRestart UpdateID StartTime EndTime
ozzie sysvol [fdn-calpoly] 13522 Service paused because staging area is
full Warning 1/17/2005 3:30:00 PM 1450960 - 18:09:35 2 1 2 50 1/17/2005
7:03:00 PM 1/17/2005 8:39:00 AM 0 37759 1/18/2005 9:39:00 AM <not set
Looking at the FRS event log (continuous), the alert data entries happened
a day ago. And again, nothing in the event logs, staging directory has
remained empty, and very little synchronisation has needed to take place
since the origonal synchronisation, as only a few files have been updated.
Still, we continue to get Ultrasound FRS staging space full events every
few hours. How can I make them stop?
I'm probably missing something really obvious here, but any help would be
appreciated.
Thank you,
Stephen B.
|
|
|
| Back to top |
|
|
Stephen
Guest
|
| Posted:
Wed Jan 19, 2005 6:47 am Post subject:
Re: Ultrasound event errors |
|
|
I hope so. Thanks!
Stephen
"Maxim Stepin [MSFT]" <maximst@online.microsoft.com> wrote in message
news:OI1hRKb$EHA.2016@TK2MSFTNGP15.phx.gbl...
| Quote: | Stephen,
This error should disapper after 24 hours since the last time event was
reported.
-- Maxim
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.
"Stephen" <sbarash@ns.calpoly.edu> wrote in message
news:OTETI1Z$EHA.3908@TK2MSFTNGP12.phx.gbl...
Have had DFS/FRS and ultrasound running without issue for some time. Last
night I added a new DFS target to an existing link. After some time I got
some errors in Ultrasound and the event log stating that the staging
directory was full. So, I edited the registry to increase the size of the
staging directory on the affected server and restarted ntfrs.
After the large initial synchronisation, the staging directory emptied,
there have not been any new event log entries, and I can physically
verify
the the targets are synchronised.
However, ultrasound continues to produce errors that the FRS staging
space
is full on this server every few hours, and shows the server as being
sick.
I resolve the ultrasound events, but they just keep coming back:
FRS event log (continuous) - FRS staging space full
The File Replication Service has detected that the staging directory is
full. See the "Staging directory is full" topic in the Ultrasound
documentation.
Alert data entries:
Server ReplicaSet EventID Description Severity Timestamp Param1 Param2
TimeSinceEvent ServerID ReplicaSetID MemberID WindowsEventID
ServiceStartTime ServerBootTime IsAfterRestart UpdateID StartTime EndTime
ozzie sysvol [fdn-calpoly] 13522 Service paused because staging area is
full Warning 1/17/2005 3:30:00 PM 1450960 - 18:09:35 2 1 2 50 1/17/2005
7:03:00 PM 1/17/2005 8:39:00 AM 0 37759 1/18/2005 9:39:00 AM <not set
Looking at the FRS event log (continuous), the alert data entries
happened a day ago. And again, nothing in the event logs, staging
directory has remained empty, and very little synchronisation has needed
to take place since the origonal synchronisation, as only a few files
have been updated. Still, we continue to get Ultrasound FRS staging space
full events every few hours. How can I make them stop?
I'm probably missing something really obvious here, but any help would be
appreciated.
Thank you,
Stephen B.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in