Exchange Server 2013 SP1 - Optimize for Single Server Use

Hello,
i've set up Exchange 2013 SP1 with at last CU6 - get exchangeserver says:
AdminDisplayVersion             : Version 15.0 (Build 995.29)
ExchangeVersion                 : 0.1 (8.0.535.0)              - - - funny number ;-) (is this an early version???)
Yes, the annoying 16028 in the application log are running every five minutes, but thats not the main question.
Which services are needed in a SINGLE-SERVER Environment, without DAG and unified messaging?
Can the Self-Checking, Health- and Self-Probing be put down?
These services are started automatic:
   Microsoft Exchange Active Directory Topology
   Microsoft Exchange Anti-spam Update
   Microsoft Exchange DAG Management
   Microsoft Exchange Diagnostics
   Microsoft Exchange EdgeSync
   Microsoft Exchange Frontend Transport
   Microsoft Exchange Health Manager
   Microsoft Exchange Mailbox Assistants
   Microsoft Exchange Mailbox Replication
   Microsoft Exchange Mailbox Transport Delivery
   Microsoft Exchange Mailbox Transport Submission
   Microsoft Exchange Migration Workflow
   Microsoft Exchange Replication
   Microsoft Exchange RPC Client Access
   Microsoft Exchange Search
   Microsoft Exchange Search Host Controller
   Microsoft Exchange Service Host
   Microsoft Exchange Throttling
   Microsoft Exchange Transport
   Microsoft Exchange Transport Log Search
   Microsoft Exchange Unified Messaging
   Microsoft Exchange Unified Messaging Call Router
   Microsoft Exchange-Informationsspeicher
   Microsoft Filtering Management Service
   Microsoft Online Services Sign-in Assistant
And with C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue\mail.que about 512 MBytes size (which may may be a designed default size)...
Have set up about 6 users mailboxes, 3 public folder in a mailbox for public folders. Only for testing purposes sent some (small) mails, no external mails received (only testing receive with 'popcon' for mail delivery to the internal boxes).
The server (2012 R2) is running only in the internal network (yes, with internet connection for updates).
No virus scanners, not third party receive or send connectors, only the 5 default (3 Frontend, 2 Hub) receive Connectors and one Send Connector to our mail provider set up and no user activity (only sometimes from me for testing).
It seems like it's doing only with itself, logging file sizes of above 11 GB (in 4 weeks), with huge amounts of probing, health checking, internal testing, internal updating etc.
Can this logging be set up to a lower level, can services be deactivated (for single server configuration),
the logging volume should be in a useful relation to the mail use of the server, a message for every self test, internal health check etc. in the log-files normally isn't useful, only when problems occur there is a need...
Thanks in advance
Andreas

Between Exchange protocol-based log files, PerfMon .blg files used by Managed Availability, IIS logs, etc., the total footprint can add up quickly and these logs are not purged automatically.  You can take a look at this site below and use the powershell
script to clean it up.
http://www.c7solutions.com/2013/04/removing-old-exchange-2013-log-files-html

