Event ID 1000 for Outlook 2003

  • Thread starter Thread starter Andrea
  • Start date Start date
A

Andrea

Faulting Application Outlook.exe, version 11.0.5510.0, stamp 3f1380f0,
faulting module mso.dll, version 11.0.5606.0, stamp 3f334cce, debug?
0, fault address 0x001befb5.

I get the above error when I'm in Outlook 2003 and I try to add an
attachment to a new email message. Right when you are supposed to
browse for the file to attach it comes up with an error of this sort.
The above is in the application log in event viewer.

I am running Windows 2000 SP4 and Outlook 2003.

Please help. This error is starting to pop up all over my
organization. Thanks in advance.

Andrea
 
Does this error show with any machine that has SP1 for Office/Outlook 2003
installed? (Build number you supplied indicates an original release.)

Does this error happen when Outlook is started in safe mode? (There are 5
different safe command line switches. /safe, /safe:1, /safe:2, /safe:3,
/safe:4. Each suppresses certain features from being read to hopefully
isolate where the crash is coming from. See Outlook's online help for
additional information about command line swtiches.)

/neo

ps - right now i suspect a third party addin. (if word is the e-mail
editor, don't forget that word addin's might also cause a bleed over and
cause outlook grief.)
 
Thanks Neo

I have some user's that are on SP1 and it happens to also.

It works when using safe mode too.

More info:
If User A logs into his own workstation, problem will happen.
User A has roaming profile.

If User B logs into User A's workstation, there is no problem.
User B has a Local Profile.

If User A logs into User B's workstation, problem does not occur.

I am having them test if User A logs into another workstation having
the issue if it will work or not.

Any advice would be helpful. Thanks again.
Andrea
 
It works in safe mode.

Some of my user's having the issue are using Office 2003 SP1.

One more thing though:

Here is a scenario:

User A logs onto his pc with a roaming profile and has the problem
User B logs into User A's pc with a local profile and there is no
problem
If User A logs into User B's pc the problem does not exist either.
Any help will be appreciated. Thanks.
 
Yes, we tried a new Outlook Profile. We also deleted his profile off
the network and off of the local workstation. Also, it seems as if you
rebuild the workstation the problem goes away. This happened for one
user. The only user we tested a rebuild on. So it seems to me, that
there is something held either in the registry or on the local pc that
loads only for him, and if a new person logs in it doesn't happen.
Also, because it exists on his local workstation, it does not follow
him. This is really weird... and is starting to pop up on more and
more workstations. Thanks for the help so far, and any more help would
be greatly appreciated. Thanks.
 
Yes, we tried a new Outlook Profile. We also deleted his profile off
the network and off of the local workstation. Also, it seems as if you
rebuild the workstation the problem goes away. This happened for one
user. The only user we tested a rebuild on. So it seems to me, that
there is something held either in the registry or on the local pc that
loads only for him, and if a new person logs in it doesn't happen.
Also, because it exists on his local workstation, it does not follow
him. This is really weird... and is starting to pop up on more and
more workstations. Thanks for the help so far, and any more help would
be greatly appreciated. Thanks.
 
Back
Top