FP 2002 publishing problems

[B.L.]

When ever I publish one web from a development server to
a production server the process starts then after
approximately 30 seconds the message (server connection
timed out) pops up. The message only occurs with one web
because I am able to publish other webs on the production
server without any errors.

The client is a windows xp pro with front page 2002 and
both servers are windows 2000 sp4 with IIS 5.0 they are
up to date with service packs and hot fixes.

I have search MS site but located one article that says
the fix is to apply the latest I.E. service pack. All
systems have the lates IE service pack.

Thanks

 

[Jim Buyens]

The usual cause for this is a Web that's grown too large.
However, the message in that case usually takes longer
than 30 seconds to appear.

The following advice is rather generic, but worth a try.

1. Open the remote Web, recalculate hyperlinks, and then
close it.
2. Open the local Web, recalculate hyperlinks, and then
try publishing.
3. If the problem persists, ask your host to stop and
restart the remove Web.
4. If the problem persists, ask your host to Check And
Fix (or run Server Health on) the remote Web.
5. If the problem persists, ask your host to reboot
the server.

Jim Buyens
Microsoft FrontPage MVP
(e-mail address removed)
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*

 

[Jim Buyens]

Jim,

What is the size limit for a web?

There's no specific size. it depends of the number of megabytes you
need to transfer, the speed of the communication line, and the amount
of time it takes the Web server to apply your changes.

A few MB is usually OK. More than 10MB gets risky.

Not sure what you mean by remove web. Do you me remove
the we then recreate it.

Oops, this was a typo. Please substitute:

3. If the problem persists, ask your host to stop and
restart the Web server.

Which tool do I need to run Server Health on the web.

This is for the FP2002 server extensions:

1. Open your root Web.
2. Choose Server from the Tools menu, and then Administration Home.
3. Click Check Server Health.
4. Select all the check boxes.
5. Click OK

I have rebooted the server.

Also no one has permissions to modify pages in the web. I
have full control permissions.

I was able to publish from another web.

Right. Either something is really taking too long, or some file or
resource is corrupted or locked.

If your data volume is really too large, you can limp along for a
while by right-clicking changed files and choosing Publish Selected
Files from teh shortcut menu. But the long-term solution is breaking
the large Web into several smaller ones.

Jim Buyens
Microsoft FrontPage MVP
(e-mail address removed)
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*

 

[Stefan B Rusynko]

Also try
1) In Windows Explorer Find and delete all FP Temp Files
2) In Windows Explorer Find and delete all hidden *.web files
Then reopen FP and try again




| Jim,
|
| What is the size limit for a web?
|
| Not sure what you mean by remove web. Do you me remove
| the we then recreate it.
|
| Which tool do I need to run Server Health on the web.
|
| I have rebooted the server.
|
| Also no one has permissions to modify pages in the web. I
| have full control permissions.
|
| I was able to publish from another web.
|
| Thanks,
| B.L.
|
|
|
| >-----Original Message-----
| >The usual cause for this is a Web that's grown too
| large.
| >However, the message in that case usually takes longer
| >than 30 seconds to appear.
| >
| >The following advice is rather generic, but worth a try.
| >
| >1. Open the remote Web, recalculate hyperlinks, and then
| > close it.
| >2. Open the local Web, recalculate hyperlinks, and then
| > try publishing.
| >3. If the problem persists, ask your host to stop and
| > restart the remove Web.
| >4. If the problem persists, ask your host to Check And
| > Fix (or run Server Health on) the remote Web.
| >5. If the problem persists, ask your host to reboot
| > the server.
| >
| >Jim Buyens
| >Microsoft FrontPage MVP
| >[email protected]
| >http://www.interlacken.com
| >Author of:
| >*------------------------------------------------------*
| >|\----------------------------------------------------/|
| >|| Microsoft Office FrontPage 2003 Inside Out ||
| >|| Microsoft FrontPage Version 2002 Inside Out ||
| >|| Web Database Development Step by Step .NET Edition ||
| >|| Troubleshooting Microsoft FrontPage 2002 ||
| >|| Faster Smarter Beginning Programming ||
| >|| (All from Microsoft Press) ||
| >|/----------------------------------------------------\|
| >*------------------------------------------------------*
| >
| >
| >>-----Original Message-----
| >>When ever I publish one web from a development server
| to
| >>a production server the process starts then after
| >>approximately 30 seconds the message (server connection
| >>timed out) pops up. The message only occurs with one
| web
| >>because I am able to publish other webs on the
| production
| >>server without any errors.
| >>
| >>The client is a windows xp pro with front page 2002 and
| >>both servers are windows 2000 sp4 with IIS 5.0 they are
| >>up to date with service packs and hot fixes.
| >>
| >>I have search MS site but located one article that says
| >>the fix is to apply the latest I.E. service pack. All
| >>systems have the lates IE service pack.
| >>
| >>Thanks
| >>.
| >>
| >.
| >