OWA
15 TopicsWhy signatures disappear in OWA
Hi, We have problem with disappearing signatures in OWA. Signatures in OWA worked without problem till last week. But today, users that have BB licences and use only OWA loosing their signatures. It repeats every 1-2 days. Have anybody experience with this problem? Can you give me advice, how to solved it? Thanks.384Views0likes1Commentupgrading from exchange 2013 to 2019, new install of 2019..cannot login to ecp or owa
hi, thanks in advance for your help. i have an existing small environment. it consists of a pair of 2022 domain controllers, the domain/forest level is set to 2016. I have an existing 2012 (not r2) server running exchange 2013 and a brand new 2022 server with newly installed exchange 2019. everything is patched fully. the install of 2019 proceeded without error. however, i cannot login to either owa or ecp on the 2019 server. when i try, i just get sent back to the login screen. in the event log, i see this warning: Event code: 3005 Event message: An unhandled exception has occurred. Event time: 8/7/2023 1:09:12 PM Event time (UTC): 8/7/2023 5:09:12 PM Event ID: 31c12d2579ac4779bfec01933febc091 Event sequence: 2 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/2/ROOT/owa-1-133359017471842518 Trust level: Full Application Virtual Path: /owa Application Path: D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\ Machine name: HOME-EXCH1 Process information: Process ID: 472 Process name: w3wp.exe Account name: NT AUTHORITY\SYSTEM Exception information: Exception type: TargetInvocationException Exception message: Exception has been thrown by the target of an invocation. at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Owin.Loader.DefaultLoader.<>c__DisplayClass12.<MakeDelegate>b__b(IAppBuilder builder) at Owin.Loader.DefaultLoader.<>c__DisplayClass1.<LoadImplementation>b__0(IAppBuilder builder) at Microsoft.Owin.Host.SystemWeb.OwinAppContext.Initialize(Action`1 startup) at Microsoft.Owin.Host.SystemWeb.OwinBuilder.Build(Action`1 startup) at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint() at System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory) at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication context) at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) ID1039: The certificate's private key could not be accessed. Ensure the access control list (ACL) on the certificate's private key grants access to the application pool user. Thumbprint: '9F650D5586F179E05BA85AE833DFB66044CA2F08' at System.IdentityModel.X509Util.EnsureAndGetPrivateRSAKey(X509Certificate2 certificate) at System.IdentityModel.RsaEncryptionCookieTransform..ctor(X509Certificate2 certificate) at Microsoft.Exchange.Security.Authentication.OAuthExtension.DataHandler.RsaGenericDataProtector..ctor(X509Certificate2[] certificates) at Microsoft.Exchange.Clients.Owa2.Server.Core.notifications.SignalR.SignalRStartup.Configuration(IAppBuilder app) Invalid provider type specified. at System.Security.Cryptography.Utils.CreateProvHandle(CspParameters parameters, Boolean randomKeyContainer) at System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType keyType, CspParameters parameters, Boolean randomKeyContainer, Int32 dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle& safeKeyHandle) at System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair() at System.Security.Cryptography.RSACryptoServiceProvider..ctor(Int32 dwKeySize, CspParameters parameters, Boolean useDefaultKeySize) at System.Security.Cryptography.X509Certificates.X509Certificate2.get_PrivateKey() at System.IdentityModel.X509Util.EnsureAndGetPrivateRSAKey(X509Certificate2 certificate) Request information: Request URL: https://localhost:444/owa/proxylogon.owa Request path: /owa/proxylogon.owa User host address: 127.0.0.1 User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITY\SYSTEM Thread information: Thread ID: 13 Thread account name: NT AUTHORITY\SYSTEM Is impersonating: False Stack trace: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Owin.Loader.DefaultLoader.<>c__DisplayClass12.<MakeDelegate>b__b(IAppBuilder builder) at Owin.Loader.DefaultLoader.<>c__DisplayClass1.<LoadImplementation>b__0(IAppBuilder builder) at Microsoft.Owin.Host.SystemWeb.OwinAppContext.Initialize(Action`1 startup) at Microsoft.Owin.Host.SystemWeb.OwinBuilder.Build(Action`1 startup) at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint() at System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory) at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication context) at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) Custom event details: i see a lot of info on the web about permissions to private keys but i have checked and the app pool user is localsystem, and system has full access to the keys. i also see some information about the provider type but this cert was generated by the install.....so would it generate a cert it could not use?? i have working on this for days and am going around in circles. i really appreciate anyone's help on this! thanksSolved2.8KViews0likes11CommentsExchange Server 2019 OWA web app when open calendar keep direct login page
After migrate all mailbox from Exchange 2013 to 2019, Outlook client / mobile app working fine. However when open OWA web app then go Calendar, may be wait for few second or click on any event, it will reload to login page. I can't see any error from event log or inetpub\logs\LogFiles. If owa IP address point back to Exchange 2013, web app calendar work again. I tired add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames with exch2019.domain.local, domain.local and autodiscover.domain.local didn't help. The exchange server only allow access internally or by vpn connection. Any idea about this? Thanks848Views0likes2CommentsExchange 2019 - Outlook/OWA all messages show the same time 8:02PM
Ok this one has me really puzzled. For some reason, which started randomly (since Feb 2023) the display time in Outlook, OWA and Phones (default app or outlook) have randomly been showing all emails as being received at 8:02PM and sometimes the next day at that time, on every message, could be ones that were sent at 11:02 am, could be ones sent at 2:22pm etc. And seems to have been some but not all users, but now more and more users are affected. All time zone and time syncs are correct. Headers shows the correct time and time zone on the messages. Messagetracking shows correct times as well. I was on Exch 2019, CU12, Nov22SU but did update to the Feb23SU(and all WU) and issue returned. It seems a reboot does fix it for a while. (Did the updates about 5-6 days ago, started again today) No major errors in event viewer other than the following, and that my SSL cert is expiring (in may) MSExchange Front End HTTP Proxy - 1003 [GetActiveCopiesForDatabaseAvailabilityGroup.FindAnotherServerLocatorServer: Server locator number of failovers since 2/22/2023 12:02:42 AM is already 25. No more failover attempts are allowed.] An internal server error occurred. The unhandled exception was: %2 but do not have a DAG The only other odd thing that I see is for some reason there is about 6 Microsoft Exchange certs (4 expire 2023, 2 expire 2026) and I believe there should only be one of those if I look at other setups1.4KViews0likes2CommentsMessages send to a moderated list aren't approved in OWA
When i send messages to a moderated list, the approval request is send to moderator. But, when the moderator clicks in the button "Approve", nothing happens. The list don't receive the approved message. This issue occurs only in OWA. In Outlook desktop the approval process runs normally.Solved949Views0likes2CommentsExchange 2013 The certificate key algorithm is not supported
Hello, We have an Exchange 2013 server, updated to CU23, which worked fine until one day, it showed the error on OWA "The certificate key algorithm is not supported"! I tried to put back an older valid certificate, reactivate all ciphers and TLS, updated to latest Microsoft patches, this error still comes back and I cannot manage the server anymore! Anyone has a clue how to resolve this issue?4.9KViews0likes8CommentsOutlook Web App (OWA) On-Premise without cloud integration
What needs to be done to operate Outlook Web App (OWA) On-Premise without cloud integration? It seems some people have asked this question for years but never got an answer. Examples: https://social.msdn.microsoft.com/Forums/ie/en-US/bcfb19d0-c8df-447c-a9a2-3b2bca8fcb4c/exchange2016-using-owa-internally-request-for-7-js-files-from-appsforofficemicrosoftcom?forum=exchangesvrdevelopment https://social.technet.microsoft.com/Forums/security/he-IL/06f5564d-bcb8-4b33-bcc8-da64fd8ccc79/content-security-policy-disable-access-to-appsforofficemicrosoftcom-in-outlook-web-app?forum=exchangesvrdevelopment When I use OWA On-Premise Microsoft Edge reports errors on the developer console (Hotkey [F12]): "Refused to load the stylesheet 'https://appsforoffice.microsoft.com/lib/1/hosted/office.js' because it violates the following Content Security Policy directive: "default-src 'self' data: 'unsafe-inline'". Note that 'style-src-elem' was not explicitly set, so 'default-src' is used as a fallback.3.3KViews0likes0CommentsTurn off add-in OWA
Hi there, I can't find any settings in the new add-in admin center to turn off/disable an add-in for OWA for the tenant. Does anyone have instructions for disabling an add-in for users in OWA on a tenant - for instance I would like to block the S4B add-in in OAW and don't see the option in the new add-in management center? Thanks!3.2KViews0likes3CommentsOWA via Exchange 2019 Edge
Hello Everybody, I'm upgrading from Exchange 2013 to Exchange 2019. I followed those steps: - Install two new Mailboxes servers in Co-existance with the old Exch 2013 servers. - Configure my new DAG - Move all mailboxes to the new servers. At this stade, all is working fine. I have an exchange 2013 CAS server in my DMZ that I want to replace with a new Exch 2019 Server Edge. To do, I followed the steps bellow: - Install the new Edge role server - Install a new certificate - Subscribe the edge server in my new mailbox server. When I configured my Firewall to route all HTTPS (OWA) flow to the new Edge server, I got a blank page instead of the OWA login page. I tried to test a direct access to https://myedgeserver.mydomain.com/owato see if it can works, same result. The OWA requests are proxied by the Edge Server? How to verify it? I'm doining something wrong? Need your help after 2 days googling a solution. Regards.2KViews0likes1Comment