There are two separate things happening here. If IISCosign is not able to intialize the log file, it will continue to run.
There are changes to the schema from 2.0.0 through 2.1.0. It's possible a 2.0.x-configuration file will confuse a 2.1.0 filter. Also, there should be a more detailed message saying exactly what is wrong. For example, putting a bad element in the middle of the config file, this appears in the Event Viewer: Config file parsing error at line 33: Element content is invalid according to the DTD/Schema. Expecting: LoginServer. What is the exact text of the denied page? If IISCosign does not load properly, it will show this: The server is currently disabled. Seeing as how users are being redirected to the login server, the error is probably a permission issue with the files the web server is trying to serve. Jarod On May 5, 2008, at 4:20 PM, Farrell, Craig wrote: > Jarod > > I updated to 2.1r2. Didn't correct the issue. Still getting error > in event log about can't init the log file. User are prompted to > login but get redirected to a page says denied. > > Edited config to redirect to event log. What is funny. Right after > that the filter would not load anymore. Saying it couldn't read > config file. Creating a new config file. I use notepad or an editor > that is called PFE. > > PSU provides a version 2 template for the config file. Is is > tailored for PSU. > > Craig > > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
