Query Store transaction preventing restoring database
I have a database backup that was taken on SQL Server 2019 instance. While trying to restore it to a SQL Server 2025 instance, the files restored without issue, but it remained "In Recovery" for three days before I tried to take it to Emergency, Single User, and back online, though it still remained in recovery. I then took the backup to a SQL Server 2019 instance and was able to restore it and bring it online there. Though the logs on both servers had shown similar errors to these two. The Page and Log record Id were consistant. ```text Database ID 5, Page (1:47416) is marked RestorePending, which may indicate disk corruption. During undoing of logged operation in database (page(1:301040) if any), an error occurred at log record ID (15885:36832:180). ``` Doing some investigation has provided that there is a stuck transaction, and I was able to pin this down to Query Store. OPENTRAN (This spid was from the original server.): ```text ransaction information for database 'BrokenDatabase'. Oldest active transaction: SPID (server process ID): 26s UID (user ID) : -1 Name : DELETE LSN : (15885:19072:1) Start time : Mar 1 2025 7:27:58:633PM SID : 0x01 DBCC execution completed. If DBCC printed error messages, contact your system administrator. ``` I had the Top and bottom 50 of 938 transactions from fn_dblog, but since it contains data this community will not allow it. Makes it harder to get an answer without the data showing that query store is the issue, but to play by the rules you have give lackluster information, because the guidelines are even searching through code blocks, markdown, and tables. With Query Store in the Read_Write mode, I was unable to return anything from sys.query_store_plan and / or sys.query_store_runtime_stats, because they were locked by the ASYNC_LOAD of QDS. All that I have collected show that is internal to the Query Store. sys.internal_tables: | name | object_id | principal_id | schema_id | parent_object_id | type | type_desc | create_date | modify_date | is_ms_shipped | is_published | is_schema_published | internal_type | internal_type_desc | parent_id | parent_minor_id | lob_data_space_id | filestream_data_space_id | | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | | plan_persist_runtime_stats | 213575799 | NULL | 4 | 0 | IT | INTERNAL_TABLE | 2019-09-24 | 2019-12-28 | 0 | 0 | 0 | 243 | QUERY_DISK_STORE_RUNTIME_STATS | 0 | 0 | 0 | NULL | sys.dm_tran_active_transactions: | transaction_id | database_id | database_transaction_begin_time | database_transaction_type | database_transaction_state | database_transaction_status | database_transaction_status2 | database_transaction_log_record_count | database_transaction_replicate_record_count | database_transaction_log_bytes_used | database_transaction_log_bytes_reserved | database_transaction_log_bytes_used_system | database_transaction_log_bytes_reserved_system | database_transaction_begin_lsn | database_transaction_last_lsn | database_transaction_most_recent_savepoint_lsn | database_transaction_commit_lsn | database_transaction_last_rollback_lsn | database_transaction_next_undo_lsn | | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | | 255756374 | 5 | NULL | 1 | 4 | 524289 | 1 | 0 | 0 | 0 | 10677320 | 0 | 0 | 15885-00000-19072-00001 | 15885-00000-36952-00023 | NULL | NULL | NULL | 15885-00000-36832-00179 | Last Thursday, I was able to force the database to turn query store off, I tried after that setting it for Read_only and then clearing Query Store, but the clearing went into a lock for ASYNC_LOAD of QDS, after 6 hours of nothing happening and checking requests and seeing the lock, I ended that task. It was not actively doing anything just sleeping. My ultimate goal is to be able to get his database to the SQL Server 2025 instance and have it online. What can I do with the original backup or currently the online version of the database on the SQL Server 2019 instance to be able to make that happen?Exchange 2019 + ADFS is it possible to configure ModernAuth for third-party Android mail clients?
Hello, Our organization operates under Uzbekistan's data localization and banking secrecy regulations, which require customer and corporate data — including email — to remain on infrastructure physically located within the country and under direct regulatory oversight. This precludes the use of cloud-hosted mail services such as Microsoft 365/Exchange Online, and requires a fully on-premises Exchange deployment with local identity federation (AD FS) instead of Azure AD. Environment: Exchange Server 2019 CU14, single server (MX01), pure on-premises. AD FS is registered as an AuthServer (Type: ADFS), no Azure AD / hybrid tenant involved. The AuthServer is configured correctly: AuthorizationEndpoint and TokenIssuingEndpoint are populated, IsDefaultAuthorizationEndpoint: True, and DomainName points to our mail domain. Realm/ServiceName are configured as well. Symptom: The native iOS Mail client (account added manually, no MDM profile) correctly redirects to our AD FS login page on first setup — the full Modern Auth flow works. A third-party EAS client (Nine by NitroDesk, Android) never receives an OAuth challenge at all — it falls back to Basic authentication. Get-ActiveSyncVirtualDirectory/Set-ActiveSyncVirtualDirectory in this build simply has no -OAuthAuthentication parameter (unlike EWS/OAB). Log finding: When testing with the Nine client, the following was captured in the Exchange HttpProxy/Eas logs: S:ServiceCommonMetadata.OAuthError=Flighting is not enabled for domain 'webmail.<domain>'. S:ServiceCommonMetadata.OAuthErrorCategory=OAuthNotAvailable Questions: What exactly controls "Flighting" for EAS OAuth in a pure on-prem Exchange 2019 CU14 + AD FS scenario (no Azure AD)? Is there a documented, supported way to enable it (New-FlightOverride? something else)? Is EAS Modern Auth even supported for an arbitrary/generic OAuth client (not Apple, not Outlook) in this scenario, or is it effectively an allowlist limited to specific client_ids (Apple Native Mail / Outlook)? How does native iOS Mail get redirected to AD FS without ever receiving an authorization_uri in the EAS/Autodiscover 401 challenge — is there an undocumented discovery path (e.g., hardcoded per registered client_id)? Thank you in advance for any insight.
Preview .eml and .msg files in SharePoint on premises
I have a question regarding Preview of files. In Office 365 there are a lot of options to preview files. But I am looking into SharePoint server. And especially into eml and msg files can you preview them in SharePoint On Premises? And is it already possible in the 2013 version or do you need to upgrade? If a upgrade will be made it will be 2019. Is it also important to have Enterprise or Standard if it works? Thanks in advance.
Help~After installing Exchange 2019, mail is stuck in Draft in OWA
Hi all I dont undertand this symptom. Now I installed one new DC, one new Exchange 2019(CU13) in active directory domain. and I just set recieve connector(check anonymous user in Default Exchange) and created send connector and I sent mail to my own mailbox(administrator), and I also sent mail to other mailboxes, but I only have stuck Draft folder in OWA. before install Exchange 2019 CU13, I installed Exchange 2029 CU15 but it was same symptom so after removing Exchange 2019 CU15, I reinstalled Exchange CU 13. but it was same. DC and Exchange OS are Windows Server 2022 Standard on Dell H/W. ipv4 192.168.10.202 subnet 255.255.255.0 GW 192.168.10.1 Dns1 192.168.10.201(DC) It's the same as the link below, but there's nothing solved. T.T https://www.reddit.com/r/exchangeserver/comments/1daxga2/exchange_server_2019_emails_get_stuck_in_drafts/#:~:text=Here's%20some%20information%20about%20emails%20getting%20stuck,lots%20of%20space%20may%20not%20always%20work. If anyone knows how to solve this problem, please help meMigration Exchange 2016 to 2019 then SE
Hello, we replaced our old Exchange 2016 Server, to Exchange SE. After the update users notified me, that the search is taking long. We also have a lot of Errors in the Eventlog 3056 Scenario: UpdateMasterTable. The app master table could not be saved due to a conflict. Mailbox: x Error: Property conflict: DisplayName: 'BigFunnelPoiNotNeededReason', Resolvable: 'True', OriginalValue: 'Object is null', ClientValue: '2', ServerValue: '2' Property conflict: DisplayName: 'BigFunnelCorrelationId', Resolvable: 'True', OriginalValue: 'Object is null', ClientValue: 'Property: [{0b63e350-9ccc-11d0-bcdb-00805fccce04}:'BigFunnelCorrelationId'] BigFunnelCorrelationId, PropertyErrorCode: NotFound, PropertyErrorDescription: .', ServerValue: 'Property: [{0b63e350-9ccc-11d0-bcdb-00805fccce04}:'BigFunnelCorrelationId'] BigFunnelCorrelationId, PropertyErrorCode: NotFound, PropertyErrorDescription: .' Property conflict: DisplayName: 'BigFunnelIndexingStart', Resolvable: 'True', OriginalValue: 'Object is null', ClientValue: 'Property: [{0b63e350-9ccc-11d0-bcdb-00805fccce04}:'BigFunnelIndexingStart'] BigFunnelIndexingStart, PropertyErrorCode: NotFound, PropertyErrorDescription: .', ServerValue: 'Property: [{0b63e350-9ccc-11d0-bcdb-00805fccce04}:'BigFunnelIndexingStart'] BigFunnelIndexingStart, PropertyErrorCode: NotFound, PropertyErrorDescription: .' Property conflict: DisplayName: 'BigFunnelMessageUncompressedPOIVersion', Resolvable: 'True', OriginalValue: 'Object is null', ClientValue: 'Property: [0x36660003] BigFunnelMessageUncompressedPOIVersion, PropertyErrorCode: NotFound, PropertyErrorDescription: .', ServerValue: 'Property: [0x36660003] BigFunnelMessageUncompressedPOIVersion, PropertyErrorCode: NotFound, PropertyErrorDescription: .' Property conflict: DisplayName: 'BigFunnelPOIContentFlags', Resolvable: 'True', OriginalValue: 'Object is null', ClientValue: 'Property: [0x36630003] BigFunnelPOIContentFlags, PropertyErrorCode: NotFound, PropertyErrorDescription: .', ServerValue: 'Property: [0x36630003] BigFunnelPOIContentFlags, PropertyErrorCode: NotFound, PropertyErrorDescription: .' Property conflict: DisplayName: 'BigFunnelPOIUncompressed' Does somebody know how we can fix this problem? We find already that article that is similar but the workaround for the search (not the mirgration) doesnt work for us. We need Outlook cached. https://learn.microsoft.com/en-us/answers/questions/5508363/outlook-search-not-working-reliably-after-exchange
How to know if Exchange oAuth Metadata is refresh
Hi, I have an environment with Exchange 2013 hybrid coexistence with Exchange 2019 now. oAuth is enabled. I am suspecting the current environment, servers won't refresh the oAuth Metadata themselves. Is there any logs I can trace that? What event ID indicate the metadata is updated?
Supported / recommended .Net versions Exchange SE on Windows Server 2019
I’m reading up on the Exchange SE upgrade, but there’s something I don’t understand. We are currently running Exchange 2019 CU15 on a Windows Server 2019 server (desktop experience). My initial plan is to perform an in-place upgrade from Exchange 2019 CU15 to Exchange SE, while remaining on Windows Server 2019 for the time being. From what I’ve read, this should be possible: https://techcommunity.microsoft.com/blog/exchange/why-%E2%80%9Cin-place-upgrade%E2%80%9D-from-exchange-2019-to-exchange-se-is-low-risk/4410173 https://learn.microsoft.com/en-us/answers/questions/2182463/upgrade-exchange-2019-to-exchange-se According to the supportability matrix, this should also be supported: https://learn.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix Exchange Server SE is supported on Windows Server 2019. What I don’t understand is the table for .NET Framework support. It seems like Windows Server 2019 is missing for Exchange Server SE in that table, just like Exchange Server 2019 CU15 on Windows Server 2019 with its corresponding .NET version. https://learn.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019#additional-requirements-and-information Does anyone have an explanation for this? I’d love to hear it!
