Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
nsrmmd.exe application error
- Thread starter oasys
- Start date
As nsrmmd is the program that controls the backup device, it is used for backup and recoveries.
Besides that, nobody could help if you do not specify at least minimum details like
NetWorker version, Service Packs etc...
More info from ..\nsr\logs\daemon.log will as well not harm.
Besides that, nobody could help if you do not specify at least minimum details like
NetWorker version, Service Packs etc...
More info from ..\nsr\logs\daemon.log will as well not harm.
- Thread starter
- #3
Sorry:
Networker 6.1 on a windows 2000 server with SP2
There does't appear to be any thing in the Daemon.log other than label names being used, completed backup sets, the same message as below about groups already running, sending email to user that sets are complete or not.
I have checked the event logs on the server, there seems to be on consist error for networker that is "Group SQLDaily aborted, savegrp is already running". This error is not only for SQLDaily but for other groups as well.
I'm assuming that savegrp is the same as job group, if this is the case nothing else appears to be runing.
Networker 6.1 on a windows 2000 server with SP2
There does't appear to be any thing in the Daemon.log other than label names being used, completed backup sets, the same message as below about groups already running, sending email to user that sets are complete or not.
I have checked the event logs on the server, there seems to be on consist error for networker that is "Group SQLDaily aborted, savegrp is already running". This error is not only for SQLDaily but for other groups as well.
I'm assuming that savegrp is the same as job group, if this is the case nothing else appears to be runing.
Please update to 6.2 this should not require new enablers, i have had problems with 6.1 which have been fixed in 6.2.
Other then that you need to give log more info, what are your devices, what is in Deamon log, message log, what is cleints version of networker ?
Test individual cleints by placing them in Default group and running them, you may find a client that hangs , may be becasue it has removable storage device, jukebox attached or similar thing which does not backup correclty via ALL save set, you need to specify C, D or E and not ALL if you hvae such a device that way it wont try to backup jukebox type of devices and hang.
Other then that you need to give log more info, what are your devices, what is in Deamon log, message log, what is cleints version of networker ?
Test individual cleints by placing them in Default group and running them, you may find a client that hangs , may be becasue it has removable storage device, jukebox attached or similar thing which does not backup correclty via ALL save set, you need to specify C, D or E and not ALL if you hvae such a device that way it wont try to backup jukebox type of devices and hang.
Correct, a group is started every day at the same time. If your backups or clones take too long, the group has not finished when the group is started the next day. This of course will cause problems.
Find out why your backup take so long and avoid it. Also try to optimize cloning (if used). Let's solve this problem first.
Find out why your backup take so long and avoid it. Also try to optimize cloning (if used). Let's solve this problem first.
- Thread starter
- #6
I'm a little confused, if I open up the groups and if I see the clock that means the jobs are still running, but that is not the case. All I see is the ! to me meaning that the job is finished. If I click on details for one of the group which it appears to be running, it looks like it has finished. If I check the monitor tab there is nothing in there that indicates that the job is still going.
What I have found is that a most of the jobs are set to All instead of the C: D: as recommended. I will make the changes an see what happens.
The client versions are 6.0.1.0
The device is a ALT P1000 with 4 tape drives in it.
Index log has a lot of this:
Oct 11 18:56:20 bus1.tmpl2k.local: NetWorker Index: (warning) Filesystem containing file index for client 'cgyfs02' is getting full. This error appears for a lot of groups resent dates.
Getting back to basics what log files should I be looking at to see if where the problem might be? I know of the index, message and daemon.logs? Are there any others that I should be aware of?
What I have found is that a most of the jobs are set to All instead of the C: D: as recommended. I will make the changes an see what happens.
The client versions are 6.0.1.0
The device is a ALT P1000 with 4 tape drives in it.
Index log has a lot of this:
Oct 11 18:56:20 bus1.tmpl2k.local: NetWorker Index: (warning) Filesystem containing file index for client 'cgyfs02' is getting full. This error appears for a lot of groups resent dates.
Getting back to basics what log files should I be looking at to see if where the problem might be? I know of the index, message and daemon.logs? Are there any others that I should be aware of?
O.K. - the icons may show a different information but the message about the aborted group states the problem clearly.
The message about the index getting full means that you are running out of space on your NetWorker disk (the \nsr directory). You should correct this. However, it should not harm the system - worst case, new backups will just wait until you delete some files.
All log files are saved in ..\nsr\logs. There is no other location. My personal favorite is the daemon.log file - it tells you what NW does not report somehow else.
However, we are just discussing different problems than your initial one. Actually, there is a hint in the NW 6.1.1/Windows release notes (pages 21) about a known MS problem:
Desktop Heap Size Limitation in Windows NT/2000 (LGTpa31647)
Windows NT and 2000 have a set desktop heap size limitation that produces the
following error message:
The application failed to initialize properly
The problem is described in the following articles found in the Microsoft Knowledge
Base at • PRB: “Failed initialization on Comctl32.dll” from a Service (Article ID: Q225102)
• Overcoming User32.dll Initialization Failure Errors (Article ID: Q142676)
The message about the index getting full means that you are running out of space on your NetWorker disk (the \nsr directory). You should correct this. However, it should not harm the system - worst case, new backups will just wait until you delete some files.
All log files are saved in ..\nsr\logs. There is no other location. My personal favorite is the daemon.log file - it tells you what NW does not report somehow else.
However, we are just discussing different problems than your initial one. Actually, there is a hint in the NW 6.1.1/Windows release notes (pages 21) about a known MS problem:
Desktop Heap Size Limitation in Windows NT/2000 (LGTpa31647)
Windows NT and 2000 have a set desktop heap size limitation that produces the
following error message:
The application failed to initialize properly
The problem is described in the following articles found in the Microsoft Knowledge
Base at • PRB: “Failed initialization on Comctl32.dll” from a Service (Article ID: Q225102)
• Overcoming User32.dll Initialization Failure Errors (Article ID: Q142676)
DavinaTreiber
Technical User
DON'T upgrade to 6.2 as fazil1 suggested. 6.2 is a dead end and is also quite old now. It was produced only to support XP clients and some NDMP functionality. If you upgrade, go to 6.1.4 (much newer than 6.2) or to 7.1.1.
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question