Exchange 2013 /m:recoverserver constantly failing due to MSExchangeSubmission.exe

Hi all,
I am trying to recover my lab Exchange 2013 server after removing a component of IIS messed all IIS functions, including all virtual directories.
The server is running on Hyper-V so I have removed and rebuilt the OS disk whilst the Exchange data resides on a separate disk. I've reset the computer account in AD and then run the command:
setup /m:recoverserver /targetdir:"d:\Program Files\Microsoft Exchange\v15" /DoNotStartTransport /IAcceptExchangeServerLicenseTerms
I have now done this a number of times and on each occasion it fails when attempting to start the Microsoft Exchange Transport Submission service. The error in the event log is as follows:
Log Name:      Application
Source:        Application Error
Date:          30/03/2013 20:18:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HV-E2K13
Description:
Faulting application name: MSExchangeSubmission.exe, version: 15.0.516.29, time stamp: 0x506956b8
Faulting module name: Microsoft.Exchange.Net.ni.dll, version: 15.0.516.27, time stamp: 0x5064072e
Exception code: 0xc00000fd
Fault offset: 0x0000000000639d07
Faulting process id: 0x1cc8
Faulting application start time: 0x01ce2d83cbb5568e
Faulting application path: D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll
Report Id: 0a1e3a42-9977-11e2-93f1-00155d0a4b05
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-30T20:18:53.000000000Z" />
    <EventRecordID>112812</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HV-E2K13</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MSExchangeSubmission.exe</Data>
    <Data>15.0.516.29</Data>
    <Data>506956b8</Data>
    <Data>Microsoft.Exchange.Net.ni.dll</Data>
    <Data>15.0.516.27</Data>
    <Data>5064072e</Data>
    <Data>c00000fd</Data>
    <Data>0000000000639d07</Data>
    <Data>1cc8</Data>
    <Data>01ce2d83cbb5568e</Data>
    <Data>D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe</Data>
    <Data>C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll</Data>
    <Data>0a1e3a42-9977-11e2-93f1-00155d0a4b05</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
Any thoughts?
Paul

Hi,
Im dealing with the same errors when i'm trying to restore our productive mailbox from a disaster.
I've tried everything listed here but last Milind Naphade commentary.
I'm in that right now, i ll tell if it's working soon.
Ty!
Hi Again. It Failed to start MSExchangeSubmission.exe
Here is the event on eventvwr (Some details on spanish wich is the language of my server)
Nombre de la aplicación con errores: MSExchangeSubmission.exe, versión: 15.0.516.29, marca de tiempo: 0x506956b8
Nombre del módulo con errores: Microsoft.Exchange.Net.ni.dll, versión: 15.0.516.27, marca de tiempo: 0x5064072e
Código de excepción: 0xc00000fd
Desplazamiento de errores: 0x000000000062f697
Identificador del proceso con errores: 0x7d0
Hora de inicio de la aplicación con errores: 0x01cfac0a0bb16a68
Ruta de acceso de la aplicación con errores: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeSubmission.exe
Ruta de acceso del módulo con errores: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\b028905d8fd3faa99c9801b69b1500da\Microsoft.Exchange.Net.ni.dll
Identificador del informe: 4a9638fc-17fd-11e4-9404-000c29f101d8
Nombre completo del paquete con errores: 
Identificador de aplicación relativa del paquete con errores: 
ExchangeSetup.log   ends with:
[07/30/2014 15:19:10.0220] [1] The following 1 error(s) occurred during task execution:
[07/30/2014 15:19:10.0220] [1] 0.  ErrorRecord: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
[07/30/2014 15:19:10.0220] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
   en Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   en Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   en Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
   en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   en Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
   en Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[07/30/2014 15:19:10.0236] [1] [ERROR] The following error was generated when "$error.Clear(); 
