Did you update the AI certificate? I think a new one came out about a month or 
so ago.

-Stephen

> On Jul 8, 2015, at 10:25 AM, Krueger, Jeff <[email protected]> wrote:
> 
> It seems our asset intelligence synchronization point is no longer working.  
> It was working before but now we see the below on the Asset Intelligence node 
> in the console, and getting errors in the AIUpdateSvc.log.  All the posts I 
> find on this seem to point to proxy issues, but we have a proxy server 
> configured in the site settings and have no problem syncing software updates…
>  
> <image003.jpg>
>  
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:31:26 GMT:Already 4 retries, clearing retry schedule
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:31:26 GMT:1 Data/Status copied to outbox
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:46:26 GMT:Reading persisted settings from registry
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:46:26 GMT:Using proxy: Server=http://prxyserveraddress:9090/, 
> Credentials=default
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:46:26 GMT:Sync Now detected
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:46:26 GMT:Next scheduled sync time: 07/12/2015 00:00:00; Polling 
> Interval:900 seconds
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:46:26 GMT:Authentication: Did not find machine certificate in ALM store
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:46:26 GMT:Enrollment Certicate Path is empty, use bootstrap cert
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:46:26 GMT:Created bootstrap cert from byte array
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:46:26 GMT:[Subject]
>   CN=e72756d8-8fe6-4bdd-90cb-31470ef06e18
> [Issuer]
>   CN=CatalogServiceIssuingCert.manage.microsoft.com
> [Serial Number]
>   #########################
> [Not Before]
>   6/19/2012 4:03:31 PM
> [Not After]
>   6/19/2015 4:03:30 PM
> [Thumbprint]
>   ########################
> Asset Intelligence Catalog Sync Service Warning: 0 : Wed, 08 Jul 2015 
> 14:48:06 GMT:WebException trying to enroll: Status = Timeout
> Asset Intelligence Catalog Sync Service Error: 0 : Wed, 08 Jul 2015 14:48:06 
> GMT:Retrieve Machine Cert, Error - The operation has timed out
> Asset Intelligence Catalog Sync Service Error: 0 : Wed, 08 Jul 2015 14:48:06 
> GMT:Exception attempting sync - The operation has timed out
> Asset Intelligence Catalog Sync Service Information: 0 : Wed, 08 Jul 2015 
> 14:48:06 GMT:Exception details:
> Microsoft.AssetIntelligence.CatalogSyncException: The operation has timed out 
> ---> System.Net.WebException: The operation has timed out
>    at System.Net.HttpWebRequest.GetResponse()
>    at Microsoft.AssetIntelligence.CatalogService.ProcessRedirection(Uri uri)
>    at Microsoft.AssetIntelligence.CatalogService.GetWebRequest(Uri uri)
>    at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String 
> methodName, Object[] parameters)
>    at Microsoft.AssetIntelligence.CatalogService.Enroll(String 
> enrollmentRequest)
>    at Microsoft.AssetIntelligence.SyncAdapter.Enroll(X509Certificate2 
> bootstrapCert)
>    --- End of inner exception stack trace ---
>    at Microsoft.AssetIntelligence.SyncAdapter.Enroll(X509Certificate2 
> bootstrapCert)
>    at Microsoft.AssetIntelligence.CatalogUpdateSvc.RetrieveMachineCert()
>    at Microsoft.AssetIntelligence.CatalogUpdateSvc.DoWork()
> 
> 
> 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