having this error come up repeatedly, it just pushes the processor to a
constant 60%. if i kill the inventory service and delete files out of the
dbdir, then do a startinv, everything works fine for about 2 minutes -- then
this will start up again. it's not the same machine(s) over & over. the
machines that fail have the zen4 agent, zen3.2 & zen6.5 components seem to
work fine. our machine will start the inventory process on screen saver
activation. running nw65, zen65 backend, r/w replica of tree on server.
machine is dedicated to zen65, inventory server is installed on the same box
as root server w/ machines attached.

the inventory service object shows this as it's server status:

106: Storer successfully connected to the database.
105: Database connection failed.
106: Storer successfully connected to the database.
105: Database connection failed.
106: Storer successfully connected to the database.
105: Database connection failed.
106: Storer successfully connected to the database.
105: Database connection failed.
106: Storer successfully connected to the database.
105: Database connection failed.

here's the inventory screen on the console:

Trying to connect to the database -> MW_DBA
jdbc:sybase:Tds:172.22.176.5:2638?ServiceName=mgmt db&JCONNECT_VERSION=4
Successfully connected to the database
Database connection restored.Retrying the str file
000347C74E32_1095956942000
7.STR
Storer: started storing 000347C74E32_1095956942000_147.STR (120198 bytes)
Storer: Full scan being processed for CN=SOUTH-CIRC.OU=Workstations.O=SOUTH
Error in parsing:Could not process 000347C74E32_1095956942000_147.STR due to
Operation failure..will retry

Trying to connect to the database -> MW_DBA
jdbc:sybase:Tds:172.22.176.5:2638?ServiceName=mgmt db&JCONNECT_VERSION=4
Successfully connected to the database
Database connection restored.Retrying the str file
000347C74E32_1095956942000
7.STR
Storer: started storing 000347C74E32_1095956942000_147.STR (120198 bytes)
Storer: Full scan being processed for CN=SOUTH-CIRC.OU=Workstations.O=SOUTH
Error in parsing:Could not process 000347C74E32_1095956942000_147.STR due to
Operation failure..will retry

--
Josh Messerschmitt