- This topic has 8 replies, 3 voices, and was last updated 7 years, 2 months ago by
.
-
Posts
-
I am noticing client check-ins are not not showing up on WDM Console or the RapportDB on a recent unique setup. Unique setup includes Clients and WDM server on a private network with just a switch, so no router, no DNS, and static IP for clients and server. Any recommendation on how I can pinpoint the cause of this issue?
The clients are sending their check-in data with a result of 200 in IIS logs. It seem somewhere between hserver.dll and RapportDB, check-in data is lost. I used process monitor to see if I could get any insight into this issue. I did notice Buffer Overflow errors for IIS worker for some operation to read hserver.dll. Creation time of this error seems off as the date reported is 15 day in the past(Pictured Below), but process monitor only show real time data.
<center>
<br>
</center>Process Monitor is not the tool to use for troubleshooting.
Try Debug View.CG
Used Debug View did not see much. I am going to leave it running a little bit longer. One item I saw is “[4444] [RPTSRVCOMM] SendMessage – Unable To Connect To: 192.168.1.143:8008”
192.168.1.143 is my WDM server in the example. The actual server with issue is on a Class B IP subnet with a mask of 255.255.0.0.
No firewall in the path between the clients and WDM server.
Quick update, so 3 out of 14 station have checked into the console. The only difference with the three stations and rest, is that the three where setup on this special subnet. The other station where taken from another subnet with DHCP to this private network. I am planning on resetting the the client to defaults to see if this addresses the issue. Not sure how that would have this affect, but it is worth a shot.
I’m seeing an odd issue where terminals at random will show as red/not checked in within WDM, even though they’re clearly on and active. I have a test terminal right here that is up, active, has been on the network all day, but is telling me it hasn’t checked in since yesterday almost 24 hours ago.
Turns out my issue was caused by a duplicate server address entry in the database. Support worked with me on it.
connected to the DB and found that there was duplicate entries for Hserver services on the Server table.
-Hence deleted the Server table and restarted the WDM server which has fixed the issue.
Solution: Deleting the Server table has fixed the issue.
- You must be logged in to reply to this topic.