Home

Results 1 to 4 of 4

Thread: Collector failed to get WIF path

Hybrid View

  1. #1
    tagross NNTP User

    Collector failed to get WIF path

    I recently installed Zen 7 Asset Inventory and am trying to get the client
    to run on some test workstations. I have built an msi install from the
    snapshot option in AdminStudio and have made sure that 7461:TCP,UDP is
    open on the windows firewall. I get the following error on the
    workstation in the colw32.log file and no inventory info shows up on the
    server except the MAC, IP address and hostname:

    Collector Starting
    failed to get WIF path

  2. #2
    TDH NNTP User

    Re: Collector failed to get WIF path

    Hi, Tim.

    That message indicates that the Collector found a WIFName registry key
    (HKLMSoftwareTally Systems Corp.TSCensusCollectionClient:WifName) but the
    registry key was unpopulated as the Collector expects it to be. The Client
    ordinarily populates that key, then the Collector finds it.

    Are you trying to run the Collector directly instead of through the Client?

    You can run the Client in diagnostic mode to help troubleshoot - first,
    edit the Collection Option Set to set Diagnostic on (that's on the
    Collector tab, "Advanced" button). That pushes Diag.Exe and DoRes.DLL out
    to the Client. Next, after those two files are on the workstation (you
    could also push them there manually), you can turn that diagnostic option
    off. That option ONLY runs the COLLECTOR in diagnostic mode, not the
    Client. You want the Client.

    To get the Client to run in diagnostic mode now, create a new text file at
    the workstation. It should be named CPS.Ini, and it should contain the
    following two lines:

    [CollectionClient]
    diagnostic=1

    Last, "bounce" the Collection Client service - stop the service, then
    restart it. When it comes up, it'll display a diagnostic window that'll
    help you troubleshoot the problem.

    -- Tim --



  3. #3
    tagross NNTP User

    Re: Collector failed to get WIF path

    I'm not sure what you mean by running the collector directly. I have
    not tried to launch any program apart from those that startup
    automatically in services.

    I've also done the steps you suggested and nothing really pops out at me.
    Of course, since I just installed it, I'm a little new to Asset Mgmt
    anyway.

    On Wed, 12 Dec 2007 18:32:19 +0000, TDH wrote:

    > Hi, Tim.
    >
    > That message indicates that the Collector found a WIFName registry key
    > (HKLMSoftwareTally Systems Corp.TSCensusCollectionClient:WifName) but the
    > registry key was unpopulated as the Collector expects it to be. The Client
    > ordinarily populates that key, then the Collector finds it.
    >
    > Are you trying to run the Collector directly instead of through the Client?
    >
    > You can run the Client in diagnostic mode to help troubleshoot - first,
    > edit the Collection Option Set to set Diagnostic on (that's on the
    > Collector tab, "Advanced" button). That pushes Diag.Exe and DoRes.DLL out
    > to the Client. Next, after those two files are on the workstation (you
    > could also push them there manually), you can turn that diagnostic option
    > off. That option ONLY runs the COLLECTOR in diagnostic mode, not the
    > Client. You want the Client.
    >
    > To get the Client to run in diagnostic mode now, create a new text file at
    > the workstation. It should be named CPS.Ini, and it should contain the
    > following two lines:
    >
    > [CollectionClient]
    > diagnostic=1
    >
    > Last, "bounce" the Collection Client service - stop the service, then
    > restart it. When it comes up, it'll display a diagnostic window that'll
    > help you troubleshoot the problem.
    >
    > -- Tim --



  4. #4
    tagross NNTP User

    Re: Collector failed to get WIF path

    Please ignore my A.A.A.D.D. (Age Activated Attention Deficit Disorder).

    I had stopped the Inventory process on the Server and forgotten to
    restart it!

    On Wed, 12 Dec 2007 22:58:08 +0000, Tim Gross wrote:

    > I'm not sure what you mean by running the collector directly. I have
    > not tried to launch any program apart from those that startup
    > automatically in services.
    >
    > I've also done the steps you suggested and nothing really pops out at me.
    > Of course, since I just installed it, I'm a little new to Asset Mgmt
    > anyway.
    >
    > On Wed, 12 Dec 2007 18:32:19 +0000, TDH wrote:
    >
    >> Hi, Tim.
    >>
    >> That message indicates that the Collector found a WIFName registry key
    >> (HKLMSoftwareTally Systems Corp.TSCensusCollectionClient:WifName) but the
    >> registry key was unpopulated as the Collector expects it to be. The Client
    >> ordinarily populates that key, then the Collector finds it.
    >>
    >> Are you trying to run the Collector directly instead of through the Client?
    >>
    >> You can run the Client in diagnostic mode to help troubleshoot - first,
    >> edit the Collection Option Set to set Diagnostic on (that's on the
    >> Collector tab, "Advanced" button). That pushes Diag.Exe and DoRes.DLL out
    >> to the Client. Next, after those two files are on the workstation (you
    >> could also push them there manually), you can turn that diagnostic option
    >> off. That option ONLY runs the COLLECTOR in diagnostic mode, not the
    >> Client. You want the Client.
    >>
    >> To get the Client to run in diagnostic mode now, create a new text file at
    >> the workstation. It should be named CPS.Ini, and it should contain the
    >> following two lines:
    >>
    >> [CollectionClient]
    >> diagnostic=1
    >>
    >> Last, "bounce" the Collection Client service - stop the service, then
    >> restart it. When it comes up, it'll display a diagnostic window that'll
    >> help you troubleshoot the problem.
    >>
    >> -- Tim --



Similar Threads

  1. Replies: 8
    Last Post: 26-Jul-2008, 07:54 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •