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 ...
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.
I am trying to update just the ActiveX control.
My version.xml says:
<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"/>
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_al l_win_pl_sgn.z
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.
--edited to fix typo
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.