J
Jerome Cohen
This problem is driving us mad, and I saw someone else posting a very
similar problem, again no support from MS!
-----------------------
Win2K/IIS 5.0, web farm load balanced by Local director. same setup on each
web server.
I have an application that is mapped to a network folder, physically located
on a file server , also Win2K.
on each web server, the root level of the application, directly located
under "Default Web Site", is maped liked this: \\fileserver\rootDir . we
have dozens of foldfers under the main folder.
When we update ASP files, some times, some
web servers, continue to server the old version even 1-2 days after the
update, and we have to reset IIS. the mapping has been checked numerous
times, its 100%. the same web server can react to updates on same folder ,
and next time not react.
date-time synched perfectly among file server and all web servers.
important to notice - same web servers host also CFM pages on same physical
folder, mapped by CFM admin on each web server. NEVER had a problem with
ColdFusion not recognizing an update!
similar problem, again no support from MS!
-----------------------
Win2K/IIS 5.0, web farm load balanced by Local director. same setup on each
web server.
I have an application that is mapped to a network folder, physically located
on a file server , also Win2K.
on each web server, the root level of the application, directly located
under "Default Web Site", is maped liked this: \\fileserver\rootDir . we
have dozens of foldfers under the main folder.
When we update ASP files, some times, some
web servers, continue to server the old version even 1-2 days after the
update, and we have to reset IIS. the mapping has been checked numerous
times, its 100%. the same web server can react to updates on same folder ,
and next time not react.
date-time synched perfectly among file server and all web servers.
important to notice - same web servers host also CFM pages on same physical
folder, mapped by CFM admin on each web server. NEVER had a problem with
ColdFusion not recognizing an update!