Copy link to clipboard
Copied
Hi,
I would like to provide Flash Player updates for my PCs using an interal update server.
mms.cfg
AutoUpdateDisable=0
SilentAutoUpdateEnable=1
SilentAutoUpdateServerDomain=server.domain.local
SilentAutoUpdateVerboseLogging=1
FlashInstall.log
2014-2-26+14-57-58.949 [info] 1628 server.domain.local
2014-2-26+14-57-58.949 [info] 1629 server.domain.local
2014-2-26+14-57-58.949 [info] 1614
2014-2-26+14-57-58.949 [info] 1615
2014-2-26+14-57-58.949 [info] 1618
2014-2-26+14-57-58.949 [info] 1619 1063
2014-2-26+14-57-58.980 [info] 1628 server.domain.local
2014-2-26+14-57-58.980 [info] 1629 server.domain.local
2014-2-26+14-57-58.980 [info] 1614
2014-2-26+14-57-58.980 [info] 1615
2014-2-26+14-57-58.980 [info] 1618
2014-2-26+14-57-58.980 [info] 1608
2014-2-26+14-57-58.980 [info] 1604
2014-2-26+14-57-58.996 [info] 1630 /pub/flashplayer/update/current/sau/11/xml/version.xml
2014-2-26+14-57-59.105 [info] 1630 /pub/flashplayer/update/current/sau/11/xml/patch.xml
2014-2-26+14-57-59.371 [warning] 1449
2014-2-26+14-57-59.371 [info] 1600
2014-2-26+14-57-59.433 [error] 1217 -2146881269
2014-2-26+14-57-59.433 [error] 1234 183
2014-2-26+14-57-59.433 [info] 1612
2014-2-26+14-57-59.433 [info] 1620
Because the update is not working it would be very helpful to get a list of all those status codes inside the FlashInstall.log
Are there any suggestions what to do?
Thank you for your help.
Copy link to clipboard
Copied
Please check this admin guide.
http://www.adobe.com/devnet/flashplayer/articles/flash_player_admin_guide.html
Copy link to clipboard
Copied
Thank you for your reply.
I have already checked the admin guide and if you can see any hint in there that could help me, I would be very happy if you could tell me.
I have NO idea what those error codes mean, this is why I am asking for a table of error codes.
If I had such a table I would be able to investigate where my mistake is.
But without it, its just guessing ...
Copy link to clipboard
Copied
Hello,
Error 1217 = failed to validate signature, but it could be misleading, and 1234 = ActiveX update failed.
Are you only updating only the ActiveX control, or both the ActiveX control and the Plugin?
Please post the contents of the version.xml file and list the directory structure of how you have the files posted in your internal server.
Thank you.
--
Maria
Copy link to clipboard
Copied
Hello,
I am trying to update just the ActiveX control.
My version.xml says:
<?xml version="1.0"?>
<version>
<ActiveX major="12" minor="0" buildMajor="0" buildMinor="70"/>
<Plugin major="12" minor="0" buildMajor="0" buildMinor="70"/>
<MacPlugin major="12" minor="0" buildMajor="0" buildMinor="70"/>
<SAUConfig checkFrequency="1"/>
</version>
Folder structure:
\\SERVER\C$\XAMPP\HTDOCS\PUB
\---flashplayer
\---update
\---current
\---sau
\---11
+---install
| install_all_win_64_ax_sgn.z
| install_all_win_64_pl_sgn.z
| install_all_win_ax_sgn.z
| install_all_win_pl_sgn.z
|
\---xml
patch.xml
version.xml
Thank you for your help.
PS: I am not using 12 as fp-major-version because of 404 @ http://fpdownload2.macromedia.com/pub/flashplayer/update/current/sau/12/install/install_all_win_pl_s...
Copy link to clipboard
Copied
Hi,
You're directory structure is correct. It should be '11' regardless of actual fp-major-version.
The 'Background updates from an internal server' section of the Flash Player Administrators Guide (pages 20 & 21) indicates how to configure the directory structure and the files to post.
You do, however, have extraneous files. Please delete the following files:
None of these are included in fp_background_update.cab that we post. Try deleting these, especially the patch.xml.
--
Maria
--edited to fix typo
Copy link to clipboard
Copied
Hi,
Following your suggestions I deleted the mentioned files and found an error in the version.xml:
The line end was in UNIX-mode, but the line end of the version.xml inside fp_background_update.cab is in DOS/Windows-mode.
This is because I downloaded the version.xml directly from http://fpdownload2.macromedia.com/pub/flashplayer/update/current/sau/11/xml/version.xml
After replacing the file the client update completed without problems. So this seems to fix the issue.
Thank you very much for your help.