Calendar folder property is missing outlook 2010 ошибка
If your Outlook folders are missing or deleted, you have three options to recover deleted or missing folder in Outlook 2016, 2013, 2010, 2007, 2003 and 2002. Try each of them to retrieve your Outlook messages, calendars, contacts, tasks or other information.
Table of Contents
About the Author
Reviews and Awards
Many users have a terrible experience of deleting or losing an Outlook folder with valuable information by accident. If you are suffering from the same problem, don't worry! This page offers full solutions to help recover emails, messages, appointments, calendars, tasks or notes from the disappeared folder in Outlook 2016, 2013, 2010, 2007, 2003 and 2002.
Workable Solutions | Step-by-step Troubleshooting |
---|---|
Fix 1. Recover from Trash | In Outlook, click "Deleted Items" or "Trash" folder. Right-click file and then click "Move" > "Other Folder". Full steps |
Fix 2. Recover from server | In Outlook, go to "Deleted Items". Click "Recover Deleted Items From Server" and recover deleted emails. Full steps |
Fix 3. Recover with software | Use EaseUS email recovery software to scan and recover permanently deleted or missing Outlook Folder. Full steps |
Recover from Deleted Items or Trash
Applies to: Accidentally delete an item from your Outlook folder and never emptied the "Deleted Items" or "Trash" folder.
If you deleted a folder in Outlook by soft-delete, which means you hit the "Delete" button while right-clicking on the item, or drag and move the item to trash, the first place to check is the Deleted Items or Trash folder according to the type of email account you have in Outlook.
Step 1. In Outlook, go to your email folder list, and then click "Deleted Items" or "Trash" folder.
Step 2. You can recover the messages/calendars/contacts/tasks by right-clicking and then click "Move" > "Other Folder" > "Inbox" or other corresponding folders in Outlook, at last click "OK".
You can't recover a folder that's been permanently deleted. But you can still use the following two ways to recover permanently deleted emails from the folder you deleted in Outlook.
Recover Deleted Items in the Deleted Folder the Server
Applies to: Permanently delete an item from the inbox or from another Outlook folder by selecting it and pressing Shift+Delete. Delete an item from the Deleted Items folder or empty the Deleted Items folder and can't restore the missing items.
Step 1. In Outlook, go to your email folder list, and then click "Deleted Items".
Step 2. Make sure Home is selected, and then click "Recover Deleted Items From Server". Then, Microsoft will recover permanently deleted emails from their exchange server and list them for you.
Tip If Recover Deleted Items From Server isn't there; your account doesn't support recovering an item that's no longer in your Deleted Items folder.
Step 3. Select the item you want to recover, click "Restore Selected Items", and then click "OK". After you recover an item, you can find it in your "Deleted Items" folder and then move it to another folder.
Although Microsoft Outlook has the inbuilt fixes for retrieving the removed items, not everyone can benefit from the features. If the above two methods fail, you still have EaseUS data recovery software to help you recover a deleted folder in Outlook as the last attempt.
Recover Deleted Folder in Outlook with EaseUS Data Recovery Software
Applies to: recover of all types of Outlook data files with the .pst or .ost file extension.
EaseUS hard drive recovery software supports both PST file recovery and OST file recovery. It can quickly scan the whole hard drive on your PC and find the deleted folder in Outlook for you. Apart from deletion recovery, this versatile data recovery program also supports restoring emails in many other complex situations, like formatted recovery, lost partition recovery, OS crash recovery, RAW partition recovery, etc.
Now, download this email recovery tool and start to retrieve the deleted or lost folder in Outlook within three steps.
Step 1. Choose the drive or partition where you lost email files, and click "Scan".
Step 2. The software will initiate a scanning process immediately. Wait patiently until the scanning process completes. To quickly locate the email files, click "Others" in the left panel. Then, look for PST files or Outlook files in the file type list.
Step 3. Then, choose the desired email files and click "Recover". Save the files to another location instead of the original one.
Import PST/OST Files into Outlook
To retrieve your email to Outlook, do as the following steps.
1. Start Outlook. Go to "File" > "Open & Export" > "Import/Export" > "Import from another program or file" > "Open Outlook Data File".
2. In the navigation pane, drag and drop the emails, contacts, other folders from .pst file to your existing Outlook folders.
On This Page
Note This release is not available at this time. We are investigating a problem with this release.
Note This release is not available at this time. We are investigating a problem with this release.
I think that answers your question.
Was this update installed before your problems started?
Yes. There were no event log entries until after I installed the update.
Is there a way to undo the hotfix?
Is the update listed in Add Remove programs? If not, try System Restore, if you have restore points back far enough. Support filed a bug report for it but no resolution at this time.
The update was pulled for an unrelated problem, although I have no idea what that problem is.
All of the Office 2010 July 2013 CU's have been pulled.
I removed KB2817371 and it appears to have resolved the Calendar Folder property is missing event log spam.
- Proposed as answer by Diane Poremsky [MVP] MVP Sunday, June 23, 2013 3:57 AM
- Marked as answer by Max Meng Tuesday, June 25, 2013 7:10 AM
- Unmarked as answer by BSOD2600 Wednesday, July 24, 2013 11:41 PM
Same problem is back after installing Office 2010 SP2 :(
Per the change log downloadable spreadsheet , "Service Pack 2 also includes a rollup of all Cumulative Updates through April 2013, and all Public Updates through May 2013". Doesn't seem like that is a true statement as it must've also included some aspects of the July 2013 Outlook CU.
I also have the same issue after installing the Office 2010 SP2 Update. It is not listed as a known issue in KB 2687520.
Hope this helps, Gerry
i have the same error too with sp2.
I'm not using Exchange
i have the same error too after installing Office 2010 x86 SP2: in the event viewer.msc a lot of advices about Calendar Folder Property is missing, after each time I run Outlook.
Before SP2 nothing about this very annoing problem
same issue on 7 computers running Office 2010 pro 32bit on Windows 7 64 bit, including 2 of my own computers
none of the computers are related to each other, each seperate clients of mine
all are stand alones and none are using an exchange account just a regular pop account
Seems this error msg is all over the internet on several sites
Whoever installed Sp2 seems to be having the same error msgs when opening Outlook
Hello,
Just off the pst files to Outlook- plugged and the problem disappears. Only that is not an option because the user must have access to the old pst file . Tested on Outlook configured with and without exchange .
Windows 7 32bit and Office 2010 sp2 .
I wonder whether the removal of the amendment " outlook- x - none.msp " from sp2 to resolve the matter . Tomorrow I'll test so I know.
best regards,
Nazir79
Well Nazir79 I hope that your test on the "Outlook-x-none.msp" from SP2 will be the solution of the problem.
I wanted to add my voice to the chorus to help validate the urgency for a solution whether from Microsoft or someone with knowledge and compassion that would not have otherwise allowed Microsoft push out a bad product.
windows 8 pro 64, Office home and business 2010 64 bit
Calendar Folder property is missing
Calendar Folder property is empty
The warnings are generated when Outlook 2010 SP2 opens and each time I interact with Outlook [make a calendar entry, create a task, open a contact]. The event log fills up like drinking water from a fire hydrant.
I know this was triggered by SP2 because I had examined the event log the day before the "update" and it was normal with no warnings. The only update I did was SP2 for Microsoft Office Home and Business 2010.
This is more than just an annoyance. I am concerned that future use will escalate issues to a point of major failure.
For what it is worth, I can sync successfully my outlook calendar and contacts with my Galaxy S4 using Samsung Kies.
please see the post and response by Tony Chen about this issue
Having the same issue after SP2 upgrade. User got to have several shared calendars to manage. Uninstalling SP2 will work but we need to have it fix.
I have this problem too and it is resolved(for me) by uninstalling the July updates.
Look forward to hearing from MS that the problem is acknowledged and to seeing updates to resolve the problem. Until then I have hidden these updates and will not be re-installing them.
They are not ignoring the issue and a fix is targeted for the August or September update (depending on further investigation and testing results). There is no negative side-effects known to this issue other then the Event Log entry.
The negative side effect is that for those users who have a shared calendar, it will not show the full information. It will just show s "busy". Even after removing the calendar right and adding it back again.
Does MS perform testing prior to releasing updates? Curious that such a simple/obvious issue could slip past some pretty smart and capable people. Sad to say, my Application Log looks like BSOD2600's (thanks for the "Data Visualization").
Where I used to work, we always performed "rollout tests" in a duplicate production environment to find/fix problem prior to release. And the few times that anything did slip past that testing, we certainly pulled it prior to re-releasing.
They are not ignoring the issue and a fix is targeted for the August or September update (depending on further investigation and testing results). There is no negative side-effects known to this issue other then the Event Log entry.
Robert, could you please direct me to an article that suggests this target fix date of August or September? I'd like to keep track of it so I can begin test deployments again as soon as this problem is resolved.
Robert, could you please direct me to an article that suggests this target fix date of August or September? I'd like to keep track of it so I can begin test deployments again as soon as this problem is resolved.
Currently, there is no article about this issue and it hasn't been fixed in the August update either nor will it be available for the September update/hotfix. The latest information I got was "it will take a couple of months".
The investigations still indicate that the issue is "purely cosmetic" but getting it out of the code takes a while.
To keep track of the issue yourself, open a support incident with Microsoft. Since it is a known bug, no support charges will apply but you might need to supply credit card information to register your support request.
Currently, there is no article about this issue and it hasn't been fixed in the August update either nor will it be available for the September update/hotfix. The latest information I got was "it will take a couple of months".
The investigations still indicate that the issue is "purely cosmetic" but getting it out of the code takes a while.
To keep track of the issue yourself, open a support incident with Microsoft. Since it is a known bug, no support charges will apply but you might need to supply credit card information to register your support request.
Robert Sparnaaij
Just downloaded the most recent Office updates today 9/11/13. The problem is still NOT Fixed. When I uninstall Office SP2, the warning goes away. But my updates are always reminding me to update ..Uh!
Why has this issue gone on so long without a fix.
I am facing the same issue too. But additionally, not sure if related, sending emails seems affected as it stalled while Outlook is trying to synch and it seems forever
Sorry for the answer proposals-click of the mouse.
We have found that this error relates to shared calendars in Outlook. The more shared calendars you have, the more errors. Also, the errors are generated each time you LEAVE your calendar view. If you watch the event log, you'll see that visiting the calendar view does not cause the errors, but as soon as you switch back to your inbox, the errors are generated.
At least, this is the case in my environment. If anyone else cares to confirm, please do, but I doubt it will speed the fix process :-)
Office 2010 (14.0.7106.5001) 32bit
Appears after SP2 installed.
When click on Inbox in logs 27 generated.
No shared calendars
It may be related to calendars in archive folders. If you have archive folders open, close them. Close and open Outlook. Check for Event 27.
The properties of calendars in archive folders do not have a Permissions tab. I think the Permissions tab is the missing property referenced in the Event 27 message.
SP2 and KB27947070 may have some code that looks for permission on calendars, even calendars in archive folders. Prior to them calendars in archive folders may not have been checked for permissions.
still comes up after closing all archive folders and restarting outlook.
also the errors still roll in even just being @ the inbox, not touching my calendar at all.
kind of annoying, but other than a few KB more logs per day doesn't seem to be a big deal.
We see that error appearing here as soon as someone adds a calendar from SharePoint to Outlook. The calendars work fine though.
In our case, on further checking, the problem is not archive folders per se; it's the lack of permissions on calendar folders in .pst files. We use Exchange 2010, so the only .pst files users had were archive.pst. If a user closed their archive.pst file, using Outlook did not generate Event 27.
If you don't use Exchange, you probably have a .pst file as your primary Outlook data file, so you can't do without it.
We don't use SharePoint, so the only comment I have is if there are no .pst files in use, I'd be surprised if Event 27 is generated.
In our case the event dissapeared after uninstalling KB2794707
I was able to reproduce the problem in the following way:
My Machine: Windows 7 Ultimate SP2, Outlook 2010 SP 2 (KB2687455).
Create a new, empty PST file on my local hard drive, "MyTemp"
Create a new, folder for Calendar items inside the "MyTemp" PST file, call it "MyTempCalendar"
Create one new calendar appointment, call it MyTest.
Use the event viewer and look at the "outlook" application log. note the time
Open (i.e. click) the MyTest appointment, note the time.
Look at the new entries in the "outlook" application log: ID 27, " Calendar Folder property is missing"
This repeats every time I open this appointment.
Now wait for a FIX from Microsoft.
Marcelo - un webmaster de Argentina
Same here. Waiting for a fix too.Marcelo - un webmaster de Argentina
Good news it's acknowledged. Bad news, there's still no fix.
What in the hell does this mean in English??
Your first sentence is gibberish.
i had a similar problem . i had set 4.2.2.2 as a statistic DNS on my pc
Even Outlook web access was not opening
I changed it to obtain DNS server address automatically, that fixed the issue
I have the same Problem, Office 2010 SP2 on Win2008 R2 Server, every time the shared calender is opened, the event "Calender Folder Property is missing". We have 250 Users who are all working over Citrix and it is very annoying because it happens often that outlook hung up (cause of this) in the citrix session. So the users had to logoff and login again. Still waiting for an fix.
Two things seem to cause this issue for me:
- If I have users in Calendar Groups that are either no longer in Exchange (2013) or do not have calendar information set, then Outlook will kick out this error.
- There is a SharePoint company calendar that's pushed out to Outlook that appears to cause this as well. I can delete the calendar and the error goes away for the session, but it comes back once Outlook is closed and opened and the shared calendar is pushed back out.
In both instances, the error is only committed to the log when leaving the calendar view.
I too am having this issue, and I did not notice it until today when I went to check the logs to try & resolve another issue. but the log is absolutely being spammed w/these ID 27 errors!
Another month passes and no resolution of this issue.
Hope this helps, Gerry
Yes it solved it for me. Thanks for posting the link.
Hope this helps, Gerry
Thanks for the Hotfix! Works fine!
Instant response, good documentation and fast fix of the problem. as you would expect from a market leader. *insertironicsmileyofyourchoice*
For those who have trouble installing extracted file from "471202_intl_i386_zip.exe", you may also use a utility like Winzip to extract the file for a second time, and you would get this file: outlook-x-none.msp
Right click the file and click Apply.
Hope this helps.
To go one (or a few) steps further, if you need to apply this hotfix to many computers on a network, try the following (working in my environment):
1. Extract the msp file from the exe as SoHard noted above.
2. Place the msp in a centrally accessible location.
3. Create a batch file (like OutlookHotfix.bat) with the following contents:
net use t:
c:\windows\system32\msiexec.exe /p t:\outlook-x-none.msp /qn
PAUSE
net use t: /delete
4. Create a .txt file with a list of computer names to receive the hotfix (each on separate line)
5. Run psexec (downloadable tool) with the following command from command prompt:
This will execute the batch file for each computer in the list, in order. The batch file maps the folder containing the msp file as a "t" drive, then executes msiexec with options to apply the msp. It then pauses (to avoid issues with trying to unmap before process completely finishes), and when user hits enter (i had to hit enter twice in some cases), then unmaps the "t" drive. Edit: The psexec command copies the batch file to the target machine (that's what the "-c" does), and executes it.
I ended up doing this because psexec will not directly execute the msiexec/msp command correctly, I believe due to using a unc path. If you place the msp file in a location that's already a mapped drive, you may not have to use this workaround, but in the interest of being thorough, I have included it here.
On This Page
Note This release is not available at this time. We are investigating a problem with this release.
Note This release is not available at this time. We are investigating a problem with this release.
I think that answers your question.
Was this update installed before your problems started?
Yes. There were no event log entries until after I installed the update.
Is there a way to undo the hotfix?
Is the update listed in Add Remove programs? If not, try System Restore, if you have restore points back far enough. Support filed a bug report for it but no resolution at this time.
The update was pulled for an unrelated problem, although I have no idea what that problem is.
All of the Office 2010 July 2013 CU's have been pulled.
I removed KB2817371 and it appears to have resolved the Calendar Folder property is missing event log spam.
- Предложено в качестве ответа Diane Poremsky [MVP] MVP 23 июня 2013 г. 3:57
- Помечено в качестве ответа Max Meng 25 июня 2013 г. 7:10
- Снята пометка об ответе BSOD2600 24 июля 2013 г. 23:41
Same problem is back after installing Office 2010 SP2 :(
Per the change log downloadable spreadsheet , "Service Pack 2 also includes a rollup of all Cumulative Updates through April 2013, and all Public Updates through May 2013". Doesn't seem like that is a true statement as it must've also included some aspects of the July 2013 Outlook CU.
I also have the same issue after installing the Office 2010 SP2 Update. It is not listed as a known issue in KB 2687520.
Hope this helps, Gerry
i have the same error too with sp2.
I'm not using Exchange
i have the same error too after installing Office 2010 x86 SP2: in the event viewer.msc a lot of advices about Calendar Folder Property is missing, after each time I run Outlook.
Before SP2 nothing about this very annoing problem
same issue on 7 computers running Office 2010 pro 32bit on Windows 7 64 bit, including 2 of my own computers
none of the computers are related to each other, each seperate clients of mine
all are stand alones and none are using an exchange account just a regular pop account
Seems this error msg is all over the internet on several sites
Whoever installed Sp2 seems to be having the same error msgs when opening Outlook
Hello,
Just off the pst files to Outlook- plugged and the problem disappears. Only that is not an option because the user must have access to the old pst file . Tested on Outlook configured with and without exchange .
Windows 7 32bit and Office 2010 sp2 .
I wonder whether the removal of the amendment " outlook- x - none.msp " from sp2 to resolve the matter . Tomorrow I'll test so I know.
best regards,
Nazir79
Well Nazir79 I hope that your test on the "Outlook-x-none.msp" from SP2 will be the solution of the problem.
I wanted to add my voice to the chorus to help validate the urgency for a solution whether from Microsoft or someone with knowledge and compassion that would not have otherwise allowed Microsoft push out a bad product.
windows 8 pro 64, Office home and business 2010 64 bit
Calendar Folder property is missing
Calendar Folder property is empty
The warnings are generated when Outlook 2010 SP2 opens and each time I interact with Outlook [make a calendar entry, create a task, open a contact]. The event log fills up like drinking water from a fire hydrant.
I know this was triggered by SP2 because I had examined the event log the day before the "update" and it was normal with no warnings. The only update I did was SP2 for Microsoft Office Home and Business 2010.
This is more than just an annoyance. I am concerned that future use will escalate issues to a point of major failure.
For what it is worth, I can sync successfully my outlook calendar and contacts with my Galaxy S4 using Samsung Kies.
please see the post and response by Tony Chen about this issue
Having the same issue after SP2 upgrade. User got to have several shared calendars to manage. Uninstalling SP2 will work but we need to have it fix.
I have this problem too and it is resolved(for me) by uninstalling the July updates.
Look forward to hearing from MS that the problem is acknowledged and to seeing updates to resolve the problem. Until then I have hidden these updates and will not be re-installing them.
They are not ignoring the issue and a fix is targeted for the August or September update (depending on further investigation and testing results). There is no negative side-effects known to this issue other then the Event Log entry.
The negative side effect is that for those users who have a shared calendar, it will not show the full information. It will just show s "busy". Even after removing the calendar right and adding it back again.
Does MS perform testing prior to releasing updates? Curious that such a simple/obvious issue could slip past some pretty smart and capable people. Sad to say, my Application Log looks like BSOD2600's (thanks for the "Data Visualization").
Where I used to work, we always performed "rollout tests" in a duplicate production environment to find/fix problem prior to release. And the few times that anything did slip past that testing, we certainly pulled it prior to re-releasing.
They are not ignoring the issue and a fix is targeted for the August or September update (depending on further investigation and testing results). There is no negative side-effects known to this issue other then the Event Log entry.
Robert, could you please direct me to an article that suggests this target fix date of August or September? I'd like to keep track of it so I can begin test deployments again as soon as this problem is resolved.
Robert, could you please direct me to an article that suggests this target fix date of August or September? I'd like to keep track of it so I can begin test deployments again as soon as this problem is resolved.
Currently, there is no article about this issue and it hasn't been fixed in the August update either nor will it be available for the September update/hotfix. The latest information I got was "it will take a couple of months".
The investigations still indicate that the issue is "purely cosmetic" but getting it out of the code takes a while.
To keep track of the issue yourself, open a support incident with Microsoft. Since it is a known bug, no support charges will apply but you might need to supply credit card information to register your support request.
Currently, there is no article about this issue and it hasn't been fixed in the August update either nor will it be available for the September update/hotfix. The latest information I got was "it will take a couple of months".
The investigations still indicate that the issue is "purely cosmetic" but getting it out of the code takes a while.
To keep track of the issue yourself, open a support incident with Microsoft. Since it is a known bug, no support charges will apply but you might need to supply credit card information to register your support request.
Robert Sparnaaij
Just downloaded the most recent Office updates today 9/11/13. The problem is still NOT Fixed. When I uninstall Office SP2, the warning goes away. But my updates are always reminding me to update ..Uh!
Why has this issue gone on so long without a fix.
I am facing the same issue too. But additionally, not sure if related, sending emails seems affected as it stalled while Outlook is trying to synch and it seems forever
Sorry for the answer proposals-click of the mouse.
We have found that this error relates to shared calendars in Outlook. The more shared calendars you have, the more errors. Also, the errors are generated each time you LEAVE your calendar view. If you watch the event log, you'll see that visiting the calendar view does not cause the errors, but as soon as you switch back to your inbox, the errors are generated.
At least, this is the case in my environment. If anyone else cares to confirm, please do, but I doubt it will speed the fix process :-)
Office 2010 (14.0.7106.5001) 32bit
Appears after SP2 installed.
When click on Inbox in logs 27 generated.
No shared calendars
It may be related to calendars in archive folders. If you have archive folders open, close them. Close and open Outlook. Check for Event 27.
The properties of calendars in archive folders do not have a Permissions tab. I think the Permissions tab is the missing property referenced in the Event 27 message.
SP2 and KB27947070 may have some code that looks for permission on calendars, even calendars in archive folders. Prior to them calendars in archive folders may not have been checked for permissions.
still comes up after closing all archive folders and restarting outlook.
also the errors still roll in even just being @ the inbox, not touching my calendar at all.
kind of annoying, but other than a few KB more logs per day doesn't seem to be a big deal.
We see that error appearing here as soon as someone adds a calendar from SharePoint to Outlook. The calendars work fine though.
In our case, on further checking, the problem is not archive folders per se; it's the lack of permissions on calendar folders in .pst files. We use Exchange 2010, so the only .pst files users had were archive.pst. If a user closed their archive.pst file, using Outlook did not generate Event 27.
If you don't use Exchange, you probably have a .pst file as your primary Outlook data file, so you can't do without it.
We don't use SharePoint, so the only comment I have is if there are no .pst files in use, I'd be surprised if Event 27 is generated.
In our case the event dissapeared after uninstalling KB2794707
I was able to reproduce the problem in the following way:
My Machine: Windows 7 Ultimate SP2, Outlook 2010 SP 2 (KB2687455).
Create a new, empty PST file on my local hard drive, "MyTemp"
Create a new, folder for Calendar items inside the "MyTemp" PST file, call it "MyTempCalendar"
Create one new calendar appointment, call it MyTest.
Use the event viewer and look at the "outlook" application log. note the time
Open (i.e. click) the MyTest appointment, note the time.
Look at the new entries in the "outlook" application log: ID 27, " Calendar Folder property is missing"
This repeats every time I open this appointment.
Now wait for a FIX from Microsoft.
Marcelo - un webmaster de Argentina
Same here. Waiting for a fix too.Marcelo - un webmaster de Argentina
Good news it's acknowledged. Bad news, there's still no fix.
What in the hell does this mean in English??
Your first sentence is gibberish.
i had a similar problem . i had set 4.2.2.2 as a statistic DNS on my pc
Even Outlook web access was not opening
I changed it to obtain DNS server address automatically, that fixed the issue
I have the same Problem, Office 2010 SP2 on Win2008 R2 Server, every time the shared calender is opened, the event "Calender Folder Property is missing". We have 250 Users who are all working over Citrix and it is very annoying because it happens often that outlook hung up (cause of this) in the citrix session. So the users had to logoff and login again. Still waiting for an fix.
Two things seem to cause this issue for me:
- If I have users in Calendar Groups that are either no longer in Exchange (2013) or do not have calendar information set, then Outlook will kick out this error.
- There is a SharePoint company calendar that's pushed out to Outlook that appears to cause this as well. I can delete the calendar and the error goes away for the session, but it comes back once Outlook is closed and opened and the shared calendar is pushed back out.
In both instances, the error is only committed to the log when leaving the calendar view.
I too am having this issue, and I did not notice it until today when I went to check the logs to try & resolve another issue. but the log is absolutely being spammed w/these ID 27 errors!
Another month passes and no resolution of this issue.
Hope this helps, Gerry
Yes it solved it for me. Thanks for posting the link.
Hope this helps, Gerry
Thanks for the Hotfix! Works fine!
Instant response, good documentation and fast fix of the problem. as you would expect from a market leader. *insertironicsmileyofyourchoice*
For those who have trouble installing extracted file from "471202_intl_i386_zip.exe", you may also use a utility like Winzip to extract the file for a second time, and you would get this file: outlook-x-none.msp
Right click the file and click Apply.
Hope this helps.
To go one (or a few) steps further, if you need to apply this hotfix to many computers on a network, try the following (working in my environment):
1. Extract the msp file from the exe as SoHard noted above.
2. Place the msp in a centrally accessible location.
3. Create a batch file (like OutlookHotfix.bat) with the following contents:
net use t:
c:\windows\system32\msiexec.exe /p t:\outlook-x-none.msp /qn
PAUSE
net use t: /delete
4. Create a .txt file with a list of computer names to receive the hotfix (each on separate line)
5. Run psexec (downloadable tool) with the following command from command prompt:
This will execute the batch file for each computer in the list, in order. The batch file maps the folder containing the msp file as a "t" drive, then executes msiexec with options to apply the msp. It then pauses (to avoid issues with trying to unmap before process completely finishes), and when user hits enter (i had to hit enter twice in some cases), then unmaps the "t" drive. Edit: The psexec command copies the batch file to the target machine (that's what the "-c" does), and executes it.
I ended up doing this because psexec will not directly execute the msiexec/msp command correctly, I believe due to using a unc path. If you place the msp file in a location that's already a mapped drive, you may not have to use this workaround, but in the interest of being thorough, I have included it here.
After installing Office 2010 SP2 (or an earlier update), Outlook 2010 users started noticing Event ID 27, "Calendar Folder property is missing" warnings in the Event viewer's Application log. While annoying, it's not harmful and should only be generated when Outlook is first started, one event for each calendar in the profile.
Microsoft discovered this warning is triggered for users who have a PST in their profile, including PSTs that were created by connecting to a SharePoint site, subscribing to Internet Calendars, as well as used by POP3 and IMAP accounts and AutoArchive.
Microsoft's workaround? Remove the PST files. Seriously.
To work around this problem, PSTs can be removed from the profile. To remove PSTs from your Outlook profile, follow these steps:1. Open Microsoft Outlook 2010.
2. Click File, and then click Account Settings.
3. Click the Data Files tab.
4. Select the data file that you want to remove, and then click Remove.
Removing PSTs from your profile will not remove the PSTs from your system. Removing some PSTs may result in loss of functionality in Outlook. For example, removing the SharePoint Lists PST will remove connections to SharePoint sites.
"Removing some PSTs may result in loss of functionality in Outlook." "may" reduce functionality? I think removing any PST from a profile is highly likely to reduce functionality in Outlook, especially if it belongs to a POP3 or IMAP account.
Personally, I'll live with the annoying events and keep my SharePoint connections, while I wait for a real fix. It's easy enough to create a filter in the event log that hides Event 27 and they'll age off.
To create a filter, open the Event viewer and right-click on Application log and choose Filter Current Log.
Type -27 in the Includes/Excludes field in the middle of the dialog and click Ok. This will hide Event 27 but show all other events.
Event ID 27: Calendar Folder property is missing (fixed) was last modified: February 13th, 2018 by Diane Poremsky
After applying Office 2010 Service Pack 2 or one of the last updates that were released for Service Pack 1 (KB2817371 or later), you may see the following warning popping up multiple times in the Application Log of the Event Viewer:
Source: Outlook
EventID: 27
Description: Calendar Folder Property is missing
Office 2010 Service Pack 2 is safe to use
While it might seem scary to suddenly have that many warning events, investigation by the Outlook Team shows that there is no actual harm done to the system and the issue is basically “purely cosmetic”.
This means that there isn’t any direct need to uninstall SP2 and proceeding deployment of SP2 is fully supported.
Update:
A fix for this issue will be part of the December 2013 update for Outlook 2010 (released on December 10 to be precise).
There is also a quite vocal thread with additional information about this issue in the Outlook IT Pro TechNet forum.
Solutions and alternatives
A warning event is logged upon starting Outlook for each Calendar that you have when you have a pst-file attached to your mail profile.
Currently, the proposed solution in the KB article is to remove any pst-files from your mail profile.
While this may be a viable solution when you only have an Exchange account or Outlook Hotmail Connector account configured in your mail profile, it certainly isn’t possible to do this when you have a POP3 or IMAP account configured in Outlook or are also connected to a SharePoint Server or Web Calendars.
As mentioned previously, the warnings can be safely ignored. However, if you want them out of your Event Viewer, you can hide them by applying a filter.
- Use the “Filter Current Log…” link in the Actions pane of the Event Viewer or from the right click menu on “Application” under Windows Logs.
- Specify the following:
- Event level: Warning
- Event sources: Outlook
- Includes/Excludes Event IDs: -27
To set the exclude filter, don’t forget the minus ( – ) in front of 27.
(Click on image to enlarge)
Note:
Don’t worry about your Event Log or hard disk filling up: By default, the Application log will only grow up to 20MB and will automatically purge older items when this size has been reached.
In praxis this means that it can keep over 25.000 events which, for the average system, is almost a year back. The amount of items logged by this Outlook bug is hardly affecting that.
Читайте также: