Link to home
Create AccountLog in
Avatar of Andreas Gieryic
Andreas GieryicFlag for United States of America

asked on

Cannot open any Microsoft Office 2013 document on the server from one workstation

I have a Windows 7 Pro workstation running Office 2013. The workstation has all of the latest Windows 7 and Office 2013 updates.
-  Its connected to an SBS2008 server
- Everyone is set up to use SBS2008 Exchange server 2007 email. The Microsoft Office 2013 is a full install and not a subscription

When the user opens a spreadsheet saved on the server, he cannot open it up. Excel starts to open by displaying the Excel logo twice and then only opens the Excel template page where it shows all of the recently open files on the left side and all of the available Excel templates to the right
- Confirmed that this issue is true for all of the Office data files (Word, Excel, Powerpoint. .etc
- There are no issues opening any Office data files on the local drive
- No other user is having this issue

Troubleshooting Steps
-      tested and confirmed,  opening any office application files on the local drive, opens fine
-      tested and confirmed,  opening any office application files anywhere on the server, will not open,  
-      Logged off as the user and then logged on as the server administrator from his PC and was able to open any office document on the server as well as local files
-      ran a repair of the Microsoft Office 2013.  No Change
-      restriped the users full control security access to all his data on the server to no avail. User has no issues opening any non-office data files suchs PDF's and JPG's  . .etc
However, if I copy any office related data file from the server to the local PC, it opens fine
- I have not yet tried to log in to another workstation as this one user
-      My thought at this point is that I’ll have to recreate his user profile. We plan retiring the server and upgrading. I could move the user to a workgroup and reconfigure the email and drive mappings.
Avatar of John
Flag of Canada image

Try a full Repair of Office and test again.

Then, make a new, test, Windows User Profile (account).  At this point, this is just a different test account.  Log in, set up Office (not much to do) and test opening a document.  Does it work?
Avatar of Andreas Gieryic


I already performed a full office repair as mentioned above.
I tested the server admin account with no issues

I created an SBSTEST account.  Gave it access to the PC and added domain account to the local administrator's group. Worked fine with no issues
So then the user account is damaged and you need to re-create it.
That's what I thought.  
Not looking forward to doing that for this profile is quite large.
I was mistaken, I am still using the SBS2008 Exchange, we have not yet moved to Office 365 Exchange email
Just to give me peace of mind, I'll try logging on with his credentials on another workstation. I'm not using a roaming profile. Not sure what that will prove.
Please keep us posted.
I logged onto a different workstation as the problematic user and experienced no issues opening any office data files on the server

I'm wondering what the easiest task would be now with reference to the user's profile.
-We will be retiring this server within the next month or so. At that time, I'll have to move the PC into a workgroup before moving it into a new domain with the new server and server operating system
- I have to think this through because it's been near 10 years when I had to re-create a user profile using the SBS 2008 console and hopefully pointing it back to its current exchange email folder
Avatar of John
Flag of Canada image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
I also forgot to mention above, that I believe this issue happened after I installed 38 additional Microsoft updates. This particular PC had issues getting updates and I had to force the updates. I tried to do a system restore to an earlier time, but that's disabled by default. I could try to uninstall all the updates that were recently installed. What's your thought on that?
We update our client machines and do not damage profiles in the process.  

… I had to force the updates   <-- I think something went wrong and the best way would be to rebuild the machine and then use the existing profile.
I agree with you, John. I do have a Windows 7 system image that was created a few months ago that I may use but I think a rebuild is the best option. This will resolve other small issues that this PC was having

If I rebuilding, I will rebuild it in a workgroup and then point to the exchange server for email. That way, when I set up the new 2016 server, it will be ready to enter the new domain.
That seems correct and certainly worth a try.
Thanks John
You are most welcome and /I was pleased to help you resolve this
Avatar of Olgierd Ungehojer
Olgierd Ungehojer

Did you check GPO for this computer, it sound like some permission issue, but by Computer GPO. Is this computer in the same OU like others computers?