Here's a question. have you tried logging on as that user to a *different*
workstation? If so, try blowing away that user's profile and recreating it.
I've seen really odd stuff happen with respect to profiles. stuff like no
longer having access to their profile if you change 'em from admin to user,
etc.

 

John-AldrichPerception_2

 

From: Cameron Cooper [mailto:[email protected]] 
Sent: Friday, September 03, 2010 1:57 PM
To: NT System Admin Issues
Subject: RE: Excel Sharing Violation

 

Same thing happens with a copy of the document.  No other add-ins that the
other users don't have.  Only add-ins in Excel (for all users) is for
ZetaFax.

 

_____________________________

Cameron Cooper

Network Administrator | CompTIA A+ Certified

Aurico Reports, Inc

Phone: 847-890-4021 | Fax: 847-255-1896

[email protected] | www.aurico.com

 

From: Jonathan Link [mailto:[email protected]] 
Sent: Friday, September 03, 2010 12:51 PM
To: NT System Admin Issues
Subject: Re: Excel Sharing Violation

 

What happens on a copy of the document?

Are there addins in use by others that he might not have, or has an older
version?

On Fri, Sep 3, 2010 at 1:49 PM, Cameron Cooper <[email protected]> wrote:

I've looked all over the intertubes and haven't found anything to help
resolve the following issue..

 

We have several users that share a workbook in Excel 2010 (on windows 7),
all can access the workbook and save except one user.  When the one user
goes to save they get the following error: Your changes could not be saved
to "filename" because of a sharing violation.  Try saving to a different
file.  When you click on "help", it mentions that the antivirus active
protection is causing the issue.  We have Vipre Enterprise Premium installed
and when I looked at the active protection/quarantine/blocked items there's
nothing there.  Here are the steps I've taken so far:

 

-          Stopped the Vipre services, opened the excel workbook and still
receive the same error

-          Checked the NIC properties, all set accordingly

-          Checked that the computer was part of the domain and it's on the
correct domain

-          Checked the workbooks permissions on the network share and the
user has full rights

-          Switched the user from Power User to Administrator and still the
same error comes up

-          Removed and then recreated the users profile in windows and still
the same error comes up

-          Checked the users account properties in AD to confirm that the
account wasn't locked out and that they were a member in the correct groups

 

At a loss here on what could be causing this.

 

_____________________________

Cameron Cooper

Network Administrator | CompTIA A+ Certified

Aurico Reports, Inc

Phone: 847-890-4021 | Fax: 847-255-1896

[email protected] | www.aurico.com <http://www.aurico.com/> 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

<<image001.jpg>>

<<image002.jpg>>

Reply via email to