PW 2007 not signing users off or releasing licenses

[Ed Bellman]

I sent this one to MS tech support and they were about as helpful as a box of rocks - i.e. check pop-up blockers, uninstall and reinstall PW on the server, sorry that's all we can suggest at this time....

We are running PW 7.70.2009 and when our users log off of PW by using the Log Off button and have pop-ups allowed from this domain the server (Windows Server 2003) does not release their account/license. Even after the idle time is exceed by what I have it set as in Admin Setup (45min) their account still sits there until I manually boot them off myself.

Anyone else had or have this problem? I think I'm more ticked for essentially being blown off by MS tech support than anything else. Logging on once or twice a day and booting off users who have been logged on for 2 hours or more isn't a huge pain but there should be no need to do something like this.

Yes and Yes. We have had the same issue with PW and tech support. We are using 7.5 PW and it is still an issue for us. I have only been told to check my pop-up blocker and that this is the next action

"We want to advise you that this issue will be considered for inclusion in a near future product release. We encourage you to check back with us in 3-6 months for more information regarding the status of your inquiry. If you have further questions, please reference this incident when you contact Meridian Support Services.

The following workaround is being provided:
Use admin pages to log users out."

[Ed Bellman]

Why the Admin edit in my original post? I don't think I was unprofessional in anything I said. I was certainly open and honest, maybe that's the problem?

You are correct Ed, and after further discussion here, we are reposting your original message.

We appreciate your feedback and we want this site to contain open and honest feedback on the topics that are pertinent.

[Ed Bellman]

Tito, thank you. I understand not wanting Meridian-bashing on your site but I don't think that is what I was doing, it certainly was not my intent at least. Just venting on the interweb and trying to share experiences and feedback!

Ed and jdinchak,
Please contact Microsoft about the following KB: http://support.microsoft.com/kb/934903/en-us

This should help anyone that is running Windows Server 2003 SP2 and is having problems with Prolog Website releasing users who have logged off properly (thus you need to release them manually in the Prolog Website admin page 3).

I received this from Jason at HardHat Technologies who thinks someone at Meridian pointed them to this (must give credit when credit is due Jason knows of one customer has been resolved using this. I would recommend contacting Microsoft for the applicable files and then trying this in a test environment. When using in a production environment, please use the typical precautions (back up anything of value to you!!!).

[Ed Bellman]

This appears to have fixed our problem as well.

To be honest, Meridian did email this suggestion to me a week or two ago and because of a miscommunication between myself and our IT Manager I thought we had this installed and it hadn't helped. When you emailed me this again Eric I doubled checked and then realized we didn't have it installed and so we did it right away and seem to be fine!

Thanks!

Are any of you still having an issue with Prolog Website on Windows 2003 Server SP2 or R2?

I called MPS about Issue 54995 for a few customers. On our system, we have this problem on Server 2003 SP2 and R2. The Microsoft hot fix didn't work on the SP2 install (and neither did upgrading to R2). Rolling back to SP1 worked fine. I'm having Lynette in MPS Tech Support test this out. I'd hate to see MPS "support" these two versions of Server 2003 and have this issue. We are using Prolog 2007R2. I'll let you know what Tech Support comes up with.

Sorry we "joined the bandwagon" a year late

late edit: We resolved our problem by rebooting the whole web server and not just the 'virtual' server. When in doubt, pull the plug on the whole thing. We can only hope Windows 2008 Server has the hot fix included.

[ramz]

On Prolog website, we did have this issue and the hotfix did work. Running 2003 SP2.

[mrpickle]

MS KB934903 solved the issue of ghosted PW sessions in the PW admin page. Our environment: two-load balanced PW2007-R2 servers; W2K3-R2 SP2; SQL2005 clustered. Now no need to manually boot PW sessions via dB or the PW admin UI.