Category: Troubleshooting

Check the Event Viewer from PowerShell

Below are examples of checking the event viewer via PowerShell.
Running local with event id and date range
Get-WinEvent -FilterHashtable @{logname=’application’;id=4107;StartTime=”1/15/11″;EndTime=”1/17/11″}
 
Running on remote computer with event ID
Get-WinEvent -computername <remote computer> -FilterHashtable @{logname=’application’;id=15006}

Allow Exchange 2013 to accept remote powershell from Orchestrator

Scenario: Orchestrator was not able to connect and run Exchange powershell commands. The error received is:

Error opening remote PowerShell runspace to endpointhttp://exchangeservername/powershell: Connecting to remote server failed with the following error message : The WinRM client cannot process the request.
 
Resolution:
1. Make sure the Execution Policy on the Exchange Shell is set to RemoteSigned.
a. Use Get-ExecutionPolicy to see what it is.
b. Use Set-ExecutionPolicy RemoteSigned to set it.
2. Enable Basic and Windows Authentication on the Powershell IIS Site.
a. Expand: Default Web siteàPowershell.
b. Click on Authentication
c. Enable Basic and Windows Authentication.
  
The above steps did the trick for me, but the site below offers a few more steps.

Connecting to Exchange 2013 EWS with Exchange 2010 Folder Permissions

Scenario: When making Exchange 2013 EWS calls that proxies down to a Exchange 2010 mailbox connecting via shared folder permissions of another Exchange 2010 mailbox, the EWS connection may be unstable. Programs such as Starfish, SoapUI, or other programs making EWS calls, may or may not connect consistently and some errors encountered are 400 Bad Request errors.

Resolution: We created a new mailbox in Exchange 2013 and gave this mailbox the folder share permissions to the Exchange 2010 mailboxes. Making EWS calls to Exchange 2013 by using the 2013 mailbox to connect to the mailbox folders of the 2010 mailbox, EWS had become stable and successful.

Wrong photo showing for an e-mail receipent in Outlook 2010

Issue- The wrong photo is showing for an e-mail receipent when a customer tries to send a message. This is only happening sending from her acccount.
 
Resolution- The person sending the message had a local contact with a second e-mail address listed associated with a picture. Deleting the wrong information in the contact resolves the issue

Rebuilding search index

If you search for items in Microsoft Office Outlook 2007 and 2010 and do not receive the results that you expect, the indexing of your Microsoft Windows and Microsoft Office system data files (the search catalog) may not be complete.
Symptoms of an incomplete index include the following:
  • Partial or no search results are returned.
  • Items that you expect to appear based on your search criteria are not displayed.
You can rebuild the search catalog, which restarts the indexing of your data files. The search catalog is a file where all of your Outlook and Microsoft Windows items (data files) are indexed. To rebuild your search catalog, do the following:
  1. Exit Outlook.
  2. In Microsoft Windows, click the Start button, and then click Control Panel.
  3. Do one of the following:
    • Windows Vista Click System Maintenance, and then click Indexing Options.
Note In Classic view, double-click Indexing Options.
  • Microsoft Windows XP Under See Also, click Other Control Panel Options, and then click Indexing Options.
Note In Classic view, double-click Indexing Options.
  1. Click Modify, select the check boxes for the locations you want to index, and then click OK.
  2. Click Advanced.
  3. Click Rebuild.
  4. Restart Outlook

unable to search for an existing AD account to create a room mailbox

Unable to see existing AD account to create room mailbox.
Issue – Customer wanted a room account created from an existing AD account. When creating the room and choosing existing user, AD account would not display
Resolution- This is by the design. Room accounts are associated with disabled AD accounts. The AD account needs to be disabled prior to create the room mailbox

Cannot send email to a distribution list

Issue: Customer called to inform that she was getting the error below when sending to a distribution list in Exchange server. User’s mailbox is homed on another mail server
Your message wasn’t delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
Resolution:
1. Find the Distribution list in Exchange using the mgmt console
2. Right click on it, properties, mail flow settings
3. Double click on Message delivery restrictions
4. Uncheck require that all senders are authenticated box and click ok
5. You have now resolved the issue

Outlook web access did not initialize. Contact your administrator

Error: Outlook web access did not initialize. Contact your administrator.
Cause: Customer’s alias in Active directory didn’t match user logon name
Resolution: Corrected customer’s alias to match user logon name. Also changed uid attribute using ADSIedit to match corrected alias

meeting requests sent to a user gets sent to another outlook user

Issue:
 
user A sends meeting request to user B, user C(in a different department) gets the meeting request even though she was not invited. This only happened when meeting request is sent to user B
 
resolution:
 
Problem was fixed by having user A close outlook, re-open Outlook by typing
 
start, run, Outlook /Cleanrules, close outlook and run Outlook /cleanfreebusy
 
This fixed the problem. User C no longer received meeting requests sent to User B