SQL Timeouts / Environment Failures

– Wyse Devige Manager MMC:
When viewing ‘update manager > scheduled tasks’ the error ‘Timeout Expired – SQL database’ appears. Sometimes after trying 10 times we can view the scheduled tasks.

I’ve seen this issue when problems were occuring on the database server. It might be worth checking your database server to make sure it is operating properly.

– When it is possible to deploy an image (on a V90 for example) The client boots, connects to the wyse server, but then displays ‘Environment Failure’
The IIS components seem to be working fine (http, ftp)

From my experience, this indicates you’re trying to push an image to a machine that the image isn’t compatible with. I don’t know if that is the only cause for this, or if it is even the correct answer.

For example, I have quite a few v90 machiens in the field. Apparently the v90 is discontinued, and was replaced by the v90L. I wasn’t aware that my company had been purchasing them until they started calling me with this error. The image that I had created for the v90 didn’t work with the v90L.

– When running rptdiag.exe the tool gives an error at ‘Testing Database’ ‘Currently validating: Rapport Web Service’ ‘Connection To HServer failed’ And a C++ error appears afterwards

I’ve had problems with iis crashing, thus making connections to the HServer impossible. It’s possible that hserver isn’t available while you’re trying to test the database. Try giving the computer a restart to refresh all the services and make sure they’re up and running. I know that in some environments, rebooting the server is a no-no. In that case, you can try this script to restart the “core” WDM services.

:Init

@Echo Off

Cls



:Stop

Echo

Echo Stopping Core WDM Services

Echo

Echo ¦ World Wide Web Publishing Service

Net Stop W3Svc

Echo ¦ Microsoft FTP Services

Net Stop MSFTPSVC

Echo ¦ Rapport

Net Stop RAPPORT4

Echo

Echo Core WDM Services Stopped

Echo



:Start

Echo

Echo Starting Core WDM Services

Echo

Echo ¦ World Wide Web Publishing Service

Net Start W3Svc

Echo ¦ Microsoft FTP Services

Net Start MSFTPSVC

Echo ¦ Rapport

Net Start RAPPORT4

Net Start HServerInit

Echo

Echo Core WDM Services Started

Echo

Just save the contents to a text file and rename it RestartWDM.cmd or whatever you want to all it. Then double click it.

– On a sidenote, the IIS logs from the Wyse HTTP site is filled with:
‘VSQL02 192.168.10.2 80 PUT /hserver.dll &V01|&IMAC=00806454B029|CID=117||WFE=1|WF=0|OS=1|VI=1|AL=c:programüfilesrapport’
Wich is a non-existing path.

This looks to me like a transaction where the thin client is checking in with the WDM server. Is 192.168.10.2 a thin client? I’m pretty sure it is, because of the MAC address — I believe the 008064xxxxxx block belongs to Wyse.

If I had to take a guess, and this is a complete guess, I bet AL is something like Agent Location, and shows the location on the thin client where the WDM/Rapport agent is installed. So look on your thin client for this directory, not your server.

While I know I didn’t give any concrete fixes, hopefully I got you looking in the right direction.