500 ERROR trying to access ECP - Exchange 2019
I installed Exchange 2019, but when I was trying to access to ECP in order to configure MS Exchange Server I got this error: (I tried using ecp, exchange or owa) Then I reviewed some posts but when I opened the EMS I got the following error: Connecting to remote server andeslion.andeslion.com failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. Any suggestion where I should look at? Thanks
Connect to Exchange 2019 Management Shell over HTTPS
Hello Community, we have an Exchange Server 2019 CU12 Hybrid environment and we want to automate the common Exchange tasks with Service Now (create mailbox, Distribution list) as i have to create the items on the on-prem Exchange servers i need th Exchnage CMDlets to push the commands with Powershell scripts. As the Service Now Mid Server don't have this Exchange Cmdlets installed my idea was to connect the Service Now Mid Server with the Exchange management Shell and the run the commands. Based on Security reasons we want to connect the Exchange Management Shell over HTTPS and not over HTTP. Unfortunately, Microsoft only documented HTTP connection "https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-servers-using-remote-powershell?view=exchange-ps" I found also a how-to to enable SSL for Management Shell o the Exchange Server 2016. I follwed the instruction but its still not working. Ist there a Best practice available to allow Exchange Management Shell connections over HTTPS? Best regards, Alex
IMAP | OAUTH2.0 | Thunderbird Email Configuration |
Hello Team, I have 2 separate standalone forests without INTERNET, in which Exchange Server 2016 CU22 , & Exchange Server 2019 CU11 is running independently on On-Premise servers. This question is not about 2 forests or their configuration. The users are separate and I don't need anything between them. 1. I was recently asked to configure Thunderbird Email Client (latest one) and it was not working. Emails were receiving but unable to send emails. It keeps giving message to either login or certificate warning. 2. I started testing and re-configuring IMAP Services. Now IMAP Profiles are successfully configured in Outlook Client but not on Thunderbird. Test-IMAPConnectivity works fine. 3. Also, thunderbird client is not able to auto-configure or search for the configuration. Autodiscover Service is configured correctly. 4. I noticed that, I have configured Set-ClientAccessService -AutoDiscoverServiceInternalUri correctly whereas I have left Set-AutoDiscoverVirtualDirectory -InternalURL to Null. Is this Correct? I searched for many articles for virtual directory configuration but they don't configure AutoDiscoverVirtualDirectory Am I missing something here. 5. Is there any SMTP Auth that I need to configure? 6. I was reading about OAUTH2.0. Do I need to configure anything in this regard? I'm not planning on upgrading the infrastructure for next couple of months as it is not needed urgently by business. 5. Is there a way or offline tool to test for Exchange Certificates, TLSCert etc? I reconfigured Microsoft Exchange Server Auth Cert because it was not appearing in Get-AuthConfig... There is a strong reason why it has no internet, so please don't ask me to upload logs. Please share the commands and scripts, I will proceed from there. LATEST UPDATE: I came across this URL https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission and understood that I might I have to enable SMTP Auth at Organizational or Mailbox Level. The sad part is I was not able to find the settings in both servers. I don't get any option listed as "SmtpClientAuthenticaionDisabled". Is this command not available in my version of exchange. Thanks in advance Najeeb
Exchange Upgrade 2019 CU9 to CU11
Hello All, Nino_Bilic @Vasil Michev, After we upgrade our exchange from 2019 CU9 to CU11, we start getting below warning every few seconds, tried so many articles also deleted and recreated OAB virtual directories but till the issue same. These three file size is 1 KB global.asax, web.config.bak & web.config ib this location C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\OAB\. it suppose to be 6KB for web.config.bak & web.config. In one article from Microsoft i read just by replacing the files from working exchange server fixed the issue not sure if its a right solution. appreciate if any one can help us. Event code: 3006 Event message: A parser error has occurred. Event time: 3/15/2022 8:19:51 AM Event time (UTC): 3/15/2022 4:19:51 AM Event ID: f515642012be4d04b126477081e68c4b Event sequence: 1 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/ROOT/OAB-1071-132917915910090237 Trust level: Full Application Virtual Path: /OAB Application Path: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\OAB\ Machine name: EXMAILSVR Process information: Process ID: 24048 Process name: w3wp.exe Account name: NT AUTHORITY\SYSTEM Exception information: Exception type: HttpException Exception message: Could not load type 'Microsoft.Exchange.HttpProxy.ProxyApplication'. at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() at System.Web.Compilation.BuildManager.CallAppInitializeMethod() at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) Could not load type 'Microsoft.Exchange.HttpProxy.ProxyApplication'. at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.ApplicationBuildProvider.GetGlobalAsaxBuildResult(Boolean isPrecompiledApp) at System.Web.Compilation.BuildManager.CompileGlobalAsax() at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() Could not load type 'Microsoft.Exchange.HttpProxy.ProxyApplication'. at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) Could not load type 'Microsoft.Exchange.HttpProxy.ProxyApplication'. at System.Web.UI.TemplateParser.GetType(String typeName, Boolean ignoreCase, Boolean throwOnError) at System.Web.UI.TemplateParser.ProcessInheritsAttribute(String baseTypeName, String codeFileBaseTypeName, String src, Assembly assembly) at System.Web.UI.TemplateParser.PostProcessMainDirectiveAttributes(IDictionary parseData) Request information: Request URL: https://localhost/OAB/ Request path: /OAB/ User host address: 127.0.0.1 User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITY\SYSTEM Thread information: Thread ID: 47 Thread account name: NT AUTHORITY\SYSTEM Is impersonating: False Stack trace: at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() at System.Web.Compilation.BuildManager.CallAppInitializeMethod() at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) Custom event details:
infected log files in the database
Trojan log files in the database, the backup is also damaged, can you help me? I also find something not clear in the following path: screen1 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_4.0.30319\Names Trojan bases are damaged, and phishing, how can I recover? What steps to take to minimize the consequences? screen1:
Event ID 12018 and Exchange 2019
We have recently migrated from on-premise Exchange 2016 to hybrid with Exchange 2016 server used primarily for management. I have been interested in switching from a commercial SAN certificate to LetsEncrypt, but the idea of having my event logs perpetually full of 12017 and 12018 events due to Lets Encrypt's 90 day certs has made that unattractive. Does Exchange 2019 behave any better in regards to how frequently it complains about certificates expiring 90 days in the future?
