Excel and Word file saving locations

We discovered an issue with Word and Excel that is related to the migration to the new SAN. It was resolved at 11:30 AM today.

The issue is caused by Word and Excel having a default Save location which is specified as \\osd-home1\staff\, which is the location mapped to the H: drive for staff. The new location of the H: drive, on the new SAN,  is \\osdna1-a\home\staff\.

The result is that if you opened something this morning in Word or Excel, made changes, then saved, Word or Excel saved your changes on the old SAN unless you intentionally saved it to the new H: drive (and why would you?) So when you try to open the revised file, it seems to be unchanged.

Fear not- the changed file is still there. To access the file, open Windows Explorer and type \\osd-home1\staff in the address bar and press Enter. Then browse to the directory in which you saved the file. You can drag the file to your new H: drive (at \\osdna1-a\home\staff) or open the, select Save As..., and navigate to the H: drive.

Word and Excel were fixed at 11:30 AM, and the group policy settings were pushed out at 12:20 PM, so it should work correctly now. If you have problems, please reboot your computer first to see if it is fixed, then try to find the files using the workaround described above.

Strange issues with Microsoft Word not working

UPDATE 2008-08-05
These issues have been resolved for everyone except those who use the Lawson Excel plugins in Office 2003. We are still working on those.

---

We are dealing with multiple reports of Microsoft Word not working for some people. Symptoms include:

• Word crashes frequently
• Cannot save documents
• Crashes during mail merge
• Error "can't fire event"
• Error "not enough memory"
• Unable to view embedded images in PowerPoint (okay, not Word, but still Office)

One correlation is that Office 2003 seems to have these issues, whereas Office XP does not. The only people who should have Office 2003 are those who need the Lawson Excel plugins for Office 2003. Reverting others back to XP seems to help.

There are other issues that we are still investigating, but resolving the issue with Office 2003 is a high priority.