Hi Everyone,
I hope that you are all enjoying your Monday :D
We are having pretty much the same issue on a site here and would like some
feedback if anyone has any ideas.
An overland NEO8000 keeps on blocking for unknown reasons. A restart of the
autochanger usually repairs this.
Here are the errors in the daemon.log
02/02/08 11:21:27 nsrmmgd: RAP error: Invalid resource data.
02/02/08 11:21:27 nsrmmgd: Cannot update operation status resource (instance
7946).
02/02/08 11:21:29 nsrd: Operation 7947 started : Load volume `LTO450L3'.
.
02/02/08 11:21:31 nsrd: [Jukebox `rd=sapp065:NEO8000', operation # 7947].
device is not idle
02/02/08 11:21:31 nsrmmgd: device is not idle
02/02/08 11:21:32 nsrmmgd: Jukebox `rd=sapp065:NEO8000' failed to load the
requested volume.
02/02/08 11:21:35 nsrd: [Jukebox `rd=sapp065:NEO8000', operation # 7947].
Finished with status: retryable
02/02/08 11:21:35 nsrmmgd: RAP error: Invalid resource data.
02/02/08 11:21:35 nsrmmgd: Cannot update operation status resource (instance
7947).
In the Windows Event log, the following appears:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 28/01/2008
Time: 13:37:32
User: N/A
Computer: SAPP065
Description:
Faulting application nsrmmd.exe, version 7.3.3.0, faulting module nsrmmd.exe,
version 7.3.3.0, fault address 0x00025fac.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6e 73 72 ure nsr
0018: 6d 6d 64 2e 65 78 65 20 mmd.exe
0020: 37 2e 33 2e 33 2e 30 20 7.3.3.0
0028: 69 6e 20 6e 73 72 6d 6d in nsrmm
0030: 64 2e 65 78 65 20 37 2e d.exe 7.
0038: 33 2e 33 2e 30 20 61 74 3.3.0 at
0040: 20 6f 66 66 73 65 74 20 offset
0048: 30 30 30 32 35 66 61 63 00025fac
Any ideas most Appreciated
Best regards
+----------------------------------------------------------------------
|This was sent by hydec AT fr.mti DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
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
|