1. In Windows, open Control Panel.
  2. Open Folder Options.
  3. On the View tab, under Advanced settings, under Files and Folders, under Hidden files and folders, select Show hidden files, folders, and drives.

The following table shows the location and content of the various plain text log files.

Type of log file
Subfolder
File name
Outlook 2013
Outlook 2010
Outlook 2007
Outlook Autodiscover
Temp
olkdisc.log
No
Yes
Yes
Exchange ActiveSync
Temp/EASLogFiles
datafilename.bin
datafilename.xml
Yes
No
No
Availability service
Temp/OlkAS
date-time-fb.log
No
No
Yes
Availability service, OOF, and meeting suggestion
Temp/OlkAS
date-time-AS.log
No
Yes
No
Protection rules
Temp/OlkAS
date-time-PB4S.log
No
Yes
No
Unified messaging
Temp/OlkAS
date-time-UM.log
No
Yes
No
Unified messaging configuration
Temp/OlkAS
date-time-UMCFG.log
No
Yes
No
Out-of-office
Temp/OlkAS
date-time-oof.log
No
No
Yes
Meeting suggestion
Temp/OlkAS
date-time-ms.log
No
No
Yes
Outlook calendar
Temp/OlCalLogs
OLKCalLog_date-time.etl
Yes
Yes
Yes
Transport
Temp/Outlook Logging
opmlog.log
Yes
Yes
Yes
SMTP
Temp/Outlook Logging
emailaddress-Outgoing-date-time.log
Yes
Yes
Yes
POP3
Temp/Outlook Logging
emailaddress-Incoming-date-time.log
Yes
Yes
Yes
IMAP
Temp/Outlook Logging
IMAP-emailaddress-Incoming-date-time.log
Yes
Yes
Yes
HTTP DAV
Temp/Outlook Logging
HTTP-emailaddress-date-time.log
No
Yes
Yes
Outlook Hotmail Connector
Temp/Outlook Logging
OLC-emailaddress-date-time.log
OLC-date-time.log
emailaddress.txt
No
Yes
Yes
Out-of-office
Temp/Outlook Logging
date-time-oof.log
No
Yes
No
Outlook profile
Temp/Outlook Logging
PROF_OUTLOOK_threadID_action_year.month.day_hour.minute.second.txt
Yes
Yes
No
Outlook sharing engine
Free music without download. Temp/Outlook Logging
Sharing Enginedate .log
Yes
Yes
Yes
Outlook-Windows Desktop Search indexing
Temp/Outlook Logging
datafilename.log
Yes
Yes
Yes
Outlook advanced ETW
Temp/Outlook Logging
Outlook-date-time.etl
Yes
Yes
No
Mailtips
Temp/Outlook Logging
date-time-mailtips.log
No
Yes
No
Free busy
Temp/Outlook Logging
date-time-fb.log
No
Yes
No
Outlook Sharing Engine
Temp/Outlook Logging
Sharing Enginedatetime-mailtips.log
Yes
Yes
Yes
Outlook first run process
Temp/Outlook Logging
firstrun.log
Yes
Yes
Yes

Administrator information

As an administrator, you can use the registry to turn logging on or off, and you can also deploy logging settings to users.

Active4 years, 5 months ago
This error is on Windows 7 Home Premium on my laptop (x64). I am trying to learn more about Windows Internals by using local kernel debugging in WinDBG, followed by LiveKD. I have Windows Debugging Tools for Windows 7 installed.
I keep getting the following errors - what could be wrong (in the screenshot I use kd instead of windbg to capture the error message; the shell is run as administrator)? I tried running LiveKD because WinDBG was failing. I just wanted to look at internal data structures.
BTW, WinDBG asked me to run 'bcdedit -debug on and reboot to enable it' - I ran it and rebooted the machine. There was no change in the boot sequence - the machine booted directly into Windows 7 as usual.
ARV

Enable Gpo Debugging Windows 7

ARV
3253 gold badges6 silver badges14 bronze badges

2 Answers

I managed to fix it by re-installing debugging tools for windows. To do this, I first uninstalled it, and downloaded the x64 Windows 7 SDK ISO from this link (http://www.microsoft.com/en-us/download/details.aspx?id=8442). The file name is GRMSDKX_EN_DVD.iso. Be sure to check the SHA1 checksum of the downloaded ISO image - in my case, my first download was incomplete and the installation didn't go smoothly. I chose to install only the WinDBG tools the second time and now I can debug the kernel locally. After I downloaded the latest version of SysInternals suite, I am also able to run LiveKD without any issues.
ARVARV
3253 gold badges6 silver badges14 bronze badges
I run into the same situation once. Yet figure out what happened to me was that I forgot to run windbg as administrator. Basically to enable local kernel debugging on Windows 7, only few steps are needed.
  1. start cmd as Administrator, run 'bcdedit -debug on'
  2. reboot
  3. (optional) install symbols
  4. install windbg (x64 if you are using windows 7 64bit, otherwise install x86.)
  5. run windbg as Administrator
  6. set symbol path in windbg menu
  7. enjoy it, there should be no more errors.

Enable Firewire Debugging Windows 7

Alan DuanAlan Duan

Debugging Windows Xp

Not the answer you're looking for? Browse other questions tagged windows-7windbg or ask your own question.