Solved

Slow publish with FrontPage 2002 on IIS 6 and Windows 2003

Posted on 2004-04-19
34
719 Views
Last Modified: 2013-12-24
Hi,

I setup 2 new Windows 2003/IIS v6 Servers to host our intranet.  One server for 'Production' and the other for 'Development'.  These are brand new, high-speed servers.

Now that I've got everything setup and working (all permissions work as designed, ASP.Net apps work, and all intranet , publishing from Development to Production is extremely slow.  Much slower than on the older, Win2k/IIS v5 server.  As an example, at the point where both Prod and Dev are in synch, publishing on the old server too 31 seconds (it just looked at each directory, found no changes and did nothing).  The same publish on the new server took over 34 minutes.

Even connecting to the server through MS Visual Studio 2003 is extremely slow on the 1st attempt.  It can take 5 - 10 minutes where it only takes seconds on the old server.

I have FP 2002 server extensions installed and configured on the new machines.  The Web Service Extensions that are 'allowed' on IIS 6 are:  ASP.Net v1.1.4322, FrontPage Server Extensions 2002, Indexing Service and Windows SharePoint Services.

Has anybody had a similar problem?  Any ideas of where I should look?  I did a search and was able to find only one reference to slow publishing with FrontPage 2002 & Windows 2003.  That post mentioned that there is a "glitch" with server 2003 and FP2002 and that Microsoft is aware of it, but has no fix or response (post created 8/22/2003).

Thanks in advance..
0
Comment
Question by:SBLfromNS
  • 18
  • 16
34 Comments
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
Using the same here (Windows 2003 Server) but using Front Page 2003.  No extra slowness or anything.  Do you have the firewalls disabled?  Not too sure if that might be causing the lag.  But when you say connecting - that is my first thought

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
Hi and thanks for your input.

The new servers are Intranet servers and are not behind a firewall.  I've had the network guy check the networking settings for both servers and he said that everything is setup OK.  Additionally, he tested the connection by copying a very large file (500MB+) to the servers and it was very fast.

I performed a publish from the production server to another web on the same server and it was also very, very slow.  I thought this might rule out any network/firewall issues as the culprit.
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
When you say that he tested the connection - did he use FTP or FP?

The computer you are publishing to on the intranet - does it show up in your network places?  

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
Yes, both the Dev and Prod computers I'm publishing to show up in 'My Network Places'.

The network guy tested the connection by doing a 'copy' from one computer to another over the network.  It was neither ftp or FP.

--
 Blake
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
Just a quick thing - shut down FP & choose to publish only one file.  Does that take awhile to accomplish?  Do you know if inedxing is turned on on the server?
-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
I changed a htm file on the Dev server and published only that one file.  Publishing was fast, no slowness.

When publishing entire webs, the publishing seemed to slow down while examining subwebs. It would take 45 - 60 seconds to examine the subweb, determine that there were no differences between Dev and Prod and then move on to the next subweb.

The intranet has many subwebs, hence the slowness.  This did not affect the speed on the old server, running Win2k/IIS 6.

Yes, the Indexing service is turned on.  It was also turned on with the old server.  The slowness in publishing was occurring before the indexing service was turned on.

--
 Blake
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
Hm I thought that turning on the indexing service would make it faster.  What about the patches as well?  And now come to think of it - before I got my own servers - I was using FP 2002 on my old machine & Windows 2003 @ the hosting company.  Publishing was very slow.  I had them re-boot the server.  Does that help any?  

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
FP is patched up to SP2.  I'll download SP3 and give it another try.

I rebooted both Dev and Prod servers and proceeded to publish to Prod.

The publish was still very slow (39min. vs. 33 min last time).  This kind of publish takes about 31 seconds on the old server.

--
 Blake
0
 

Author Comment

by:SBLfromNS
Comment Utility
Hi, I downloaded and installed SP3.  No change in publishing times.

--
 Blake
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
Just curious - when you go into the admin site for the FP extensions - what version do you have?

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
I have the FP extensions installed via the Add/Remove Programs of Win2003, version 5.0.2.5012
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
Let me see if I can bring in another person to maybe help out..

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
Thanks.  I'm stumped.  My only thought at this point is that maybe there is some kind of incompatibility with FP2002 on Win2003/IIS 6?  I did see a reference to that by doing a google groups search:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=ueLO9RD5DHA.2300%40TK2MSFTNGP10.phx.gbl&rnum=1&prev=/groups%3Fq%3Dfrontpage%2Bpainfully%2Bslow%2Bopening%2Bwebsite%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3DueLO9RD5DHA.2300%2540TK2MSFTNGP10.phx.gbl%26rnum%3D1
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
I also used FP on Windows 2003 Beta a long time ago no problems.  But when my hosting company did get a some new Windows 2003 servers - I noticed a problem.  What OS is the FP 2002 on?

-Corey
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
He just replied.  Said he just actually got off the phone with the same issue with someone else.  He put in a call to MS but it seems the only way to fully fix this is to go back to Windows 2000.  Are you able to publish to Windows 2003 at a faster rate at another location?

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
Going back to Windows 2000 is not an option for us....The current Win2000 server with which we are hosting our intranet is urgently needed for another application.  Also, we are going to be migrating some of the intranet functionality over to Window SharePoint Services sites.

Do you think that publishing with FrontPage 2003 would help?  If so, are there any implications with publishing with FP2003 to a site that was created with FP2002?

Thanks..

--
 Blake
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
Well I know what is what I use (internet) - no problems.  And no - you should not have any problems upgrading.  You should not see any difference.  Fp 2003 has a lot more functionality than FP XP.  

Do you have any sites off-site using Windows 2003 that you are able to connect to to possibly see if it is still slow?
-Corey
0
Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

 

Author Comment

by:SBLfromNS
Comment Utility
No other sites to connect to...The only site we use FP for is the internal intranet...No outside sites...

I'll see if I can find a machine to test using FP 2003 on...
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
I can give you a test IP address to use if you want on IIS 6.0 / Windows 2003

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
Sure!  

I've never published outside of our company intranet.   How would this work?  Would I go to the site, open it with Front Page and do a publish of that site?  To where?  My company would not allow me to publish our site outside...

Thanks...

--
 Blake
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
Well create a fake site.  I just started this new site - actually we just moved it over & I have not published anything to it just yet.

You will publish to:
http://64.27.10.63
Using:
user name: pay-it.com_fp
p/w: sblfromns

-Corey
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
How did that do?

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
I don't think it did that well...I tried to publish a site with about 200MB of stuff..Our intranet is about 800MB so I tried with 25%.  It took hours to bring everything across and then FP appeared to be taking a long time at the 'Processing updates' stage...I had to head home around 6pm EST and it was not complete... First thing this morning it was no further ahead and I happenned to notice a dialog box in FP that said that the connection was unexpectedly closed by the server.

I'll try a re-publish...The content is already on the server so I'm thinking that the copying would not need to take place again.. I'll let you know how it goes...

Thanks..

--
 Blake
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
OK - cool.  They were just asking me when I was going to have the site up LOL.  I told them we were working on it.  

You might consider getting FP 2003 - that is what I am on & no problems.  

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
I'm going to see if I can get FP 2003.  I'll let you know how that works out.
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
OK..  At this point that does seem like the best thing.  I just really wanted to make sure that you could publish to another Windows 2003 server & experience the same issues.  I wanted to rule out any problems on your server.

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
I've got the FP2003 installed.  Patched with latest patches as found on the officeupdate site.  I'm in the process of publishing from the current intranet to the New intranet server.  I've chosen to publish only changed files.