Similar Messages

  • Exchange Server 2013 SP1 Install on Windows Server 2012 R2

    I am trying to install Exchange 2013 SP1 onto a Windows Server 2012 R2. I get an error message that the operating system is not supported. I have installed all the prerequisite.

    Does that mean that you can't install Exchange 2013 Sp1 with a Remote Desktop Role together included with Server 2012 R2?
    Or is it possible to restore the Remote Desktop Role afterwards?
    You can't install any build of Exchange 2013 on any server that has the RDS Role installed. So in other words, this is not a "limitation" with Exchange 2013 SP1 and Windows Server 2012 R2.
    Additional Reading, check out: Exchange OWA/Activesync conflicting with RD Gateway
    role
    Martina Miskovic

  • What is the order for upgrading exchange server 2013 SP1 servers to CU7?

    Hi All 
    I am planning to upgrade my exchange server 2013 SP1CU4 to CU7 . As per my understanding , we always proceed with the CAS servers and then the Mailbox Servers during up-gradation.
    But I am confused now , since I have seen articles stating , that the Mailbox servers has to be upgraded first and then the CAS servers in exchange 2013. 
    What will be the correct order . My environment consists of 2 Mailbox servers in DAG and 2 CAS servers (Exchange server 2013 SP1)
    Thanks in Advance .
    Joyso Senior Messaging Admin

    Hi Joyso,
    The Microsoft recommendation regarding the order in which the Exchange 2013 server roles should be installed or Upgraded is Mailbox and then CAS.
    It makes sense as the CAS Role is a stateless server and all major components are held by the Mailbox Role.
    Until a 2013 mailbox server comes online, the CAS server is pretty much useless. Hence, the recommended installation order in 2013 is the reverse of 2010 – Mailbox role first & then CAS
    Note: If your DAG have more nodes, you need first upgrade all non-PAM nodes and then upgrade PAM node.
    Some References:
    The recommendation from the Product Group is to install Exchange 2013 Preview Mailbox Role first, and then the
    CAS role.
    If you're separating your server roles, we recommend installing the Mailbox server role first.
    Upgrade your Exchange 2013 server roles in the required order. First, upgrade Mailbox servers
    and then upgrade Client Access servers. -Upgrade DAG Mailbox servers
    Exchange 2013 Server Roles Installation Order – Mailbox First:
    Regards,
    Satyajit
    Please “Vote As Helpful”
    if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Messaging tracking logs filename format changed in Exchange Server 2013 sp1

    Hi,
    I have noticed that the file name format is changed for exchange server 2013 sp1.
    Now it will have hh attached to it like
    MSGTRKMSyyyymmddhh-n.log;
    MSGTRKMDyyyymmddhh-n.log:
    MSGTRKyyyymmddhh-n.log.
    So the "hh" will goes from 00 to 23 for single day.
    So Lets say at 24 april 2014 first fill is created @7.30 AM, so the first file name will be
    MSGTRK2014042400-1.log. Now exchange server will create new file every hour by incrementing hh part of file name. Now the last file i.e
    MSGTRK2014042423-1.log will be created on 25 April 2014 at 6.30 AM.
    I am not able to understand why exchange server is creating the file with old date on next day ( with 24 April on file name time stamp on 25 April).
    And also how it will be decided to create the first file @ 7.30 AM.
    Can anyone explain to me about this ? Why it is happening like this?
    Thanks
    Sandeep Gupta

    Hi Sandeep,
    This could related to the time difference. What’s the time zone of your server? In my lab, many files in the last day were created in the next day. For example, files in 20140410
    were created on 20140411.
    Also, as you mentioned, the file name format is as:
    MSGTRKMSyyyymmddhh-n.log;
    MSGTRKMDyyyymmddhh-n.log:
    MSGTRKyyyymmddhh-n.log.
    However as I know, the format is like
    MSGTRKyyyymmdd-m.log, it will not have “hh”(you mean hours) in the behind and the file is not created every hour but create a new file when the old is full. So please capture some screenshots of the message tracking files
    and the date/time information of the file to verify.
    Title: Message Tracking
    Link:
    http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx
    Regards, Eric Zou

  • SP1 files for Project Server 2013

    Hi,
    Where can we found the true SP1 files for SharePoint Server, Project Server and Project Pro 2013,
    after the withdraw of first SP1 ?
    Thanks

    Hello,
    SharePoint Server 2013:
    http://support.microsoft.com/kb/2880552
    Project Server 2013: http://support.microsoft.com/kb/2880553
    Project 2013: http://support.microsoft.com/kb/2817433
    Paul
    Paul Mather | Twitter |
    http://pwmather.wordpress.com | CPS

  • Strange Exchange name when connecting with Outlook 2013 to Exchange server 2013 SP1

    I've setup a test environment with Windows Server standard 2012 R2 and Exchange Server 2013 SP1...
    In- and outbound SMTP works fine, as well as connecting with OWA and Mac Outlook client...
    Oddly though when setting up an Outlook 2013 connection....it recognizes the email address correctly, but later on can't connect and shows a dialog to enter the server and email account manually....though the profiled fields show something like:
    Exchange Server: [email protected]
    Mailbox: =SMTP:[email protected]
    When I fill in the right fields....it won't connect and falls back to the values above...
    Something wrong in the Exchange setup?

    Hmm...found aguide here:
    http://enterpriseit.co/microsoft-exchange/2013/ssl-certificate-request/
    Though it doesn't mention anything that with the self-signed certs it won't allow Outlook 2013 to connect...
    So from my point of view Outlook 2013 should be able to connect anyway...as during the connect process you can install the self-signed cert.....so must be something else then...

  • Exchange Server 2013 SP1 - Internal Email Flow slowness

    Hi Fellows,
    I have a brand new implementation of Exchange Server 2013 SP1 with three mailbox servers and 3 CAS servers.
    I am facing a considerable slow transportation of email internally. although there are just 3 mailboxes on the infrastructure at the moment.
    When a user sends email to himself or other two accounts, delivery takes from 15 seconds to 35 seconds to be delivered.
    Experience is same even if the email is sent from OWA, ActiveSync or Outlook.
    Header analysis shows the message exchange between mailbox servers is taking time. any clue?
    Decreasing Tarpit interval on Mailbox server receive connectors will be helpful?
    Network communication, Storage performance, Server performance are all as good as we love to.
    Thanks.
    J.A

    Hello,
    When a user send message to a internal user in a AD site, the connector will not be used. I recommend you use message tracking to check the issue occur on server side or transport process. Please use queue viewer to check if there is mail traffic.
    Cara Chen
    TechNet Community Support

  • After installing Project Server 2013 (without updating SharePoint Server 2013 SP1))

    I am facing the problem while opening project web app. I configured the SharePoint 2013 and project server 2013. Here is the detail what I performed the steps:
    OS Server 2012 R2, SQL Server 2012, SharePoint server 2013 version
    15.0.4420.1017, Project Server 2013 version
    15.0.4454.1000. SharePoint configured and running successfully. After project web app site provisioning successfully completed. I got the below error.
    Microsoft.Office.Project.PWA.WebParts.PWAPart' from assembly 'Microsoft.Office.Project.Server.PWA, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' cannot reduce access.
    I run this psconfig -cmd upgrade -inplace b2b -wait -force. But still getting same error.
    Previous steps:
    Earlier I had also tried to install SharePoint Server 2013 SP1 "3823428". After the installation SP1 some of sharePoint site features suddenly stopped e.g: Cannot  browse "Service Applications -->
    Manage service applications"  option even after re-start the server. This was previous error after upgrading SP1
    "Method 'get_IsClientValid' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices,
    Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation"
    Anyone can help me!!! Thanks...
    Faisal Numan

    hello,
    For SP2013 and PS2013 to work properly on Windows Server 2012 R2 you need to use the SP1 install media for both, download SharePoint 2013 with SP1 and Project Server 2013 with SP1
    http://support.microsoft.com/kb/2891274
    http://blogs.technet.com/b/office_sustained_engineering/archive/2014/03/03/announcing-availability-of-slipstreamed-office-2013-and-sharepoint-server-2013-with-sp1.aspx
    http://blogs.technet.com/b/projectsupport/archive/2014/02/25/project-2013-and-project-server-2013-service-pack-1.aspx
    Paul
    Paul Mather | Twitter |
    http://pwmather.wordpress.com | CPS

  • How to check whether it is Exchnage Server 2013 SP1 or any other version of exchnage server 2013, with the help of registry.

    Hi,
    I need to check the Service Pack level of Exchange Server 2013, from Registry.
    I investgated for it, but the vale of product Minor version in Registry is same as of exchange server 2013 CU3 or any other exchange 2013.
    So, please let me know, what is the proper way to identify the SP level of exchnage server 2013.
    Thanks in advance..

    Use the powershell command
    Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion
    This will provides what version of exchange server 2013 are using..
    Refer the below article for more detail..
    http://technet.microsoft.com/en-us/library/hh135098%28v=exchg.150%29.aspx
    Exchange Queries

  • Project Server 2013 SP1 only

    Hi,
    Can Project Server be updated to SP1 and leave SharePoint without it? it seems there is some kind of trouble
    http://social.technet.microsoft.com/Forums/en-US/45b56c00-b894-445d-9e4b-c44b158f0531/after-project-server-2013-sp1-update-without-updating-sharepoint-server-2013?forum=projserv2010setup
    Thanks

    Hi,
    We need SharePoint Server SP1 installed first and then install Project Server SP1

  • I get one or the other error when i install SQL server 2012 SP1 in my Lab server

    I get multiple errors when i install SQL server 2012 SP1 In my lab server.
    Not sure why i keep getting different errors all the time when i install SQL server 2012 & 2012 SP1.
    Below are error codes, screen shots and also a log of the error.
    1.  Eror code 0X84B40000
    Also dint understand any thing from this article related to the above error 
    http://social.technet.microsoft.com/Forums/sqlserver/en-US/5b6cc928-0db8-4fe4-a5d3-21672225f0ca/i-get-error-code-0x84b40000-when-trying-to-install-sql-server-mgmt-studio-to-an-existing-sql?forum=sqlexpress
    2. Eror code 0x851A001A
    Can any one plz help as i always get one or the other error.
    ====================================
    Screen shot: 
    Please note the below screen shot has given the error code 0x851A001A which is same in case of failure of all the other features which have failed during this installation. Hence i have uploaded only one screen shot.
    2. Log file content.
    =================================
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893606
      Start time:                    2014-05-04 21:15:35
      End time:                      2014-05-04 21:51:45
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  SERVER1
      Machine processor count:       2
      OS version:                    Windows Server 2008 R2
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Database Engine Services                 1033      
              Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            SQL Server Replication                   1033      
              Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                
    Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Data Quality Services                    1033    
                Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSAS11.MSSQLSERVER             Analysis Services                        1033  
                  Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSRS11.MSSQLSERVER             Reporting Services - Native              1033        
            Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Management Tools - Basic  
                  1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Management Tools - Complete  
               1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools Connectivity  
                 1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools Backwards Compatibility
        1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools SDK      
                      1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Integration Services    
                    1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Reporting Services - SharePoint
                                                       11.0.2100.60    No        
    Package properties:
      Description:                   Microsoft SQL Server 2012 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         F:\x64\setup\
      Installation edition:          Enterprise
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 ms\sql
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                true
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SCOM
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SCOM
      INSTANCENAME:                  SCOM
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SCOM
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 ms\sql
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           MS\Gautam, MS\SCOM Users
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
    Detailed results:
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\SystemConfigurationCheck_Report.htm

    Sorry about the error in the path, but you find the files that's the main thing.
    Indeed it is a certificate problem:
    2014-05-04 21:47:43.56 spid12s Error: 17190, Severity: 16, State: 1.
    2014-05-04 21:47:43.56 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-05-04 21:47:43.56 spid12s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
    2014-05-04 21:47:43.57 spid12s Error: 17826, Severity: 18, State: 3.
    2014-05-04 21:47:43.57 spid12s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-05-04 21:47:43.57 spid12s Error: 17120, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    I've recall that I've tried to help people with this error before, but I'm sure they were able to sort it out.
    Anyway, this blog post,
    http://blogs.msdn.com/b/sqljourney/archive/2012/10/09/sql-2008-service-fails-to-come-online-with-a-valid-certificate-could-not-be-found-and-it-is-not-possible-to-create-a-self-signed-certificate.aspx
    suggests the issue is a corrupted user profile, and you should try to use a different service account.
    This blog also seems to have a simple solution, but I cannot vouch for that it will work:
    http://www.beejblog.com/2012/02/sql-server-solved-unable-to-initialize.html
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.

    I am trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
    It verifies the connection and then throws the error:
    The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
    WSUS Server : Windows Server 2012 R2
    Remote SQL Server: 2012 SP1 CU7 hosted on Windows Server 2012 R2
    Please let me know if anyone has experienced this issue.

    We were trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
    It verifies the connection and then throws the error:
    The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
    Same error even after rebooting the server multiple times.
    WSUS Server : Windows Server Standard2012 R2
    Remote SQL Server: Windows Server 2012 SP1 CU7 hosted on Windows Server 2012 R2
    Event ID 7000:
    The Windows Internal Database service failed to start due to the following error:
    The service did not start due to a logon failure.
    Event ID 7041
    The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
    Logon failure: the user has not been granted the requested logon type at this computer.
    Service: MSSQL$MICROSOFT##WID
    Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
    This service account does not have the required user right "Log on as a service."
    User Action
    Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user
    right is assigned to the Cluster service account on all nodes in the cluster.
    If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated
    with this node might be removing the right.
    I found following article:
    "MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
    http://support.microsoft.com/kb/2832204/en-us
    To work around the issue, use one of the following methods:
    Assign the Log on as a service user right to NT SERVICE\ALL SERVICES in the GPO that defines the user right.
    Exclude the computer from the GPO that defines the user right.
    We moved the SCCM server to OU where no policies were getting applied and then applied the new GPO to that OU. Restarted the server and we were able to install WSUS role.
    Regards
    PR

  • Biztalk Server 2013 does not support Windows Server 2012 R2

    is there any document or statement from MS that States "Biztalk Server 2013 does not support Windows Server 2012 R2"

    Hi Mohit,
    I haven't come across any document, but there is a blog from Microsoft about it.
    http://blogs.msdn.com/b/biztalknotes/archive/2013/10/29/biztalk-2013-compatibility-with-latest-platforms-of-microsoft.aspx
    Maheshkumar S Tiwari|User Page|Blog|BizTalk
    Server : How Map Works on Port Level

  • After i installed updates for my mac mini server, the web services for the server app wont start, it gives an error massage: "Error Reading Settings"

    After i installed updates for my mac mini server, the web services for the server app wont start, it gives an error massage: "Error Reading Settings"
    The system logs reads:
    Mar 29 22:06:25 server servermgrd[82]: servermgr_web:  Error Domain=XSServerFoundationErrorDomain Code=4 "Failed to read settings: Exception:
              undefined method `downcase' for nil:NilClass
              ." UserInfo=0x7fc547901080 {NSLocalizedDescription=Failed to read settings: Exception:
              undefined method `downcase' for nil:NilClass

    To check the local network for some of the common configuration problems, launch Terminal.app and issue the following diagnostic command:
    sudo changeip -checkhostname
    That'll report some local configuration information and then either no errors detected and no changes required, or it'll point to whatever configuration errors or issues it might detect.  That doesn't catch everything, but it catches the common errors.
    FWIW, 192.168.0.0/24 and 192.168.1.0/24 are poor choices for the local network, as VPNs are based on IP routing and IP routing gets tangled when the same subnet is used on both ends of the VPN. 192.168.0.0/24 and 192.168.1.0/24 are near ubiquitous in home networks and coffee shops.

  • How to uploade multiple flatfiles for single transaction using BDC?

    How to uploade multiple flatfiles for single transaction using BDC?

    Hi,
    You need to upload all data files into an internal table first either using OPEN DATASET (application server files) or GUI_UPLOAD (PC files).
    Then loop at the internal table and call BDC transaction to process the data.
    Regards,
    Ferry Lianto

Maybe you are looking for