Pinned Posts
Forum Widgets
Latest Discussions
Azure Migrate Physical Server Discovery - ServerDiscoveryService.exe Crash Bug
Summary The Azure Migrate appliance for physical server discovery fails to complete discovery due to a crash bug in ServerDiscoveryService.exe. The service successfully connects to target servers but crashes during WSMan transport cleanup before any discovery data is collected. Environment Appliance OS: Windows Server 2022 Standard Evaluation (Build 20348) Appliance Type: Physical server discovery (script-based installation) ServerDiscoveryService.exe Version: 2.0.3300.663 .NET Version: 8.0.22 (CoreCLR 8.0.2225.52707) Target Servers: Windows Server (various) and Linux, all on-premises Discovery Agent Version: 2.0.03300.663 Appliance Configuration Manager Version: 6.1.294.1847 Symptoms Target server validation succeeds in the appliance configuration manager CIM sessions connect successfully (logs show "TestConnection succeeded for CIM Session with HTTP protocol") Connections are immediately disposed with "Disposing all connections when the process is shutdown" No discovery data is collected Azure portal shows error 60001 with misleading "Could not load file or assembly 'Microsoft.Management.Infrastructure'" message Discovery status remains "Discovery Incomplete" for all Windows servers Root Cause The ServerDiscoveryService.exe process crashes repeatedly with an unhandled NullReferenceException in the WSMan transport finalizer. This is visible in the Windows Application Event Log: Application: ServerDiscoveryService.exe CoreCLR Version: 8.0.2225.52707 .NET Version: 8.0.22 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException: Object reference not set to an instance of an object. at System.Management.Automation.Remoting.Client.BaseClientTransportManager.CloseAsync() at System.Management.Automation.Remoting.Client.WSManClientSessionTransportManager.CloseAsync() at System.Management.Automation.Remoting.Client.BaseClientTransportManager.Finalize() The crash also triggers an access violation: Faulting application name: ServerDiscoveryService.exe, version: 2.0.3300.663 Exception code: 0xc0000005 Faulting application path: C:\Program Files\Microsoft Azure Server Discovery Service\ServerDiscoveryService.exe These crashes occur approximately every 10 minutes. Troubleshooting Completed Verified manual connectivity works: PowerShell Invoke-Command and New-CimSession both succeed from the appliance to target servers using the same credentials Verified WinRM configuration: Targets have WinRM HTTP listener on port 5985, LocalAccountTokenFilterPolicy is set to 1 Verified assemblies exist: Microsoft.Management.Infrastructure.dll is present in the GAC on both the appliance and target servers Tested both FQDNs and IP addresses: Same failure occurs with both Tested both local and domain credentials: Same failure with properly formatted credentials (domain\user) Verified time synchronization: Appliance clock is accurate Verified appliance is up to date: All components show current versions Tested with fresh appliance: Previously tried OVA-based appliance with similar results; rebuilt using Microsoft's PowerShell script installer on clean Server 2022—same issue Relevant Log Locations C:\ProgramData\Microsoft Azure\Logs\ConfigManager\ClientOperations_*.log - Shows successful CIM connections followed by immediate disposal C:\ProgramData\Microsoft Azure\Logs\ConfigManager\ApplianceOnboarding-Portal-*.log - Shows error 60000 "UnhandledException" with message "Internal error occured." (note: typo is in original) Windows Event Log (Application) - Contains the actual crash stack traces Conclusion This is a code defect in ServerDiscoveryService.exe—a null reference exception in a finalizer is a programming error that cannot be caused by configuration or environmental factors. The service connects successfully but crashes before completing its work. Request Please escalate to the Azure Migrate engineering team for a bug fix in ServerDiscoveryService.exe version 2.0.3300.663.
LAB: Set up DR for SQL in Azure VM by using Always on feature
Why create DR for SQL in azure VMs? Creating a disaster recovery (DR) plan for SQL Server in Azure Virtual Machines (VMs) is crucial to ensure business continuity and data protection. Azure VMs offer flexible and scalable solutions for high availability and disaster recovery, such as Always On availability groups, failover clustering, and geo-replication. These features help minimize downtime and data loss during unexpected events, ensuring that your SQL Server databases remain accessible and resilient. By leveraging Azure's built-in DR capabilities, organizations can meet their recovery time objectives (RTO) and recovery point objectives (RPO), safeguarding critical business operations. Architectural diagram Steps Create two SQL Server VM, one for on-premises and another for azure (for sake of lab I am creating both in azure vm. The experience is same for both scenario) Follow the below steps in both SQL VMs to prep for DR. Set domain for sql servers Restart VM (Very Important to make changes effective) Make sure the sql servers are joined to same domain system--> Advanced setting--> computer name-->Change domain Restart VM Create Secondary VM using SQL supported image ( I am selecting standard SQL edition option) Add roles and features In Features select Failover clustering Complete installation Enable Always on feature Repeat step for both VMs Create a primary db in SQL1 In primary create test database and add data -- Create the database CREATE DATABASE userdatabase; -- Switch to the new database USE userdatabase; -- Create the table CREATE TABLE userinfo ( email VARCHAR(255) NOT NULL, name VARCHAR(255) NOT NULL ); -- Insert dummy data into the userinfo table INSERT INTO userinfo (email, name) VALUES ('john.doe@example.com', 'John Doe'); INSERT INTO userinfo (email, name) VALUES ('jane.smith@example.com', 'Jane Smith'); INSERT INTO userinfo (email, name) VALUES ('alice.jones@example.com', 'Alice Jones'); INSERT INTO userinfo (email, name) VALUES ('bob.brown@example.com', 'Bob Brown'); SELECT * from userinfo Create cluster Create Availability group Now you can see both servers are part of same availability group test failoverRegister now for the Migrate to Innovate Summit
Join the summit on March 11, presented in partnership with Intel. Stay agile, innovate for the future, and maintain a competitive edge by accelerating your cloud migration and modernization journey. Microsoft thought leaders will discuss the latest news and trends, showcase real-world case studies, and share how Azure can help you fully embrace AI. Join us to: Maximize business value and build the foundation for successful innovation by leveraging the latest Azure and Intel capabilities for your workloads. Dive into case studies and real-world examples showcasing how organizations have successfully transformed their business and how you can be next by migrating and modernizing on Azure. Make sure your cloud migration and modernization journey is using the best practices and strategies featured in product demonstrations. Register now > Migrate to Innovate Summit Tuesday, March 11, 2025 9:00 AM–11:30 AM Pacific Time (UTC-7)Digital event: The Future of VMware Is in Azure – July 16th, 2024
Take a deep dive into options for migrating and optimizing your workloads in a rapidly evolving VMware landscape. Join this free digital event and learn how Azure VMware Solution can support your VMware workloads while minimizing migration disruption. Register for this event with technical sessions for VMware administrators such as: Security—with topics on securing the management plane, role-based access control, patch management, and integration with Microsoft Defender for Cloud and Azure VMware Solution. Networking—with topics on hub-and-spoke vs. mesh network design, securing network traffic, traffic and networking monitoring, and hybrid deployments. Disaster recovery and resiliency—with topics on replication and cold site setup, business continuity, and easier vSphere migration with Azure VMware Solution. VMware integration with Azure services—with topics on data warehousing and data lakes, AI and machine learning analytics, DevOps solutions, and automation and lifecycle management. Join us for talks from industry leaders, technical sessions, and live Q&A. Register now > The Future of VMware Is in Azure Tuesday, July 16, 2024 9:00 AM–10:30 AM Pacific Time (UTC-7)Azure Migrate availability for Southeast Asia
Just to check whether any of you facing any issue on testing Azure Migrate in Southeast Asia region ? I'm facing a issue where the Azure Migrate dashboard can't identify the "source appliance" that configured and discovering the VMs on source location, which causing problem on setting up "Target appliance".Digital event—Migrate to Innovate: Be AI Ready, Be Secure
Learn how to fuel innovation and maintain a competitive edge with a secure, optimized, and agile foundation on Azure. Join this free digital event to see how migrating Windows Server and SQL Server to Azure helps prepare your organization to embrace AI and cloud-native services while addressing current business challenges, including saving costs and maintaining security. Register now to learn about the business outcomes of migrating to Azure, including: AI readiness: Get results with an AI-ready foundation on Azure. In a study of customers using Azure AI services, a composite of six organizations achieved a three-year ROI of 284%. Code-to-cloud security: Reduce risk and costs by replacing multiple third-party security tools with comprehensive, multilayered security. Maximizing ROI and performance: Run your workloads faster and at a lower cost. AWS is up to 5 times more expensive than Azure for Windows Server and SQL Server—and SQL Server runs up to 5.5 times faster on Azure than on AWS. Cloud agility anywhere: Help secure and govern your entire digital estate across hybrid, multicloud, and edge environments on your own terms using an adaptive cloud approach. Register now > Migrate to Innovate: Be AI Ready, Be Secure Tuesday, April 16, 2024 9:00 AM–11:00 AM Pacific Time (UTC-7)
Azure Data Factory is not bringing me Dataverse table virtual fields
I have an Azure Data Factory with a connection to Dataverse but when I create table sources to use in my pipelines I don't get the virtual fields from my dataverse lookups. For example I have a lookup to account in opportunity table, yo obtengo estos campos account: 0000-0000-0000-0000 accountname: null accountyominame: null I dont know if this is a recent error or ADF has always worked this way.Azure Site Recovery UUID Issue
Hello Team, I'm currently working with a customer who's using Azure Site Recovery (ASR) for disaster recovery in a VMware environment. They've encountered an issue where the software licenses, which are tied to the VM UUIDs, are not being validated because ASR doesn't retain the original UUIDs during replication. Has anyone faced a similar issue or have any suggestions on how to handle this? Any guidance or shared experiences would be greatly appreciated.Microsoft at Oracle CloudWorld in Las Vegas
Microsoft has a presence at Oracle CloudWorld 2023! Last week Microsoft announced their partnership with Oracle to bring Oracle database services to Azure with Oracle Database@Azure. Customers will be able to migrate mission-critical databases directly to Azure, where they can easily integrate with services like Azure Open AI, Microsoft Fabric, and Microsoft Power BI. Check out the blog here: Join Microsoft at Oracle CloudWorld in Las Vegas - Microsoft Community Hub How will you be taking advantage of this integration? Will you be attending Oracle CloudWorld 2023?Error Set-webConfigurationProperty cmdlet not recognized
I am trying to deploy Azure Migrate Installer. When I run it for the first time, I get the following: Installing C:\Install\AzureMigrateInstaller\MicrosoftAzureApplianceConfigurationManager.msi... [OK] [Script execution failed with error] The term 'Set-WebConfigurationProperty' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. [Exception caught] The term 'Set-WebConfigurationProperty' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again..Exception Retry executing the script after resolving the issue(s) or contact Microsoft Support. I first tried this on a machine that did not run IIS. I also tried it on a machine that was running IIS 10, and got the same results. What can I do to fix this issue. I am running it in the same directory as the AzureMigrateInstaller.psi.
