Posted by Grant Foraker on June 15, 2006 at 07:40:34: Uploaded files: 5
Win2003 server with all the latest. Comet.exe running on the server as my CAW and XAP host.
From a separate workstation running IE, I was testing XAP for an upcomming demo. I ran into a nasty COSH GPF. XAP was running fine until I clicked the "log out" button. XAP should have generated a simple log out page. IE hung and finally ended with a "page not found".
Switching to the server, I saw a COSH error message. See coshgpf1 screen shot. I clicked Close and got a COSH GPF message. See coshgpf2.
I closed out the remaining COS functions and tried to restart Comet.exe displaying the COSC log and received a "servers unreachable" message. See coshgpf3 and coshgpf4.
I tried several CometServices restarts but couldn't get past the "servers unreachable". I had to reboot the server. After the reboot, I started comet.exe without the COSC log on and received a "COSH timeout error". Oh s**t. I tried comet.exe again, with the COSC log on, and comet started sucessfully. And each comet.exe restart since with or without the COSC log.
Returning to the workstation, I reentered the XAP demo. COSH again crashed on the server. CometServices restarts again didn't work and I rebooted the server. This time comet.exe started sucessfully the first time.
The server is up to date (May 2006) on MS patches. It was on Comet 2005 until late April. I haven't played with the XAP demo since I moved the XAP/CAW host from a workstation to the server. January maybe.
I'm going to proceed to test the "log out" process some more but the debug cycle is a bit slow with a server reboot in the middle.