FP2003 publish has a status feature and mine shows 1 hour remaining (it's been going for about 10 min) with a Transfer rate of between 96 KB/s and 123 KB/s.  

Does that sound right?  I'm on a 100MB/s connection to my network and the new server is on 1GB/s network.  To me that sounds slow, considering that I'm on an internal network.

I may wipe out the new dev-intranet server and do a FULL publish to see how long that takes.  There is about 800MB of content on our intranet.
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
No, it does not sound right.  Just curious - do you have any firewalls set up anywhere?

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
I'll re-confirm the firewall/network config with our network guy.  The Intranet is not behind the firewall.  The network guys are going to do some diagnostics on my network connection.

Strangely, I'm also getting 'cookie blocking' problems with trying to log into experts-exchange.com.  Experts complains that I'm blocking cookies although I've got IE set to allow all cookies through.

When I do a publish from one server to another server, does the content get routed through my machine?

I'll keep you posted and once again, thanks for your assistance...
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
>When I do a publish from one server to another server, does the content get routed through my machine?

Well I would say no - but the reason I asked about the firewall - yesterday when I was testing it, my firewall came up & told me an IP address (my site) was trying to (whatever) my system.  Now I did allow it, but FP just kept verifying.  I stopped it - and re-published - took less than 10 seconds.

If the FP is on Windows XP it contains a firewall & from what I remember so does Windows 2003.  I take it you do not have a system away from your intranet to test this on?

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
No other system apart from our intranet.  I'll see if I can try from another developer machine (there is one other machine, possibly, with WinXP; I'm using Win2k Pro).

I had forgotten that Win2003 does indeed have a built-in firewall....I'll have to look into the settings on that...

Still no word from my network/firewall guys...They're going to put a 'fluke' test on my network connection...
0
 
LVL 29

Accepted Solution

by:
coreybryant earned 500 total points
Comment Utility
Let me know how it goes.  It seems somewhat of a hardware issue maybe.

-Corey
0
 

Author Comment

by:SBLfromNS
Comment Utility
Update:  The fluke test showed no anomolies with my network connection.  The network guy had me check my NIC adapter properties.  The Flow Control setting was 'enabled'; this is known to cause connection problems on our network.  Also, the Media Type setting was set at 'Hardware Default'.  This is also known to cause problems on our network.  I set it instead to 'AutoSelect'.

This helped with publishing to the new development intranet server, but publishing between the new development intranet and production intranet servers was still slow.

I asked the network guy to once again check out the network configuration with the production intranet server.  I told him the transfer rate I was experiencing.  The machine is on a 2GB network connection and should have been significantly quicker.

We discovered that the new intranet server network configuration was totally messed up.  The settings on the Cisco router were not set correctly.  We spent some time correctly configuring the server and the network switch and now the publishing times are significantly faster.

Looks like problem solved!

Thank you very much for all of your help in trouble-shooting and confirming that my setup of IIS/Win2003/FP2002 were OK.

I'm not sure if you need to reply to this comment in order for me to award you the points, but I'll give it a try.
0
 
LVL 29

Expert Comment

by:coreybryant
Comment Utility
:)  Well glad I could help.  rom what you had told me everything seemed to be OK.  I always have a few people go thru my system once it is done to see what might have been missed.  Good luck with the project!

-Corey
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

When deciding to adopt any help desk solutions many factors should be explored before taking decisions. This will change from business to another but in general there are some kind of rule of thumb. Here are some quick tips: Do we need only ticket…
In this short web based tutorial, I wanted to show users how they can still use the powers of FrontPage in conjunction with Expression Web 3.  Even though Microsoft eliminated the use of Web components, we can still use them with FrontPage and edit …
The purpose of this video is to demonstrate how to automatically show related posts at the bottom of a blog post in WordPress. This will be demonstrated using a Windows 8 PC. Plugin “Yet Another Related Posts Plugin” will be used. Go to your…
The purpose of this video is to demonstrate how to integrate Mailchimp with WordPress, by placing a Mailchimp signup form on a WordPress Page or Post. This will be demonstrated using a Windows 8 PC. Mailchimp will be used. Log into your Mailchi…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now