Hello,
I am hoping someone has already encountered and solved this issue.
We have Cosign 3 running on Win 2003.
Cosign runs fine on a test site that is a simple static HTML page. The App
Pool is running as Network Service.
We are trying to get Cosign to protect a .Net Web Application that connects to
a SQL Server database on another server. On our current production version of
this site, without Cosign, the App Pool runs as a domain service account that
is a user on the Web server and the DB server.
So, on our dev box we turn on Cosign for this site:
If we set the App Pool to run as the domain service account, just like our
production set up. Then browse to the site we get a msg from Firefox, "The
connection to the server was reset while the page was loading." No Cosign login
page.
So we take a step back and take the application out of the scenario and run
against the simple HTML test page:
If we set the App Pool to run as the domain service account, Cosign login page
does not come up. We get the same error, "The connection to the server was
reset while the page was loading." So it does not appear to be an issue with
the Application.
If we set the App Pool to run as the built in local admin account then browse
to the site we get what appears to be an IIS message "Service Unavailable" (I
triple checked the password.)
If we set the App Pool to run as the Network Service account the Cosign login
page comes right up and allows login. But of course the Network Service
account cannot connect to the database so the application does not run.
If we set the App Pool to run as my Domain Admin User ID everything works just
fine. Cosign login page comes up, then redirects to the application.
We tried making the domain service account a local admin on both machines. No
luck, Cosign still will not come up.
We tried making the domain service account a domain admin. No luck, Cosign
still will not come up.
I tried explicitly adding the domain service account to IIS_WPG and full
control on the Cosign directory. No luck.
As far as logs:
The Cosign log is spotless. No issues.
On the failed attempts IIS is throwing: 8007006d and 0x80. When googled both
these errors will eventually point you to David Wang's blog where he tells you,
that you need to troubleshoot you application, not IIS.
There seems to be some network resource that Cosign needs that the Network
Service account has access to but a Local Admin does not???
Any help is greatly appreciated.
Thanks,
Mike G.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
