Looks like the email checker double reports emails.

Meaning if one comes in it reports there's 2; if 2 come in it reports there's 4, etc.

Hadn't really had the time to test it till today.

Sent myself a test message, waited for it tor dock module to report there's mail and it reports there's 2.

I then pulled messages off the server and one comes in not 2 (my test message).

During the testing I got 1 email from someone else and it reported 4, pulled the mail and there was 2; my test message and the email from someone else.

Happy bug killing Jorge.

WsX rox.

****** Maybe more insite ****

It appears the email count increments everytime the module checks for email, if the mail hasn't been picked up in between by the email client clearing the server. It's been a while and the counter said 6 messages, but there was only 2 there. I can make a new "controll" email account that no one knows about, so it's unlikely to get anything but the test emails, to check this if it would help Jorge.

***************************
Funky Stuff in different Dock Module - CPU Monitor

Very specifc set of circumstances.

1. WB5 and Aura skin loaded.
2. After WB5 and the base system settle down I manually load WsX
3. Outlook is loaded
4. Opera is loaded
5. Started Cisco VPN Client ver. 4.6.03.0021 (to vpn into a server I manage)
6. Started RDP to log into the W2K3 Server for Admin. Maint.
7. Using cut and paste in the TS session to copy info from the event log into an email on the server (not across into the local desktop).

After an inspecific length of time (maybe 10 - 15 mins) an "Access Violation" error dialog pops up on my monitors local desk top (Not the TS Server Session), the cpu monitor dock module is blank (theme still showing but no data) and all dock modules are stopped, ie clock not moving and can't pull down the dock bars. I click "ok" the CPU monitor goes offscreen with the error dialog; the clock starts again and all WS Docks are available again.

This has ONLY happened under these specific circumstances and I think I can consistantly replicate it. This is the first time, since I installed and configured WsX and WB5, that I've done remote maint on one of the server's I manage.

It has also occured after a fresh reboot and nothing else loaded.

System is as responsive as normal before, during and after the "access vilolation" event causes the CPU Monitor to crash.

Jorge this is a feedback FYI, and not any kind of show stopper, the only thing that has happened is the CPU monitor has closed.

Ok, regarding the email checker: I'm completely unable to reproduce this here. Are you sure you didn't add the same email account twice (the email module can work with multiple email accounts) when configuring the email module? That would explain the double message reports.

Regarding the CPU module: if you can, as you say, consinstantly replicate the problem, test what happens when:

1) The CPU desktop module is closed and you have no CPU module in a shelf or in a dock. Do you still get the error?

2) The CPU desktop module is closed BUT you have a running in-shelf or in-dock CPU module (which does not display the list of CPU hogs).

You also refered that the CPU module closed - where you able to open it again without having to restart WorkShelf?

Dooh!, I have no idea how I got 2 instances of the same email account configured in it but, that's what had happened and I've deleted the duplicate. (operator head space error!)




I'll check these and post back on this.



Yes I was actually curious about that and was able to re-open it and it seemed to run fine, without incident; though I didn't run it a long time without a reboot.

At this point, I only had time to get this far, and something is going on, but, I think I need to eliminate some things first to help out based on what follows:

I rebooted to start this test clean, normal boot fresh ram stack.

I wanted to replicate the initial circumstances once more for completness (in part for missing the double email entry), so....

I started a Cisco vpn session to the network I needed to connect to, logged into the server using RDP. Opened IE session on the server in the administrative TS session logging into Hotmail, and started to open the event log to replicate the circumstances, when BANG WS dock module didn't close but NS did.

It closed so hard in fact the entire start bar and all it's pieces were gone as well as the WB5 task bar that usually comes back after exiting NS. Basically I had nothing left on the bottom of the screeen, no start bar, no systray nothing. I did a cntrl-alt-del and checked the running apps and NS wasn't in the list at all I had to use the cntrl-alt-del dialog box to shut the machine down, after manually closing WS.

The thought just hit me that I'm letting WB5 sking the vpn client and maybe I shouldn't.

I'll do more testing and unload WB5 first to make sure it's not involved causing WsX to not be happy, and get you more testing results for this ASAP, both with what you asked for and a set of tests without WB5 loaded. No sense you digging into your code if it's somehow contributng to this, especially since I loaded the newest WB5 beta code to overcome minor issues I'm having with the WB5 current release.

Strangly I'm at this point only seeing this behavior with this specific circumstance.

*************** Update ******************

I unloaded WB5 entirely and tried again and was able to do all kinds of maintanance on this server without issue.

I then exlcuded the Cisco VPN client from WB5 and did more maint on that server again without issue.

This can't be anything in WsX at this point, looks more like WsX just took the bullet when the event happened.

One more thing, since I am now not allowing WB5 to skin the client the TS session has stopped "throbbing", ie. frequent mini screen refreshes.

As a matter of fact I'm writing this while that TS session is running.

Sorry to bother you with this Jorge.

One last PS on the original thread. I killed the second account I thought I must have created by accident and when I rebooted and it would show up again.

When I set up my email address in the config I had killed the "default" account that I thought was a placeholder.

Apparently if the default account is deleted and only the user account is there, the module replicates whatever it finds; it seems to want to have 2 accounts in the config at all times.

So I added and "killed" my duplicate about 3 times before I relaized maybe I should add the "default" account back. Once I did it instantly cleaned up the email count and now seems happy. I thought I'd been drinking or dreaming that I'd killed it, till the third time.