Trend Micro WFBS Dashboard Timeout

Hi all, I thought I would post this because I spent the better part of 2 weeks working with Trend Micro on this. Unfortunately, their final solution was to completely uninstall and reinstall the software. In the end I was able to finally get resolution to this by Google searching on my own. I wasn't sure if this belonged in the IIS section or not, but I figured it wouldn't hurt since IIS is the platform running the internal Trend dashboard site.

I upgraded from CSM 3.6 to WFBS 6.0 Advanced. After I did that I noticed I could log into the security dashboard (SD) once, and then if I logged out and tried again I would get the following error (after IE froze for 10 minutes), message returned but with error status." On the server running the WFBS dashboard I noticed in event logs the following error,



This was event ID 2216, source W3SVC-WP.

I read on another forum that this could be caused by CGI timeout value that needed to be increased. So, to resolve it I downloaded IIS 6.0 resource kit and used the Metbase Explorer tool to increase the CGI value from 300-1200 (load the program>browse to computer name>LM>W3SVC>CGI timout value). The site has been stable for 24 hours.

I'm not familiar with that product. My guess is some permission setting somewhere was incorrect causing lengthy timeouts when some inaccessible file was referenced, and ultimately causing the script to time out.

Or, if you have to increase the timeout value to get things working right I'd be thinking it's a bug in the application.

It was an upgrade from an older version of the software, referred to as Client Messing Security 3.6.

The newest version, Worry Free Business Security 6.0 had a lot of new features and the http page was a good bit different.

I am thinking that the older style (whatever it was written in, developed in) didn't necessarily upgrade quite as "pain free" as their developers had hoped it would. I think you are right that the site was trying to access either a non-existent file (i.e., old code that should have been changed/removed during the upgrade process) or permissions were just slightly different enough to cause the CGI to hang.

Either way, at least there is a documented solution on the net now. I searched for a good bit and never found anything related to both the error I was getting and Trend's WFBS product.

Hi. I just fixed a similar problem, and thought the details might help you fix yours (I found your post while looking for my fix).

My Problem was Trend Micro Worry Free Business Dashboard not loading or blank page displayed
That is, when launching Trend Micro Worry Free Business Web Console/Dashboard you get a blank page in Internet Explorer (or other browser), that is, you cannot access the webconsole.

I put details of the solution here on in the solution section of the BrightVisions website (google brightvisions solutions to find it)
but it is basically this:
1. On the Security Server, open the IIS Manager (found in Administrative Tools) and find "OfficeScan" listed under "websites", then close IIS Manager.
2. Open a command prompt and then change directory to ..\Trend Micro\Security Server\PCCSRV.
3. Type the following command and press Enter:
svrsvcsetup.exe -uninstall
4. Open the IIS Manager and check that "OfficeScan" is no longer listed under "websites"
5. Type the following command and press Enter after each entry/line:
svrsvcsetup.exe -install
svrsvcsetup.exe -setvirdir
svrsvcsetup.exe -setprivilege
svrsvcsetup.exe -enablessl
6. Restart the following services:
Trend Micro Security Server Master Service
IIS Admin Service
World Wide Web Publishing service.
7. You may want to open Internet Explorer and clear the history, cookies and cashes/temporary internet files.

Hope that helps! :-)
Al - IT Support for BrightVisions Ltd

In the end I had to end the DbServer.exe process and the Trend Micro Security Server Master service. Delete the folder HTTPDB in C:\Program Files\Trend Micro\Security Server\PCCSRV\HTTPDB on the security server. I rebooted the server. After that you have to reboot all of the clients that use WFBS (i.e., your desktops, servers, latpops) so that they sync back up to the dashboard. You also have to verify all of your old settings are still correct. This did finally fix the issue though. If you are using Exchange, once you reboot the Exchange server it should show back up in the dashboard w/out issue.

p.s...like I said, don't freak out if your PCs don't re-appear in the dashboard right away. You have to reboot them in order for them to sync back up.