Thursday, July 3, 2014

Exchange 2010: How to Delete the First Database and Move the System Mailboxes

Before removing the Last Database from the system Confirm the location
(a) Transaction log file
(b) Catalogue file


The First database contains the SystemMailboxes which are the Arbitration mailbox(es).
We have to move these system mailboxes to another database before of remove the Default Database.
1. Find the Arbitration Mailbox using the Exchange Management Shell (EMS):
Get-Mailbox -Arbitration | Where {$_.Name -like "SystemMailbox*" } | ft –wrap

2. Now create a new move request in order to move the system mailboxes to another mailbox database:
New-MoveRequest -Identity "SystemMailbox{1f05a927-32d1-4e19-8ea5-67eba859f541-yourGUID}" -TargetDatabase "dbxxxx"
3. Verify whether the move request completed:
Get-MoveRequest
4. Now remove the move request
Remove-MoveRequest -Identity "the name of the request like Microsoft Exchange Approval Assistant"

Wednesday, July 2, 2014

Exchange 2007 SP3 Rollup 13 "Microsoft Information store" Crashes

Issue
=================
In Exchange 2007 environment, Single box holds Hub, CAS, MBX roles is installed with SP3 Rollup 13

OS: Microsoft Windows Server 2003 R2 Enterprise Edition x64, Service pack 2

Microsoft Information store is crashing within 2-3 Minutes and on checking the Application log shows the following Event id 



