Service Request Ticket - # 31055

Service Request Information

CONTACT Name Olsen, Kristin   View open tasks   View tasks from last 30 days   Schedule Change Contact Date Mar 13, 2009 08:31 AM
Department Human Resources Phone 88092
Location Email olsenk@wou.edu Request for more information Send 'Keeping in touch' email Send 'I'm thinking of you' email

SR INFO Type WOU #
Priority Equipment Type
Status Flagged
Description

Computer Edit WOU # 20050784[Edit Inv] (opens in a new window) Bldg/Room OFF
Service Tag Description OptiPlex GX620, Pentium 4, 3.2GHz, 2M, 800 FSB
Serial No. H4Z5L81 Location PDR

CPU Pentium 4-3.2GHz


OS Unknown Software MS Office Pro 2003 from P0054700

Wired NIC 00:12:3F:95:42:69


TECHS Submitted by Casey Sonflieth Contact csonflieth06@wou.edu 88925
Primary Technician Contact

Tracking

Entered by Date Memo
Self Resolved
Email

Public

Entered by Date Memo
Brian Berkley Mar 13, 2009 09:01 AM
****This is an email****
Hi Brian/Unix Team,
 
Never mind. Turns out I can delete the file myself.
 
Thanks anyway,
Kristi
Add Attachment
Brian Berkley Mar 13, 2009 09:01 AM
Task reassigned to Self Resolved.
Add Attachment
Brian Berkley Mar 13, 2009 09:01 AM
Status changed from (1) Pending to (5) Completed
Add Attachment
Casey Sonflieth Mar 13, 2009 08:33 AM
She tries to open the file and something says 
that it is locked for editing.  
it also says that she can do read only too.
the file that she is working on is the only one 
that says that it is locked for editing by UCS.

Phone:8-8092
Email:olsenk@wou.edu
Add Attachment
Brian Berkley Mar 13, 2009 08:33 AM
****This is an email****

Kristin,

This problem is due to the nature of the file
share server (called Samba) and the way it
interacts with open files.  Typically when a
network connection or connectivity is interrupted
while the file is open, it causes the document to
show up as locked for editing by the "user" that
the office program was installed under.  In this
case, it was Joe Crowe, who built the installation
of office for the images we put on computers (not
all of them, just older systems).

The file servers that mount the all the network
drives run on Unix, and this is an issue that can
only be resolved by the unix team.

In the meantime, the only workaround I can offer
is to open the file, save it under a new name, and
let the unix team (unix@wou.edu) know the path to
the "locked" files so they can delete them.

The "locked" files do not show up as read only in
the file system according to the unix admins.  Its
a "disconnect" that only really affects office
documents opened from the Samba file servers.
Add Attachment