Outlook 2011 Error
22.July.2011 07:26 Filed in: Tech Tips
We have had some recent reports of a new error
popping up for users when launching Outlook 2011. (We
have been using and testing Outlook 2011 since last
fall, and we have not seen or experienced this error
until this past week-and-a-half.) The error that some
users have received is pictured below.
While this is annoying, this is actually an error that you can fix yourself when you see it pop up. It is simply a matter of finding the correct "fake file" and deleting it.
First, begin by going to your home directory in the finder. (Pictured below)
Then, from there, you will navigate over to the "Library" folder in your home directory. (Ordinarily, this is not a folder that you need to go in.)
If you are getting this error, inside your "Library" folder, you will see what appears to be a file called "Caches" with a little arrow in the lower left corner. This is not actually a file. It is an alias, a "fake file".
Drag it to the trash (or right-click on it and select "Move to Trash"). Empty your trash.
Now, if you re-launch Outlook 2011, it should open for you without any trouble. Additionally, for the staff members who have applied this solution up until this point, we have not yet seen this problem re-occur.
While this is annoying, this is actually an error that you can fix yourself when you see it pop up. It is simply a matter of finding the correct "fake file" and deleting it.
First, begin by going to your home directory in the finder. (Pictured below)
Then, from there, you will navigate over to the "Library" folder in your home directory. (Ordinarily, this is not a folder that you need to go in.)
If you are getting this error, inside your "Library" folder, you will see what appears to be a file called "Caches" with a little arrow in the lower left corner. This is not actually a file. It is an alias, a "fake file".
Drag it to the trash (or right-click on it and select "Move to Trash"). Empty your trash.
Now, if you re-launch Outlook 2011, it should open for you without any trouble. Additionally, for the staff members who have applied this solution up until this point, we have not yet seen this problem re-occur.
