MS OFFICE issue on network share

Okay, so I have a public share replicated with DFS between 2 MS servers(1 2008r2 and the other 2012). On server A, I can open Office documents logged in as any user. On server B, I can only open the documents with users that have FULL CONTROL access to
the share. I can open text documents with any user on either server A or server B, but can't open Office documents on server B with a domain user that has less than FULL CONTROL rights. HELP!

Hi,
Firstly, please check the two shared folder’s share permission between the two DFS server to see if they are the same.
In the meantime, the issue is may be caused by restricted permission in Office documents, please refer to the articles below to see if it helps:
Protect your document, workbook, or presentation with passwords, permission, and other restrictions
http://office.microsoft.com/en-in/word-help/protect-your-document-workbook-or-presentation-with-passwords-permission-and-other-restrictions-HA010354324.aspx
Information Rights Management in Office 2010
http://office.microsoft.com/en-in/excel-help/information-rights-management-in-office-2010-HA010354260.aspx
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Can't open Office documents from network share

Dear,
I have a user named X that can't open Office documents from two specific shares. We call this shares T and U.
When the user X opens Office documents the error message is "...xlsx can't be opened". The problem is not client specific because when I login on the same client I can open the documents without any problem. If you copy the file to your desktop it
opens fine.
Any idea?

Anybody?
We have a problem with a customer that they can't open Office documents(Word,Excel etc.) on Windows 8 image on a network share. The error message is just that they can't open the document. The documents are on a sharepoint site and we can open the documents
within the site and also we can open the Office documents on a Windows 7 image.
I think there is a group policy for Windows 8 for this but I don't know for sure?
Anybody?

Saving documents in Office 2013 on network shares without delete permissions

