> nsrd media warning: rd=nsrrat1.host.magwien.gv.at:\\.\Tape1 
> writing: The 
> semaphore timeout period has expired., at file 1095 record 304
> 
Are there any messages in the eventlog around the time you get the
semaphore errors?
Unfortunately it is a generel 'resource not available' message:
http://www.techspot.com/vb/all/windows/t-87193-Error-0x80070079-the-sema
phore-timeout-period-has-expired.html
1. A heavy load on the server is causing processes to be delayed from
releasing semaphores.

2. A process has crashed while holding a semaphore, causing other
processes to block when trying to acquire the semaphore.

3. Deadly embrace, semaphore contention where two tasks are waiting on
each other and neither task is able to break the loop. In the simplest
case, thread A is trying to get a semaphore which is owned by B, while B
is trying to get a different semaphore which is owned by A. More complex
combinations are also possible: A wants a semaphore owned by B, who
wants a semaphore owned by C, who wants a semaphore owned by A, etc.

4. If a process was to fail to set a semaphore during execution, another
process dependent on the semaphore will be blocked awaiting the
semaphore.

So some other program (Anti Virus?) may be causing this.

Hope this helps,
regards,
Cor.

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER