HServer Not Running

  • This topic is empty.
Viewing 9 posts - 16 through 24 (of 24 total)
  • Author
    Posts
  • #13963
    McScooby
    Member
    • Total Post: 8
    • Newbie

    Hi, I’ve ran through almost all of the suggestions in this thread, don’t really want to uninstall WDM & start again. But I still get this error message in the event viewer: –

    Event Type: Error
    Event Source: HServerInit
    Event Category: None
    Event ID: 16
    Date: 24/09/2008
    Time: 09:16:12
    User: N/A
    Computer: STK-WDM-001
    Description:
    Unable to initialize the Rapport Management Software Web Server component. Either Rapport Web Server has not been installed or the Web Service is not configured properly. Please refer to the Rapport Help documentation for more information.

    If I run – http://10.8.1.107/hserver.dll?&V99
    This is the output: – &ER|Server Could Not Initialize – Check Configuration

    Thanks in advance for your help.

    #13966
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    If you have tested all suggestions already it looks like you have to go the hard way and reinstall IIS and WDM.

    CG

    #13968
    McScooby
    Member
    • Total Post: 8
    • Newbie

    Thanks for the quick answer, if I remove it all from the server & reinstall it will it affect cause all of my terminals to update with the new installation or as the server name isn’t changing will it be alright?

    #13969
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    This should not affect your clients.

    CG

    #13973
    McScooby
    Member
    • Total Post: 8
    • Newbie

    Cheers, a re-install of WDM appears to have fixed my problem.

    #13974
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    That’s great. Thanks for the update.

    #14188
    Baki
    Member
    • Total Post: 2
    • Newbie

    I have a server with Windows Server 2003 SP2 and WDM 4.7.0 installed. The database is on a seperate SQL server. I am experiencing the same issues in the previous posts here. I have gone through all the suggestions here and re-installed WDM 6 times so far and re-installed IIS a few times too. Still have the same issues…when I start WDM I get the message:

    “Unable to communicate with Hserver. Restarting service HServerInit could fix the problem.”

    When I browse to http://localhost/Hserver.dll?&V99, I get the message:

    “&ER|Server Could Not Initialize – Check Configuration”

    I have called Wyse support and the level 2 tech couldn’t help me. I have checked, and double-checked, and triple-checked all the settings. Everything is set according to all the “fixes”.

    Please help!

    #14189
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    As you are so familiar now with the installation routine ;-), have you ever tried to install everything on one server only. Maybe it is an issue with the remote DB.

    CG

    #14190
    Baki
    Member
    • Total Post: 2
    • Newbie

    Is the problem. It worked with version 4.5.1 just fine. I’ll give you as much detail as I can about how I go to this point:

    We ran version 4.5.1 with no issues. One day last week, any package in the Device Configuration container stopped being pushed/pulled. When on a WinTerm, if I tried to pull a configuration from the server, I would get an error stating: “Cannot read params.ini file from server.” The logs showed a 550 2 after the error, which could mean permissions or file not found. I’m assuming it was the latter because device configuration packages do not have a params.ini file. It was also trying to call bootstrap212.exe, which isn’t in the config package either.

    That being said, we thought that maybe something got “lost” or was failing and not showing up in the logs or event viewer. So we decided to upgrade to version 4.5.3, then to 4.7.0. Since then, I have received the Hserver error. If I look on the Server Table of the RapportDB and return all rows, instead of listening on port 80, it shows port 0. If I manually change it to port 80, the HServer errors stop on the WDM server, but the WDM still does not connect to the DB. Wyse support told me that the fact that the table shows 0 as the listening port means that WDM isn’t connecting to the DB over port 80, and it doesn’t matter if I manually change it.

    Thank you for your quick reply by the way. =)

Viewing 9 posts - 16 through 24 (of 24 total)
  • You must be logged in to reply to this topic.