I have found a few posts regarding this issue and the general resolution is to give delete permissions on the share. However, there is a KB article for Office 2010 (http://support.microsoft.com/kb/2589410)
that changes save behavior to use "Simple Copy" for saving to UNC shares, which works fine (and I can deal with .tmp file cleanup). However, this does not work for Office 2013 (as suggested here)
as you cannot install the hotfix because it requires office 2010. Is there a comparable fix for Office 2013? I have done a lot of searching but cannot find a resolution (aside from granting delete permissions).
Thanks,
Eric

Hi Eric,
The option of "Copy remotely stored files..." actually works for a document that is stored on a network or removable device (such as a disk or a removable disk). Here is a basic
description of it.
As I know that for Office to function properly it needs delete access to the folder where the files are stored.
To work around this, I'd suggest to set a backup folder to regularly backup the documents from the original folder before you grant the Delete permission. Is this an acceptable workaround for you?
Let me know if it's not suitable for you, and feel free to post back.
Thanks,
Ethan Hua CHN
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Cannot open Office 2013 Excel, Word, PPT Files on Network Share

Cannot open Office 2013 Excel, Word, PPT Files on Network Share
I am having a problem opening any Office 2013 file when it is located on a network drive. I immediately get the error:
"Microsoft Excel cannot open or save any more documents because there is not enough available memory or disk space.
. To make more memory available, close workbooks or programs you no longer need.
. To free disk space, delete files you no longer need from the disk you are saving to."
It only occurs when I try to access the file when it is stored on a network share. I cannot open any word, excel or PPT files located on my file shares.
I am on Windows 8 (pro), part of a local domain based on Server 2003, and have administrator rights to the domain and the file share where the Excel file resides (and Word files -same problem). If I copy the file locally, I can either open
it directly, or right-click, go to Properties and 'un-block' the file and then open it. But it is impractical to keep doing this, as I edit different files from the directory tree all day.
I have bing'd and google'd this extensively, and the only answers I come up with do not work, such as going into the DCOM config system and changing the user from interactive to launching user, or vice versa, or even using a specific user - mine
with the password. Since the product is so young there aren't a lot of posts on this, and nothing has improved the situation.
Can you add any insight to this? I really want to use Office 2013, but this is such an obstacle I'm going to have to downgrade if this problem cannot be resolved. Thank you very much for any help you can offer.
Evan

Dear Evan,
If DCOM config solution did not work, I'd suggest narrow down the problem by trying to access another network share on another server, try to open an Office file there, do we still have the error? It could help us determine if the issue is on the client
machine or the server side.
Best regards,
Daisy Cao
Forum Support
Please take a moment to "Mark As Answer" if they help.

Office files slow when opening from a Network Share

Hi!
So, we have a client who moved from having regular Office installations to Office 365 for Mid Size business and reinstalled the Office that comes along with Office 365. Ever since we did
that, there is a delay in opening any office files from a network share. Opening up a Word or Excel document takes up a lot longer than it did before. We have another client with the exact same issue who have Office 2013, so I think its mostly something to
do with office 2013. This problem has been going on for a month, and I have tried everything I can. I have gone through most posts on technet and the internets. Tried disabling AV, Office File Validation, added the network share to trusted locations, removed
add-ins. Nothing works! All other files opens up quickly, pdf, jpg. We can open larger jpg or pdf files faster than smaller office documents. This is a significant problem with our clients as they work in recruitment and open up resumes all day from the network
share and it takes forever to open.
Any advice or help is appreciated!
Thanks!
Shaneez

Hello,
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Mounting a network share via Applescript or Automator causes errors in MS Office apps

If I connect a network share using an automated process, either using Applescript or Automator, though the share shows up on the Desktop and I can open it and view the various folders and files, MS Office apps including Powerpoint, Excel and Word are unable to open the files. Each gives a slightly different error message. In Excel, it looks like this:
In Word, it's:
In Powerpoint, it's:
BUT, if I connect to the server share manually (using Cmnd-K in Finder), all files and folders are properly accessible. I cannot see any differences between the shares connected by the two different means on the Desktop. They have the same name, are the same size, etc.; in short, everything about them seems identical. I even took screen shots of the Get Info page from one of them connected by the different methods:
"home" connected by Automator:
and connected manually:
Does anyone have any ideas as to why this is happening or how to fix it?

I had the same issue. After upgrading kernel to 3.4.5 today the cifs share mounted with original fstab settings. I believe it was caused by this bug:
kernel changelog wrote: The double delimiter check that allows a comma in the password parsing code is
unconditional. We set "tmp_end" to the end of the string and we continue to
check for double delimiter. In the case where the password doesn't contain a
comma we end up setting tmp_end to NULL and eventually setting "options" to
"end". This results in the premature termination of the options string and hence
the values of UNCip and UNC are being set to NULL. This results in mount failure
with "Connecting to DFS root not implemented yet" error.

Issues Opening Files in Network Share

Hello,
I'm hoping someone can help me with this issue I'm having,
I use a Windows 7 desktop at my office and I have a Network Share on a Windows 2008 Server where I save all my documents and file I work on each day.
I use my Macbook Air when I'm working at my other office and when I'm traveling.
My issue is this,
I setup and able to connect to my Network Share and see all my folders and files. Although if I try to open a file it tells me it can't find the file even though I used Finder to browse right to the file and double clicked on the file. I can copy the file locally to my MacBook, work on the file and then copy it back to the Network Share.
From me testing different things this is what I have found,
It's only Word, Excel and Powerpoint documents that don't open from the Network Share. - I do have Microsoft Office 2011 Mac installed
TXT & PDF Files open just fine from the Network Share.
I doesn't matter if it's Word, Excel or Powerpoint files created on my Windows 7 desktop or my Macbook Air, once it's moved to Network Share I can't open it.
This is where it gets really confusing, other Network Shares I can open the Excel & Word files right from the Network Share, it's just my personal Network Share and I put in the right username and password for my Network Share since I can open the TXT & PDF files just fine.
I'd appricate any help with this issue.
Thanks in advanced - Jonathan

I have the same problem and i'm not the only one @ my office. seems that everybody who uses mac in our office has the same problem. So could anybody give any advice how to solve this problem? Do we need to configure shared folders on server or just our macs?

Deploying Office 365 Pro Plus from a network share?

I have setup a network share to install to a number of users, who I have applied licensing to and have created a script to run the setup with the xml configuration file.
The install runs completely fine, installs the 365 Pro Plus, but when the user goes back and starts a program, I get the activation needed button and the user clicks on it and up comes the Install product page that redirects to their online account and asks
for the Office to be installed again.
Here is my xml config file. Is the autactivate portion correct?
<Configuration>
<Add SourcePath="\\leo\office365" OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="Full" AcceptEULA="TRUE" />
<Logging Path="%temp%" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Hi,
As per the description, I understand that you are having issues with Office 365 activation after the installation.
I have tested this on my own machine (with a similar configuration.xml file). It works well if I enter the correct email address that's associated with this Office subscription.
Does this affect all users (email address)? I'd first suggest you check if you've installed the correct version of Office that's associated with these user accounts.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Setting the shared templates location by Deploying Office 365 Midsized Business "using a network share" from a on-premise location

I found the question "Deploy Office 365 pro plus using a network share or from a on-premise locaiton" the most useful of the resources
on MS yet - but I am having difficulties getting the files to download for a local deployment.
The root of the issue, that I cannot find anywhere, is how do I set the shared templates location for users in the organization. First I thought a GPO, but I cannot find that setting in the GPO in MS.
Then I thought modifying the REG- but it is in a binary key which could include other information I may not want modified(Or does it matter?)
Then I looked for ways to download the deployment but launching from an elevated prompt as IT (Domain level) returns a useless error to paraphrase- 'sorry MSOffice didn't install- do you have enough disk space'.
I have downloaded the GPO objects, but not installed them, likely I will need those later though.
Just want to path all the users to a central repository of office/excel/access/outlook templates in addition to their local templates. Concise help in steps or sites that have solved the issue are Greatly appreciated : )

Hi,
you can use the GPO ADMX templates to configure the "Workgroup templates path".
This actually configures a registry setting named: "sharedtemplates".
The registry value/type/data is:
HKEY_CURRENT_USER\Software\Policies\Microsoft\office\15.0\common\general
Name: sharedtemplates
Type: REG_EXPAND_SZ (Expandable String Value)
Data: <UNC path to folder>
From the GPO reference workbook/sheet, for Office:
http://social.technet.microsoft.com/wiki/contents/articles/4976.selected-content-relating-to-group-policy-administrative-templates-adm-and-admx.aspx
Filename: office15.admx
Scope: User
Path: Microsoft Office 2013\Shared paths
Policy Setting Name: Workgroup templates path
Supported on: At least Windows Server 2008 R2 or Windows 7
Category: Shared paths
Explain Text: Specifies the location of workgroup templates.
Registry Key: HKCU\software\policies\microsoft\office\15.0\common\general!sharedtemplates
Note: it is supported to populate this setting, with a UNC path, but not with a web path.
e.g.: \\server01\shared\templates <this is valid>
e.g.: http://server01/shared/templates <this is not valid>
This constraint (for web URIs) can be difficult to work around. If you are using SharePoint, and think WebDAV might work, it doesn't seem to work for us :(
Of course, if you have SharePoint, there are much better ways to handle document templates, but, our users are familiar with this File -> New -> from template type of method...
It can also be set manually by a user:
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Very Slow to save Office 2013 files (Excel/Word) to a network share

I have an issue with a customer's system whereby they experience problems with saving either a Word or Excel file to another workstation on the network.
The network share is located on a Windows7 Pro x64 machine. The problem can be seen on a machine that's running Windows 8.1 Pro X64 along with Office 2013. When the user attempts to save the document back to the network share, there's
a very long delay (sometime around a minute) before the save completes.
I've tried turning off indexing of off-line files (via indexing options) and also declaring the network location as a trusted location (via the Trust Centre settings from within Excel & Word).
If I simulate the same, but with a local file (eg loaded/saved to the Desktop) then there's no delay, so I conclude that it's something related to the process of saving data to the network share.
The normal copy speed across the network, and between these 2 machines, is very fast. It's only when running Word/Excel that the problem manifests itself.
Any pointers would be gratefully received!
Martin

