| Author |
Frontpage is extremely slow publishing between two IIS6 servers.
|
|
|
| I have two IIS 6 servers. One is a Developement box and the other is a
Production server. When I try and publish from the dev box to the prod
server in Frontpage 2003 the files are copied at most 20kb/s even though
the servers are connected using fast ethernet.
It does not seem to matter which direction I publish nor does it matter
which Frontpage client I use since I have tried FP2000 and FP2002 with
similar results.
What is unusal is that if my source server is an IIS 5.0 server publishing
is extrememly fast and if i try and publish from IIS 6.0 to IIS 5.0 it is
slow again.
To verify my server setups are sound I had a coworker install Windows
2003/IIS6 on two other boxes each manufactured by different vendors and
also had similar results so I do not think it is a hardware issue.
Also copying files using FTP or UNC between the servers is fast so I am
also sure I do not have a network switch/router misconfiguration.
I have opened a ticket with Microsoft Tech and they have confirmed the
issue seems to exists in their labs but have no solution.
I am curious to know if anyone else has similiar issues or even better yet
a working cofiguration.
| |
|
| Hi:
I have similar situation for publishing from local IIS 6 to remote
production site (IIS 6) with dedicated leased line. Local publishing,
however, is fast.
Also, I consistently received "Server error - client closed connections" and
I don't know "who" is the client since the error will occurred for
publishing both ways (from local to remote or from remote by to local).
"JeffT" <jtelford@ofina.on.ca> 在郵件
news:Xns94F0A44632662jtelfordofinaonca@1
40.99.99.130 中撰寫...
> I have two IIS 6 servers. One is a Developement box and the other is a
> Production server. When I try and publish from the dev box to the prod
> server in Frontpage 2003 the files are copied at most 20kb/s even though
> the servers are connected using fast ethernet.
>
> It does not seem to matter which direction I publish nor does it matter
> which Frontpage client I use since I have tried FP2000 and FP2002 with
> similar results.
>
> What is unusal is that if my source server is an IIS 5.0 server publishing
> is extrememly fast and if i try and publish from IIS 6.0 to IIS 5.0 it is
> slow again.
>
> To verify my server setups are sound I had a coworker install Windows
> 2003/IIS6 on two other boxes each manufactured by different vendors and
> also had similar results so I do not think it is a hardware issue.
>
> Also copying files using FTP or UNC between the servers is fast so I am
> also sure I do not have a network switch/router misconfiguration.
>
> I have opened a ticket with Microsoft Tech and they have confirmed the
> issue seems to exists in their labs but have no solution.
>
> I am curious to know if anyone else has similiar issues or even better yet
> a working cofiguration.
| |
| -- ken -- 2004-05-24, 4:37 pm |
| have not begun working with the IIS 6 platform (we're stil on IIS 5) but we
initially had a similar problem with our IIS 5 servers. When looking at the
Web Site properties on the Home Directory tab there is a field for
Application Protextion. It is usually default to Medium (pooled). When this
was changed to Low (IIS Process) everything cleared up on the access and
publish times.
As I mentioned, I am unfaniliar with the IIS 6 consoles but there should be
an equivalent for setting up this parameter (or I would at least think so).
I hope this helps.
-- ken --
"JeffT" <jtelford@ofina.on.ca> wrote in message
news:Xns94F0A44632662jtelfordofinaonca@1
40.99.99.130...
> I have two IIS 6 servers. One is a Developement box and the other is a
> Production server. When I try and publish from the dev box to the prod
> server in Frontpage 2003 the files are copied at most 20kb/s even though
> the servers are connected using fast ethernet.
>
> It does not seem to matter which direction I publish nor does it matter
> which Frontpage client I use since I have tried FP2000 and FP2002 with
> similar results.
>
> What is unusal is that if my source server is an IIS 5.0 server publishing
> is extrememly fast and if i try and publish from IIS 6.0 to IIS 5.0 it is
> slow again.
>
> To verify my server setups are sound I had a coworker install Windows
> 2003/IIS6 on two other boxes each manufactured by different vendors and
> also had similar results so I do not think it is a hardware issue.
>
> Also copying files using FTP or UNC between the servers is fast so I am
> also sure I do not have a network switch/router misconfiguration.
>
> I have opened a ticket with Microsoft Tech and they have confirmed the
> issue seems to exists in their labs but have no solution.
>
> I am curious to know if anyone else has similiar issues or even better yet
> a working cofiguration.
| |
| xfile 2004-05-30, 10:46 am |
| Thanks and I will look into that area.
"-- ken --" <youngken@sc.edu> 在郵件
news:uNCEXwbQEHA.236@TK2MSFTNGP10.phx.gbl 中撰寫...
> have not begun working with the IIS 6 platform (we're stil on IIS 5) but
we
> initially had a similar problem with our IIS 5 servers. When looking at
the
> Web Site properties on the Home Directory tab there is a field for
> Application Protextion. It is usually default to Medium (pooled). When
this
> was changed to Low (IIS Process) everything cleared up on the access and
> publish times.
>
> As I mentioned, I am unfaniliar with the IIS 6 consoles but there should
be
> an equivalent for setting up this parameter (or I would at least think
so).
>
> I hope this helps.
>
> -- ken --
>
>
> "JeffT" <jtelford@ofina.on.ca> wrote in message
> news:Xns94F0A44632662jtelfordofinaonca@1
40.99.99.130...
publishing[vbcol=seagreen]
is[vbcol=seagreen]
yet[vbcol=seagreen]
>
>
| |
| -- ken -- 2004-06-02, 11:11 am |
| Just following up. Did this correct your issue?
"xfile" <cou-cou@remove.msn.com> wrote in message
news:Om71gu3QEHA.3988@tk2msftngp13.phx.gbl...
> Thanks and I will look into that area.
>
>
>
> "-- ken --" <youngken@sc.edu> 在郵件
> news:uNCEXwbQEHA.236@TK2MSFTNGP10.phx.gbl 中撰寫...
> we
> the
> this
> be
> so).
though[vbcol=seagreen]
matter[vbcol=seagreen]
> publishing
> is
and[vbcol=seagreen]
am[vbcol=seagreen]
> yet
>
>
| |
| xfile 2004-06-02, 11:55 pm |
| Hi:
Thanks for following up and my problem is solved for the time being for
local publishing.
For other reasons, I reinstall the server extensions and FP and the problem
is gone.
But from local to the remote production site, the problem is remained the
same and will stop during publishing process.
We just use FTP now and make some changes after files are uploaded.
"-- ken --" <youngken@sc.edu> 在郵件
news:ezqSfFLSEHA.2496@TK2MSFTNGP11.phx.gbl 中撰寫...
> Just following up. Did this correct your issue?
>
>
> "xfile" <cou-cou@remove.msn.com> wrote in message
> news:Om71gu3QEHA.3988@tk2msftngp13.phx.gbl...
but[vbcol=seagreen]
at[vbcol=seagreen]
and[vbcol=seagreen]
should[vbcol=seagreen]
a[vbcol=seagreen]
prod[vbcol=seagreen]
> though
> matter
with[vbcol=seagreen]
it[vbcol=seagreen]
Windows[vbcol=seagreen]
> and
> am
the[vbcol=seagreen]
better[vbcol=seagreen]
>
>
| |
| Mike C 2004-06-26, 10:50 am |
| Hi Jeff,
Just wondering whether you were able to resolve this issue - we are
experiencing the exact same thing.
Thanks,
Mike
| |
| kriscargile 2004-07-10, 11:42 am |
| We had a similar problem with out Win2003 servers, FP server extensions, and VS.NET (projects taking > 5 minutes to load). Turns out that author logging was enabled for the site, but the FP process did not have write access to the logfile (author.log).
Disabling FP logging or granting the appropriate permissions solved the problem.
Look for a warning in the server Application log, source: FP 5.0, event ID 1000. |
|
|
|