[Solved] Error Code FFFC with windows update on custom Self extracting EXE install

Topics: Publishing Issue
Dec 26, 2013 at 10:49 PM
I have a custom self extracting exe build with 7zip that will extract itself and run a batch file inside it to install something. I can double click on the exe and everything works fine. Through WSPP custom install, the client tries to update this and fails with error code FFFC. Any idea what is wrong?
Coordinator
Dec 27, 2013 at 9:30 AM
Please select the update in WPP, and click on the link beside the 'Id' label. This will open a window, open the folder and open the .xml file. Copy the content of the file and paste it here.
Coordinator
Dec 27, 2013 at 7:09 PM
'FFFC' is a FileNotFound Exception. Please send me the .XML file to see where is the probleme.
Marked as answer by DCourtel on 1/17/2014 at 7:52 AM
Mar 5, 2014 at 7:46 AM
I Also have this problem, please find be XML file below
<CustomUpdate>
<Action>
<ElementType>CustomUpdateElements.VariableElement</ElementType>
<Name>Return Code</Name>
<Type>Int</Type>
<ID>e66a35b0-fa4f-4aed-a349-6f312356dba5</ID>
</Action>
<Action>
<ElementType>CustomUpdateElements.ServiceElement</ElementType>
<ServiceAction>Stop</ServiceAction>
<ServiceName>JavaQuickStarterService</ServiceName>
<PathToEXE></PathToEXE>
<StartupMode>Undefined</StartupMode>
<StartingAccount>Undefined</StartingAccount>
<Login></Login>
<Password></Password>
</Action>
<Action>
<ElementType>CustomUpdateElements.ExecutableElement</ElementType>
<PathToExecutable>D:\CustomUpdates\jdk-7u51-windows-x64.exe</PathToExecutable>
<Parameters>/s IExplorer=1</Parameters>
<KillProcess>True</KillProcess>
<TimeBeforeKilling>10</TimeBeforeKilling>
<Variable>e66a35b0-fa4f-4aed-a349-6f312356dba5</Variable>
</Action>
<Action>
<ElementType>CustomUpdateElements.WaitElement</ElementType>
<Wait>30</Wait>
</Action>
<Action>
<ElementType>CustomUpdateElements.ExecutableElement</ElementType>
<PathToExecutable>C:\Windows\System32\msiexec.exe</PathToExecutable>
<Parameters>/x {4a03706f-666a-4037-7777-5f2748764d10} /qn /norestart</Parameters>
<KillProcess>True</KillProcess>
<TimeBeforeKilling>10</TimeBeforeKilling>
<Variable/>
</Action>
<Action>
<ElementType>CustomUpdateElements.WaitElement</ElementType>
<Wait>30</Wait>
</Action>
<Action>
<ElementType>CustomUpdateElements.ServiceElement</ElementType>
<ServiceAction>Stop</ServiceAction>
<ServiceName>JavaQuickStarterService</ServiceName>
<PathToEXE></PathToEXE>
<StartupMode>Undefined</StartupMode>
<StartingAccount>Undefined</StartingAccount>
<Login></Login>
<Password></Password>
</Action>
<Action>
<ElementType>CustomUpdateElements.ServiceElement</ElementType>
<ServiceAction>ChangeStartingMode</ServiceAction>
<ServiceName>JavaQuickStarterService</ServiceName>
<PathToEXE></PathToEXE>
<StartupMode>Disabled</StartupMode>
<StartingAccount>Undefined</StartingAccount>
<Login></Login>
<Password></Password>
</Action>
<Action>
<ElementType>CustomUpdateElements.ReturnCodeElement</ElementType>
<ReturnCodeMethod>Variable</ReturnCodeMethod>
<StaticReturnCode>0</StaticReturnCode>
<Variable>e66a35b0-fa4f-4aed-a349-6f312356dba5</Variable>
</Action>
</CustomUpdate>
Mar 5, 2014 at 9:01 AM
I solved the problem, I placed the update "jdk-7u51-windows-x64.exe" in the location of installation files of WPP, then i modified the PathToExecutable And it worked