where are the differences ?

[NT]

hey
i have a problem and it miss me some knowledge

I have a excel file store on a server
i have a map on my computer to access to this folder o:\doc (with a net use
....)

when i open excel and i made file and open , i search my file on the O a
double clic on the file, it open in one second

when i open the explorer and that i double clic on the file (excel is still
already oepn), it take more than 2 minutes

1) have you already see this case

2) and where can i found documentation on the process made by microsoft to
open a file by a net use share or locally

thanks a lot nicolas

 

[Robinson Zhang [MSFT]]

Hi Nicolas,

Thank you for posting question.

From your post, my understanding on this issue is: A performance issue was
encountered when double click a excel file on mapped drive. If you try to
open it by Office Excel manually, it works fine. If I'm off base, please
feel free to let me know.

Before moving on, could you please help us confirm following points?

1. Can you please let us know the version of Office?
2. Do you use a VBScript logon script to map drive?
3. If you manually map a drive in CMD, does the issue occurs?
4. If you access the net share by UNC, does the issue occurs?

Based on my known, if VBScript logon script includes a trailing backslash
"\" character in the namespace folder name can cause similar problem. Could
you please check it if you are using VBScript logon?

Regarding the documentation on the open file process, I found the following
information from "Whitepaper: Improving Network Performance when users
access Office XP and Office 2003 Documents"

--------------------------------------------------------
The Office file format is not optimized for WAN. The Office file format
requires more frequent and smaller data blocks going across the network. It
is best to avoid opening and editing Office files over a WAN for two
reasons: potential data loss and increased IStream interface calls. With
Office files, especially Word files, there is a generation of many IStream
interface calls. The IStream interface lets you read and write data to
stream objects. Stream objects contain the data in a structured storage
object, where storage provides the structure. Simple data can be written
directly to a stream but, most frequently, streams are elements nested
within a storage object. They are similar to standard files.

Saving Word documents across a wide area network can appear to be
significantly slower than across a local area network, and the amount of
data that is transferred when users save documents across a WAN can be much
larger than the file size on disk. Up to 2.5 times as much data can be
transferred across the network, compared to the original file size on disk.
This is normal and expected when users save Word documents across a
network. The difference can be explained by the additional data transfers
that are required to help Word maintain secure access and to support
certain Word features.
--------------------------------------------------------

For more information, please refer to the following link:
Whitepaper: Improving Network Performance when users access Office XP and
Office 2003 Documents
http://office.microsoft.com/en-us/help/HA102177991033.aspx

Hope it helps.

Best regards,

Robinson Zhang
Microsoft Online Support

 

[Bernd]

-------- Original-Nachricht --------

hey
i have a problem and it miss me some knowledge

I have a excel file store on a server
i have a map on my computer to access to this folder o:\doc (with a net
use ...)

when i open excel and i made file and open , i search my file on the O a
double clic on the file, it open in one second

when i open the explorer and that i double clic on the file (excel is
still already oepn), it take more than 2 minutes

1) have you already see this case

2) and where can i found documentation on the process made by microsoft
to open a file by a net use share or locally

thanks a lot nicolas

Try this:

1. Stop the WebClient service on your machine
2. Test if this helps
3. If this helps deactivate the WebClient service, so that it never gets
started at boot time again

In some cases it worked for me.
By the way: if you don't use WebDAV, you don't need that service.

Bernd

 

[NT]

hey
thanks for your help but it doesn't help in my case
it takes the same time

 

[NT]

hello answer in the text

thanks

Hi Nicolas,

Thank you for posting question.

From your post, my understanding on this issue is: A performance issue was
encountered when double click a excel file on mapped drive. If you try to
open it by Office Excel manually, it works fine. If I'm off base, please
feel free to let me know.

Before moving on, could you please help us confirm following points?

1. Can you please let us know the version of Office? 2003 PRO
2. Do you use a VBScript logon script to map drive? no i made it manually
3. If you manually map a drive in CMD, does the issue occurs? yes
4. If you access the net share by UNC, does the issue occurs? yes




Based on my known, if VBScript logon script includes a trailing backslash
"\" character in the namespace folder name can cause similar problem.
Could
you please check it if you are using VBScript logon?

Regarding the documentation on the open file process, I found the
following
information from "Whitepaper: Improving Network Performance when users
access Office XP and Office 2003 Documents"

--------------------------------------------------------
The Office file format is not optimized for WAN. The Office file format
requires more frequent and smaller data blocks going across the network.
It
is best to avoid opening and editing Office files over a WAN for two
reasons: potential data loss and increased IStream interface calls. With
Office files, especially Word files, there is a generation of many IStream
interface calls. The IStream interface lets you read and write data to
stream objects. Stream objects contain the data in a structured storage
object, where storage provides the structure. Simple data can be written
directly to a stream but, most frequently, streams are elements nested
within a storage object. They are similar to standard files.

Saving Word documents across a wide area network can appear to be
significantly slower than across a local area network, and the amount of
data that is transferred when users save documents across a WAN can be
much
larger than the file size on disk. Up to 2.5 times as much data can be
transferred across the network, compared to the original file size on
disk.
This is normal and expected when users save Word documents across a
network. The difference can be explained by the additional data transfers
that are required to help Word maintain secure access and to support
certain Word features.
--------------------------------------------------------

For more information, please refer to the following link:
Whitepaper: Improving Network Performance when users access Office XP and
Office 2003 Documents
http://office.microsoft.com/en-us/help/HA102177991033.aspx

Hope it helps.

Best regards,

Robinson Zhang
Microsoft Online Support

 

[Robinson Zhang [MSFT]]

Hi Nicolas,

I would like to know if the suggestions helped. If you need further
assistance, please do not hesitate to let me know. I am looking forward to
your reply.

