We have 2ePO servers in our environment, ePO 4.6 Patch 2 and ePO 4.6 Patch 3. I have scheduled the task for downloading Software product list 4 times in day and evening. but it fails atleast 2 or 3 times before downloading the product list successfully. I have observed this behavior on both ePO 4.6 P1 and P3. when i run the task manually it downloads successfully always. There is no proxy server or firewall blocking the conection, also i can ping to epo.mcafee.com and telnet to port 443. there is no other error in ePOAppsrvr logs other than the below,
|9/4/12 1:59:46 PM||Started: Download Software Product List|
|9/4/12 1:59:51 PM||Downloading file C:\PROGRA~1\McAfee\EPOLIC~1\DB\licensed_products_list.xml.tmp.|
|9/4/12 1:59:51 PM||Downloading file C:\PROGRA~1\McAfee\EPOLIC~1\DB\trial_products_list.xml.tmp.|
|9/4/12 2:01:56 PM||Failed to download file C:\PROGRA~1\McAfee\EPOLIC~1\DB\licensed_products_list.xml.tmp. There was an error connecting to the server (12030).|
|9/4/12 2:01:56 PM||Failed to download file C:\PROGRA~1\McAfee\EPOLIC~1\DB\trial_products_list.xml.tmp. There was an error connecting to the server (12030).|
|9/4/12 2:01:56 PM||Failed to connect to the Software Catalog server.|
|9/4/12 2:01:56 PM||Completed: Download Software Product List (Failed to download the products list due to "Failed to connect to the Software Catalog server.")|
any help would be appreciated!
As far as I know this is happening on almost every ePO server I installed with any patch so it must be something at McAfee's site (perhaps overload or something similar...)
so i guess this is a known issue, but i don't see it documented anywhere in the known issues list of ePO 4.6 patches.
anyone from McAfee got any answer for this issue ? it would be nice to know the real reason for this unexplained problem!
On a cursory search i'm not actually finding support cases being opened in regards to this.
If you are finding issues, please open a case with McAfee support so it can be investigated.
If anyone has already done so, please share the case numbers if you can so the present status can be dug out for the thread.
We recently upgraded from ePO 4.5.4 to 4.6.4 and sure enough, the same issue stated above began occuring. I had the exact same error. Then I saw pierce's post here and DING! It worked after editing the server task, saving and re-running.