Word 2003 doesn't create a normal.dot until there are changes made from the
install defaults requiring a normal.dot for saving them (change default font
or page setup default, etc.)
Terry
: We are still occasionally having the problem. Yesterday, one of the users
I
: had already renamed the normal.dot to normal.bad started havning the
problem
: again. I searched for the current normal.dot to change that again, but
I'm
: not finding it on the system (I did search in all subfolders and hidden
: directories). Any other ideas? Thanks!
:
: "TF" wrote:
:
: > My suspicion is that there must be something incompatible in the
normal.dot
: > (stored in the users' profiles - usually documents and settings,
username,
: > application data, microsoft, template folder). Normal.dot in Word2003
isn't
: > created until such time as the user makes a change to Word's default
that
: > has to be saved to normal.dot (such as the default font, or the page
: > layout). On your next upgrade problem, try renaming normal.dot as
normal.bad
: > and see if that resolves the issue.
: >
: > Terry
: >
message
: > : > : No, I was logged in as the user but the user is an Administrator.
: > :
: > : "TF" wrote:
: > :
: > : > Were you logged in as Administrator when you ran the upgrade?
: > : >
: > : > Terry
: > : >
: > : >
: > message
: > : > : > : > : Sorry it has taken me a while to get back to this. If I create a
new
: > : > userid
: > : > : on the domain for the user and they login as the new userid, it
seems,
: > at
: > : > the
: > : > : time, to be working. However, it seems to be happening to all of
my
: > users
: > : > : when I do an upgrade beyond Office 2000. One of my users has a
brand
: > new
: > : > : computer and I just did the upgrade from 2000 to 2003. He did not
: > have
: > : > the
: > : > : stalling problem with 2000, only since I've upgraded to 2003 (this
: > week).
: > : > Do
: > : > : I have to create brand new domain logins for all users when they
: > upgrade?
: > : > :
: > : > : "Gidget Kimble" wrote:
: > : > :
: > : > : > The user who is testing for me said there is no problems when
: > opening a
: > : > local
: > : > : > document, only ones that are on the network. He also said that
as
: > he
: > : > was
: > : > : > sending me an email, Outlook was also stopping and starting.
: > : > : >
: > : > : > "TF" wrote:
: > : > : >
: > : > : > > I take it that these are documents opened from the server?
What
: > : > happens if
: > : > : > > they open a local document: do they still have the same
problem?
: > : > : > >
: > : > : > > Terry
: > : > : > >
in
: > : > message
: > : > : > > : > : > : > > : Yes I did and it's not there.
: > : > : > > :
: > : > : > > : "Suzanne S. Barnhill" wrote:
: > : > : > > :
: > : > : > > : > That file is often present even with Symantec CE. Have you
: > looked?
: > : > : > > : >
: > : > : > > : > --
: > : > : > > : > Suzanne S. Barnhill
: > : > : > > : > Microsoft MVP (Word)
: > : > : > > : > Words into Type
: > : > : > > : > Fairhope, Alabama USA
: > : > : > > :
: > : > : > > : > Email cannot be acknowledged; please post all follow-ups
to
: > the
: > : > : > > newsgroup so
: > : > : > > : > all may benefit.
: > : > : > > : >
: > : > : > > : > "Gidget Kimble" <
[email protected]>
wrote
: > in
: > : > : > > message
: > : > : > > : > : > : > : > > : > > The OFFICEAV.DLL file is not there because we are not
using
: > : > Norton but
: > : > : > > : > > Symantec Corporate Edition.
: > : > : > > : > >
: > : > : > > : > > "garfield-n-odie" wrote:
: > : > : > > : > >
: > : > : > > : > > > Search for the OFFICEAV.DLL file on the affected
users'
: > hard
: > : > drives
: > : > : > > (be
: > : > : > > : > > > sure to include system and hidden files/folders in the
: > search
: > : > : > > options).
: > : > : > > : > > > If you find it, note the folder where it is located,
and
: > use
: > : > the
: > : > : > > : > > > "regsvr32 /u" method described in
: > : > : > > : > > >
http://support.microsoft.com/?kbid=329820 "How to use
: > Office
: > : > : > > programs
: > : > : > > : > > > with the Norton AntiVirus Office plug-in" to
unregister
: > the
: > : > DLL.
: > : > : > > : > > >
: > : > : > > : > > > Gidget Kimble wrote:
: > : > : > > : > > >
: > : > : > > : > > > > I have a few users here having a problem when
opening a
: > Word
: > : > : > > document
: > : > : > > : > (or
: > : > : > > : > > > > Excel spreadsheet too) where as soon as the file is
: > opened,
: > : > Word
: > : > : > > goes
: > : > : > > : > into
: > : > : > > : > > > > not responding mode. It usually takes about 30
seconds
: > to a
: > : > : > > minute
: > : > : > > : > until you
: > : > : > > : > > > > can actually do anything with the document. All
users
: > have
: > : > : > > Windows XP
: > : > : > > : > > > > Professional. Two users are using Word 2000 and one
is
: > : > using Word
: > : > : > > : > 2002. We
: > : > : > > : > > > > are on a Server 2000 network and the files that are
: > being
: > : > opened
: > : > : > > are
: > : > : > > : > saved on
: > : > : > > : > > > > the server. We are using Symantec Corporate Edition
: > : > Antivirus
: > : > : > > : > software.
: > : > : > > : > > > >
: > : > : > > : > > > > Any thoughts? Thanks!
: > : > : > > : > > >
: > : > : > > : > > >
: > : > : > > : >
: > : > : > > : >
: > : > : > >
: > : > : > >
: > : > : > >
: > : >
: > : >
: > : >
: >
: >
: >
