{"id":125,"date":"2017-08-20T11:59:18","date_gmt":"2017-08-20T15:59:18","guid":{"rendered":"http:\/\/ziviz.us\/WP\/?p=125"},"modified":"2017-10-14T23:34:58","modified_gmt":"2017-10-15T03:34:58","slug":"adobe-update-server-sync-issues","status":"publish","type":"post","link":"https:\/\/www.ziviz.net\/WP\/2017\/08\/20\/adobe-update-server-sync-issues\/","title":{"rendered":"Adobe Update Server Sync Issues"},"content":{"rendered":"<p>I was setting up an Adobe Update Server using the Adobe Update Server Setup Tool, and it was just not working. It kept failing with error codes 2 and 4 in the console. I was pretty sure that it was our proxy that was causing the grief.<\/p>\n<p>I opened procmon and monitored the AUSST tool, I found that it was not even attempting to use the proxy. I checked the C:\\Users\\&lt;user&gt;\\AppData\\Local\\Temp\\AdobeUpdaterServerSetupTool.log but only found what the console was telling me. General network issues. In procmon however, I seen it was writing to a C:\\Users\\&lt;user&gt;\\AppData\\Local\\Temp\\CreativeCloud\\ACC\\AdobeDownload\\DLM.log. The console does not tell you about it however. I opened that one up and got a little further, though not much. It did give a better error then just network issues though. This time it gave me &#8220;failed to resolve the proxy setting on the machine&#8221; along with error 12180. If you look up 12180, it largely repeats the last error, just that the proxy settings failed. Finally out of desperation I was changing the proxy settings manually and found that, if &#8220;Auto Detect&#8221; was checked in your proxy settings, then AUSST would just give up proxy, whether you have a pac file, or manually entered proxy settings or not.<\/p>\n<p>I immediately ran into another issue. This one was a bit easier to troubleshoot. It was still failing to download files, but at least it actually made connections. In AdobeUpdaterServerSetupTool.log I seen &#8220;Failed to download icons&#8221;, &#8220;Failed to complete migration&#8221; and &#8220;Internal error occurred&#8221;. Now that I knew about the DLM.log, I checked that too. That was spitting out error 12175. This was again more helpful than the AdobeUpdateServerSetupTool.log&#8217;s output. If you look that error up, it roughly translates to SSL error occurred. I popped open WireShark and decided to see if I could find any handshake errors or anything else. I did not, but I did find the URL of the file that the machine was attempting to contact. I put that URL directly into Internet Explorer and immediately was met with a SSL trust error. The Root certificate for Adobe was not installed on the machine. I imported the cert and tool started working after that.<\/p>\n<p><strong>TLDR;<\/strong><\/p>\n<p>If you get general network type errors in AdobeUpdaterServerSetupTool.log and error 12180\/&#8221;failed to resolve the proxy setting on the machine&#8221; in the DLM.log, uncheck &#8220;Auto Detect&#8221; in your proxy settings<\/p>\n<p>If you get http security\/12175 in DLM.log and possibly &#8220;Failed to download icons&#8221;, &#8220;Failed to complete migration&#8221; and &#8220;Internal error occurred&#8221; in AdobeUpdaterServerSetupTool.log, ensure you don&#8217;t have any issues trusting Adobe&#8217;s cert chain used on their update server.<\/p>\n<p><strong>Update:<\/strong> I had an additional issue with our update server. You can read it and some general client-side troubleshooting steps <a href=\"http:\/\/ziviz.us\/WP\/2017\/10\/14\/additional-adobe-update-server-issues\/\">in this post.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I was setting up an Adobe Update Server using the Adobe Update Server Setup Tool, and it was just not working. It kept failing with error codes 2 and 4 in the console. I was pretty sure that it was our proxy that was causing the grief. I opened procmon and monitored the AUSST tool, &hellip; <a href=\"https:\/\/www.ziviz.net\/WP\/2017\/08\/20\/adobe-update-server-sync-issues\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Adobe Update Server Sync Issues&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-125","post","type-post","status-publish","format-standard","hentry","category-sysadmin"],"_links":{"self":[{"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/posts\/125","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/comments?post=125"}],"version-history":[{"count":4,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/posts\/125\/revisions"}],"predecessor-version":[{"id":132,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/posts\/125\/revisions\/132"}],"wp:attachment":[{"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/media?parent=125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/categories?post=125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ziviz.net\/WP\/wp-json\/wp\/v2\/tags?post=125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}