Forum Widgets
Latest Discussions
W2K19 vss issue
Hello, I'm looking for some troubleshooting suggestions for a 2019 Server that is experiencing vss issues. Yesterday I had a backup fail with a VSS error. Failed: Failed - 0x80042306 - IDispatch error #8454 - Retrying without VSS Writers ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed. - Returned HRESULT = 0x80042301 - Error text: VSS_E_BAD_STATE After some further troubleshooting I realised that the VSS issue extended beyond the backup system C:\windows\System32>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2013 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {4a4003f5-e11d-4f99-8071-e8a74259dfb3} State: [1] Stable Last error: No error Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {7254596f-d6ee-4268-b16b-0ac353af5af6} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {6704e612-a914-4db9-81da-fe66b9a63684} State: [1] Stable Last error: No error Writer name: 'Microsoft Hyper-V VSS Writer' Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Instance Id: {d4e0e02d-d932-424c-8708-976037c2fc5f} State: [7] Failed Last error: Timed out Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {faf20311-d7ae-446d-b82b-f73f3c94a91b} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {62ce4679-7634-423c-b549-efd60969679e} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {bd78bd8d-0bcb-4143-9494-1f94aaa9412e} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {cabe2719-7881-4a17-a306-b91bf55a0ca7} State: [7] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {327e2198-51e5-418f-857b-807592618509} State: [7] Failed Last error: Timed out Writer name: 'Certificate Authority' Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86} Writer Instance Id: {53ff0a16-053f-4b4a-a670-63dbf07f0cd0} State: [7] Failed Last error: Timed out Writer name: 'DFS Replication service writer' Writer Id: {2707761b-2324-473d-88eb-eb007a359533} Writer Instance Id: {f7b764bc-f504-4542-b423-2b2436c3c373} State: [1] Stable Last error: No error Writer name: 'NTDS' Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} Writer Instance Id: {2c66a49d-efd6-41a7-a35b-ce3362000b2a} State: [7] Failed Last error: Timed out Writer name: 'Dhcp Jet Writer' Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad} Writer Instance Id: {de15b14a-bcf4-41b9-bdf0-76af8edaee68} State: [7] Failed Last error: Timed out Writer name: 'WINS Jet Writer' Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741} Writer Instance Id: {05ee1245-8ad7-4486-9845-3d83bb443557} State: [7] Failed Last error: Timed out I have done the following: chkdsk /f on all volumes dism /online /cleanup-image /checkhealth dism /online /cleanup-image /scanhealth dism /online /cleanup-image /restorehealth sfc /scannow no errors reported After the above: vssadmin list writers reported no errors and the backup completed normally. So I thought that the issue was resolved. Today the backup failed again and vssadmin list writers is as above again. I can't see anything in the Event Log (System or Application) that looks to be relevant. At this stage the only idea that I have is to restore the server back to prior to the errors commencing, but this is a DC in a multi-DC environment, so that is not a trivial step. I'd prefer to try and resolve the issue directly if I can. Thanks VWThe TLS connection request has failed.
We are in the process of configuring a new SharePoint 2016 on-premises Farm using Azure VMs. The App and WFE run on Windows 2019 R2. The SQL DB is Windows 2022 running in CM 110. All DataCenter editions The farm is not completely configured and is not having traffic yet. I am seeing the following event (id 36874) in our Event Viewer An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The TLS connection request has failed. The servers were setup by another team so I'm not sure on what all they did to prepare them and I am not a Sysadmin by training or experience, but I can try and answer questions you may have. Could there be something missing in the setup of these servers that will prepare them for TLS communication? Is this an issue with having different ciphers available to each server due to different OS and not being able to agree on one? I verified that there are ciphers available on the DB that are in common with the ones on our SP Servers, which are in the same order on each server and should be usable. This is why I'm wondering if TLS has to be eabled or tuned on in some way when newly installing these or perhaps I'm missing something? THese are normal messages? Thank you!
Run As Administrator not always working?
I have dealt with this for about 10 years now since Server 2003/Windows XP. Just now getting around to addressing this. If this isn't the right place, I'd appreciate a link to the right place. Have a Server 2019 domain with 13 workstations all running Windows 11 Pro. Workstation user only have user access rights. On occasion I'll need to run something, such as services.msc for example with admin rights. On some workstations I can right-click services, select Run As Administrator, enter the domain admin credentials and can then stop/start/change services as needed. Yet on other workstations the Run As Administrator doesn't work. It runs services.msc. But I'm not prompted for admin credentials and can't start/stop/change the service. What can I do to make it work so I don't have to waste time logging of the normal user to log in with a domain admin account? Note that I do have and use group policies on the server. I've never "knowingly" set any policy that would prevent the Run As Administrator for working. I also have WSUS set up and it's configured with SSL if that matters. Thanks for any feedback on this. - CarlWindows Server 2019 AD & DNS replication
Hello, I'm running into issues with AD & DNS replication on a recently joined server in our environment. Environment: Three writable DCs in separate sites: Server A (Site A) – Windows Server 2019, AD DS & DNS (healthy) Server B (Site B) – Windows Server 2019, AD DS & DNS (healthy) Server C (Site B, new) – Windows Server 2019, AD DS & DNS (failing) Issues Observed Inbound replication to Server C from Server A & Server B successfully propagates for both AD and DNS zone/record changes. Outbound replication from Server C to Server A & Server B fails for both AD and DNS zone/record changes. Server A logs Event ID 1311 (KCC). Server A & B logs Event ID 1925 when trying to establish the link to Server C. What I’ve Tried: Pointed each servers NIC's to a heathy DC with the correct suffix. I've checked any windows FW and network FW rules to make sure no blockages. Verified A+SRV records for both heathy DC's. Confirmed AD-Integrated zones on all 3 servers show correct ACLs and records. I've tried running repadmin → still errors. Tested RPC connectivity: TCP 135 open. Ensured subnets/site mappings are correct in Sites and Services. I've tried to seed a zone and record on the healthy servers in efforts of t/s. Any help would be greatly appreciated!
Cameras To Redirect Custom RDP Property Does not Work
In mstsc.exe, under Local Resources > More.. there is an option for Video capture devices. Which lists my webcam and Devices that I plug in later. I have determined that this option the an RDP file is the string camerastoredirect:s:* So what I have done is ran the following command on my Connection Broker so that this line will be added to rdp file generated by the feed. Set-RDSessionCollectionConfiguration -CollectionName $CollectionName -CustomRdpProperty "camerastoredirect:s:*" When I run Get-RDSessionCollectionConfiguration I see the value has been added to CustomRdpProperty along with "use redirection server name:i:1" which seems to be a default on all collections. What I am trying to solve is, why does my custom RDP property not apply to the RDP files that are downloaded.
When using multiple monitors with Windows Server 2025, the screen flickers
Windows Server 2025, with a graphics card of NVIDIA 5070, and three monitors with different resolutions, all at 60Hz. There is a certain chance of flickering on the screen when using Server 2025. Especially when dragging windows, is there a solution? If I use Windows 11, everything is normalHyperV 12 on Windows 2025 ready for production?
Fighting with three HyperV servers in a failover cluster. I understand that now you have to use SET teaming and lbfo is no longer supported. I also understand that SET is still quite buggy. I have created three teams with two adapters in each of them, but it confuses me how they appear in "Network and internet > Ethernet" vs "Advanced Network setting. I have set the vEthernets to the static IPs that I need. But the way the NIC shows up seems random... Some of them shows the IP of the vEthenets and they are all set to DHCP Network seems very unstable if I use more than one NIC in a team. As far as I can google, I am not the only one having these issues. SET networking does not work stable if more than 1 NIC - correct? So if one needs an HA setup - how to handle NIC teaming correct? Can HyperV 12 on Windows 2025 be used in a prof. live setup? thx...
Windows event collector (WEC) troubles
Hi all. I have really frustrating issue I can`t resolve. We have set up WEC, a long time ago... Now I upgraded in-place to server 2025 and it`s behaving really weird. Problem is this: I created new subscription and my PC was sending events just fine yesterday. I rebooted server and my PC, still all is fine. Turned off my PC, went to sleep, started working in the morning and NO logs from my machine in WEC. At all. Other PCs also randomy sending logs some yes some no. So I tested WinRM connectivity all fine. Error on my PC: The forwarder is having a problem communicating with subscription manager at address http://MYWECSERVER:5985/wsman/SubscriptionManager/WEC. Error code is 2150859263 and Error Message is <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859263" Machine="MYWECSERVER"><f:Message> <f:ProviderFault provider="Subscription Manager Provider" path="%systemroot%\system32\WsmSvc.dll"> <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859263" Machine="MYWECSERVER"> <f:Message>The event source of the push subscription is in disable or inactive on the Event controller server. </f:Message></f:WSManFault></f:ProviderFault></f:Message></f:WSManFault>. I have also some errors on WEC server: The Subscription DomainComputers could not be activated on target machine MY-PERSONAL-PC due to communication error. Error Code is 0. All retries have been performed before reaching this point and so the subscription will remain inactive on this target until subscription is resubmitted / reset. Additional fault message: eventsource is in either disable or inactive state OR The Subscription DomainComputers could not be activated on target machine MY-PERSONAL-PC due to communication error. Error Code is 20. All retries have been performed before reaching this point and so the subscription will remain inactive on this target until subscription is resubmitted / reset. Additional fault message: eventsource is in either disable or inactive state Also runtime status is like this: A lot of Active computers, mine is in yellow Inactive state... I have NO idea how to fix this, and why it works for some clients and not for others and most perplexing question, why it worked yesterday until sleep. Just like that WEC sets status to Inactive and then my PC sends logs and does not change status back to Active. Thanks for all suggestions!
Untagged VLAN - Server 2025 Hyper-V
Hi, I have a strage issue and not finding a solution. Using Server 2025 with two node Hyper-V cluster. Most of the machines using VLANs which works fine. Some machines using no VLAN config. Which usually means the "Access VLAN 1" regarding our switch configuration. With Server 2019 this worked fine. With Server 2025 same NIC port, same server/NIC hardware "Untagged" VMs don't get any network connection. If I add a second NIC to the VM "Untagged" the NIC get immidiatly an IP address and has a proper connection. If I remove the first NIC, the second NIC stop working. It looks like something has changed with Server 2025 (maybe already with Server 2022). Do you have any idea what kinde of problem I have found? Thanks Jack