In the example below the server’s IP address is 10.22.5.231 and its NETBIOS name is WRKGRP1.
When I target this device I get the same error message we were seeing yesterday:
Notice at the end of the error message we see the devices name: WRKGRP1.WORKGROUP. SQL does not recognize this name:
So how do we get SQL to recognize it, we add a SQL alias in the SQL Server config manager AND there’s no need to restart the service:
Now look what happens when I target the server again, the connection error is gone:
Movere can now connect to SQL and it is capturing data down to the database level (e.g. State = “ONLINE”):
One thing worth noting, you may still see a log shipping error message. This does not impact the scan, it just means Movere can’t query the ‘msdb’ database to see if there are any log shipping settings:
If you want this error message to go away then check the sysadmin box for the NT AUTHORITY\SYSTEM account:
Scan the device again and the error message is gone:
You can then uncheck the sysadmin box after the scan has been completed, but if there are no log shipping settings on this system then you can simply ignore this error message.