WDM: Discovery Error

  • This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #370
    AvatarJoe
    Member
    • Total Post: 106
    • Legend in Own LunchBox
    • ★★★★★

    I am totally new to any type of remote management with the Wyse Clients. We’ve been doing them manually for a while now. Today I installed WDM to see how it would work in our environment, but I can’t get it to do a discover.

    I start WDM, Right Click on device manager, and click find Devices. From here, I choose the subnet I defined earlier and click OK. I get the following error message:

    Neither HServer or Standard Services are currently running. At least on of these services must be running before attempting a discover.

    There is an icon in my system tray that appears to be a program called WDM service logs. If I open it, I have 4 different windows with the following information:

    Web Service Log: nothing in here
    TFTP Log: Stopping
    Standard Services Log: error checking out as Standard Service:
    DHCP Log: STopping

    In the event logs, I see error number 10s pop up every now and then. Just before it there is always an HServer stopped event. The description for the error is not useful at all, but here it is:


    The description for Event ID ( 10 ) in Source ( Rapport4 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: The event log file is corrupt..

    Rapport4 service is running
    HServerInit is stopped. I can manually start it, but it turns off again
    MSSQL$RAPPORTDB is running.

    Firewall is disabled.

    Any idea on where my problem might be? I’ve rebooted the machine with no luck, and haven’t been able to find information on Google or Wyse.com that matches my error.

    Thanks in advance!

    #9393
    AvatarJoe
    Member
    • Total Post: 106
    • Legend in Own LunchBox
    • ★★★★★

    I was poking around the wyse knowledgebase and I found some information that helped me figure out what the problem was.

    It seems that during installation the Standard Service didn’t install properly. It installed enough to make windows think the service was running, but it really wasn’t. I verified this by querying the service from the command line and I received an error. I fixed it by manually reinstalling the service then forcing it to start. Here’s information on how to do that:

    1: Open a command prompt (start/run/CMD)
    2: Change to the Wyse Directory (CdProgram FilesWyseWDM)
    3: Uninstall the service (RptStdSvc.exe -u)
    4: Reinstall the service (RptStdSvc.exe -i)
    5: Start the service (RptStdSvc.exe -r)

    You can, at this point, query the service to see it’s status by using RptStdSvc.exe -q. If it’s running, you’ll get the following message:

    [STDSVC] – service is running

    Hope this helps someone else who might be having the same problem…

    #9395
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Nice one Joe!

    Sorry I did not get to your post sooner but its a holiday down under!

    Actually you provided a better answer that I could have so thanks for posting the results for the rest of us!!!

    Cheers,
    -TT

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.