We are running the IIS7 Cosign Module on Server 2008R2 SP1.
We are located at Penn State which is implementing Cosign in their
WebAccess Single Sign-on solution.
We are using Cosign to protect our helpdesk system, powered by Numara
Footprints.
I'm not sure what started it, but as described in Yadin Flammer's post, we
were getting a 503 error with a stopped app pool and error message. After
app pool rapid fail, we would essentially have to reboot to fix. Then it
was intermittent as to how long it would last till the pool would stop
again.
As suggested, we downloaded Cosign Module version 3.1.0rc2. That has
fixed the errors popping up in the Windows Application Log and stopped the
pool from crashing. However, now we have the issue posted by Chris Motch
where just about every person - when first logging in through
WebAccess/Cosign - gets met with the "the service is unavailable" blank
page.
Two things seem to be consistent:
1. When they get this page, if the user hits the refresh button or back
key on the browser, they continue to our helpdesk site as if nothing is
wrong. This is currently our only horrible "workaround."
2. It seems to happen when a user first goes to our protected site in a
cache cleared browser session. If the user previously used
WebAccess/Cosign to go to another protected site here on campus, such as
ITS Downloads, and then proceeds to our helpdesk they do NOT receive the
error.
I'm at a loss as to what to do. We have many endusers that go to this
site to submit tickets for assistance. They are met with an error page
and usually don't try to refresh or continue in any way. This is making
us look bad to our customers.
To implement the new version, I simply replaced the CosignModule.dll and
the cosign_schema.xml with the newer version. Did I need to do something
else? Was I supposed to do anything with this CosignModule.pdb file?
Any help would be appreciated,
Thanks,
JP
------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
