Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 276
  • Last Modified:

Accessing Large MS Word files over network (90 MB).

Users are not able to access Large MS Word files over the network.

1. Users map drive to server holding docs.
2. Double click on file. (Takes more than 25 minutes to open the document).
3. When they go to do anything in the word get an error message and MS Word just closed itself down.

Error message:

"Program is not responding"

Your help is much appreciated.

Thanks!
0
Nirmal Sharma
Asked:
Nirmal Sharma
  • 3
  • 2
  • 2
  • +3
1 Solution
 
vsg375Commented:
Hi,

Word historically has a very poor ability to handle large documents... You might consider another solution for that type of documents, llike FrameMaker :

http://www.adobe.com/products/framemaker/

What's more, collaborative work on such huge documents will be such a PITA with Word that you can consider it's almost impossible... In any case, for collaborative work on any kind of documents, you might want to consider Sharepoint, or any other 3rd party solution.

HTH
Cheers
0
 
redseatechnologiesCommented:
>>http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/099485.html

How do you expect a FreeBSD link to be helpful?

This asker is a Hall Of Fame member of Experts-Exchange - He is well aware of Google, and if he wanted to the top three results, probably would have searched for it himself.

Windows Server 2003 is not the place to spam the hell out of threads with google hits - if you want to do that, go to Windows XP or Networking

-red
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
dynamitedotorgCommented:
Probably a daft question, but have you ruled out the network between the machines as causing the problem? Does the same thing happen if you copy the file locally and open it?

I've had similar problems in the past caused by a duplexing mismatch with a network card killing network throughput, and also with AV software taking too long to scan a large file.
0
 
vsg375Commented:
Yeah, jalilthe1 ...

Second Q where our paths cross, second question where the only answer you provide is a set of irrelevant links... If you desperately long for points... You might not be in the right place, and DEFINITELY not using the right method...

dynamitedotorg, I skipped that part. Indeed, if there's a real time scanning engine present, it might considerably slow things down. Might also be a network issue, but I wouldn't bet too much on that one tho...
As regards to downloading the document locally and see what happens, that would imho only be for testing purposes, unless absolutely no collaborative work is involved. Worth trying, though, but honestly, when dealing with docs approaching 100 Mb, you're at the limits of Word if you ask me...

Red, don't mention Xp or Networking for spamming purposes, Annie might just send us there as CVs for a punishment :o))))

Cheers

0
 
Netman66Commented:
Hey Sys,

What is the client OS, the server OS and version of Office?

I'm guessing the OS is 2003 (but one can't be too sure these days!!).

:o)

0
 
redseatechnologiesCommented:
>Annie might just send us there as CVs for a punishment

I have done my tour of duty in Networking, 7 ways splits all the way :)
0
 
Netman66Commented:
I think he got the message gentlemen!

0
 
Nirmal SharmaSolution ArchitectAuthor Commented:
>>Probably a daft question, but have you ruled out the network between the machines as causing the problem?
No issue with that.

>>>Does the same thing happen if you copy the file locally and open it?
Nah!..Works great...can copy the file locally.

>>>I skipped that part. Indeed, if there's a real time scanning engine present, it might considerably slow things down.
Have disabled scan engine. still not working.

>>>What is the client OS, the server OS and version of Office?

Windows XP, MS Office 2003.

>>>I'm guessing the OS is 2003 (but one can't be too sure these days!!).
Nah!..its Windows 2000!
0
 
Netman66Commented:
Are you serious about the server being Windows 2000?

Not that I'm trying to be a "Google Monkey", but there are known issues with Office and files on network shares.  Here are a few that I remember from previous problems we've had.

http://support.microsoft.com/kb/822219/en-us

http://support.microsoft.com/kb/829700/en-us

http://support.microsoft.com/kb/313937/en-us

This one is what I am expecting;  http://support.microsoft.com/kb/814112/en-us

Let me know.


0
 
Nirmal SharmaSolution ArchitectAuthor Commented:
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 3
  • 2
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now