Error while installing exchange2007 : Unable to initialize the Microsoft Exchange Information Store service. Failed to find the

Hi,
I am trying fresh install of exchange2007, everything gone well but, finally it thrown a error saying :
Unable to initialize the Microsoft Exchange Information Store service. Failed to find the working directory parameter from the registry - Error 0x80004005.
the installation log says
6/5/2007 3:14:05 PM] [1] Processing component 'Mailbox Service Control (Last)' (Starting mailbox services).
[6/5/2007 3:14:05 PM] [1] Executing 'start-SetupService -ServiceName MSExchangeIS -MaximumWaitTime "unlimited"', handleError = False
[6/5/2007 3:14:05 PM] [2] Launching sub-task '$error.Clear(); start-SetupService -ServiceName MSExchangeIS -MaximumWaitTime "unlimited"'.
[6/5/2007 3:14:05 PM] [2] Beginning processing.
[6/5/2007 3:14:05 PM] [2] The maximum wait for the operation is set to 'unlimited'.
[6/5/2007 3:14:05 PM] [2] Service checkpoint has progressed. Previous checkpoint='0' - Current checkpoint='1'.
[6/5/2007 3:14:05 PM] [2] Will wait '10000' milliseconds for the service 'MSExchangeIS' to reach status 'Running'.
[6/5/2007 3:14:15 PM] [2] Service 'MSExchangeIS' failed to reach status 'Running' on this server after waiting for '10000' milliseconds.
[6/5/2007 3:14:15 PM] [2] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [2] [ERROR] Unexpected Error
[6/5/2007 3:14:15 PM] [2] [ERROR] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [2] Ending processing.
[6/5/2007 3:14:15 PM] [1] The following 1 error(s) occurred during task execution:
[6/5/2007 3:14:15 PM] [1] 0.  ErrorRecord: Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceFailedToStartException: Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] [ERROR] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] Setup is halting task execution because of one or more errors in a critical task.
[6/5/2007 3:14:15 PM] [1] Finished executing component tasks.
[6/5/2007 3:14:15 PM] [1] Ending processing.
[6/5/2007 3:14:18 PM] [0] End of Setup
[6/5/2007 3:14:18 PM] [0] **********************************************
this I am trying on my test system please help me out in resolving the issue
thanks in advance,

Gary,
Open Registry Editor.
In Registry Editor, navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
Create the following value (REG_SZ): Working Directory and give it a value that points to the new database folder.
Make sure you back up the registry before you do any changes on it.
Raj

