ITEM: AJ6155L

0514-001 error on cfgvidarscan and cfghiresscan (3rd party)

Question:

Env:    3.2.5, model 25T, Vidar TrueScan scanner

Desc:   On "cfgmgr", customer gets:

Method error (/etc/methods/cfgvidarscan -l /dev/vidar0):
        0514-001 System error:
sh: /etc/methods/cfgvidarscan:  not found

Method error (/etc/methods/cfghiresscan -l /dev/hires0):
        0514-001 System error:
sh: /etc/methods/cfghiresscan:  not found

Method error (/etc/methods/cfghiresscan -l /dev/hires0):
        0514-001 System error:
sh: /etc/methods/cfghiresscan:  not found

Method error (/etc/methods/cfgvidarscan -l /dev/vidar0):
        0514-001 System error:
sh: /etc/methods/cfgvidarscan:  not found

Method error (/etc/methods/cfghiresscan -l /dev/hires0):
        0514-001 System error:
sh: /etc/methods/cfghiresscan:  not found

        This is a third party driver.  The scanner had been removed
        with "rmdev -dl hires0".

        One interesting note is that the previous version of the driver
        called the device vidar0 and the newer one calls it hires0.

Action: First confirmed that there was no SCSI id conflict.  We looked
        for the configuration methods in /etc/methods and
        /usr/lib/methods; they were not present.  We found backup files
        in the following directories:

        /usr/lpp/vidarscan/inst_root/etc/methods
        /usr/lpp/hiresscan/inst_root/etc/methods

        According to the customer, the vidarscan drivers are an older
        version, and everything is now called hiresscan.  Even the
        device is now hires0.

        Checked the Config_Rules file:
        \# odmget Config_Rules | grep vidar:

rule = "/etc/methods/cfgvidarscan -l /dev/vidar0"
rule = "/etc/methods/cfgvidarscan -l /dev/hires0"

        \# odmget Config_Rules | grep hires:

rule = "/etc/methods/cfghiresscan -l /dev/hires0"
rule = "/etc/methods/cfghiresscan -l /dev/hires0"
rule = "/etc/methods/cfghiresscan -l /dev/hires0"

        \# ls -l /etc/methods | grep vidar : nothing
        \# ls -l /etc/methods | grep hires : nothing

        Made a backup of Config_Rules and removed the above entries:

        \# odmdelete -q "rule='/etc/methods/cfgvidarscan -l /dev/vidar0'" \\
                -o Config_Rules
        \# odmdelete -q "rule='/etc/methods/cfghiresscan -l /dev/hires0'" \\
                -o ConfigRules

        "cfgmgr" now came back clean.

        We found them in /usr/lpp/vidarscan/inst_root/etc/methods and
        /usr/lpp/hiresscan/inst_root/etc/methods.

        We copied over cfghiresscan to /etc/methods, copied back the
        good copy of Config_Rules, and removed the cfgvidarscan entries.

Method error (/etc/methods/cfghiresscan -l /dev/hires0)
        0514-023 The specified device does not exist in the customized
        device configuration database.

(this error appeared three times)

        \# odmget CuDv | grep hires : nothing
        \# odmget PdDv | grep hires : nothing
        \# odmget PdDv | grep vidar : nothing
        \# odmget PdAt | grep hires : nothing
        \# odmget PdCn | grep hires : nothing

        \# odmget -q "rule='/etc/methods/cfghiresscan -l /dev/hires0'" \\
                Config_Rules

Config_Rules:
        phase = 2
        seq = 0
        boot_mask = 0
        rule = "/etc/methods/cfghiresscan"

Config_Rules:
        phase = 2
        seq = 0
        boot_mask = 0
        rule = "/etc/methods/cfghiresscan"

Config_Rules:
        phase = 2
        seq = 0
        boot_mask = 0
        rule = "/etc/methods/cfghiresscan"

        \# odmget Config_Rules > /tmp/CR.edit
        Edited /tmp/CR.edit to remove two entries, and ran
        "odmdelete -o Config_Rules" and "odmadd /tmp/filename".  We ran
        "cfgmgr" again and got the 0415-023 error again.

        It seems that these drivers are not even installed.  The
        customer reinstalled the drivers and the device hires0 was
        automatically configured.  We checked Config_Rules and there
        were now two rules for cfghiresscan.  We went through the
        above process (making an ASCII file, editing it, removing all
        of Config_Rules class and running odmadd) again to remove the
        other entry.  The customer tested the scanner and everything
        works.

        There were two fundamental problems that originated this
        problem:

        1.  The drivers were no longer installed, or had been
            deleted.  This included the configuration methods.

        2.  Each successive driver install added an entry to the
            object class Config_Rules, but removing the driver did
            not remove the entry from that same class, as it did
            with the files in the Predefined Device Configuration
            Database.  This included the upgrade in drivers, that
            called the new product hires, rather than vidar.

Next:   Close call.



Support Line: 0514-001 error on cfgvidarscan and cfghiresscan (3rd party) ITEM: AJ6155L

Dated: July 1995 Category: N/A

This HTML file was generated 99/06/24~13:30:27

Comments or suggestions?
Contact us