E15030: Failed to receive data/request...

[rajpenguin]

We're running Arcserve 7 for Netware (5)....

I'm receiving E15030 numerous times, consequently servers are not being backed up. It seems the same servers are the ones not being connected to.

As indicated in a previous thread, we've rebooted the Novell server but continue to receive the error.

The db has been blown away, the server recreated etc. - essentially started from scratch, and we continue to receive this error (among others.. E15040, 3011.. see earlier thread titled BTRV from me).

Any help/suggestions is appreciated!
- Raj

 

[r2nguy]

rajpenquin:
We also have been having this problem. Are you using the nwagent? We have it specifically on two servers and it abends them both. We recently applied the latest patch: QO19341.CAZ, but to no avail. The nwagent log shows that it counts the files and amount to backup, but times out after 30 minutes. CA is currently working on why with us as this is a continuation of an original problem of not being able to backup in a mixed Novell environment (4.11 & 5.1). I will forward any positive informatiion that I receive if these are the same symptoms.

 

[aling]

NWagent is intermittently abending our NW6 servers (they do not have NW sp1).
We are backing up with AS2000.

Have you applied the 3 patches listed at the CA site? Two of them are Netware patches for NW6 and 1 is a CA patch:

(Novell docs. 10065605 and 2960484) NW6SMS1A.exe
(Novell doc. 2960932) 011210n6.exe
CA cumulative patch Qo05996

Do not reboot until all three are installed.

Also, NWagent abended server until we bound IPX to one of the cards. You do not have to back up through IPX, but it had to be bound. This fixed the constant and immediate crashing. However, we still have intermittent abends.

Thanks.

 

[fatboy69]

I would suggest checking the version of interleav.nlm on your server. 15030 are associated with 15028 and 24. I have found it to be the version of Interleav.nlm. If you are receiving these errors when backing up an NT and using rotation scheme then you need to use a custom schedule as this is a known problem within CA but not documented on their site. They keep bringing out fixes that just cause more problems.

If this is only Netware agents then apply the latest patches from CA - QO19341, QO19337(agent) and any prerequisites of the above. That will probably fix it. Also look at you duplex settings on your network card and leave the setting on the server for the protocol to use as AUTO.

You can spend way too much time on this trying to get it to work which shouldn’t be the case!!!