Similar Messages

  • Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96f.

    PLease help, I've rstored from backup three times with no success I'm getting the following error
    "Unable to initialize the Microsoft Exchange Information Store service.   - Error 0x96f. "
    It's LDap related but i have no idea why :-(
    Best Regards Bernhard

    IPv6 had been disabled for months on my SBS 2008 Server running Exchange 2007 SP1.  I ran 40 or so Windows Updates; subsequently, the next morning Exchange was no longer running; topology issues, event ID 2604, 2114 and 2601 were all over my Application
    Log.  After 12 hours of research I found this post; figured it was worth a shot and instantly all my services for Exchange fired up.  Thanks for the tip; I have no idea which update changed what in regards to needing IPv6 enabled, but that silly
    little check mark fixed it.  
    Thank you for sharing your solution! 
    Dan

  • Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed

    Each time I restart this exchange server, the Information Store and System Attendant don't start. If It try to manually start the services, I get the follow errors:
    Event ID 5003:
    Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed. This may be caused by a time change either in the client or the server machine, and may require a reboot of that machine. Other than that, verify that your domain is properly configured and is currently online.
    Event ID 1005:
    Unexpected error The clocks on the client and server machines are skewed. ID no: 80090324 Microsoft Exchange System Attendant  occurred.
    The clocks on the domain controllers and the exchange server are set to the same time zones. As well, all three clocks are in sync down to the second. Any ideas on what's causing this and how to fix it?

    Run this Command from the Exchange Server
    Net time \\ADServerName /Set
    and confirm the action,
    and then you need to restart the service
    Microsoft Exchange Active Directory Topology Service
    and confirm you are not getting the Error 4001 in the event Viewer.
    Thank you, it resolved my issue after being sweating looking for solution.
    How can I prevent this from happening? I cannot restart services on each server reboot nor lose 5 years of my life!!!
    Sokratis Laskaridis MCP, MCTS, MCITP, Small Business Specialist Netapp ASAP, Symantec STS

  • #550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error.

    Hi, 
    I created a mailbox few days before, everythign was working fine and suddenly when some one tried to send email on that mailbox it bounced back with following error:
    There's a problem with the recipient's mailbox. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
    Sent by Microsoft Exchange Server 2007 
    Diagnostic information for administrators:
    Generating server: Mail01.abc.com
    [email protected]
    #550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNotFound:16.18969:9A000000, 17.27161:00000000CC000000000000000600000000000000,
    255.23226:00000000, 255.27962:FE000000, 255.17082:0F010480, 0.26937:94000000, 4.21921:0F010480, 255.27962:FA000000, 255.1494:00000000, 255.26426:FE000000, 4.7588:0F010480, 4.6564:0F010480, 2.17597:00000000, 2.25805:00000000, 4.8936:0F010480, 4.14312:0F010480,
    4.2199:0F010480, 2.25805:00000000, 4.8936:0F010480, 2.22957:00000000, 2.19693:00000000, 2.17917:00000000, 2.27341:00000000, 4.8936:0F010480, 4.17097:0F010480, 4.8620:0F010480, 255.1750:0F010480, 0.26849:0F010480, 255.21817:0F010480, 0.26297:0F010480, 4.16585:0F010480,
    0.32441:0F010480, 4.1706:0F010480, 0.24761:0F010480, 4.20665:0F010480, 0.25785:EC030000, 4.29881:0F010480". ##
    Original message headers:
    Received: from Mailbox.abc.com ([fe80::892d:93d6:b1ac:b70a]) by mail01
     ([10.72.0.95]) with mapi; Fri, 11 Jan 2013 14:04:55 +0500
    Content-Type: application/ms-tnef; name="winmail.dat"
    Content-Transfer-Encoding: binary
    From: Anwar Amjad <[email protected]>
    To: All-HEC <[email protected]>
    Date: Fri, 11 Jan 2013 14:04:53 +0500
    Subject: FW: Suggestions & New Arrival in HEC Library
    Thread-Topic: Suggestions & New Arrival in HEC Library
    Thread-Index: Ac3vHgwR50OLs2BnQuOzo9jWg4e1gQAvJtUw
    Message-ID: <[email protected]>
    References: <[email protected]>
    In-Reply-To: <[email protected]>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator: <[email protected]>
    MIME-Version: 1.0
    X-Auto-Response-Suppress: DR, OOF, AutoReply
    After this error, i treid to send email again and there is no error and email was delivered. What was the cause of this error?
    Hasan

    Hi,
    I tried to start seeding again but it is at same status. I will try again and hopefully it will get resolved.
    But, yesterday i ran in to the most complex issue i have ever seen with Exchange.
    There was a unexpected power cut at our datacentre due to which both the nodes went down.
    After that both the nodes came up. But the all 3 databases were dismounted.
    Therefore, i ran Eseutil /mh resulting dirty shutdown.
    I was able to repair 2 databases.
    But the 3rd one was not mounting with below error.
    Microsoft Exchange Error
    Failed to mount database 'Mailbox Database'.
    Mailbox Database
    Failed
    Error:
    Exchange is unable to mount the database that you specified. Specified database: XXXXX\First Storage Group\Mailbox Database; Error code: MapiExceptionJetErrorAttachedDatabaseMismatch: Unable to mount database. (hr=0x80004005, ec=-1216).
    I was able to mount database somehow. There are 7 User mailboxes (Tier 1) on this database.
    All emails sent to the users in this database are bouncing back with the below error.
    This storage groups holds the mailboxes of my Senior Managements. And their mailboxes are down for almost 20 Hrs. I am spinning my head since yesterday but not able to find any fix. Can you please guide me in this concern.
    Best Regards
    K2
    Kapil Kashyap

  • RPC request to the Microsoft Exchange Information Store service for log truncation

    Hello all
    Running Exchange 2013 CU3 on Windows 2008R2 sp1 in a two node DAG. We are seeing the bellow warning when running a backup. How to resolve this?
    RPC request to the Microsoft Exchange Information Store service for log truncation failed for database CoramB3\Servername. Error: Failed to notify source server 'servername.coram.com' about the local truncation point. Hresult: 0xc8000713. Error: Unable to find
    the file. Also log files are not being flushed
    Bulls on Parade

    Hello,
    Please verify backup software.
    Please use vssadmin list writers command to check the status of the VSS admin. If it is in a
    failed state, please restart the Exchange replication service and then check the status again.
    Please use Get-MailboxDatabaseCopyStatus cmdlet to view health and status information about mailbox database copies.
    Please use Get-DatabaseAvailabilityGroupNetwork “DAG Name” | fl cmdlet to view configuration and state information for a DAG network.
    Please use Get-DatabaseAvailabilityGroupNetwork DAG Name\MAPINetwork | fl cmdlet and Get-DatabaseAvailabilityGroupNetwork DAG Name\ReplicationNetwork | fl cmdlet to
    check configuration information for MAPI network and Replication Network.
    If the above configuration information is ok, please check if there are other related errors in application log.
    Cara Chen
    TechNet Community Support

  • The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. Event 1121

    Hello all,
    We migrated our Exchange server from 2003 to 2010. After the mailbox move requests were finished we had one that was stuck. We basically skipped it as we had a lot of other things to finish over the weekend. Here we are a year later, the old exchange server
    is gone and so is an old DC. I am receiving an error every four minutes in event viewer.
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
    Request GUID: '3e46b7cb-2ac0-42c1-98e8-57517a19ee40' 
    Database GUID: '5c6c573b-4f45-4ce3-b296-11cf69c2e2b6'
    Error: Unable to find 'OLD Domain Controller' computer information in domain controller 'OLD Domain Controller' to perform the suitability check. Verify the fully qualified domain name..
    I have checked in EMC for move requests. None are listed. I have checked the DCs listed in EMC properties. Old DC is not listed.
    I also ran these commands in shell to attempt to cancel the stuck request.
    Get-MoveRequest -MoveStatus Completed;Pending;InProgress;Failed;CompletedWithWarning;Suspended;Queued;CompletionWithProgress : Remove-MoveRequest
    NO changes. Still throwing error. Any suggestions? I also tried using the guid and shell to look at the move request. Systems replies no such request.

    Hello,
    Please try to restart iis services to check the result.
    If the issue persists, I recommend you ping you DC server on your exchange server to check if your exchange server can communicate with your DC server.
    If there are other DCs, please try to use set-adserversettings cmdlet to specify a DC for your exchange server.
    Set-AdServerSettings
    http://technet.microsoft.com/en-us/library/dd298063(v=exchg.150).aspx
    Besides, please install the lasted rollup to check the result.
    Cara Chen
    TechNet Community Support

  • The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. : Error: An Active Directory Constraint Violation error occurred

    Hello,
    We have a multi domain parent child AD domain infrastructure and now we upgraded our exchange from Exchange 2007 to Exchange 2013. Since last few days, we see the below error on the mailbox server event viewer.
    EVENT ID : 1121
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. 
    Request GUID: '93a7d1ca-68a1-4cd9-9edb-a4ce2f7bb4cd' 
    Database GUID: '83d028ec-439d-4904-a0e4-1d3bc0f58809' 
    Error: An Active Directory Constraint Violation error occurred on <domain controller FQDN>. Additional information: The name reference is invalid. 
    This may be caused by replication latency between Active Directory domain controllers. 
    Active directory response: 000020B5: AtrErr: DSID-0315286E, #1:
    Our Exchange setup is in parent domain, but we keep on getting this error for various domain controllers in each child domain in the same site. We then configured one of the parent domain domain controller on Exchange. Still we are getting this error for
    the configured parent domain DC.
    Verified the AD replication and there is no latency or pending stuffs.
    Any support  to resolve this issue will be highly appreciated. Thank you in advance.
    Regards,
    Jnana R Dash

    Hi,
    In addition to Ed's suggestion, I would like to clarify the following things for troubleshooting:
    1. Please restart IIS at first.
    2. If the issue persists, please ping your DC on your Exchange server to check if Exchange can communicate with DC.
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error

    Since demoting a child domain a few days ago, Exchange 2013 is still trying to contact it and as a result generating errors in the application event logs.  I had a similar problem which I solved by removing some old migration batches, now I have a problem
    with the Microsoft Exchange Mailbox Replication service.
    The event logged is:
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
    Request GUID: '0b6c0f5a-0563-48e2-8b97-e0781c6cc69a' 
    Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
    Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for
    domain 'admin.riddlesdown.local'.. --> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or
    configured incorrectly DNS server.
    The domain doesn't exist in AD Sites and Services, I have removed all traces from DNS but this is still occurring.  When I run Get-ADServerSettings | fl it reports no trace of the domain or a DC that was previously in it.
    How can I stop these events occurring and is it likely to be causing something else not to work correctly.
    We are running Exchange 2013 CU1

    No, that didn't work.  Here are more details:
    Source: MSExchange ADAccess (EventID: 2130)
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or configured
    incorrectly DNS server.
    Source: MSExchange ADAccess (EventID: 2119)
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Error DNS_ERROR_RCODE_NAME_ERROR (0x8007232B) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin.riddlesdown.local
     The query was for the SRV record for _ldap._tcp.dc._msdcs.admin.riddlesdown.local
     Common causes of this error include the following:
     - The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller
    at set intervals. This computer is configured to use DNS servers with following IP addresses:
    10.59.100.7
    10.59.100.8
    fec0:0:0:ffff::1Microsoft.Exchange.Directory.TopologyService.exe
    fec0:0:0:ffff::2Microsoft.Exchange.Directory.TopologyService.exe
    fec0:0:0:ffff::3Microsoft.Exchange.Directory.TopologyService.exe
     - One or more of the following zones do not include delegation to its child zone:
    admin.riddlesdown.local
    riddlesdown.local
    local
    . (the root zone)
    Source: MSExchange Mailbox Replication Service (EventID: 1121)
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
    Request GUID: '87f4b926-0621-43d3-afeb-fe475ee6d850' 
    Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
    Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
    --> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
    Something is cause the Exchange server to go looking for our old domain, but what and why?

  • PST Import to archive mailbox - Stays in queue until i restart the microsoft exchange mailbox replication service

    Good Day all,
    Stretched dag between site a and site b.  Cas array at each site.  Mailboxes primarily are located in site a unless there is a major outage then the dag flips to site b.  setup two archive databases, one in site A on a non replicated partition
    of the dag server and one in site B on a separate mailbox only server.
    All exchange servers are patched to the latest sp and rollup.
    site a has no issues at all, everything i import queues up and processes with no problems
    at site b two imports will process and then stop until i restart the microsoft exchange mailbox replication service on the cas server.  No errors no nothing just lots of move request sitting in the queue.
    considering i have an insane amount of psts to import there does anyone have any suggestions besides setting up a task to restart the imicrosoft exchange mailbox replication service every 15 minutes?
    thanks for your help in advance

    Yeah I know from my research when I was setting up the dag you were not a fan of the stretched DAG but it works for us really well and passed all fail over tests that we ran on it <knocking on wood>.
    Yes its running but it stops working after one session.  I have had success in raising the transfer count from 2 to 5 but I can't really go much higher without taking down the server.  the problem is when I am transferring someone with hundreds
    of PSTs I have to babysit it...which sucks..
    anyway, thanks for your help and have a great day :)

  • Restarting the MS Exchange Information Store

    Exchange 2013 SP1 with 2 member server DAG. We installed the 2nd member server product key and need to restart the information store. What is the proper way to restart the information store with a DAG?
    The dag member that needs to have the information store restarted is hosting a passive copy of the DB. From what I am reading, it looks like maintenance mode only needs to be set on the server hosting the active copy?

    Exchange 2013 SP1 with 2 member server DAG. We installed the 2nd member server product key and need to restart the information store. What is the proper way to restart the information store with a DAG?
    The dag member that needs to have the information store restarted is hosting a passive copy of the DB. From what I am reading, it looks like maintenance mode only needs to be set on the server hosting the active copy?
    If the databases are all passive, simply restart the IS service. It will take a few minutes for things to look healthy again with get-maiboxdatabasecopystatus and it will be good.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • I'm unable to load my Microsoft Exchange account.  Think I'm entering the wrong info for domain and user but haven't figured out the correct inputs...

    I think the problem is with my domain and user name information.  Does anyone have any suggestions...

    I know that when i tried to add a Live/Hotmail account I tried MS Ex but ended up having to forward my Live to my Gmail or just add an IMAP account.

  • Exchange 2010 Information Store Service not Starting ERROR 1003

    Error message when I try to manually start the service myself :
    Windows could not start the Microsoft Exchange Information Store on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service specific error code -1003.
    Please help me resolve this issue, I have been working on it for two solid days with no progress. 
    The Event Log Report : The Microsoft Exchange Information Store service terminated with service-specific error %%-1003.
    System
    Provider
    [ Name]
    Service Control Manager
    [ Guid]
    {555908d1-a6d7-4695-8e1e-26931d2012f4}
    [ EventSourceName]
    Service Control Manager
    EventID
    7024
    [ Qualifiers]
    49152
    Version
    0
    Level
    2
    Task
    0
    Opcode
    0
    Keywords
    0x8080000000000000
    TimeCreated
    [ SystemTime]
    2013-12-10T09:43:09.741080700Z
    EventRecordID
    680929
    Correlation
    Execution
    [ ProcessID]
    548
    [ ThreadID]
    10672
    Channel
    System
    Computer
    SBS2011.******.local
    Security
    EventData
    param1
    Microsoft Exchange Information Store
    param2
    %%-1003
    Error 0xfffffc15 starting the Microsoft Exchange Information Store. 
    Failed to set Default Jet params.

    The server seemed to have restarted on the weekend and the monday I was alerted of the problem. 
    Yes I did have a anti-virus program running on the server and I have removed the AV Kaspersky Endpoint 8 and the Security Centre but I cannot remove the Mail Server but I think I have turned it off. 
    EDIT: 
    Sorry and yes all the other services seem to start fine.
    Originally discovered the issue when users could not open Outlook then I discovered the Database was un-mounted and the service was not starting. 
    only other event I can find :
    The Microsoft Exchange Information Store service terminated with service-specific error %%-1003.
    System
    Provider
    [ Name]
    Service Control Manager
    [ Guid]
    {555908d1-a6d7-4695-8e1e-26931d2012f4}
    [ EventSourceName]
    Service Control Manager
    EventID
    7024
    [ Qualifiers]
    49152
    Version
    0
    Level
    2
    Task
    0
    Opcode
    0
    Keywords
    0x8080000000000000
    TimeCreated
    [ SystemTime]
    2013-12-10T10:45:38.168386900Z
    EventRecordID
    682044
    Correlation
    Execution
    [ ProcessID]
    548
    [ ThreadID]
    12532
    Channel
    System
    Computer
    SBS2011.xxxxx.local
    Security
    EventData
    param1
    Microsoft Exchange Information Store
    param2
    %%-1003

  • Error while installing OEM Grid Control

    I am getting error while installing OEM Grid control (with existing database) at OMS Configuration. So, I cancelled the installation and deleted all databases and started the instal again. I am still getting an error at OMS configuration.
    I am trying to read through the threads here to see if anyone has solved it. I see a lot of threads on this topic but not sure how you guys resolved it.
    Can anyone help here.
    In the oracle installer, I see the message : The c:\oraclehomes\agent10g\cfgtoollogs\configToolfailedCommands" script contains all commans that failed, were skipped or cancelled ....
    --in this file, all I see is:
    rem Copyright (C)1999, 2006 Oracle
    oracle.sysman.emcp.agent.AgentPlugIn
    How should I proceed
    Thanks
    Ramya
    Edited by: Ramya Reddy on Mar 9, 2009 5:25 PM

    go to AOh\bin and run agentca -f and check agent status

  • Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database 1006.

    HI all,
    I ran into a problem with one of the servers in my DAG.  Due to a backup failure, the log partition filled up and the Exchange database went offline on this particular server.  The DAG continued to function on the other server.  So this particular
    DB01 had only some test accounts in it so I removed the database copy.  Unfortunately the removal must not have completed correctly. 
    After recovering the needed space in the partition, I tried to recopy the database and it failed.  So I deleted the entire database from the active server and it successfully removed it from the active server.  Now on both the servers the database
    is not showing, however I'm receiving the error below which indicates to me that the service still thinks the database exists.  I am also getting event 4113 Database redundancy health check failed for the database copy as it shows there is only one copy
    of the database (failed redundancy) but there should be zero copies.
    This database no longer exists in AD as I have verified this with ADSI so it must have something on the exchange server that is still telling the service the database exists. 
    Can you point me to the location to clean this up?
    Log Name:      Application
    Source:        MSExchange Mailbox Replication
    Date:          02/25/2011 2:00:07 PM
    Event ID:      1006
    Task Category: Service
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      email1.domain.com
    Description:
    The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
    Database: DB01
    Error: MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=243]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=200][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x3EB    
        Lid: 26937 
        Lid: 21921   StoreEc: 0x3EB    
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 22086 
        Lid: 27206 
        Lid: 17990 
        Lid: 16966   StoreEc: 0x8004010F
        Lid: 31433   StoreEc: 0x8004010F
        Lid: 8620    StoreEc: 0x3EB    
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849 
        Lid: 21817   ROP Failure: 0x3EB    
        Lid: 26297 
        Lid: 16585   StoreEc: 0x3EB    
        Lid: 32441 
        Lid: 1706    StoreEc: 0x3EB    
        Lid: 24761 
        Lid: 20665   StoreEc: 0x3EB    
        Lid: 25785 
        Lid: 29881   StoreEc: 0x3EB    
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange Mailbox Replication" />
        <EventID Qualifiers="32772">1006</EventID>
        <Level>3</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-02-25T22:00:07.000000000Z" />
        <EventRecordID>181576</EventRecordID>
        <Channel>Application</Channel>
        <Computer>email1.domain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>DB01</Data>
        <Data>MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=243]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=200][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x3EB    
        Lid: 26937 
        Lid: 21921   StoreEc: 0x3EB    
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 22086 
        Lid: 27206 
        Lid: 17990 
        Lid: 16966   StoreEc: 0x8004010F
        Lid: 31433   StoreEc: 0x8004010F
        Lid: 8620    StoreEc: 0x3EB    
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849 
        Lid: 21817   ROP Failure: 0x3EB    
        Lid: 26297 
        Lid: 16585   StoreEc: 0x3EB    
        Lid: 32441 
        Lid: 1706    StoreEc: 0x3EB    
        Lid: 24761 
        Lid: 20665   StoreEc: 0x3EB    
        Lid: 25785 
        Lid: 29881   StoreEc: 0x3EB     </Data>
      </EventData>
    </Event>

    Hi
    This error occurs because the MailboxReplicationService (MRS) currently caches Mailbox Database information past the lifetime of some databases. 
    Restarting the service will clear the cache.
    Maybe it is the simplest way to solve it.
    If it doesn’t work, you can try cmd to check it.
    Get-MailboxDatabase : Can you find the database which you delete?
    Remove-MailboxDatabase -Identity "MyDatabase": You can try to delete database if you can see the database.

  • Error while installing the named instance SQL 2012 Sp1

    Hi,
    I am getting below error while installing the named instance with features Data base engine. on same server box 2 named instance already installed and working...please suggest. i have done a lot of troubleshooting..(configure local system for Db engines
    during installation, tried to install after another domain ID., repair and uninstalled existing and retried.) .. please s if i need to do anything else to resolve the issue.. installation account is domain admin account...
    Can i rename the installation domain account profile from sql server that used for 2 named instance and for 3 rd named instance i am trying... is any impact after profile rename from the local sql server on any instance already configured...
    Shailendra Dev

    thanks alberto.
    here is 
    2015-03-24 19:48:49.42 Server      Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) 
    Oct 19 2012 13:38:57 
    Copyright (c) Microsoft Corporation
    Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
    2015-03-24 19:48:49.42 Server      (c) Microsoft Corporation.
    2015-03-24 19:48:49.42 Server      All rights reserved.
    2015-03-24 19:48:49.42 Server      Server process ID is 3460.
    2015-03-24 19:48:49.42 Server      System Manufacturer: 'Xen', System Model: 'HVM domU'.
    2015-03-24 19:48:49.42 Server      Authentication mode is WINDOWS-ONLY.
    2015-03-24 19:48:49.42 Server      Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG'.
    2015-03-24 19:48:49.42 Server      The service account is 'AIRWORKS\scadmin'. This is an informational message; no user action is required.
    2015-03-24 19:48:49.42 Server      Registry startup parameters: 
    -d D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\master.mdf
    -e D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG
    -l D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\mastlog.ldf
    2015-03-24 19:48:49.42 Server      Command Line Startup Parameters:
    -s "SCSMDB"
    -m "SqlSetup"
    -T 4022
    -T 4010
    -T 1905
    -T 3701
    -T 8015
    2015-03-24 19:48:49.69 Server      SQL Server detected 1 sockets with 1 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2015-03-24 19:48:49.69 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2015-03-24 19:48:49.69 Server      Detected 15624 MB of RAM. This is an informational message; no user action is required.
    2015-03-24 19:48:49.69 Server      Using conventional memory in the memory manager.
    2015-03-24 19:48:49.98 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2015-03-24 19:48:50.01 Server      This instance of SQL Server last reported using a process ID of 5124 at 3/24/2015 7:48:48 PM (local) 3/24/2015 2:18:48 PM (UTC). This is an informational message only; no user action is required.
    2015-03-24 19:48:50.03 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2015-03-24 19:48:50.07 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2015-03-24 19:48:50.30 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2015-03-24 19:48:50.58 spid5s      Warning ******************
    2015-03-24 19:48:50.65 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2015-03-24 19:48:50.66 spid5s      Starting up database 'master'.
    2015-03-24 19:48:50.90 spid5s      9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:51.04 Server      CLR version v4.0.30319 loaded.
    2015-03-24 19:48:51.17 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:51.17 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2015-03-24 19:48:51.39 Server      Software Usage Metrics is enabled.
    2015-03-24 19:48:51.81 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2015-03-24 19:48:51.83 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2015-03-24 19:48:51.86 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2015-03-24 19:48:52.02 spid5s      SQL Trace ID 1 was started by login "sa".
    2015-03-24 19:48:52.16 spid5s      Server name is 'AWISCDB\SCSMDB'. This is an informational message only. No user action is required.
    2015-03-24 19:48:52.35 spid12s     The certificate [Cert Hash(sha1) "151C8B90A9A8AF12F5EFAE3439F691E2C01A7355"] was successfully loaded for encryption.
    2015-03-24 19:48:52.35 spid12s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SCSMDB ].
    2015-03-24 19:48:52.40 spid12s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806.
    This is an informational message only. No user action is required.
    2015-03-24 19:48:52.43 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: 0x490, state: 16. Failure to register a SPN might cause integrated
    authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
    2015-03-24 19:48:52.45 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational
    message. No user action is required.
    2015-03-24 19:48:54.03 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service. 
    2015-03-24 19:48:54.03 spid14s     A new instance of the full-text filter daemon host process has been successfully started.
    2015-03-24 19:48:54.86 spid6s      Starting up database 'mssqlsystemresource'.
    2015-03-24 19:48:54.86 spid5s      Starting up database 'msdb'.
    2015-03-24 19:48:54.87 spid6s      The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
    2015-03-24 19:48:55.21 spid5s      12 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:55.32 spid5s      0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:55.32 spid6s      Starting up database 'model'.
    2015-03-24 19:48:55.32 spid5s      Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
    2015-03-24 19:48:55.72 spid6s      Clearing tempdb database.
    2015-03-24 19:48:57.22 spid6s      Starting up database 'tempdb'.
    2015-03-24 19:48:59.04 spid5s      Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 184551476 to level 184552376.
    2015-03-24 19:48:59.04 spid5s      ----------------------------------
    2015-03-24 19:48:59.04 spid5s      Starting execution of PRE_MSDB.SQL
    2015-03-24 19:48:59.04 spid5s      ----------------------------------
    2015-03-24 19:49:00.23 spid5s      Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
    2015-03-24 19:49:00.57 spid5s      -----------------------------------------
    2015-03-24 19:49:00.57 spid5s      Starting execution of PRE_SQLAGENT100.SQL
    2015-03-24 19:49:00.57 spid5s      -----------------------------------------
    2015-03-24 19:49:00.61 spid5s      Setting database option COMPATIBILITY_LEVEL to 110 for database 'msdb'.
    2015-03-24 19:49:00.73 spid5s      Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:00.73 spid5s      Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:01.78 spid5s      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    2015-03-24 19:49:01.79 spid5s      Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    2015-03-24 19:49:01.80 spid5s      DBCC TRACEOFF 1717, server process ID (SPID) 5. This is an informational message only; no user action is required.
    2015-03-24 19:49:01.80 spid5s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.
    2015-03-24 19:49:01.81 spid5s       
    2015-03-24 19:49:01.81 spid5s      Creating table temp_sysjobschedules
    2015-03-24 19:49:01.91 spid5s       
    2015-03-24 19:49:01.91 spid5s      Alter table sysdownloadlist...
    2015-03-24 19:49:01.92 spid5s       
    2015-03-24 19:49:01.92 spid5s      Alter table sysjobhistory...
    2015-03-24 19:49:01.92 spid5s       
    2015-03-24 19:49:01.92 spid5s      Alter table systargetservers...
    2015-03-24 19:49:01.92 spid5s       
    2015-03-24 19:49:01.92 spid5s      Alter table sysjobsteps...
    2015-03-24 19:49:01.99 spid5s      Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:01.99 spid5s      Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:01.99 spid5s       
    2015-03-24 19:49:01.99 spid5s      -----------------------------------------
    2015-03-24 19:49:01.99 spid5s      Execution of PRE_SQLAGENT100.SQL complete
    2015-03-24 19:49:01.99 spid5s      -----------------------------------------
    2015-03-24 19:49:02.01 spid5s      DMF pre-upgrade steps...
    2015-03-24 19:49:02.13 spid5s      DC pre-upgrade steps...
    2015-03-24 19:49:02.13 spid5s      Check if Data collector config table exists...
    2015-03-24 19:49:02.13 spid5s      Data Collector state before upgrade: 0
    2015-03-24 19:49:02.13 spid5s      pre_dc100::Check if syscollector_collection_sets_internal table exists...
    2015-03-24 19:49:02.13 spid5s      pre_dc100::Capturing Collection set status in temp table...
    2015-03-24 19:49:02.19 spid5s      Deleting cached auto-generated T-SQL Data Collection packages from msdb...
    2015-03-24 19:49:02.19 spid5s      End of DC pre-upgrade steps.
    2015-03-24 19:49:02.19 spid5s      DAC pre-upgrade steps...
    2015-03-24 19:49:02.19 spid5s      Starting DAC pre-upgrade steps ...
    2015-03-24 19:49:02.19 spid5s      End of DAC pre-upgrade steps.
    2015-03-24 19:49:02.19 spid5s      ----------------------------------
    2015-03-24 19:49:02.19 spid5s      Starting execution of MSDB.SQL
    2015-03-24 19:49:02.19 spid5s      ----------------------------------
    2015-03-24 19:49:02.23 spid5s      Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:02.23 spid5s      Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:02.27 spid5s      Checking the size of MSDB...
    2015-03-24 19:49:02.53 spid5s       
    2015-03-24 19:49:02.53 spid5s      Setting database option TRUSTWORTHY to ON for database 'msdb'.
    2015-03-24 19:49:02.53 spid5s      Setting database option RECOVERY to SIMPLE for database 'msdb'.
    2015-03-24 19:49:02.64 spid5s      ----------------------------------
    2015-03-24 19:49:02.64 spid5s      Finished execution of MSDB.SQL
    2015-03-24 19:49:02.64 spid5s      ----------------------------------
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      Starting execution of MSDB_VERSIONING.SQL
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      Finished execution of MSDB_VERSIONING.SQL
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      Dropping view MSdatatype_mappings...
    2015-03-24 19:49:02.65 spid5s      Dropping view sysdatatypemappings...
    2015-03-24 19:49:02.65 spid5s      Dropping table MSdbms_datatype_mapping...
    2015-03-24 19:49:02.66 spid5s      Dropping table MSdbms_map...
    2015-03-24 19:49:02.67 spid5s      Dropping table MSdbms_datatype...
    2015-03-24 19:49:02.67 spid5s      Dropping table MSdbms...
    2015-03-24 19:49:02.73 spid5s      Creating table MSdbms
    2015-03-24 19:49:02.75 spid5s      Creating table MSdbms_datatype
    2015-03-24 19:49:03.01 spid5s      Creating table MSdbms_map
    2015-03-24 19:49:03.02 spid5s      Creating table MSdbms_datatype_mapping
    2015-03-24 19:49:03.03 spid5s      Definining default datatype mappings
    2015-03-24 19:49:03.04 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE8
    2015-03-24 19:49:03.21 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE9
    2015-03-24 19:49:03.29 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE10
    2015-03-24 19:49:03.37 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE11
    2015-03-24 19:49:03.46 spid5s      Creating datatype mappings for MSSQLSERVER to DB2
    2015-03-24 19:49:03.54 spid5s      Creating datatype mappings for MSSQLSERVER to SYBASE
    2015-03-24 19:49:03.62 spid5s      Creating datatype mappings for ORACLE8 to MSSQLSERVER
    2015-03-24 19:49:03.71 spid5s      Creating datatype mappings for ORACLE9 to MSSQLSERVER
    2015-03-24 19:49:03.83 spid5s      Creating datatype mappings for ORACLE10 to MSSQLServer
    2015-03-24 19:49:03.95 spid5s      Creating datatype mappings for ORACLE11 to MSSQLServer
    2015-03-24 19:49:04.08 spid5s      Creating view MSdatatype_mappings
    2015-03-24 19:49:04.08 spid5s      Creating view sysdatatypemappings
    2015-03-24 19:49:05.08 spid5s       
    2015-03-24 19:49:05.08 spid5s      Creating table syssubsystems...
    2015-03-24 19:49:05.09 spid5s       
    2015-03-24 19:49:05.09 spid5s      Creating view sysproxyloginsubsystem_view...
    2015-03-24 19:49:05.11 spid5s       
    2015-03-24 19:49:05.11 spid5s      Creating trigger trig_sysoriginatingservers_delete...
    2015-03-24 19:49:05.11 spid5s       
    2015-03-24 19:49:05.11 spid5s      Creating view sysoriginatingservers_view...
    2015-03-24 19:49:05.12 spid5s       
    2015-03-24 19:49:05.12 spid5s      Creating trigger trig_sysjobs_insert_update...
    2015-03-24 19:49:05.13 spid5s       
    2015-03-24 19:49:05.13 spid5s      Creating view sysjobs_view...
    2015-03-24 19:49:05.15 spid5s       
    2015-03-24 19:49:05.15 spid5s      Creating trigger trig_sysschedules_insert_update...
    2015-03-24 19:49:05.16 spid5s       
    2015-03-24 19:49:05.16 spid5s      Creating view sysschedules_localserver_view...
    2015-03-24 19:49:05.21 spid5s       
    2015-03-24 19:49:05.21 spid5s      Creating view systargetservers_view...
    2015-03-24 19:49:05.23 spid5s       
    2015-03-24 19:49:05.23 spid5s      Creating view sysalerts_performance_counters_view...
    2015-03-24 19:49:05.25 spid5s       
    2015-03-24 19:49:05.25 spid5s      Creating function SQLAGENT_SUSER_SNAME ...
    2015-03-24 19:49:05.25 spid5s       
    2015-03-24 19:49:05.25 spid5s      Creating function SQLAGENT_SUSER_SID ...
    2015-03-24 19:49:05.26 spid5s       
    2015-03-24 19:49:05.26 spid5s      Creating procedure SP_SQLAGENT_IS_SRVROLEMEMBER...
    2015-03-24 19:49:05.27 spid5s       
    2015-03-24 19:49:05.27 spid5s      Creating procedure sp_verify_category_identifiers...
    2015-03-24 19:49:05.27 spid5s       
    2015-03-24 19:49:05.27 spid5s      Creating function agent_datetime...
    2015-03-24 19:49:05.27 spid5s       
    2015-03-24 19:49:05.27 spid5s      Creating procedure sp_verify_proxy_identifiers...
    2015-03-24 19:49:05.28 spid5s       
    2015-03-24 19:49:05.28 spid5s      Creating procedure sp_verify_credential_identifiers...
    2015-03-24 19:49:05.29 spid5s       
    2015-03-24 19:49:05.29 spid5s      Creating procedure sp_verify_subsystems...
    2015-03-24 19:49:05.30 spid5s       
    2015-03-24 19:49:05.30 spid5s      Creating procedure sp_verify_subsystem_identifiers...
    2015-03-24 19:49:05.30 spid5s       
    2015-03-24 19:49:05.30 spid5s      Creating procedure sp_verify_login_identifiers...
    2015-03-24 19:49:05.31 spid5s       
    2015-03-24 19:49:05.31 spid5s      Creating procedure sp_verify_proxy...
    2015-03-24 19:49:05.31 spid5s       
    2015-03-24 19:49:05.31 spid5s      Creating procedure sp_add_proxy...
    2015-03-24 19:49:05.32 spid5s       
    2015-03-24 19:49:05.32 spid5s      Creating procedure sp_delete_proxy...
    2015-03-24 19:49:05.32 spid5s       
    2015-03-24 19:49:05.32 spid5s      Creating procedure sp_update_proxy...
    2015-03-24 19:49:05.33 spid5s       
    2015-03-24 19:49:05.33 spid5s      Creating procedure sp_sqlagent_is_member...
    2015-03-24 19:49:05.33 spid5s       
    2015-03-24 19:49:05.33 spid5s      Creating procedure sp_verify_proxy_permissions...
    2015-03-24 19:49:05.34 spid5s       
    2015-03-24 19:49:05.34 spid5s      Creating procedure sp_help_proxy...
    2015-03-24 19:49:05.35 spid5s       
    2015-03-24 19:49:05.35 spid5s      Creating procedure sp_get_proxy_properties...
    2015-03-24 19:49:05.36 spid5s       
    2015-03-24 19:49:05.36 spid5s      Creating procedure sp_grant_proxy_to_subsystem...
    2015-03-24 19:49:05.36 spid5s       
    2015-03-24 19:49:05.36 spid5s      Creating procedure sp_grant_login_to_proxy...
    2015-03-24 19:49:05.37 spid5s       
    2015-03-24 19:49:05.37 spid5s      Creating procedure sp_revoke_login_from_proxy...
    2015-03-24 19:49:05.37 spid5s       
    2015-03-24 19:49:05.37 spid5s      Creating procedure sp_revoke_proxy_from_subsystem...
    2015-03-24 19:49:05.38 spid5s       
    2015-03-24 19:49:05.38 spid5s      Creating procedure sp_enum_proxy_for_subsystem...
    2015-03-24 19:49:05.38 spid5s       
    2015-03-24 19:49:05.38 spid5s      Creating procedure sp_enum_login_for_proxy...
    2015-03-24 19:49:05.39 spid5s       
    2015-03-24 19:49:05.39 spid5s      Creating procedure sp_reassign_proxy...
    2015-03-24 19:49:05.40 spid5s       
    2015-03-24 19:49:05.40 spid5s      Creating procedure sp_sqlagent_get_startup_info...
    2015-03-24 19:49:05.41 spid5s       
    2015-03-24 19:49:05.41 spid5s      Creating procedure sp_sqlagent_update_agent_xps...
    2015-03-24 19:49:05.42 spid5s       
    2015-03-24 19:49:05.42 spid5s      Creating procedure sp_sqlagent_has_server_access...
    2015-03-24 19:49:05.45 spid5s       
    2015-03-24 19:49:05.45 spid5s      Creating procedure sp_sqlagent_get_perf_counters...
    2015-03-24 19:49:05.46 spid5s       
    2015-03-24 19:49:05.46 spid5s      Creating procedure sp_sqlagent_notify...
    2015-03-24 19:49:05.47 spid5s       
    2015-03-24 19:49:05.47 spid5s      Creating procedure sp_is_sqlagent_starting...
    2015-03-24 19:49:05.47 spid5s       
    2015-03-24 19:49:05.47 spid5s      Creating procedure sp_verify_job_identifiers...
    2015-03-24 19:49:05.48 spid5s       
    2015-03-24 19:49:05.48 spid5s      Creating procedure sp_verify_schedule_identifiers...
    2015-03-24 19:49:05.49 spid5s       
    2015-03-24 19:49:05.49 spid5s      Creating procedure sp_verify_jobproc_caller...
    2015-03-24 19:49:05.50 spid5s       
    2015-03-24 19:49:05.50 spid5s      Creating procedure sp_downloaded_row_limiter...
    2015-03-24 19:49:05.51 spid5s       
    2015-03-24 19:49:05.51 spid5s      Creating procedure sp_post_msx_operation...
    2015-03-24 19:49:05.54 spid5s       
    2015-03-24 19:49:05.54 spid5s      Creating procedure sp_verify_performance_condition...
    2015-03-24 19:49:05.58 spid5s       
    2015-03-24 19:49:05.58 spid5s      Creating procedure sp_verify_job_date...
    2015-03-24 19:49:05.59 spid5s       
    2015-03-24 19:49:05.59 spid5s      Creating procedure sp_verify_job_time...
    2015-03-24 19:49:05.61 spid5s       
    2015-03-24 19:49:05.61 spid5s      Creating procedure sp_verify_alert...
    2015-03-24 19:49:05.62 spid5s       
    2015-03-24 19:49:05.62 spid5s      Creating procedure sp_update_alert...
    2015-03-24 19:49:05.63 spid5s       
    2015-03-24 19:49:05.63 spid5s      Creating procedure sp_delete_job_references...
    2015-03-24 19:49:05.65 spid5s       
    2015-03-24 19:49:05.65 spid5s      Creating procedure sp_delete_all_msx_jobs...
    2015-03-24 19:49:05.66 spid5s       
    2015-03-24 19:49:05.66 spid5s      Creating procedure sp_generate_target_server_job_assignment_sql...
    2015-03-24 19:49:05.66 spid5s       
    2015-03-24 19:49:05.66 spid5s      Creating procedure sp_generate_server_description...
    2015-03-24 19:49:05.67 spid5s       
    2015-03-24 19:49:05.67 spid5s      Creating procedure sp_msx_set_account...
    2015-03-24 19:49:05.68 spid5s       
    2015-03-24 19:49:05.68 spid5s      Creating procedure sp_msx_get_account...
    2015-03-24 19:49:05.69 spid5s       
    2015-03-24 19:49:05.69 spid5s      Creating procedure sp_delete_operator...
    2015-03-24 19:49:05.70 spid5s       
    2015-03-24 19:49:05.70 spid5s      Creating procedure sp_msx_defect...
    2015-03-24 19:49:05.71 spid5s       
    2015-03-24 19:49:05.71 spid5s      Creating procedure sp_msx_enlist...
    2015-03-24 19:49:05.72 spid5s       
    2015-03-24 19:49:05.72 spid5s      Creating procedure sp_delete_targetserver...
    2015-03-24 19:49:05.73 spid5s       
    2015-03-24 19:49:05.73 spid5s      Creating procedure sp_enlist_tsx
    2015-03-24 19:49:05.74 spid5s       
    2015-03-24 19:49:05.74 spid5s      Creating procedure sp_get_sqlagent_properties...
    2015-03-24 19:49:05.76 spid5s       
    2015-03-24 19:49:05.76 spid5s      Create procedure sp_set_sqlagent_properties...
    2015-03-24 19:49:05.76 spid5s       
    2015-03-24 19:49:05.76 spid5s      Creating procedure sp_add_targetservergroup...
    2015-03-24 19:49:05.77 spid5s       
    2015-03-24 19:49:05.77 spid5s      Creating procedure sp_update_targetservergroup...
    2015-03-24 19:49:05.78 spid5s       
    2015-03-24 19:49:05.78 spid5s      Creating procedure sp_delete_targetservergroup...
    2015-03-24 19:49:05.78 spid5s       
    2015-03-24 19:49:05.78 spid5s      Creating procedure sp_help_targetservergroup...
    2015-03-24 19:49:05.79 spid5s       
    2015-03-24 19:49:05.79 spid5s      Creating procedure sp_add_targetsvgrp_member...
    2015-03-24 19:49:05.80 spid5s       
    2015-03-24 19:49:05.80 spid5s      Creating procedure sp_delete_targetsvrgrp_member...
    2015-03-24 19:49:05.81 spid5s       
    2015-03-24 19:49:05.81 spid5s      Creating procedure sp_verify_category...
    2015-03-24 19:49:05.81 spid5s       
    2015-03-24 19:49:05.81 spid5s      Creating procedure sp_add_category...
    2015-03-24 19:49:05.82 spid5s       
    2015-03-24 19:49:05.82 spid5s      Creating procedure sp_update_category...
    2015-03-24 19:49:05.83 spid5s       
    2015-03-24 19:49:05.83 spid5s      Creating procedure sp_delete_category...
    2015-03-24 19:49:05.83 spid5s       
    2015-03-24 19:49:05.84 spid5s      Creating procedure sp_help_category...
    2015-03-24 19:49:05.84 spid5s       
    2015-03-24 19:49:05.84 spid5s      Creating procedure sp_help_targetserver...
    2015-03-24 19:49:05.85 spid5s       
    2015-03-24 19:49:05.85 spid5s      Creating procedure sp_resync_targetserver...
    2015-03-24 19:49:06.06 spid5s       
    2015-03-24 19:49:06.06 spid5s      Creating procedure sp_purge_jobhistory...
    2015-03-24 19:49:06.09 spid5s       
    2015-03-24 19:49:06.09 spid5s      Creating procedure sp_help_jobhistory...
    2015-03-24 19:49:06.10 spid5s       
    2015-03-24 19:49:06.10 spid5s      Creating procedure sp_add_jobserver...
    2015-03-24 19:49:06.11 spid5s       
    2015-03-24 19:49:06.11 spid5s      Creating procedure sp_delete_jobserver...
    2015-03-24 19:49:06.11 spid5s      Error: 10011, Severity: 16, State: 1.
    2015-03-24 19:49:06.11 spid5s      Access denied.
    2015-03-24 19:49:06.11 spid5s      Error: 917, Severity: 15, State: 1.
    2015-03-24 19:49:06.11 spid5s      An upgrade script batch failed to execute for database 'master' due to compilation error. Check the previous error message  for the line which caused compilation to fail.
    2015-03-24 19:49:06.11 spid5s      Error: 912, Severity: 21, State: 2.
    2015-03-24 19:49:06.11 spid5s      Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 917, state 1, severity 15. This is a serious error condition which might interfere with regular
    operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective
    actions and re-start the database so that the script upgrade steps run to completion.
    2015-03-24 19:49:06.11 spid5s      Error: 3417, Severity: 21, State: 3.
    2015-03-24 19:49:06.11 spid5s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books
    Online.
    2015-03-24 19:49:06.12 spid5s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2015-03-24 19:49:06.50 spid12s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service. 
    Shailendra Dev

Maybe you are looking for