Sorry this is going to be a longer one, but I've been dealing with a support 
case for some issues with content distribution that is stuck at an in progress 
status on some DPs on secondary sites.  The support engineer that I've been 
working with has suggested that our secondary site server is having issues 
sending status messages about content distribution to the primary site server 
because it is supposedly trying to talk to the internet based MP.  He's saying 
this based on the ClientLocation.log entries as shown below. I read the log and 
see that it is assigned to the MP off the primary site server, it is getting a 
local and proxy mp of the secondary site server (which is itself) and though it 
is enumerating the MP that it would have if it were on the internet it is not 
getting assigned to it.

Also the support engineer has said that the system is too busy processing 
status messages and they they're backed up and that's why those packages are 
stuck as in progress. Though there is no problem with new content getting 
distributed just a large group that are stuck on 4 server as in progress, new 
packages go to these same servers with no issues.  Where would I find any 
backed up status messages besides the inboxes?  The support engineer queried 
WMI for status messages per DP and said that all the results returned are 
unprocessed.  Is this accurate?  Where else can I check for unprocessed status 
messages? Inboxes on the primary are not backed up, database replication links 
are good. A suggestion was made to turn off content validation as that would 
help the status messages to process faster


>From ClientLocation.log on secondary site server
Domain joined client is in Intranet            ClientLocation   5/20/2014 
6:08:16 PM    5804 (0x16AC)
Rotating assigned management point, new management point [1] is: 
PrimarySite.corp.my.company.com (7958) with capabilities: <Capabilities 
SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>        
        ClientLocation   5/20/2014 6:08:16 PM    5804 (0x16AC)
Assigned MP changed from <PrimarySite.corp.my.company.com> to 
<PrimarySite.corp.my.company.com>.                ClientLocation   5/20/2014 
6:08:16 PM    5804 (0x16AC)
Rotating internet management point, new management point [1] is: 
ConfigMgr.company.com (0) with capabilities: <Capabilities SchemaVersion 
="1.0"><Property Name="SSL" Version="1" /></Capabilities>        ClientLocation 
               5/20/2014 6:08:17 PM    5804 (0x16AC)
Rotating assigned management point, new management point [1] is: 
PrimarySite.corp.my.company.com (7958) with capabilities: <Capabilities 
SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>        
        ClientLocation   5/20/2014 6:08:17 PM    5804 (0x16AC)
Assigned MP changed from <PrimarySite.corp.my.company.com> to 
<PrimarySite.corp.my.company.com>.                ClientLocation   5/20/2014 
6:08:17 PM    5804 (0x16AC)
Rotating proxy management point, new management point [1] is: 
SecondarySite.corp.my.company.com (7958) with capabilities: <Capabilities 
SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>        
        ClientLocation   5/20/2014 6:08:18 PM    5804 (0x16AC)
Rotating local management point, new management point [1] is: 
SecondarySite.corp.my.company.com (7958) with capabilities: <Capabilities 
SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>        
        ClientLocation   5/20/2014 6:08:18 PM    5804 (0x16AC)

Thanks
-Jeff


________________________________

CONFIDENTIALITY NOTICE: This email contains information from the sender that 
may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected 
from disclosure. This email is intended for use only by the person or entity to 
whom it is addressed. If you are not the intended recipient, any use, 
disclosure, copying, distribution, printing, or any action taken in reliance on 
the contents of this email, is strictly prohibited. If you received this email 
in error, please contact the sending party by reply email, delete the email 
from your computer system and shred any paper copies.

Note to Patients: There are a number of risks you should consider before using 
e-mail to communicate with us. See our Privacy & Security page on 
www.henryford.com for more detailed information as well as information 
concerning MyChart, our new patient portal. If you do not believe that our 
policy gives you the privacy and security protection you need, do not send 
e-mail or Internet communications to us.



Reply via email to