Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
Azure Migrate Question - Replication appliance keeps showing credentials error for MSSQLSERVER
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 73%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKP%3C/text%3E%3C/svg%3E)
Kerry Primm
0
Reputation points
Despite using domain admin credentials, I am getting a MSSQLSERVER error in the action center after running discovery from the VM hosting the replication appliance. I initially tried creating a local admin account on the target physical server that I am trying to migrate, but kept getting a WinRM error and it validated my domain credentials first try so I left that behind. Is that the fix? To get winRM working with local admin credentials? Please note, the SQL slider was turned off on my last attempt and it still flagged the MSSQLSERVER credentials. The servers are on Server 2016, and I have been going the 'recommended' moderized replication .zip. But when I tried opening a ticket with Microsoft it asked if I was using Server 22, and instantly stopped me from opening a ticket with a red exclamation point and said "upgrade to Windows Server 2022". Is that why I am experiencing this? The appliance configuration manager gives me all green check marks, but I keep getting the action item described above that wont let me move onto the mobility appliance.
Any advice is appreciated.
Thanks!
Kerry
Azure Migrate
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 72%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENP%3C/text%3E%3C/svg%3E)
Naveena Patlolla 7,500 Reputation points Microsoft External Staff Moderator2025-12-02T07:23:17.96+00:00 Hi Kerry Primm
Please try the below troubleshooting steps:
- Validate Your Credentials: Even though you're using domain admin credentials, ensure that the credentials provided for your SQL Server are indeed valid. You can go to the appliance configuration manager and try re-validating the credentials you have set up.
- WinRM Configuration: If you're getting a WinRM error when attempting to use local admin credentials, making sure that WinRM is configured correctly is crucial. You might want to enable WinRM on the physical server to allow communication. You can do this by running the following command in an elevated PowerShell prompt on the target server:
winrm quickconfig - Check SQL Discovery Settings: Since you mentioned that the SQL slider was turned off, make sure that you have the correct settings configured to enable SQL Server discovery. You might need to provide specific credentials for SQL Server if needed.
- Windows Server Version: The warning about needing to upgrade to Windows Server 2022 might be relevant because certain features and functionalities in Azure Migrate can depend on OS versions. If upgrading is an option for you, that might alleviate some of the issues you're encountering.
- Monitor Action Center: Keep an eye on the Action Center for any specific error messages during the discovery process. These messages can provide clues on what might be going wrong.
- Reboot and Retry: Sometimes a simple reboot of the appliance and the target server can resolve lingering connectivity issues. After rebooting, try running the discovery again.
References:
- Resolve server migration replication issues in Azure Migrate
- Provide server credentials to discover SQL Server instances and databases
- Troubleshooting ongoing server discovery
- Common SQL Server instances and database discovery errors
Please let me know if you face any challenge here, I can help you to resolve this issue further
If the solution was helpful, please click "Upvote"
-
Naveena Patlolla 7,500 Reputation points Microsoft External Staff Moderator
2025-12-03T12:45:45.1+00:00 Hi Kerry Primm
Just want to check if the solution worked for you or else please let us know if any help, we are always here to help whenever you need us.
Sign in to comment
Sign in to answer