|
| Hi There,
I am not quite sure I should post this question here. I assume there is
co-working issue between IIS6.0 and Indigo.
Our indigo service hosted with IIS 6.0 behaves kind of weird: when accessing
our Indigo services after the server has been running some time (let's say,
10 hours, 12 hours overnight), 401.1 unauthorized access error occurs. Not
only the indigo services, any access to public websites on this server gives
the same problem.
Our deployment enviroment is like this:
Windows 2003 SP1 (a member of PDC 2000), IIS6.0, .NET 2.0, WinFx Runtime Feb
CTP
Our Indigo service's VDir security: Anonymous, Integrated Windows
Indigo service security mode: Message, UserName
Client: WPF(Avalon) application
Testing URLs:
Indigo service: http://www.worktech.ca/WMWCFService...ItemService.svc
ClickOnce Avalon application:
http://www.worktech.ca/worktech/XXX...Roads&ID=003000
Can you help us identify whether the problem is related to Indigo or not?
Thanks,
Billy
|
|