For your reference, I have reposted my reply:

==============================================
Hi Nicolas,

Thank you for posting question.

From your post, my understanding on this issue is: A performance issue was
encountered when double click a excel file on mapped drive. If you try to
open it by Office Excel manually, it works fine. If I'm off base, please
feel free to let me know.

Before moving on, could you please help us confirm following points?

1. Can you please let us know the version of Office?
2. Do you use a VBScript logon script to map drive?
3. If you manually map a drive in CMD, does the issue occurs?
4. If you access the net share by UNC, does the issue occurs?

Based on my known, if VBScript logon script includes a trailing backslash
"\" character in the namespace folder name can cause similar problem. Could
you please check it if you are using VBScript logon?

Regarding the documentation on the open file process, I found the following
information from "Whitepaper: Improving Network Performance when users
access Office XP and Office 2003 Documents"

--------------------------------------------------------
The Office file format is not optimized for WAN. The Office file format
requires more frequent and smaller data blocks going across the network. It
is best to avoid opening and editing Office files over a WAN for two
reasons: potential data loss and increased IStream interface calls. With
Office files, specially Word files, there is a generation of many IStream
interface calls. The IStream interface lets you read and write data to
stream objects. Stream objects ontain the data in a structured storage
object, where storage provides the structure. Simple data can be written
directly to a stream but, most frequently, streams are elements nested
within a storage object. They are similar to standard files.

Saving Word documents across a wide area network can appear to be
significantly slower than across a local area network, and the amount of
data that is transferred when users save documents across a WAN can be much
larger than the file size on disk. Up to 2.5 times as much data can be
transferred across the network, compared to the original file size on disk.
This is normal and expected when users save Word documents across a
network. The difference can be explained by the additional data transfers
that are required to help Word maintain secure access and to support
certain Word features.
--------------------------------------------------------

For more information, please refer to the following link:
Whitepaper: Improving Network Performance when users access Office XP and
Office 2003 Documents
http://office.microsoft.com/en-us/help/HA102177991033.aspx

Hope it helps.

Best regards,

Robinson Zhang
Microsoft Online Support

 

[Robinson Zhang [MSFT]]

Hi Nicolas,

I am just writing to see whether there is anything that I can do for you on
this issue. If you have any concerns, please feel free to let me know. I am
glad to be of assistance.

Have a nice day!

Best regards,

Robinson Zhang
Microsoft Online Support

 

[Kelly]

Please include the original post.

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool Plus!
http://www.kellys-korner-xp.com/taskbarplus!.htm

 

[Nate Grossman]

Please include the original post.

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool Plus!
http://www.kellys-korner-xp.com/taskbarplus!.htm

No one at MSFT appears to know how to do that.

Hi Nicolas,

I am just writing to see whether there is anything that I can do for you
on
this issue. If you have any concerns, please feel free to let me know. I
am
glad to be of assistance.

Have a nice day!

Best regards,

Robinson Zhang
Microsoft Online Support

 

[Robinson Zhang [MSFT]]

Hi Nicolas,

I would like to know if the suggestions helped. If you need further
assistance, please do not hesitate to let me know. I am looking forward to
your reply.

For your reference, I have reposted my reply:

==============================================
Hi Nicolas,

Thank you for posting question.

From your post, my understanding on this issue is: A performance issue was
encountered when double click a excel file on mapped drive. If you try to
open it by Office Excel manually, it works fine. If I'm off base, please
feel free to let me know.

Before moving on, could you please help us confirm following points?

1. Can you please let us know the version of Office?
2. Do you use a VBScript logon script to map drive?
3. If you manually map a drive in CMD, does the issue occurs?
4. If you access the net share by UNC, does the issue occurs?

Based on my known, if VBScript logon script includes a trailing backslash
"\" character in the namespace folder name can cause similar problem. Could
you please check it if you are using VBScript logon?

Regarding the documentation on the open file process, I found the following
information from "Whitepaper: Improving Network Performance when users
access Office XP and Office 2003 Documents"

--------------------------------------------------------
The Office file format is not optimized for WAN. The Office file format
requires more frequent and smaller data blocks going across the network. It
is best to avoid opening and editing Office files over a WAN for two
reasons: potential data loss and increased IStream interface calls. With
Office files, specially Word files, there is a generation of many IStream
interface calls. The IStream interface lets you read and write data to
stream objects. Stream objects ontain the data in a structured storage
object, where storage provides the structure. Simple data can be written
directly to a stream but, most frequently, streams are elements nested
within a storage object. They are similar to standard files.

Saving Word documents across a wide area network can appear to be
significantly slower than across a local area network, and the amount of
data that is transferred when users save documents across a WAN can be much
larger than the file size on disk. Up to 2.5 times as much data can be
transferred across the network, compared to the original file size on disk.
This is normal and expected when users save Word documents across a
network. The difference can be explained by the additional data transfers
that are required to help Word maintain secure access and to support
certain Word features.
--------------------------------------------------------

For more information, please refer to the following link:
Whitepaper: Improving Network Performance when users access Office XP and
Office 2003 Documents
http://office.microsoft.com/en-us/help/HA102177991033.aspx

Hope it helps.

Best regards,

Robinson Zhang
Microsoft Online Support


-------- Original-Nachricht --------

 

[Kelly]

Zhang it! )

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Please include the original post.

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool Plus!
http://www.kellys-korner-xp.com/taskbarplus!.htm

No one at MSFT appears to know how to do that.

Hi Nicolas,

I am just writing to see whether there is anything that I can do for you
on
this issue. If you have any concerns, please feel free to let me know. I
am
glad to be of assistance.

Have a nice day!

Best regards,

Robinson Zhang
Microsoft Online Support