Hi Martin,
Please first try to disable your antivirus software and check the issue again.
This issue may also occur if you use the Encrypting File System (EFS) to secure the Temporary Internet Files folder. If this is the situation, please refer to the following article and try to fix the issue:
http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2014/05/05/slow-saving-of-office-files-to-a-network-server-using-efs.aspx
In addition, please check if the information in the following link applies:
http://support.microsoft.com/kb/313937/en-us
Please let me know the result.
Best Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Office 365 x64 Click-to-Run Not Automatically Updating from Network Share

We are piloting Office 365 x64 and pointing the clients to a network share (see config file below) for updates. When we subsequently download the updates to the share the clients will not automatically install them. If we manually do so from
within an app (File > Account > Update Options > Update Now) it works fine. The ACL and Sharing permissions allow Everyone and Domain Computers read-only access (in addition to some other ancillary accounts). I've tried manually running
the Office Automatic Updates from Task Scheduler and left the box running overnight. I've rebooted, logged back on, closed and opened the app several times. Nothing happens, just always sits at the current version.
Anyone have any ideas?
      Thanks,
         Bryan
Here's the UpdateURL registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Configuration\UpdateUrl = \\<SERVERNAME>\Office_365\Pilot
ProPlusx64.xml:
<Configuration>
<Add OfficeClientEdition="64" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Updates Enabled="TRUE" UpdatePath="\\<SERVERNAME>\Office_365\Pilot\" />
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />
<Property Name="AUTOACTIVATE" Value="1" />
<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
</Configuration>
Here's what I think is the log file:
Timestamp Process TID Area Category EventID Level Message Correlation
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x554 Click-To-Run Telemetry aqkhc Medium {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","ExeVer":"15.0.4615.1002","SecuritySessionId":"0","ModulePath":"C:\Program Files\Microsoft Office 15\ClientX64\OfficeClickToRun.exe","CommandLine":"/service","Bitness":"64","IntegrityLevel":"0x4000"}
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x554 Click-To-Run Telemetry aqkhe Medium {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","OSVersion":"6.1","SP":"1","ProductType":"1","ProcessorArch":"9","Locale":"1033"}
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run annt7 Medium ProcessPool::Initialize - Initializing Main Process Pool
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run annuf Medium SystemProcessPool::DoInitialize - Initializing System Process Pool
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run anntv Medium ConfigurationManager::Initialize - Initializing ConfigurationManager
05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run annt4 Medium Pipeline::Initialize - Initializing pipeline with PipelineServerName: "ClickToRun_Pipeline" and InstallationPath: "C:\Program Files\Microsoft Office 15"
05/01/2015 11:21:11.154 OFFICECL (0x550) 0x568 Click-To-Run annt1 Medium Orchestration::Initialize - Initializing Orchestration
05/01/2015 11:21:11.201 OFFICECL (0x550) 0x568 Click-To-Run annto Medium ApiServer::Initialize - Initializing ApiServer for endpoint: C2RClientAPI_Server_System
05/01/2015 11:24:50.661 OFFICECL (0x550) 0x828 Click-To-Run annty Medium ExecutionContext::QueueScenario - Set executing scenario to UPDATE
05/01/2015 11:24:50.661 OFFICECL (0x550) 0x828 Click-To-Run annuz Medium TaskFactory::TryLoadScenario - Start loading UPDATE scenario
05/01/2015 11:24:50.661 OFFICECL (0x550) 0x828 Click-To-Run annu0 Medium TaskFactory::TryLoadScenario - Loading UPDATE scenario is successful
05/01/2015 11:24:50.676 OFFICECL (0x550) 0x828 Click-To-Run amavh Medium ScenarioController::Initialize - requested display level: False
05/01/2015 11:24:50.676 OFFICECL (0x550) 0x828 Click-To-Run annua Medium ProcessPool::QueueTaskItem - Task SCENARIO:{AC2F0D89-6518-48E9-A0D9-EF039C456034} is being scheduled to run in this process
05/01/2015 11:24:50.676 OFFICECL (0x550) 0x828 Click-To-Run aoicd Medium ExecutionContext::QueueScenario - Successfully queue scenario UPDATE.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run annua Medium ProcessPool::QueueTaskItem - Task UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0} is being scheduled to run in this process
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run annvj Medium Worker::TaskExecutionThreadProc - Task SCENARIO:{AC2F0D89-6518-48E9-A0D9-EF039C456034} completed with TaskState TASKSTATE_EXECUTING.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run annu6 Medium TaskGroup::DoHandleWorkerCompleteEvent - Task {AC2F0D89-6518-48E9-A0D9-EF039C456034} complete event is handled by task {AC2F0D89-6518-48E9-A0D9-EF039C456034}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run apm4n Medium TaskGroup::Finalize - Task AC2F0D89-6518-48E9-A0D9-EF039C456034 is not finished.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run Telemetry amb0n Medium TaskUpdateDetection::ApplySettings: Beginning Update Scenario. {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","TargetVersion":"UNDEFINED","InstallID":"C5912794-7300-4A10-840B-575B03DB98F8","TaskId":"77176F9C-873B-4A7D-8051-EBEB52DDE8B0","TaskState":"TASKSTATE_EXECUTING","UpdatePathType":"CUSTOM","TaskType":"UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0}","Scenario":"UPDATE","TriggeringUI":"UNDEFINED","TaskCaller":"SCHEDULEDTASK"}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run Telemetry aoh6s Medium TaskUpdateDetection::Execute: Ending Update scenario, task trigger source disabled. {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","InstallID":"C5912794-7300-4A10-840B-575B03DB98F8","TaskState":"TASKSTATE_EXECUTING","TaskId":"77176F9C-873B-4A7D-8051-EBEB52DDE8B0","TaskType":"UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0}","Scenario":"UPDATE"}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run annvj Medium Worker::TaskExecutionThreadProc - Task UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0} completed with TaskState TASKSTATE_FAILED.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4b Medium Task::DoHandleWorkerCompleteEvent - Setting Task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0) Task State to (TASKSTATE_FAILED)
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run aqkg7 Medium Task::DoHandleWorkerCompleteEvent - No event is specified for task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0)
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run Telemetry apm4e Medium Task::HandleTaskStateFailed - Handling TaskState (TASKSTATE_FAILED) for task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0). {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","InstallID":"C5912794-7300-4A10-840B-575B03DB98F8","TaskState":"TASKSTATE_FAILED","TaskId":"77176F9C-873B-4A7D-8051-EBEB52DDE8B0","TaskType":"UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0}","Scenario":"UPDATE"}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apkpk Monitorable ScenarioController::CheckProcessPool - Failed to get/create ui process pool, and we are not the ui handler. Cannot process event
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run annu6 Medium TaskGroup::DoHandleWorkerCompleteEvent - Task {77176F9C-873B-4A7D-8051-EBEB52DDE8B0} complete event is handled by task {AC2F0D89-6518-48E9-A0D9-EF039C456034}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {AC2F0D89-6518-48E9-A0D9-EF039C456034}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4a Monitorable Task::DoCancel - Can't cancel task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0) because it is in TASKSTATE_FAILED state
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (57173191-24E0-42E1-96F4-914AF8CFD1D5) in TASKSTATE_NOTSTARTED, set to Cancelled.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (AA63EED2-70B9-4E21-952C-9CFB09EC37C0) in TASKSTATE_NOTSTARTED, set to Cancelled.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {D1506E3F-4B2A-41D3-913B-FA3E889CE20D}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {539BA5C1-BC18-4D11-AF61-CF6EDC58DC33}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (D1E1E548-917D-4D75-8AE5-FC76856C66DC) in TASKSTATE_NOTSTARTED, set to Cancelled.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {9A54EEBA-7B8D-4BD5-8EFE-D21E58FFFEE3}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {9C141B7D-2B22-4C33-9C5C-F6F3394AD19E}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {501487AD-0A47-419D-AF30-B9E616A4579B}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {0270BAF9-3CE0-46EE-A3FE-099ABC06BC14}
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (F0E5AF5D-5D82-4370-A2A6-C064CBC39247) in TASKSTATE_NOTSTARTED, set to Cancelled.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 0270BAF9-3CE0-46EE-A3FE-099ABC06BC14.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 501487AD-0A47-419D-AF30-B9E616A4579B.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (A5E75ADF-8BF1-44C4-8900-1BE6070EB609) in TASKSTATE_NOTSTARTED, set to Cancelled.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 9C141B7D-2B22-4C33-9C5C-F6F3394AD19E.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 9A54EEBA-7B8D-4BD5-8EFE-D21E58FFFEE3.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 539BA5C1-BC18-4D11-AF61-CF6EDC58DC33.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task D1506E3F-4B2A-41D3-913B-FA3E889CE20D.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task AC2F0D89-6518-48E9-A0D9-EF039C456034.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task AC2F0D89-6518-48E9-A0D9-EF039C456034.
05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run annt0 Medium ExecutionContext::ResetExecutingScenario - Reset executing scenario

Hi,
I replied in the other thread:
http://social.technet.microsoft.com/Forums/office/en-US/e9e6be40-fb92-4734-9f94-9dee5599b1d8/office-365-pro-plus-2013-update-wont-apply-automatically?forum=officeitpro#c156ed8c-f65c-450c-9e0f-85f0de513c20
It seems when the install finished it added an extra Office\Data to the path. My path should be \\hsbswpush02\GPsoftware\o365\Office\Data\15.0.4551.1005
but it shows
\\hsbswpush02\GPsoftware\o365\Office\Data\Office\Data15.0.4551.1005
If I edit the path and delete the extra Office\Data Office 365 ProPlus updates from my network location. I cannot figure out why it is adding the extra Office\Data to the path.
My config file looks like this:
  <Updates Enabled="TRUE" UpdatePath="\\hsbswpush02\GPsoftware\o365\Office\Data" />
have you tried omitting the \Office\Data element, from the Updates element ?
http://technet.microsoft.com/en-us/library/jj219426.aspx#BKMK_UpdatesElement
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Excel 2013 hangs while trying to open a file from network share

Hi,
I am having issue opening excel file from a network share. it happens randomly, the file opens and hangs abruptly. Nothing happens after that ( we can only move the cursor), if we click on the excel sheet we get a beep sound. after i kill the excel process
and open it again ,it works fine.
Where did the member use the Excel file? Local disk, SharePoint, File server, or network shared disk?
       Network shared file and sometime locally
Does the issue occur in the special file or every file?
      it happens randomly and the whole excel freezes. i have to kill the excel session.
Which Office version is the file created? Excel 2013 or early? If it is XLS format, please try to convert to XLSX to test.
   Network file server has office 2010 and the user is trying to open it in excel 2013
Does the file have some macros?
Yes, they have macros in some files
Does the issue occur recently? If it is, have you installed some programs or update before you encountered it?
       it happened before too.
Do you get some error message when Excel crashed?
Yeah. Attaching the error message from event viewer. We get file corrupt errors and below too.
Please suggest

Hi Suren424,
Since your first image showed that "To see if more information about the problem is available, check the problem history in the Action Center control panel." Please go to this path (Control Panel\All Control Panel Items\Action Center\Problem Reports)
to check the detailed information, and you might upload the screenshot or info here.
Then, please try the following methods and check if they are helpful:
1. File --> Options --> Advanced --> uncheck "Ignore other applications that use Dynamic Data Exchange (DDE)"
2. Turn off "Protected View" --> (File –-> Options –-> Trust Center --> Protected View --> Uncheck all options
3. I notice that >>Network file server has office 2010 and the user is trying to open it in excel 2013 <<, it also might be caused by the Microsoft Office File Validation for Office 2010, please try to change setting in server with
the link:
http://support.microsoft.com/kb/2501584
If you have any update , please feel free let us know.
Regards,
George Zhao
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click "[email protected]"

Multiple users accessing document on network share

In our small office we have a couple of numbers douments that are regulary accessed and updated by 3 different people on three different machines, the numbers documents they access are stored on a network share on the Mac Server in the office.
The problem we have is that all three able to open a file at the same time, obviously this is causing all sorts of isues. People losing data they have put into the file and also causes issues with someone being unable to save the file while someone else has it open.
Surely there must be some sort of feature that when one person has the file open, its is locked for editing to everybody else that attempts to access it, I have searched around but cant seem to find anything to solve the problem. Anybody here have any suggestions?
Thanks
Craig

Once a document is all set up, and then you are just making relatively minor edits, then you might find it useful to "share" it on iCloud and have everyone access it and edit it via Numbers on icloud.com rather than Numbers on the Mac. That way you can all work on it at the same time without losing changes.
SG

Windows 8.1 Network Share 0x8007003b Error Copying Files

Hi All,
I'm having an issue when copying files from a Windows network share. If the file is above 5MB it will start copying and then after a minute or two I will get an error such as:
Interrupted Action
An unexpected error is keeping you from copying the file. If you continue to receive this error, you can use the error code to search for help with this problem.
Error 0x8007003B: An unexpected network error occurred.
The network share is in a different office and is accessible over a point-to-point VPN, so the connection is not that fast.
But before everyone tells me to start diagnosing the router and or VPN please take note of the following:
My colleague who is running Windows 7 can copy files from the network share fine
If I run a Windows 7 VM on my Windows 8.1 laptop I can copy the files across fine
I also know it isn't an issue with this particular file share. I set up a little lab, where I had one VM which had a shared folder and 2 other client VMs one running Windows 7 and one running Windows 8.1. I limited the bandwidth to the two client
VMs to a similar speed we see across our VPN. The result was that the Windows 8.1 failed with the same error above, whereas the Windows 7 copied fine.
There is also a noticeable difference visually when copying using Windows 8.1 and Windows 7:
Windows 7 - The progress bar progresses smoothly giving the current speed and estimated time remaining
Windows 8.1 - The progress bar progresses in a jumpy fashion. E.g. it shows no progress, then after a minute it jumps and shows 16% progress, then shows no further progress, then jumps by another 18%. There is no estimated time remaining.
I ran Wireshark to investigate what was going on at the network layer. I see the following behaviour:
Windows 8.1 - The file is copying fine then all of a sudden there are a lot of TCP dupack packets. After which the Windows 8.1 client sends a RST packet and then the error pops up.
Windows 7 - The file is copying fine then you also see a load of TCP dupack packets, however no error is displayed and it continues copying fine.
I'd appreciate any help with this I'm hoping there are some settings I can change to make Windows 8.1 behave more like Windows 7!
FYI originally posed here (but was advised to ask on Technet) - https://answers.microsoft.com/en-us/windows/forum/windows8_1-files/windows-81-network-share-0x8007003b-error-copying/300bc9a4-597b-402a-b885-9dd6f6fb51a2
Thanks,
Zak

Hi MeipoXu,
Sorry, it has taken me so long to reply. I thought I had subscribed to receive updates on this thread, but I didn't see anything!
I've ran the commands you gave but some of them did not work, I got the following error:
Set global command failed on IPv4 The parameter is incorrect.
However, output of current settings are below.
TCP Global Parameters
Receive-Side Scaling State : disabled
Chimney Offload State : disabled
NetDMA State : disabled
Direct Cache Access (DCA) : disabled
Receive Window Auto-Tuning Level : normal
Add-On Congestion Control Provider : none
ECN Capability : disabled
RFC 1323 Timestamps : disabled
Initial RTO : 3000
Receive Segment Coalescing State : disabled
Non Sack Rtt Resiliency : disabled
Max SYN Retransmissions : 2
To answer your original questions.
Do you mean the file below 5 MB will copy fine ?
5MB is not a hard limit. If the file is small enough it will copy before it errors out. A file of around 5MB or so fails with an error.
Have you tried to copy the files from another Windows 8.1 machine (This will help us to verify whether the issue is casued by the specific machine)?Have you tried to copy another file from the network share to have a check ?
Yes I've tried from another Windows 8.1 machine and have the same behaviour. It is the same with different files from the network share. And the same with different network shares.
I am seeing nothing in the event viewer when the error occurs. I do not believe this to be a VPN issue because I can recreate this situation perfectly. As I mentioned in the original post- I
also know it isn't an issue with this particular file share. I set up a little lab, where I had one VM which had a shared folder and 2 other client VMs one running Windows 7 and one running Windows 8.1. I limited the bandwidth to the two client VMs to a similar
speed we see across our VPN. The result was that the Windows 8.1 failed with the same error above, whereas the Windows 7 copied fine.
Basically, I had virtual machines all on the same local network. One virtual machine was hosting a file share with files on it. I created one Windows 7 VM and one Windows 8.1 VM. Using VMWare Workstation you can limit the network bandwidth to the VMs. When
I did not limit the network bandwidth I could copy all files of all sizes fine. However, when I limit the network bandwidth to a speed of around 30-50KBps, the Windows 8.1 VM fails to copy files with the same error. But Windows 7 VM copies the files fine.
The point of limiting the bandwidth in this way is to create a similar scenario to that I see when connecting over the VPN.
This all leads me to believe there is some sort of issue with copying files from fileshares over slow connections using Windows 8.1.
Cheers,
Zak

Very slow responce when working with Office file on DFS-Share

Very slow responce when working with Office file on DFS-Share
We have implemented the following configuration
Domain level Windows 2000. Two member servers with Windows Server 2008 R2, sharing the same DFS namespace with, at the moment, one folder target called Home.
Users complaining that the access to different MS Office files is very slow. Even creating a new MS Word document using right click context menu takes up to 4 minutes to open. Saving, for example, one singe Excel sheet takes also few minutes.
Tested with both, MS Office 2007 and MS Office 2010. Makes no difference. When using Office 2010 you can see the message like contacting:
\\DomainName\Root\Home\UserName. Other files like TXT, JPG or PDF are not affected.
What makes the thing really weird is the fact, that the behavior described above can absolutely change after client machine being rebooted, suddenly everything becomes very fast and this condition can revert back again just after the next
reboot.
Considerations until now:
1. This has nothing to do with the file size. Even tiny files are affected.
2. AD Sites are configured correctly and the client workstations see themselves in the correct sites.
3. This is not an Office issue. If I map my folder target not as DFS, but directly as shared network drive
\\ServerName\Root\Home\UserName , everything functions as expected
What makes me suspicious: when using f.e. TCPView to monitor connections, I can see, that each time I make any operation on an office file, there will be a connection established to one of the domain controllers, sometimes to remote ones,
located in other countries. But on the other side, even if the connection is established to the nearest DC, operations are still very very slow!
Just forget to say. All clients are Windows 7
Thanks to all who respond.

Dear all,
sorry for the delayed reply. The problem has been solved now and since September 19<sup>th</sup>. everything is functioning as expected.
What was done:
Deleted replication targets excepting the initial ones
Carefully recreated folder targets
Deleted and recreated replication groups
Disabled SNP features on both namespace servers
Created EnableTCPA registry entry
Checked that the following Updates are installed
http://support.microsoft.com/kb/2688074
http://support.microsoft.com/kb/2647452
Concering Office File validation KB2553065 - This Update was already declined on our WSUS server
Kind Regards
Eduard

MS OFFICE issue on network share

Similar Messages

Maybe you are looking for