Event Type:       Error
Event Source:       MSExchangeIS
Event Category:       General
Event ID:       9659
Date:             7/1/2014
Time:             12:15:50 PM
User:             N/A
Computer:       computername
Description:
The Microsoft Exchange Information Store encountered an unexpected exception 0xC0000005 at address 00000001403B8C4B while processing a request for user NETWORK SERVICE.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 45 00 63 00 44 00 6f 00   E.c.D.o.
0008: 52 00 70 00 63 00 45 00   R.p.c.E.
0010: 78 00 74 00 32 00 00 00   x.t.2...
0018: 5b 44 49 41 47 5f 43 54   [DIAG_CT
0020: 58 5d 00 00 0e 02 00 00   X]......
0028: ff 4c 0d 00 00 00 00 00   ÿL......
0030: 00 03 00 02 00 00 b9 8e   ......¹Ž
0038: 00 10 0f 01 04 80 d3 15   .....€Ó.
0040: 40 10 0f 01 04 80 a9 fe   @....€©þ
0048: 00 10 ec 03 00 00 71 5d   ..ì...q]
0050: 40 10 ec 03 00 00 d2 55   @.ì...ÒU
0058: 60 20 0f 01 04 80 00 80   ` ...€.€
0060: 6f 67 0f 01 04 80 f1 5e   og...€ñ^
0068: 40 10 0f 01 04 80 1c 41   @....€.A
0070: 00 10 0f 01 04 80 49 9a   .....€Iš
0078: 00 10 0f 01 04 80 49 da   .....€IÚ
0080: 40 10 0f 01 04 80 1c 6c   @....€.l
0088: 00 10 94 00 00 00 1c 5c   ..”....\
0090: 00 10 0f 01 04 80 b9 8e   .....€¹Ž
0098: 00 10 0f 01 04 80 d3 15   .....€Ó.
00a0: 40 10 0f 01 04 80 a9 fe   @....€©þ
00a8: 00 10 0f 01 04 80 d2 55   .....€ÒU
00b0: 60 20 0f 01 04 80 40 00   ` ...€@.
00b8: 8f 66 0f 01 04 80 d2 55   f...€ÒU
00c0: 60 20 0f 01 04 80 02 01   ` ...€..
00c8: 80 38 0f 01 04 80 ac 1a   €8...€¬.
00d0: 40 10 0f 01 04 80 d2 55   @....€ÒU
00d8: 60 20 0f 01 04 80 02 01   ` ...€..
00e0: 80 38 0f 01 04 80 ac 1a   €8...€¬.
00e8: 40 10 0f 01 04 80 1c 41   @....€.A
00f0: 00 10 0f 01 04 80 1c 41   .....€.A
00f8: 00 10 0f 01 04 80 49 9a   .....€Iš
0100: 00 10 0f 01 04 80 49 da   .....€IÚ
0108: 40 10 0f 01 04 80 1c 6c   @....€.l
0110: 00 10 0f 01 04 80 1c 5c   .....€.\
0118: 00 10 0f 01 04 80 b9 8e   .....€¹Ž
0120: 00 10 0f 01 04 80 d3 15   .....€Ó.
0128: 40 10 0f 01 04 80 a9 fe   @....€©þ
0130: 00 10 0f 01 04 80 1c 79   .....€.y
0138: 00 10 0f 01 04 80 49 9a   .....€Iš
0140: 00 10 0f 01 04 80 49 da   .....€IÚ
0148: 40 10 0f 01 04 80 1c 6c   @....€.l
0150: 00 10 0f 01 04 80 1c 5c   .....€.\
0158: 00 10 0f 01 04 80 b9 8e   .....€¹Ž
0160: 00 10 0f 01 04 80 d3 15   .....€Ó.
0168: 40 10 0f 01 04 80 a9 fe   @....€©þ
0170: 00 10 0f 01 04 80 1c 41   .....€.A
0178: 00 10 0f 01 04 80 49 9a   .....€Iš
0180: 00 10 0f 01 04 80 49 da   .....€IÚ
0188: 40 10 0f 01 04 80 1c 6c   @....€.l
0190: 00 10 0f 01 04 80 1c 5c   .....€.\
0198: 00 10 0f 01 04 80 b9 8e   .....€¹Ž
01a0: 00 10 0f 01 04 80 d3 15   .....€Ó.
01a8: 40 10 0f 01 04 80 a9 fe   @....€©þ
01b0: 00 10 0f 01 04 80 b4 34   .....€´4
01b8: 40 10 bd f9 ff ff b4 34   @.½ùÿÿ´4
01c0: 40 10 bd f9 ff ff c0 1c   @.½ùÿÿÀ.
01c8: 40 10 0f 01 04 80 c8 10   @....€È.
01d0: 40 10 0f 01 04 80 c1 1d   @....€Á.
01d8: 40 10 0f 01 04 80 48 16   @....€H.
01e0: 40 10 0f 01 04 80 1c 41   @....€.A
01e8: 00 10 0f 01 04 80 49 9a   .....€Iš
01f0: 00 10 0f 01 04 80 49 da   .....€IÚ
01f8: 40 10 0f 01 04 80 1c 6c   @....€.l
0200: 00 10 0f 01 04 80 1c 5c   .....€.\
0208: 00 10 0f 01 04 80 b9 8e   .....€¹Ž
0210: 00 10 0f 01 04 80 d3 15   .....€Ó.
0218: 40 10 0f 01 04 80 a9 fe   @....€©þ
0220: 00 10 0f 01 04 80 d2 55   .....€ÒU
0228: 60 20 0f 01 04 80 40 00   ` ...€@.
0230: 8f 66 0f 01 04 80         f...€  



Event Type:       Error
Event Source:       MSExchange Common
Event Category:       General
Event ID:       4999
Date:             7/1/2014
Time:             12:15:50 PM
User:             N/A
Computer:       
computername

Description:
Watson report about to be sent to dw20.exe for process id: 5236, with parameters: E12N, c-rtl-AMD64, 08.03.0348.001, store.exe, store.exe, 3b8c4b, c0000005, b5d1, 08.03.0348.001.  ErrorReportingEnabled: True

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.




Event Type:       Error
Event Source:       Microsoft Exchange Server
Event Category:       None
Event ID:       5000
Date:             7/1/2014
Time:             12:15:50 PM
User:             N/A
Computer:       
computername

Description:
EventType e12n, P1 c-rtl-amd64, P2 08.03.0348.001, P3 store.exe, P4 store.exe, P5 3b8c4b, P6 c0000005, P7 b5d1, P8 08.03.0348.001, P9 NIL, P10 NIL.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 65 00 31 00 32 00 6e 00   e.1.2.n.
0008: 2c 00 20 00 63 00 2d 00   ,. .c.-.
0010: 72 00 74 00 6c 00 2d 00   r.t.l.-.
0018: 61 00 6d 00 64 00 36 00   a.m.d.6.
0020: 34 00 2c 00 20 00 30 00   4.,. .0.
0028: 38 00 2e 00 30 00 33 00   8...0.3.
0030: 2e 00 30 00 33 00 34 00   ..0.3.4.
0038: 38 00 2e 00 30 00 30 00   8...0.0.
0040: 31 00 2c 00 20 00 73 00   1.,. .s.
0048: 74 00 6f 00 72 00 65 00   t.o.r.e.
0050: 2e 00 65 00 78 00 65 00   ..e.x.e.
0058: 2c 00 20 00 73 00 74 00   ,. .s.t.
0060: 6f 00 72 00 65 00 2e 00   o.r.e...
0068: 65 00 78 00 65 00 2c 00   e.x.e.,.
0070: 20 00 33 00 62 00 38 00    .3.b.8.
0078: 63 00 34 00 62 00 2c 00   c.4.b.,.
0080: 20 00 63 00 30 00 30 00    .c.0.0.
0088: 30 00 30 00 30 00 30 00   0.0.0.0.
0090: 35 00 2c 00 20 00 62 00   5.,. .b.
0098: 35 00 64 00 31 00 2c 00   5.d.1.,.
00a0: 20 00 30 00 38 00 2e 00    .0.8...
00a8: 30 00 33 00 2e 00 30 00   0.3...0.
00b0: 33 00 34 00 38 00 2e 00   3.4.8...
00b8: 30 00 30 00 31 00 2c 00   0.0.1.,.
00c0: 20 00 4e 00 49 00 4c 00    .N.I.L.
00c8: 20 00 4e 00 49 00 4c 00    .N.I.L.
00d0: 0d 00 0a 00               ....    





Event Type:       Error
Event Source:       Application Error
Event Category:       (100)
Event ID:       1000
Date:             7/1/2014
Time:             12:15:56 PM
User:             N/A
Computer:       
computername
Description:
Faulting application store.exe, version 8.3.348.1, faulting module store.exe, version 8.3.348.1, fault address 0x00000000003b8c4b.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 73 74 6f   ure  sto
0018: 72 65 2e 65 78 65 20 38   re.exe 8
0020: 2e 33 2e 33 34 38 2e 31   .3.348.1
0028: 20 69 6e 20 73 74 6f 72    in stor
0030: 65 2e 65 78 65 20 38 2e   e.exe 8.
0038: 33 2e 33 34 38 2e 31 20   3.348.1
0040: 61 74 20 6f 66 66 73 65   at offse
0048: 74 20 30 30 30 30 30 30   t 000000
0050: 30 30 30 30 33 62 38 63   00003b8c
0058: 34 62                     4b      




To resolve this issue

===============

researching on issue, suggests you install Latest update and since Windows Server is x64 bit so /4GB switch is also not an option to check. 


Found no Antivirus or any third party device except Storage driver and NIC driver


EXBPA is also not helping indicating towards any issues.


Increased the diagnostic logging on MsExchange Store to expert from EMC, alternatively you can also increased the diagnostic logging from Registry key or from EMS.


From Shell

Set-EventlogLevel "servername\MsExchange Store Driver" -Level Expert

I stopped all the Exchange related service on the server and restarted the Information store, It's not crashing so i have to find what could be causing the crash.

Since the only Exchange related service is running is "information store" so thought of starting Transport Service

Now, Started Transport service, MSExchange store Crashed, so changed the "Data" folder under Transport Roles, Location could be "Microsoft\Exchange server\Transport Roles\Data\Queue" so here i renamed the Data folder to "Old Data" and restart Transport service, no issues now, MsExchange Information Store is not crashing


Gradually started all the services and information store is not crashing.





Thursday, June 5, 2014

Exchange 2010 Log locations

SMTP Protocol Log location

Receive Log
C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive

Send Log
C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend

Tuesday, June 3, 2014

Telnet to Office 365



From command prompt
===========================================

telnet microsoft-com.mail.protection.outlook.com 25

ehlo yourdomain.com          "your Office domain address or domain.com"

mail from: youremail@yourdomain.com      your "Office365 Email address"

rcpt to: unknown@microsoft.com      "random microsoft address will work"

Please remember not to use Backspace in case if typed something wrong, hit enter and retype the whole command or wait till you received the output of the command.

Install Telnet on Windows 7

Previously, we are using the SERVERMANAGERCMD command to install 
Telnet on the client but on Windows 7 this command is deprecated 

SERVERMANAGERCMD -I TELNET-CLIENT

On Windows 7, Use this command from "Command Prompt"
pkgmgr /iu:”TelnetServer”


To install Telnet Server on Windows 7 and Windows Vista

  1. Click Start, and then click Control Panel.
  2. On the Control Panel Home page, click Programs.
  3. Under the section titled Programs and Features, click Turn Windows features on or off.
  4. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  5. In the Windows Features list, select Telnet Server, and then click OK.

Friday, May 23, 2014

How Outlook Connects to Exchange server

In Exchange 2000 and 2003, we had a basic front-end and back-end architecture, where the front-end servers accepted requests from clients and proxied them to the back-end servers for processing.  An Exchange 2000/2003 front-end server could proxy RPC over HTTP (now known as Outlook Anywhere), HTTPS (OWA, Entourage etc.), POP, and IMAP clients to the relevant back-end servers. The front-end servers also supported multiple referrals to public folder data on back-end servers.

In Exchange 2000/2003, internal Outlook MAPI clients did not use the front-end server at all; they connected directly to the back-end servers via MAPI over RPC. In fact, because the DSProxy component did not run on the front-end servers, you could not point Outlook MAPI clients to the NetBIOS name or FQDN of a front-end server.
With Exchange 2000/2003, the DSAccess component also accessed the Netlogon service on the domain controller and global catalog servers in Active Directory directly via Remote Procedure Calls (RPCs), and then Outlook clients connected directly to the DCs/GCs. Outlook 2000 and earlier connected to DSProxy.

from:http://www.msexchange.org/articles-tutorials/exchange-server-2007/planning-architecture/uncovering-new-rpc-client-access-service-exchange-2010-part1.html

Monday, May 19, 2014

Enable Tracing for Store

Enable Tracing for Store

1. Click Start -> Run and enter extra. Press Enter.
2. In the popped window, click "Select a task"
3. Click "Trace Control", click OK in the warning prompt
4. Write down the trace file name and location displayed in next page
5. Click "Set manual trace tags"
6. Choose *ALL* in "Trace Types", then in the "Components to Trace", select STORE
7. In "Trace Tags", make sure the followings are selected:

tagAccessDenied
tagAccessDeniedDetails
tagDeliverMail
tagDispatchRpcCalls
tagDispatchRpcReturns
tagError
tagPFDLocalDelivery
tagRpcIntfErrors

8. Click "Start Tracing"