Server name is empty in address.

Hi,

 

I am getting this error on one of my DP.

Error is reported in the PkgXferMgr.log on the site server.

Sending thread starting for Job: 33315, package: %PKGID%, Version: 4, Priority: 2, server: %DP-FQDN%, DPPriority: 200

Server name is empty in address.

Couldn't parse the address.

Attempt to connect failed.

Restart time = 7/28/2014 3:29:16 PM Malay Peninsula Standard Time

Sending failed. Failure count = 1, Restart time = 7/28/2014 3:22:16 PM Malay Peninsula Standard Time

 

It started out of the blue as I was distributing multiple packages to the DP. Once it started, all subsequent distributions to this DP failed.

I tried reinstalling the DP (the ConfigMgr role, not the OS), but the problem persists.

 

How do I go about trobuleshooting this?

 

Thanks.

July 28th, 2014 9:57pm

Never heard of anything like this before. I'd add a different computer as a DP to see if that works (even a workstation OS). When you add/re-add the computer, make sure you type the NetBIOS name/FQDN correctly. Ensure that the site server is a local admin on the remote computer (or that you've specified a different connection account).

Of course, as you know, a reboot always resolves everything, so that is something to consider :-)

Free Windows Admin Tool Kit Click here and download it now
July 28th, 2014 10:13pm

Hi,

It is a production environment and I need to fix this particular DP. As for permissions - they are all correct; it was a functioning DP after all.

Reboot didn't help unfortunately.


Thanks.

July 28th, 2014 10:15pm

Well I still suggest trying a different one to see if it is a site server issue or a remote DP issue. And did you reboot the site server, or the remote computer?

You asked for suggestions, and I'm offering some :-) You can choose to try what you want or don't want, but I'm offering what I'd do to try it resolve it.

Free Windows Admin Tool Kit Click here and download it now
July 28th, 2014 10:17pm

And of course, CSS is always an option too.
July 28th, 2014 10:17pm

Recovering the secondary site resolved the issue - seems to be related to databases.
  • Marked as answer by Sysadmin1O1 Monday, July 28, 2014 10:23 PM
Free Windows Admin Tool Kit Click here and download it now
July 28th, 2014 10:23pm

Recovering the secondary site resolved the issue - seems to be related to databases.

Hello all,

I have the same issue, what did you do exactly to resolve that?

Thank's

July 22nd, 2015 4:39am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics