The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click here for more information.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ERROR: The remote name could not be resolved

jrobs3
By
Level 4

It would appear our old SCCM Server still referenced somewhere when attempting to DeleteESDObjects. The Error Logs indicate "The remote name could not be resolved: <old sccm servername>" and refer to the DeleteESDOjects.log. Upon checking the log, it says:
"Connecting to  //<old sccm servername>/ESDWebService/ESDWebService.asmx
Time out 120000
Failed to delete collection PS1002B7"
then a couple lines stating database update complete, then "Error deleting collection PS1002B7 The remote name could not be resolved: '<old sccm servername>'
Is there a Database table where I can delete this collection from trying to clean up on the old server? I have no idea what would even be referencing the old server. The Admin|Settings|Deployment configuration is set to the new one and has been for some time. 

(1) Solution

CharlesW
By Level 12 Flexeran
Level 12 Flexeran
The cleanup routine for old collections/deployments is driven off the table WD_SiteToAdvert. This table stores the mappings between catalog items and the collections/deployments associated with those catalog items.. The easiest way to resolve this would be to run the following query:

delete from wd_SiteToAdvert where server = '<old sccm servername>'

Technically, to stop the error, all you would really have to do is set the column flagForDelete=0, but since these entries referencing the old server are pointing to an effectively dead server, there is no real reason to keep them around.

View solution in original post

(2) Replies

CharlesW
By Level 12 Flexeran
Level 12 Flexeran
The cleanup routine for old collections/deployments is driven off the table WD_SiteToAdvert. This table stores the mappings between catalog items and the collections/deployments associated with those catalog items.. The easiest way to resolve this would be to run the following query:

delete from wd_SiteToAdvert where server = '<old sccm servername>'

Technically, to stop the error, all you would really have to do is set the column flagForDelete=0, but since these entries referencing the old server are pointing to an effectively dead server, there is no real reason to keep them around.

Thank you, Charles! That worked like a charm. Greatly appreciated.