Failed to get WIF path

Question

I have Zen 7 Asset Inventory (7.00.0050 SP1 Interim Release 14) installed
on a W2K3 standard SP2 server.
I was getting inventory from my test clients until a couple of weeks ago.
I discovered this because I rolled out the lights out install of the
client to the rest of my workstations (about 450) last night and none of
them showed up in the web console.
Now on my clients (old and new), with Diagnostics on, I get "failed to get
WIF path" in the colw32.log on all my clients. This is the only error
that I can find anywhere.
I have verified that the inventory
service is running.
I have captured packets on both client and server and
verified that there is traffic to and from 7460 and 7461 as expected.
My catalog.ini file on the clients is empty and there is not a current
..wif file in the InboxCC folder.
What am I doing wrong?

Answer 1

Not really. :-)
On Fri, 25 Jan 2008 19:46:01 +0000, TDH wrote:
>
> You'd be amazed at just how often that happens... 8)
>
> -- Tim --
>
> tagross;1454053 Wrote:
>> I've figured this out and I want to share it so that if anyone does the
>> same dumb thing I did they know how to fix it.
>>
>> When I created the NAL installation app I didn't make sure the the
>> registry keys:
>> \HKEY_LOCAL_MACHINE\SOFTWARE\Tally Systems
>> Corp.\TSCensus\CollectionClient\WorkstationOID & WifName
>>
>> were not populated with the wrong info. The agents were trying to
>> connect
>> to the server with a duplicate Workstation OID and everything was wrong
>> so
>> it kept overwriting 1 single entry on the server.
>>
>> I created a new app that deleted those reg entries and Voila', my
>> workstations began showing up in my inventory. I also created a .mst
>> and
>> updated my original install app to not populate those fields.
>>
>> On Thu, 24 Jan 2008 18:10:19 +0000, Tim Gross wrote:
>>
>> > I built a generic clean XP machine and installed the client from the
>> CD
>> > and it initially got the same error. However, after a couple of
>> minutes I
>> > noticed that it built a .wif file and registered with the server so
>> > apparently there is a problem with our policies.
>> >
>> > Which policies specifically do I need to check?
>> >
>> > On Thu, 24 Jan 2008 16:20:39 +0000, TDH wrote:
>> >
>> >> Tim, that message indicates that the Collector has found the
>> registry key
>> >> from which it expects to get the name of the WIF (inventory) file
>> it's
>> >> expected to write, but the registry key is empty at collection time.
>> Do
>> >> you have a corporate policy in place that inhibits writing to the
>> >> workstations' registries? Are the ZAM Clients running as a service
>> with
>> >> administrative credentials?
>> >>
>> >> The ZAM Client and Collector need full access privileges to the ZAM
>> >> portion of the Program Files directory as well as to their own
>> portion of
>> >> the registry at HKEY_LOCAL_MACHINESOFTWARETally Systems
>> >> Corp.TSCensusCollectionClient.
>> >>
>> >> -- Tim --