cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Download Failed

Download Failed

Summary

This article will explain how to overcome a 'Download Failed' error when checking for updates.

Symptoms

When checking for updates with the agent.exe using the following command line:

agent.exe -sn{F8C68CD6-1317-4C1E-B554-B9325DADBA91}, appmenu

The following error may appear:

FNCError

Cause

This can be caused by the 'Server' line in the {Product_Guid}.ini being missing/incorrect or the port number is missing/incorrect. In the example below the port number should be set to '80'.

[Main]
ScheduleInterval=30
Instances=Default
Segment=829
Version=1.00.0000
MessageFilter=-1
LastCheckPerformed=3/9/2015
LanguageID=1033
RecordDemographics=1
PRODUCTLINK=ZCEFCC78F6EFC77C8F9ACE7E889AB978FD9DC978FFEEBF748CEDBA7A8A98C90AFC9FBC0A899AC
Server=http://spock:8099/
[UID]
ALL=1
[NewMsgs]
1002=0
1003=0





Resolution

Check the {Product_Guid}.ini on the client machine and make sure the 'Server' line is pointing to the notification server URL and using the correct port number. In the example below the port number is set back to '80'.

[Main]

ScheduleInterval=30
Instances=Default
Segment=829
Version=1.00.0000
MessageFilter=-1
LastCheckPerformed=3/9/2015
LanguageID=1033
RecordDemographics=1
PRODUCTLINK=ZCEFCC78F6EFC77C8F9ACE7E889AB978FD9DC978FFEEBF748CEDBA7A8A98C90AFC9FBC0A899AC
Server=http://spock:80/
[UID]
ALL=1
[NewMsgs]
1002=0
1003=0

*Note: the {Product_Guid}.ini files can be found in the following directory, '
C:\ProgramData\FLEXnet\Connect\Database' on a client machine.
Labels (1)
Was this article helpful? Yes No
No ratings
Version history
Revision #:
1 of 1
Last update:
‎Nov 06, 2018 10:56 PM
Updated by: