A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Outlook » Calendar
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Save as Web Page extremely slow in 2007 compared to 2003



 
 
Thread Tools Display Modes
  #1  
Old July 28th, 2008, 09:14 PM posted to microsoft.public.outlook.calendaring
Dave Williamson
external usenet poster
 
Posts: 2
Default Save as Web Page extremely slow in 2007 compared to 2003

We upgraded a couple of clients from Outlook 2003 to Outlook 2007. On both
clients the Calendar "Save as web page" is extremely slow saving the calendar.

The Outlook client is saving to



Using the same outlook calendar contents ...

In Outlook 2003 the "save as web page" completes in less than 1 minute.

In Outlook 2007 the "save as web page" takes over 1.5 hours.

Does anyone know if this is a known issue or if there is some default
setting in Outlook 2007 that causes this behavior?
  #3  
Old July 29th, 2008, 02:06 PM posted to microsoft.public.outlook.calendaring
Dave Williamson
external usenet poster
 
Posts: 2
Default Save as Web Page extremely slow in 2007 compared to 2003

Office Enterprise 2007 (with outlook 2007) was installed fresh on the 2 new
clients. Then a calendar export (pst) from Outlook 2003 was used to import
into Outlook 2007.

Both clients are on Windows XP SP3.




"Diane Poremsky [MVP]" wrote:

Did you make new profiles when you upgraded to 2007? What OS are you using?

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Exchange Messaging Outlook newsletter:


Outlook Tips:
http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com

You can access this newsgroup by visiting
http://www.microsoft.com/office/comm...s/default.mspx or point your
newsreader to msnews.microsoft.com.


"Dave Williamson" Dave wrote in
message ...
We upgraded a couple of clients from Outlook 2003 to Outlook 2007. On
both
clients the Calendar "Save as web page" is extremely slow saving the
calendar.

The Outlook client is saving to



Using the same outlook calendar contents ...

In Outlook 2003 the "save as web page" completes in less than 1 minute.

In Outlook 2007 the "save as web page" takes over 1.5 hours.

Does anyone know if this is a known issue or if there is some default
setting in Outlook 2007 that causes this behavior?



  #5  
Old July 30th, 2008, 02:09 PM posted to microsoft.public.outlook.calendaring
Dave Williamson[_2_]
external usenet poster
 
Posts: 9
Default Save as Web Page extremely slow in 2007 compared to 2003

Without using Import/Export ... what is the best way to get the existing
calendar from the Outlook 2003 PC to the Outlook 2007 PC?



"Brian Tillman" wrote:

Dave Williamson Dave wrote:

Office Enterprise 2007 (with outlook 2007) was installed fresh on the
2 new clients. Then a calendar export (pst) from Outlook 2003 was
used to import into Outlook 2007.


Exporting and importing could have an effect. There's never any reason to
use import/export when transferring data between Outlook instances. On top
if that, importing from a PST can damage the mail profile.
--
Brian Tillman [MVP-Outlook]


  #6  
Old July 30th, 2008, 02:38 PM posted to microsoft.public.outlook.calendaring
Brian Tillman
external usenet poster
 
Posts: 21,988
Default Save as Web Page extremely slow in 2007 compared to 2003

Dave Williamson wrote:

Without using Import/Export ... what is the best way to get the
existing calendar from the Outlook 2003 PC to the Outlook 2007 PC?


Copy the original PST to the hard drive on the second PC, making sure you do
NOT overwrite any existing PST, then open the copied PST in Outlook with
FileOpenOutlook Data File. You can either use it in place, copy the data
it contains to the second Outlook's default folders, or make the added PST
the delivery location.
--
Brian Tillman [MVP-Outlook]

  #7  
Old July 30th, 2008, 03:11 PM posted to microsoft.public.outlook.calendaring
Dave Williamson[_2_]
external usenet poster
 
Posts: 9
Default Save as Web Page extremely slow in 2007 compared to 2003

Ok. I'll give it a try.

One thing occurred to me as I was thinking about this post. When Outlook
2007 was installed ... and prior to it having any data imported .... the Save
as Web Page was slow given the calendar was empty ... if I recall it took
around 2 minutes to "save as web page" an empty calendar. At the time I
didn't think much of it. Now though it does seem pertinent.

I used SysInternals TCPView to watch the TCP connections and found that the
ftp-data connection would Establish and then enter the Time Wait state rather
quickly. However, there was a significant delay before the next ftp-data
connection was attempted (about 15 seconds or so).

There seemed to be a lot of established ftp connections that were initially
created then remained there throughout the process. They were as follows:

alg.exe FTP Established
alg.exe FTP Established
Outlook.exe FTP Established
Outlook.exe FTP Established
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT

Then after 15 seconds or so the connections would briefly show:

alg.exe FTP Established
alg.exe FTP Established
alg.exe FTP SYN_SENT
Outlook.exe FTP Established
Outlook.exe FTP Established
Outlook.exe FTP Established
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT

The above cycle repeated itself until Outlook came back to responsiveness
and the Calendar had been saved. Then the TCPView showed:

alg.exe FTP Established
Outlook.exe FTP Established

The above 2 FTP connections remained until Outlook was closed.



"Brian Tillman" wrote:

Dave Williamson wrote:

Without using Import/Export ... what is the best way to get the
existing calendar from the Outlook 2003 PC to the Outlook 2007 PC?


Copy the original PST to the hard drive on the second PC, making sure you do
NOT overwrite any existing PST, then open the copied PST in Outlook with
FileOpenOutlook Data File. You can either use it in place, copy the data
it contains to the second Outlook's default folders, or make the added PST
the delivery location.
--
Brian Tillman [MVP-Outlook]


  #8  
Old July 30th, 2008, 09:01 PM posted to microsoft.public.outlook.calendaring
Brian Tillman
external usenet poster
 
Posts: 21,988
Default Save as Web Page extremely slow in 2007 compared to 2003

Dave Williamson wrote:

One thing occurred to me as I was thinking about this post. When
Outlook 2007 was installed ... and prior to it having any data
imported .... the Save as Web Page was slow given the calendar was
empty ... if I recall it took around 2 minutes to "save as web page"
an empty calendar. At the time I didn't think much of it. Now
though it does seem pertinent.


I have no personal experience with publishing calendars to a web page.
Perhaps someone else can help with it.
--
Brian Tillman [MVP-Outlook]

  #9  
Old July 31st, 2008, 02:12 AM posted to microsoft.public.outlook.calendaring
Diane Poremsky [MVP]
external usenet poster
 
Posts: 17,338
Default Save as Web Page extremely slow in 2007 compared to 2003

I don't think an empty calendar would have an effect, neither would
importing the contents to a new pst. One way to check is how fast it is if
you save to the hard drive rather than a web or FTP server. If its speedy
then its not the pst or # of appointments that cause the slowdown when
uploading to a network location.


--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


EMO - a weekly newsletter about Outlook and Exchange:


Outlook Tips:
http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com

You can access this newsgroup by visiting
http://www.microsoft.com/office/comm...s/default.mspx or point your
newsreader to msnews.microsoft.com.


"Dave Williamson" wrote in
message ...
Ok. I'll give it a try.

One thing occurred to me as I was thinking about this post. When Outlook
2007 was installed ... and prior to it having any data imported .... the
Save
as Web Page was slow given the calendar was empty ... if I recall it took
around 2 minutes to "save as web page" an empty calendar. At the time I
didn't think much of it. Now though it does seem pertinent.

I used SysInternals TCPView to watch the TCP connections and found that
the
ftp-data connection would Establish and then enter the Time Wait state
rather
quickly. However, there was a significant delay before the next ftp-data
connection was attempted (about 15 seconds or so).

There seemed to be a lot of established ftp connections that were
initially
created then remained there throughout the process. They were as follows:

alg.exe FTP Established
alg.exe FTP Established
Outlook.exe FTP Established
Outlook.exe FTP Established
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT

Then after 15 seconds or so the connections would briefly show:

alg.exe FTP Established
alg.exe FTP Established
alg.exe FTP SYN_SENT
Outlook.exe FTP Established
Outlook.exe FTP Established
Outlook.exe FTP Established
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT

The above cycle repeated itself until Outlook came back to responsiveness
and the Calendar had been saved. Then the TCPView showed:

alg.exe FTP Established
Outlook.exe FTP Established

The above 2 FTP connections remained until Outlook was closed.



"Brian Tillman" wrote:

Dave Williamson wrote:

Without using Import/Export ... what is the best way to get the
existing calendar from the Outlook 2003 PC to the Outlook 2007 PC?


Copy the original PST to the hard drive on the second PC, making sure you
do
NOT overwrite any existing PST, then open the copied PST in Outlook with
FileOpenOutlook Data File. You can either use it in place, copy the
data
it contains to the second Outlook's default folders, or make the added
PST
the delivery location.
--
Brian Tillman [MVP-Outlook]


  #10  
Old July 31st, 2008, 02:14 AM posted to microsoft.public.outlook.calendaring
Diane Poremsky [MVP]
external usenet poster
 
Posts: 17,338
Default Save as Web Page extremely slow in 2007 compared to 2003

BTW - what firewall are you using?

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


EMO - a weekly newsletter about Outlook and Exchange:


Outlook Tips:
http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com

You can access this newsgroup by visiting
http://www.microsoft.com/office/comm...s/default.mspx or point your
newsreader to msnews.microsoft.com.


"Dave Williamson" wrote in
message ...
Ok. I'll give it a try.

One thing occurred to me as I was thinking about this post. When Outlook
2007 was installed ... and prior to it having any data imported .... the
Save
as Web Page was slow given the calendar was empty ... if I recall it took
around 2 minutes to "save as web page" an empty calendar. At the time I
didn't think much of it. Now though it does seem pertinent.

I used SysInternals TCPView to watch the TCP connections and found that
the
ftp-data connection would Establish and then enter the Time Wait state
rather
quickly. However, there was a significant delay before the next ftp-data
connection was attempted (about 15 seconds or so).

There seemed to be a lot of established ftp connections that were
initially
created then remained there throughout the process. They were as follows:

alg.exe FTP Established
alg.exe FTP Established
Outlook.exe FTP Established
Outlook.exe FTP Established
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT

Then after 15 seconds or so the connections would briefly show:

alg.exe FTP Established
alg.exe FTP Established
alg.exe FTP SYN_SENT
Outlook.exe FTP Established
Outlook.exe FTP Established
Outlook.exe FTP Established
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT
[System Process]":0 FTP-DATA TIME_WAIT

The above cycle repeated itself until Outlook came back to responsiveness
and the Calendar had been saved. Then the TCPView showed:

alg.exe FTP Established
Outlook.exe FTP Established

The above 2 FTP connections remained until Outlook was closed.



"Brian Tillman" wrote:

Dave Williamson wrote:

Without using Import/Export ... what is the best way to get the
existing calendar from the Outlook 2003 PC to the Outlook 2007 PC?


Copy the original PST to the hard drive on the second PC, making sure you
do
NOT overwrite any existing PST, then open the copied PST in Outlook with
FileOpenOutlook Data File. You can either use it in place, copy the
data
it contains to the second Outlook's default folders, or make the added
PST
the delivery location.
--
Brian Tillman [MVP-Outlook]


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 08:29 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.