- This topic is empty.
1. December 2006 at 11:40 #222novusMember
- Total Post: 6
On a new install of WDM 4.5 on a w2k3 R2 box the Hserverinit service does not start properly. I have seen this issue before with 4.4.1 but installing the recommended hotfixes solved this issue. Do i have to install these hotfixes on 4.5 as well?
I have turned off DEP.
Thanks2. December 2006 at 5:56 #8913karazielMember
- Total Post: 74
- Back Stage Pass
I’ve found a couple of things to look for:
Check for URLScan or any other http filtering tools for “security” that my be blocking the http strings. – including proxy
Ensure the anonymous access is enabled
Check the status of your IUSR account (default for anonymous access)- you might need to reset the password
You might also need to promote the IUSR, or another user to alleviate permission issue that may be passed down by AD.
Ensure no other web server is running on same server
type this into IE browser:
If you get back anything other than the 404 Page not found, (a server time stamp) then all is well
If that fails, replace the localhost portion with the actual server IP
Behavior should be same as above
If prompted for login, then its permission issue.
-k12. April 2007 at 15:52 #9426
We’ve just rebuilt our rapport server 4.4.1 on vmware. We are getting this same problem with hserverinit starting and then immediately stopping.
We are on server 2003 sp2. I’ve gone to your hot fix section and installed all of those along with turning off DEP. We have anonymous access enabled. IUSR account password set to never expire. And no other webserver running on this server.
The reason we’re trying to get this fixed is so that our new S10 wont hangup on connecting to Hserver when it starts up. I edited our config file to disable rapport agent and that sped the terminal back up but then ofcourse I can’t manage the device which kind of sucks.
Have you guys come across any other things which might cause this service to stop? Maybe something on SP2?
P.S. This site is amazing and I want to thank you all for all the info I have gathered from it.12. April 2007 at 18:09 #9427JoeMember
- Total Post: 106
- Legend in Own LunchBox
I had a problem, and the resolution I came up with might help you as well. I posted it in another thread here:
My solution was to reinstall the service. You can easily do that with the following steps:
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)
No guarantee that it will work for you, but I had a similar problem where the service would start up, and immediately stop. It was running under WinXP SP2 with no firewall enabled.12. April 2007 at 18:33 #9428
Thanks Joe. I gave it a try but that didnt seem to help. I went and looked at your other post and ran the query and it says the service is running. But when I go into Services and look at it its stopped.12. April 2007 at 23:46 #9431
Thanks for the support of the site, its kind of a strange hobby of mine doing this but I enjoy it.
The HServerInit service in meant to stop, it will briefly start and then stop again when the server boots so do not worry about it not being up.
If you you open the console and it says the “Hservice is not started” or there are errors in the event log about the Hservice/web service not starting then this is a problem. It is actually saying the Rapport service tried to start and use the Hservice and it failed – confusing I know.
So, do you have any errors in the event log or on opening the console? Joe’s suggestion was great to fix the Rapport service. I have not tested on SP2 so I can not say if this is an issue. Also, check IIS it on port 80 and that the local Rapport account has its password set to never expire.
Post back with the event logs and we can go from there,
-TT13. April 2007 at 13:14 #9433
Hmmm, if its meant to start then stop then I’m probably just confused as the to cause of my problem. I’ll give you my full story.
My hospital purchased an S10 as a demo to start replacing some of our 3150’s and 3125’s. We got one from CDW and started working on it. There was a memory error we got taken care of with new firmware from wyse (5.2.033) But after we got our terminal talking to our rapport server, instead of the instant boot up and ica connecting right away to our published app, the terminal sits on connecting to Hserver for almost 2 minutes. Then it finishes its look up and connects to the published app.
When I modify the config file to Disable Rapport then it bypasses the connecting part and connects really fast again (which is the point of getting these new terminals as our users hate the long wait times on the CE devices) But Disabling the rapport agent defeats the purpose of having rapport to manage the terminals remotely.
I had tried to look some things up and I had “thought” that the connecting to HServer was it trying to connect to rapport and that it was taking so long because the Hserverinit service was not running. But if its not supposed to be running then there went that theory. Does this mean that if I want to use the S10 and Rapport that the terminal has to connect for 2 minutes whenever it gets restarted/power goes out?
Thanks again for all the help.13. April 2007 at 22:45 #9434
Ahhh, OK the extra information helps.
So my assumption is that with the existing CE units Rapport is working fine?
The firmware you have (5.2.033) is new and infact not released yet so here is a test. Go to wyse.com and download the S10 firmware and down grade on unit – is it fast now? (it should not pause on the contacting to hserver). Also with the older firmware does the S10 show up in Rapport correctly?
My guess is either you have a really new S10 and I belive there may be a patch required for Rapport 4.4.1 or the new (beta) 5.2 code has an issue.
You can roll the device up to the new code at the end of testing and dissable the hagent again.
If you post the results and I will hit some contacts about the patches,
-TT16. April 2007 at 20:45 #9438
Sorry its been really busy here today and I wasn’t able to check the forum til now (right before I head home) I will try the downgrade tomorrow and see what happens and let you know. Thanks for the help.
-Mike17. April 2007 at 16:01 #9442
Ok I rolled back to 5.1.028 and its still taking a long time to contact Hserver. After it gets passed that it said it failed to open and I have 2 IP’s that are no where near any IP’s in our organization let alone the rapport server. I get:
Hagent: open “22.214.171.124,126.96.36.199” failed
But I have in my config the server IP (10.33.1.57) and when I go check network settings under rapport server it has 10.33.1.57 there so I’m not sure why I’m getthing these weird IP’s not where I can delete them from.17. April 2007 at 21:29 #9444karazielMember
- Total Post: 74
- Back Stage Pass
Try resetting the unit to factory defaults and then get a network trace to see if theres a DHCP server/Proxy that’s giving the device bad IP info.
Could be a DNS issue.18. April 2007 at 10:22 #9453mwsMember
- Total Post: 2
I Installed the WDM on a Testserver – some days ago i thought that i should do it on a *Active* server!
“So i installed the wdm on the other Server – this server is also our intranet server!”
and if i start the wdm i got the warning:
HServer is not running. This will result in limited functionality and no Service Log messages for HServer.
But i can’t start the Hserver Service because if i do that i get the Errormessage:
The service “HServerInit ” on “Local computer” could not be
Error 1068: The dependenceservice or the dependencegroup could not be started.
So i looked which service and so on should run and i found the www-publishingservice and if i want to start that one i got the Errormessage:
The service “WWW-Publishingservice” on “Local computer” could not be
Error 126: the indicated module was not found
what could i do?
have a nice day
pieter18. April 2007 at 13:12 #9458
Unfortunately WDM uses an ISAPI filter in the base of the IIS web site and it does not play ball with other web traffic – in other works WDM wants IIS to its self.
I would always recommend a clean install of WDM on its own server, to save hardware look at VMware – WDM works well in this environment.
See this article for general installation notes:
Note if you are using WDM 4.5.1 you will not need all the hot-fixes as these are included in this recent release,
-TT18. April 2007 at 13:15 #9459mwsMember
- Total Post: 2
thanks for help!
i will do it again on another server!18. April 2007 at 13:17 #9461
Heheh – no problem! Sorry you have to install it again…
- You must be logged in to reply to this topic.