asked on

ArcServe 11.1 - CANWLIC.NLM states Host not initialized

Running CA ArcServe 11.1 SP3 on a NW 6.5 SP7 system, I've suddenly started receiving the following error messages loading ArcServe:

"CANWLIC.NLM: Host not initialized"

As a result, ASDB eventually unloads and ArcServe left not functional. :-(

System is running FC and connected to a SAN. No changes has been made to licensing, modules or their load order on the server.

Any ideas?

-- Klaus

ASKER CERTIFIED SOLUTION

Naga Bhanu Kiran Kota

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

kacfm

ASKER

Hi Bhanu

Unfortunately it seems that changer and drive as well as the FC board registers correctly. (Please see the snippet for CSLOADER.LOG).

I haven't been changing the configuration on the server, the changer or the FC network. Not directly

I've got configurations running in other locations that works. On those locations, CSLOADER.LOG contains identical entries and CANWLIC.NLM

CANWLIC.NLM is a license verification utility. The "physical" error message puzzles me...

-- Klaus

From CSLOADER.LOG:
------------------
********************************************************
Oct-08 01:12:28    BINDING : ADAPTER [QL2X00.HAM]  /  [2] DEVICES
Oct-08 01:12:29    DEV 000: [V599-A3-D1:1] ADIC    Scalar i500     410 Is
                   Registered
Oct-08 01:12:29    DEV 001: [V599-A3-D1:0] IBM     ULTRIUM-TD4     74H Is
                   Registered
Oct-08 01:12:30    ********************************************************
Oct-08 01:12:30    Searching for valid Adapters, Please wait.
Oct-08 01:12:30    BrightStor ARCserve r11.1 SP3 SCSI CDM FC Device Driver
                   (Build 991.011 01/03/07)
Oct-08 01:12:31    r11.10 SP3     1 March, 2007
Oct-08 01:12:35    Fibre Channel Board Driver is ready

Open in new window

kacfm

ASKER

Update: Digging deeper into the setup, it turns out that the setup is using the SAN Option on a total of 5 serveres on this location. The primary server was *NOT* the backupserver, but on of the production servers hosting a data share. ArcServe on the production server was for som reason not running properly.

So, in reality, it was a physical/hardware problem although the hardware in this case was kind of virtualized(controlled by another party.

I now have som other problems like STANDARD.NLM crashing on the backup server, but that's going to be another story...

-- Klaus

-- Klaus

kacfm

ASKER

Using the SAN option on several servers made things a little foggy...
Cheers.