start-SetupService -ServiceName MSExchangeSubmission
" was run: "El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.".
[07/30/2014 15:19:10.0236] [1] [ERROR] Service 'MSExchangeSubmission' failed to reach status 'Running' on this server.
[07/30/2014 15:19:10.0236] [1] [ERROR-REFERENCE] Id=MailboxServiceControlLast___23a36fed7b6947e0906f388b5a90135c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07/30/2014 15:19:10.0251] [1] Setup is stopping now because of one or more critical errors.
[07/30/2014 15:19:10.0251] [1] Finished executing component tasks.
[07/30/2014 15:19:10.0267] [1] Ending processing DisasterRecovery-MailboxRole
[07/30/2014 15:19:10.0282] [0] No se completó la operación de instalación de Exchange Server. Puede encontrar más detalles en ExchangeSetup.log ubicado en la <SystemDrive>: carpeta \ExchangeSetupLogs.
[07/30/2014 15:19:10.0282] [0] End of Setup
[07/30/2014 15:19:10.0282] [0] **********************************************
Any suggestion please??? idk what else can i do!

Similar Messages

  • Exchange 2013: Content Index State Failed

    I am running two, two node DAG's with Exchange 2013.
    One DAG pair is running 5 databases with Server 2012 Standard and the second DAG pair is running Server 2008 R2 SP1 Standard with a single shared database.
    No matter what I try, ALL 6 databases show "ContentIndexState: Failed" with "ContentIndexErrorMessage: An internal error occurred for the database or its index.".
    I have tried rebuilding the indexes manually, automatically and manually copying the database files between servers.  I also receive errors when trying to failover the databases because the content index state is failed.
    In my test environment I have a very similar setup working fine with no issues.
    Please let me know what I can try to get this resolved.
    The error I receive when running the following set of commands is:
    suspend-MailboxDatabaseCopy dag2db1\mbox1
    update-MailboxDatabaseCopy dag2db1\mbox1 -deleteexistingfiles
    [PS] C:\Windows\system32>update-mailboxdatabasecopy dag2db1\mbox1 -deleteexistingfiles
    Confirm
    Are you sure you want to perform this action?
    Updating database copy DAG2DB1\MBOX1 on server MBOX1
    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): a
    WARNING: Seeding of content index catalog for database 'DAG2DB1' failed. Please verify that the Microsoft Search (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: Therevwas no endpoint listening
    at net.tcp://localhost:17063/Management/SeedingAgent-0A2745DF-4522-42AB-9115-5DDE9EDEF1C612/Single that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details..
    [PS] C:\Windows\system32>

    Hi Folks,
    Here we go;
    "On
    August 14th, we announced the removal of the
    MS13-061 Security Update for Exchange Server 2013 due to an issue where the patch changed settings for the search infrastructure, placing the content index for all databases into a failed state.  As of today, we have released updated security updates
    for both Exchange 2013 RTM CU1 and Exchange 2013 RTM CU2."
    Details below;
    http://blogs.technet.com/b/exchange/archive/2013/08/27/now-available-updated-release-of-ms13-061-security-update-for-exchange-server-2013.aspx
    Yavuz Eren Demir
    After installing this patch (Exchange2013-KB2874216-v2-x64-en.msp) seeding of the databases was impossible.
    Error:
    warning
    Seeding of content index catalog for database 'Database02' failed. Please verify that the Microsoft Search (Exchange) and
    the Host Controller service for Exchange services are running and try the operation again. Error: Could not connect to net.tcp://localhost:3863/Management/SeedingAgent-F293698C-B2D0-40CA-A2C3-FB37982E708712/Single. The connection attempt lasted for a time
    span of 00:00:02.0592000. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:3863. .
    Looking at the two services mentioned in this warning I've noticed the Microsoft Exchange Search Host Controller (HostControllerService)
    was disabled
    After Changing it to Automatic and enabling it, the problem was salved

  • Exchange 2013 SP1 readiness check failing

    Trying to install our first Exchange 2013 SP1 server on Windows 2012 R2 in our datacentre, the readiness check fails with:
    Error:
    The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
    There are many more errors relating to Enterprise admin rights etc.
    Please note that:
    My account is Domain admin, Schema admin and Enterprise admin member, it always has been.
    I tried the built-in AD Administrator which of course is part of the groups as well, no difference.
    Active Directory is at 2008 R2 for domain and forest functional levels.
    I tried rejoining the new Exchange designated server to the domain
    I've installed RSAT-ADDS, the Managed API 4.0 and all the other windows roles via powershell
    There is a local domain controller that is a global catalog server on the new Exchange server subnet
    I tried running the Exchange Setup on a different server on the same subnet as where the active 2010 Exchange server resides as well as the FSMO AD role holder resides, this works fine. I even did the AD prep from there no problem, that made no difference
    on the datacentre server
    AD replicates fine between the FSMO role holder and the Datacentre (no errors in dcdiag or repadmin /showrepl)
    This error is in the event log:
    The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    ExSetupUI.exe
    6724
    Get Servers for domain.local
    TopologyClientTcpEndpoint (localhost)
    3
    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0475315. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
    at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    --- End of inner exception stack trace ---
    Server stack trace:
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
    at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at System.ServiceModel.ICommunicationObject.Open()
    at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
    at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
    the message resource is present but the message is not found in the string/message table

    So I decided to re-install the OS, worked perfectly now. Only difference from before would be:
    SCCM hasn't pushed SCEP 2012 to the new build of the same server yet
    The original server was installed in a different AD site and then it was physically mode and reassigned to an new AD site and subnet
    I might have installed the pre-reqs in a slightly different order (RSAT-ADDS, all the IIS etc things via powershell
    and then the UCM API 4.0. (saw few comments that the order of how you install them matters in other forums).
    10 or so Microsoft Windows updates haven't installed on the new OS build yet.
    Other than that, its identical. But if its not broken don't fix it, perhaps the above can help someone else though. 

  • Exchange 2013 Window Backup failure - fails to clean up log files - error FFFFFFFC

    Hello,
    We currently have an Exchange 2013 - Exchange 2007 coexistence setup.
    1x Windows Server 2008 R2 with Exchange 2007 CAS/HUB
    1x Windows Server 2008 R2 with Exchange 2007 MBX
    1x Windows Server 2008 R2 with Exchange 2013 CU 3 (all roles)
    Since our current backup solution (Symantec Backup Exec 2010 R3) does not support backing up Exchange 2013 CU3 databases, we are using the builtin Windows Backup feature to backup the Exchange 2013 CU3 databases.
    This has functioned for a while, until all of a sudden, the log files are not cleared anymore, causing our log disk to fill up.
    Our Exchange 2013 server looks like this:
    C: Windows + Exchange installation
    D: Databases
    E: Database Log Files
    F: Archive Databases
    G: Archive Database Log Files
    S: Dedicated backup volume
    The backup is scheduled to run every day at 21:00 hours, performing a full VSS backup of D:,E:,F: and G: to the volume S:
    Windows backup log says the backup completed with exceptions, leaving the Exchange logs untouched and filling the drive.
    The Windows Backup Command Line tools are NOT installed since they are not compatible with Exchange 2013.
    In the eventvwr we can see the following error:
    The Microsoft Exchange Replication service VSS Writer (Instance a33ec440-7f12-4c50-806b-1bc5ceaf8aad) failed with error FFFFFFFC when processing the backup completion event.
    The command VSSADMIN LIST WRITERS displays the following:
    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {cf84a907-76dc-428c-90e0-c18a3f9db493}
       State: [1] Stable
       Last error: Retryable error
    Restarting the Microsoft Exchange Replication (MSExchangeRepl) clears the writer error, same with a reboot, however the error comes backup after the next backup.
    Any thoughts on how to resolve this issue?
    Thanks.

    Hello,
    Here is a blog for your reference.
    http://blogs.technet.com/b/timmcmic/archive/2012/03/11/exchange-and-vss-my-exchange-writer-is-in-a-failed-retryable-state.aspx
    If there is any useful information after you change the logging to expert, please free let me know.
    Cara Chen
    TechNet Community Support

  • Exchange 2013 migration ends as Failed but the migration is OK

    Hi
    After Exchange 2013 SP1 I started getting this error when migration users to 2013 or within 2013.
    We are now at CU5 and the problem remains.
    When a migrations has come to the Synced or Successful state the ECP shows status Failed!
    If you view details you see the right status. In the report you see no errors, all looks good.
    So you you just synced a mailbox you have to complete the migration from PowerShell.
    I see no event in the log about this.
    I tried recreating the arbitration mailbox but no luck.
    Is more a cosmetic problem but a bit annoying!
    Anyone seen this?
    Regards
    Robert

    Hi Robert,
    Does the issue happen to all migrated mailboxes or just some specific mailbox?
    Please click Refresh 
    Please use the Exchange Management Shell to display migration user statistics:
    Get-MigrationUser -Identity [email protected] | FL
    Get-MigrationUserStatistics -Identity TestUser@ contoso.com -IncludeReport | FL
    Here is an article about Migration status report in EAC:
    http://technet.microsoft.com/en-us/library/jj898491(v=exchg.150).aspx
    If possible, please also collect the EAC screenshot about your issue and the commands results here without sensitive information for further analysis.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 Edge Transport install fails

    I'm trying to install the Edge Transport for Exchange 2013 but it gets to step 7 of 9:
    then give's the following error
    Error:
    The following error was generated when "$error.Clear();
     new-ExchangeServer
    " was run: "Value cannot be null.
    Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
    Then in event viewer I have the following two events.
    Watson report about to be sent for process id: 260, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, ExSetupUI, M.E.Data.Directory, M.E.D.D.ADObjectId.GetChildId, System.ArgumentNullException, 2ac6, 15.00.0847.031.
    ErrorReportingEnabled: True
    and
    Exchange Server component Edge Transport Role failed.
    Error: Error:
    The following error was generated when "$error.Clear();
     new-ExchangeServer
    " was run: "Value cannot be null.
    Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
    I've rebuilt the server but since it has something to do with the GUID I assumed it wouldn't work but I was grasping at straws and it didn't fix the issue.
    I can run the setup again and it does finish but it doesn't show up in the list of servers in the ecp management. I've yet to find a solution on this issue if anyone has a suggestion or two it would be greatly appreciated.

    Thanks for response.
    when I run Get-ExchangeServer I get the following
    Name                Site                 ServerRole  Edition     AdminDisplayVersion
    Exchange03                               Edge        Standard... Version
    15.0 (Bu...
    and the errors that are in the log
    [02/17/2015 20:06:33.0084] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: ADAM is installed on this machine; only the Microsoft Exchange Edge Transport server role may be installed.  See the Exchange setup log
    for more information on this error.
    [02/17/2015 20:07:50.0288] [1] The following 1 error(s) occurred during task execution:
    [02/17/2015 20:07:50.0288] [1] 0.  ErrorRecord: Service SMTPSVC was not found on computer '.'.
    [02/17/2015 20:07:50.0288] [1] The previous errors were generated by a non-critical task and will be ignored.
    then I have a load of error that failed to load dependency below is a small sample
    [02/17/2015 20:07:57.0648] [2] Process standard output: Installing assembly C:\Program Files\Microsoft\Exchange Server\V15\bin\edgetransport.exe
    Failed to load dependency Microsoft.Management.OData of assembly Microsoft.Exchange.Configuration.ObjectModel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception
    from HRESULT: 0x80070002)
    Failed to load dependency Microsoft.Ceres.InteractionEngine.Processing.BuiltIn of assembly Microsoft.Exchange.Data.Storage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified.
    (Exception from HRESULT: 0x80070002)
    Failed to load dependency Microsoft.Ceres.NlpBase.RichTypes of assembly Microsoft.Exchange.Data.Storage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception
    from HRESULT: 0x80070002)
    Failed to load dependency System.IdentityModel.Tokens.Jwt of assembly Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception from
    HRESULT: 0x80070002)
    Failed to load dependency Microsoft.Passport.RPS of assembly Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception from HRESULT:
    0x80070002)
    Thanks

  • Exchange 2013 CU 6 update fails on transport service

    i ran the update and it keeps getting the following error and i cannot find any info on the error
    Exchange Server component Mailbox role: Transport service failed.
    Error: Error:
    The following error was generated when "$error.Clear();
              $feVdirName = "PowerShell (Default Web Site)";
              $beVdirName = "PowerShell (Exchange Back End)";
              $vdirName = "PowerShell";
              $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";
              get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory
    -DomainController $RoleDomainController;
              new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back
    End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");
              new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false
    -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";
            " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'MST-MAIL1.fibigroup.net/Exchange Back End'.
    Parameter name: VirtualDirectoryName
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Hi,
    Thanks for your response.
    The error explains that the virtual directory 'PowerShell' already exists, so we need to remove the 'PowerShell' under "Default Web Site" and "Exchange Back End" firstly, and then continue to upgrade the Exchange 2013 CU6.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2013 SP1: Fix for failing MSExchangeTransport service

    We had a newly updated Exchange 2013 SP1 that would not start the Transport service
    "Netstat -b" showed that a service was listening to port 25 on all IP's (0.0.0.0:25) and when the service could not get the port, it would die, and Exchange would attempt to restart it over and over.
    After many tears, I found this solution: 
    Through the console or the ECP, check the Frontend receive connectors and find the one that is listening on 0.0.0.0:25, which is probably the Default Frontend Receive.  Disable it.
    Restart the MSExchangeTransport and MSExchangeTransportFrontEnd services.
    If both services restart normally, troubleshooting is complete.
    We use several custom connectors carried forward from the previous installation, which was SBS 2008.  If this applies to you, take notice.

    Normally, the Default Frontend Receive Connector (0.0.0.0:25) is the messaging entry point for your organization (I am assuming that you have a single MBX/CAS server).
    1. If you disable the Default Frontend Receive Connector (0.0.0.0:25), you block inbound email.
    2. Most probably, the cause for your problem are the Custom Receive Connectors. Check their type, and if it is Hub Transport, delete and re-create them as Front End Receive connectors.
    Step by Step Screencasts and Video Tutorials

  • Exchange 2013 - 451 DNS query failed with error ErrorTimeout

    Hi all, I know that there are many similar topics in forum, but  my problem is a bit different.
    My environment : Exchange Server 2013 (Windows Server 2008 R2 Ent) , Domain Controller + DNS (Windows Server 2008 R2 Ent) . EX Server uses DC as preferred DNS Server .
    Sometimes, I cannot send email to customers / people of some domains, I get error in my MS Outlook :
    Delivery is delayed to these recipients or groups:
    [email protected]
    [email protected]
    Subject: *****
    This message hasn't been delivered yet. Delivery will continue to be attempted.
    The server will keep trying to deliver this message for the next 1 days, 22 hours and 52 minutes. You'll be notified if the message can't be delivered by that time.
    Diagnostic information for administrators:
    Generating server: ex.mydomain.com
    [email protected]
    Remote Server returned '400 4.4.7 Message delayed'
    [email protected]
    Remote Server returned '400 4.4.7 Message delayed'
    Original message headers:
    Then I open Exchange Toolbox ==> Queue Viewer, what I see about messages which are sent to customerdomain.com :
    From Exchange Server command promt, I can query dns
    nslookup
    Default Server: mydc.mydomain.com
    Address: 192.168.10.2
    > set type=mx
    > customerdomain.com
    Server: mydc.mydomain.com
    Address: 192.168.10.2
    Non-authoritative answer:
    customerdomain.com MX preference = 0, mail exchanger = aspmx.l.google.com
    customerdomain.com MX preference = 5, mail exchanger = alt1.aspmx.l.google.com
    customerdomain.com MX preference = 5, mail exchanger = alt2.aspmx.l.google.com
    customerdomain.com MX preference = 10, mail exchanger = aspmx2.googleemail.com
    customerdomain.com MX preference = 10, mail exchanger = aspmx3.googleemail.com
    aspmx.l.google.com internet address = 74.125.200.27
    I can telnet to their mx server port 25 (of course they use gmail hosting) and send email to [email protected] normally.
    It just happen sometimes, with some domain (I can send/receive email with customerdomain.com normally before).
    How can I fix it ?

    Hi all,
    I think the problem because "DNS Suffix" ? although I uncheck "Append parent suffix of the primary DNS suffix" under Advanced TCP/IP Setting of network interface. Please see this:
    When I query by using dns client on DNS server:
    C:\Users\Administrator>nslookup
    Default Server: ad.mydomain.com
    Address: 192.168.0.3
    > gmail.com
    Server: ad.mydomain.com
    Address: 192.168.0.3
    Non-authoritative answer:
    Name: gmail.com
    Addresses: 2404:6800:4005:802::1015
    173.194.127.86
    173.194.127.85
    > set type=mx
    > gmail.com
    Server: ad.mydomain.com
    Address: 192.168.0.3
    Non-authoritative answer:
    gmail.com MX preference = 10, mail exchanger = alt1.gmail-smtp-in.l.google
    .com
    gmail.com MX preference = 30, mail exchanger = alt3.gmail-smtp-in.l.google
    .com
    gmail.com MX preference = 20, mail exchanger = alt2.gmail-smtp-in.l.google
    .com
    gmail.com MX preference = 5, mail exchanger = gmail-smtp-in.l.google.com
    gmail.com MX preference = 40, mail exchanger = alt4.gmail-smtp-in.l.google
    .com
    alt1.gmail-smtp-in.l.google.com internet address = 173.194.72.26
    alt2.gmail-smtp-in.l.google.com internet address = 74.125.25.26
    gmail-smtp-in.l.google.com internet address = 74.125.68.27
    alt4.gmail-smtp-in.l.google.com AAAA IPv6 address = 2607:f8b0:4001:c07::1b
    When I query by using command promt on DNS server, but point the dns server to 8.8.8.8:
    C:\Users\Administrator>nslookup
    Default Server: ad.mydomain.com
    Address: 192.168.0.3
    > server 8.8.8.8
    Default Server: google-public-dns-a.google.com
    Address: 8.8.8.8
    > gmail.com
    Server: google-public-dns-a.google.com
    Address: 8.8.8.8
    Non-authoritative answer:
    Name: gmail.com.mydomain.com
    Address: 187.26.231.129
    > set type=mx
    > gmail.com
    Server: google-public-dns-a.google.com
    Address: 8.8.8.8
    itl.com
    primary name server = ns1.netnames.net
    responsible mail addr = hostmaster.netnames.net
    serial = 2011071103
    refresh = 10800 (3 hours)
    retry = 1800 (30 mins)
    expire = 3600000 (41 days 16 hours)
    default TTL = 21600 (6 hours)
    It append mydomain.com into query, I configured my dns server forward to 8.8.8.8

  • Exchange 2013 CU 6 update fails on mailbox role

    i am installing cu6 update and everything is fine till i get to the mailbox role service
    have no idea why its giving this error
    i am installing as the domain administrator
    Error:
    The following error was generated when "$error.Clear();
              if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
                if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
                  # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
                  get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
                  $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
                  $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
                  $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
                  if ( $mbxs.length -eq 0)
                    $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                    if($dbs.Length -ne 0)
                      $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                      if ($mbxUser.Length -ne 0)
                        enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
                else
                  write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
            " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.".
    Error:
    The following error was generated when "$error.Clear();
              if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
                if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
                  # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
                  get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
                  $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
                  $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
                  $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
                  if ( $mbxs.length -eq 0)
                    $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                    if($dbs.Length -ne 0)
                      $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                      if ($mbxUser.Length -ne 0)
                        enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
                else
                  write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
            " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow)
       at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.Validate(TDataObject dataObject)
       at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
       at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Hi,
    Please recreate the Discovery Search Mailbox to check result.
    You can look at the following article.
    http://technet.microsoft.com/en-us/library/dn750894(v=exchg.150).aspx
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Reading Exchange Online tenant version failed due to an exception when trying to install Exchange 2013 in a hybrid environment.

    We currently have an Exchange 2010 hybrid install and we have migrated all of our email accounts to Office 365.  Now, I want to do an on-premise install of Exchange 2013 to better manage the hybrid setup.  When I try to install Exchange 2013 it
    asks for my O365 credentials to do a hybrid check but always fails with the above message.  I've done quite a bit of searching but haven't come up with anything useful.
    Here is what appears in the exchange setup log:  
    [09/22/2014 15:48:27.0024] [0] Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log for more information.
    [09/22/2014 15:48:27.0024] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, 
    [09/22/2014 15:48:27.0024] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, 
    [09/22/2014 15:48:27.0147] [0] Session=Tenant Total Cmdlet Time=1.6931035s
    [09/22/2014 15:48:27.0148] [0] Microsoft.Exchange.Management.Deployment.HybridConfigurationDetection.HybridConfigurationDetectionException: Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log
    for more information. ---> System.TypeLoadException: Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,

    Hi,
    I recommend you post this in
    office 365 forum also, as they should have more professional knowledge on hybrid deployments
    and you may get effective solution timely.
    In addition, I found a similar thread for you reference:
    http://community.office365.com/en-us/f/156/t/255739.aspx
    According to the reply of this thread, if you run the HCW (Hybrid Configuration Wizard) to deploy the Exchange Hybrid environment, there will generate an HCW log
    file for this deployment.
    Additional troubleshooting information is available in the Update-HybridConfiguration log file located at C:\Program Files\Microsoft\Exchange Server\V1*\Logging\Update-HybridConfiguration\HybridConfiguration****.log
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Uninstall Exchange 2013 failed on step number 8 Languages

    Dear All,
    I am not able to uninstall exchange 2013. the process is failing on step 8 Languages. Please advise

    Any one please guide how to uninstall Exchange 2013?
    Thanks in advance

  • Exchange 2013 SP 1 fails MSSpeech_SR_TELE.ca-ES.msi

    Hi
    After trying to install exchange 2013 SP 1 it fails with the following error : MSSpeech_SR_TELE.ca-ES.msi couldn't be opened.
    I'm running the upgrade through the command line with elevated privileges.
    I've re downloaded the sp already 2 times to no avail.
    The file exists in the extracted version.
    Same error occurred in CU 2 I've read on forums.
    [03/03/2014 13:27:57.0852] [1] [ERROR] The following error was generated when "$error.Clear();
              Install-MsiPackage `
                -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi")) `
                -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
                -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-ca-ES.msilog"))
            " was run: "Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\[03/03/2014 13:27:57.0852] [1] [ERROR] The following error was generated when "$error.Clear();
              Install-MsiPackage `
                -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi")) `
                -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
                -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-ca-ES.msilog"))
            " was run: "Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\[03/03/2014 13:27:57.0852] [1] [ERROR] The following error was generated when "$error.Clear();
              Install-MsiPackage `
                -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi")) `
                -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
                -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-ca-ES.msilog"))
            " was run: "Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify
    that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.".
    [03/03/2014 13:27:57.0852] [1] [ERROR] Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify that the package exists and
    that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.
    [03/03/2014 13:27:57.0852] [1] [ERROR] This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
    [03/03/2014 13:27:57.0852] [1] [ERROR-REFERENCE] Id=SpeechComponent___c2c075b985784599a14e8fa90dbc0403 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup'. This installation package could not be opened. Verify that the package exists and that you
    can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.".
    [03/03/2014 13:27:57.0852] [1] [ERROR] Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify that the package exists and
    that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.
    [03/03/2014 13:27:57.0852] [1] [ERROR] This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
    [03/03/2014 13:27:57.0852] [1] [ERROR-REFERENCE] Id=SpeechComponent___c2c075b985784599a14e8fa90dbc0403 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup'. This installation package could not be opened. Verify that the package exists and that you
    can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.".
    [03/03/2014 13:27:57.0852] [1] [ERROR] Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify that the package exists and
    that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.
    [03/03/2014 13:27:57.0852] [1] [ERROR] This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
    [03/03/2014 13:27:57.0852] [1] [ERROR-REFERENCE] Id=SpeechComponent___c2c075b985784599a14e8fa90dbc0403 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup

    Thanks for the update John!
    From what I have read, it can work running the upgrade in Windows Powershell, but the syntax must be right.
    .\Setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms
    compared to:
    Setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms
    Rhoderick Milne has a great blog post about this, so check it out: 
    6 Mistakes To Avoid With Exchange 2013 CU Command Line Installations . Personally I haven't tried that - So used to always run any exchange CU/SP or Rollup in the command line :)
    Martina Miskovic

  • Can't uninstall Exchange 2013 - (Distribution groups)

    I need help uninstalling Exchange 2013. The uninstaller fails with these 2 errors:
    This computer is responsible for expanding the membership of 1 distribution groups. These groups must be reassigned to another server before Setup can continue.
    This computer is responsible for expanding the membership of 1 dynamic distribution groups. These groups must be reassigned to another server before Setup can continue.
    I've gone so far as to disabling all distribution groups which removes its email properties and the uninstaller still fails.
    This is what happens in the eventlog:
    System.Management.Automation.ParseException: At line:1 char:67
    + Get-DynamicDistributionGroup | where {$_.ExpansionServer -eq '/o='s-Hertogenbosc ...
    +                                                                   ~~~~~~~~~~~~~
    Unexpected token 's-Hertogenbosch/ou=Exchange' in expression or statement.
    At line:1 char:175
    + ... s/cn=CADEXCDB13'}
    +                    ~~
    The string is missing the terminator: '.
    At line:1 char:38
    + Get-DynamicDistributionGroup | where {$_.ExpansionServer -eq '/o='s-Hertogenbosc ...
    +                                      ~
    Missing closing '}' in statement block.
       at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
    ] [ParentValue:"<NULL>"] [Thread:11] [Duration:00:00:00.0156248]
    I'm sure what happens here is the powershell commands looking at the distribution groups fail, because of our city name ('s-Hertogenbosch). Because of the apostrophe, the parameter is not passed successfully of this legacyExchangeDN. As this check fails,
    I believe the readiness check fails on these steps.
    This legacy administrative group name is still left from a 2003 -> 2010 -> 2013 migration.
    I've opened a Microsoft support request for this last week, but I thought someone might have dealt with this? I want to do a clean uninstall if possible.

    After I removed the distribution groups, I did restart the server.
    The problem is the the powershell script to check for existing distribution groups use a single quote to pass the server name to it. The server name contains a single quote itself so the parameter is not passed successfully.  If the powershell script
    used a double quote it would pass the parameter correctly.
    This works:
    Get-DistributionGroup | where ExpansionServer -eq "/o='s-Hertogenbosch/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CADEXCDB13"
    This does not work:
    Get-DistributionGroup | where ExpansionServer -eq '/o='s-Hertogenbosch/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CADEXCDB13'
    Do you see the difference? (Parameter is passed in a single or double quotation)

  • Lync integration not working after Exchange 2013 SP1 is installed...

    Hi,
    I have two Exchange 2013 servers running and everything is fine, almost.
    The problem is that on the first server we had OWA with Lync integration working before installing SP1, but after the installation of SP1, it doesn't Work any more.
    The second server was installed with SP1 from the start, but we can't get the Lync integration to Work on this one either..
    When we log in to OWA, it just starts to sign in but then says "there was a problem signing in, if this continues please contact your helpdesk"
    I have checked the Exchange server for events, and i can see the event ID 112 everytime i recycle the Application Pool, so there are some connection between Exchange and Lync..
    Have any of you Guys seen or experienced any thing like this?
    Thanks in advance.
    Regards
    Kenneth

    Hi,
    I recommend that you refer to the following article to troubleshoot the issue:
    Troubleshooting tips for Exchange 2013 OWA IM Integration to Lync 2013
    This post describes how to configure Exchange 2013 OWA to have IM integration to Lync 2013. Here I would like to give some troubleshooting tips in case you can't get the integration to work.
    In addition, here is a similar thread for your reference:
    Lync 2013 with Exchange 2013 SP1 OWA integration failed   
    Hope this helps!
    Thanks.                              
    Niko Cheng
    TechNet Community Support

Maybe you are looking for

  • Set page item from a stored procedure

    Dear reader We would like to have a stored procedure to run every 10 minutes. When the procedure starts, the user has to be warned that the update process is running. When the procedure is finished, the user should receive a message that the update p

  • Magic Mouse Guide for Windows 7 and Vista,,,

    Hello All, I recieved my Magic Mouse and it works great under OSX but I couldn't get it working under Windows at all. Searching here and around the web, I've compiled a guide on how I got it working. Hopefully, Apple will release proper drivers in th

  • Add new F4 (searchhelp) for material in sales order

    Hi there! I read the following related poste: customisation of F4 for material in sales order In that post Atul wanted to change an existing search help. My problem is differnet I think. What I have: In VA01 I have many different SearchHelps for the

  • Confused after re-install of OS... Base software not th

    After I re-installed windows due to some issues I was having, I've not been able to get my sound card right. I don't need a PC if my sound card ain't right. LOL After install of the drivers and everything else I can find to install, I don't have any

  • ADF : How to import a java class in jspx page

    Hi All, In jsp we have page directive to import a java class. Do we have anything similar to that in a jspx page?