flashplayer.log Warning codes 1474 and 1475

Report · Oct 29, 2014

Hello,

I am using an internal server to push updates to our flash player in a test environment. I have the current version of 15.0.0.189 installed on my client machines, and the same version on my internal server. I am attempting to verify functionality by examining the flashupdate.log file. It seems that everything is working, however i have 2 [warning] codes in my log and I was hoping i could get some assistance in figuring out what they are.

My system info is this:

Client system: Windows 7 Professional 32bit

Client Flash Version: 15.0.0.189

Server System: Windows Server 2012

Server Flash Version: 15.0.0.189

Server File Structure:

An excerpt of my log follows. Obviously the myflashupdate.server is a placeholder for my actual server.

<-----BEGIN LOG---->

2014-10-28+15-46-0.198 [info] 1628 myflashupdate.server

2014-10-28+15-46-0.198 [info] 1629 myflashupdate.servero

2014-10-28+15-46-0.198 [info] 1614

2014-10-28+15-46-0.198 [info] 1615

2014-10-28+15-46-0.214 [info] 1618

2014-10-28+15-46-0.214 [info] 1619 1063

2014-10-28+15-46-0.245 [info] 1628 myflashupdate.server

2014-10-28+15-46-0.245 [info] 1629 myflashupdate.server

2014-10-28+15-46-0.245 [info] 1614

2014-10-28+15-46-0.261 [info] 1615

2014-10-28+15-46-0.261 [info] 1618

2014-10-28+15-46-0.261 [info] 1604

2014-10-28+15-46-0.261 [info] 1608

2014-10-28+15-46-0.276 [info] 1631 /pub/flashplayer/update/current/sau/currentmajor.xml

2014-10-28+15-46-0.354 [warning] 1474 12044

2014-10-28+15-46-0.354 [warning] 1475

2014-10-28+15-46-0.354 [info] 1432

2014-10-28+15-46-0.370 [info] 1612

2014-10-28+15-46-0.370 [info] 1620

2014-10-28+16-46-0.180 [info] 1628 myflashupdate.server

2014-10-28+16-46-0.180 [info] 1629 myflashupdate.server

<----END LOG---->

Does this log mean my updates are working correctly (Aside from trying to pull the same version as the one installed)?

What are the 2 Warning codes?

Thanks you for any and all replies!

Report · Oct 29, 2014

hello,

Error 1474 means the call to /pub/flashplayer/update/current/sau/currentmajor.xml has failed, and 1475 means could not retrieve currentmajor.xml. This indicates that you do not have the curerntmajor.xml file in your directory structure. This is a new file introduced a few releases ago and must exist at the /sau level. I can't determine based on your screenshot if the file is present or not. If not, please download the latest Background Update Resources package from the Adobe Flash Player Distribution | Adobe page and deploy that to your server.

If your version XML files have version 15.0.0.189 in them the Background Update Service will not try to pull down the version posted to the server. It'll determine that the version available is the same as the version installed and terminate the process.

--

Maria

Report · Oct 29, 2014

Thanks for your reply!

I didn't notice somehow that the folders were only listed in my screenshot. the currentmajor.xml is in the sau directory as showcased by the screenshot below. the contents are:

\sau\currentmajor.xml

<version>

<Player major="15" majorBeta="15" />

</version>

\sau\15\xml\version.xml

<?xml version="1.0" ?>

<version>

<ActiveX major="15" minor="0" buildMajor="0" buildMinor="189" />

<Plugin major="15" minor="0" buildMajor="0" buildMinor="189" />

<MacPlugin major="15" minor="0" buildMajor="0" buildMinor="189" />

<SAUConfig checkFrequency="1" />

</version>

Report · Nov 19, 2014

Hello Maria,

I am still having this issue, is there any way i could provide you more information to assist me in solving this?

Report · Nov 19, 2014

Hi,

Are you deploying the files from the package we post to the licensing page, or are you creating the files yourself? The package contains the files in the correct folder structure and should be posted to the server in the /sau directory as they appear in the package, replacing existing files. I would like to examine the files that currently exist on your server. Please send me the files, using the instructions posted here, How to share a document.

Thank you in advance.

--

Maria

Report · Nov 19, 2014

I'd also like to see the network activity when the request is made to the server. Can you use something like Charles Proxy to record the network traffic when the request to the currentmajor.xml file is made and send me the file?

Thank you.

--

Maria

Report · Jul 16, 2015

Did this got solved ? i am having the same errors.. and i cant find anywhere what these codes are about.

Report · Jul 16, 2015

Hi fmcs

This thread is over 7 months old and the OP never replied. I've no idea if they resolved the issue or not. Are you hosting the Background Update resources locally, as the OP?

--

Maria

Report · Jul 17, 2015

Yes, in a local server.All the files are in the right place. ports 80 and 443 open.. self signed certificate installed in the web server and in the clients.. i can see currentmajor.xml in the browser and version.xml also.

i have version 16.0.0.305 installed in the machines and want to update to the last one available. 18.0.0.209

i have searched the all internet and cant find a reason for this.

Report · Jul 17, 2015

Hi FMCS,

Are you using all of the files in the fp_background_update.cab file, or did you you already have the XML files on your local server and edited those instead of using the files from the archive? If the latter, please provide the files you edited (see the 'how to share a document' link below)

What are the permissions on the files on the server? Sometimes when copying/FTPing files, the permissions change.

Please do the following:

Post a screenshot of the directory structure (including files).
Enable Background Update verbose logging by adding SilentAutoUpdateVerboseLoggin=1 to the mms.cfg file at the following location:
- 32-bit OS: C:\Windows\System32\Macromed\Flash
- 64-bit OS: C:\Windows\SysWOW64\Macromed\Flash
Install the previous version (e.g. 16.0.0.305)
Run the SAU Service
After it finishes, post the contents of the FlashInstall.log file from the same location as the mms.cfg file in step 2 above. The file may be fairly long, if so you can upload the file (and the screenshot if you want) using the How to share a document instructions.
If you uploaded the file(s) post the URL to the files in your reply.

--

Maria

Report · Jul 17, 2015

This is a fresh installation in a lab to understand how it works to later implement in a production environment.

The xml files are the ones extractod from the cab file.

i already have the SilentAutoUpdateVerboseLoggin=1 in the file.

This is the error i get.

The log shows the following warnings

2014-10-15+14-22-2.771 [info] 1628 updates.domain.local

2014-10-15+14-22-2.771 [info] 1629updates.domain.local

2014-10-15+14-22-2.771 [info] 1614

2014-10-15+14-22-2.771 [info] 1615

2014-10-15+14-22-2.771 [info] 1618

2014-10-15+14-22-2.771 [info] 1619 1063

2014-10-15+14-22-2.786 [info] 1628 updates.domain.local

2014-10-15+14-22-2.786 [info] 1629 updates.domain.local

2014-10-15+14-22-2.786 [info] 1614

2014-10-15+14-22-2.786 [info] 1615

2014-10-15+14-22-2.786 [info] 1618

2014-10-15+14-22-2.786 [info] 1608

2014-10-15+14-22-2.786 [info] 1604

2014-10-15+14-22-2.786 [info] 1631 /pub/flashplayer/update/current/sau//currentmajor.xml

2014-10-15+14-22-2.833 [warning] 1470 12175

2014-10-15+14-22-2.833 [warning] 1474 183

2014-10-15+14-22-2.833 [warning] 1475

2014-10-15+14-22-2.849 [info] 1432

2014-10-15+14-22-2.849 [info] 1612

2014-10-15+14-22-2.849 [info] 1620

What permissions should be on the files ?? I didnt look at those.. but i will monday.

Also i will run wireshark and see if i can find some useful information.

Thank you.

Report · Jul 20, 2015

Hi FMCS,

Please do the following:

Using the browser, navigate to the curentmajor.xml file using HTTPS.
- Post a screenshot of the results
Post a screenshot of the /pub/flashplayer/update/current directory tree showing each sub-directory in the tree (do not write an outline as in the first post in this discussion, post a screenshot of the actual directory tree)
Provide a complete FlashInstall.log file for an impacted system. Since this will most likely be fairly long, you can upload the file using the How to share a document‌ instructions.
- Post the URL in your reply.

Thank you.

--

Maria

Report · Jan 24, 2017

I have the same errors what was the fix to this issue?

Report · Jan 25, 2017

Hi,

There was no follow-up post from the OP to my requests, so I don't know if they fixed the issue or not.

Since the OPs in this topic were all hosting the Background Update resources locally, I'm assuming you are too. I'll need more information from you to troubleshoot the error:

What is the operating system, including version, the files are being hosted on?
- Please confirm that the files are deployed correctly and appropriate access to the required ports has been granted
What is the operating system, including version, of the client system that is failing to update?
Post an excerpt of the log file, like the previous OPs did showing more details. Simply posting the error code is not enough. For privacy, you can obfuscate your domain as the OPs did
Are you using the files from the fp_background_update.cab or from elsewhere?
Screenshot/layout of the directories and files as deployed on your local server
copy/paste the contents of the currentmajor.xml file

Essentially, please provide the same information the OP posted, and information I had requested from the OP.

Thank you.

--

Maria

Report · Jan 26, 2017

content from /24/xml/version.xml

<?xml version="1.0"?>

-<version> <ActiveX buildMinor="194" buildMajor="0" minor="0" major="24"/> <Plugin buildMinor="194" buildMajor="0" minor="0" major="24"/> <Pepper buildMinor="194" buildMajor="0" minor="0" major="24"/> <MacPlugin buildMinor="194" buildMajor="0" minor="0" major="24"/> <MacPepper buildMinor="194" buildMajor="0" minor="0" major="24"/> <SAUConfig checkFrequency="1"/> </version>

Windows server 2008 R2, fp_background_update.cab is most current from your distribution.

Log File

2017-1-25+23-53-0.141 [info] 1608

2017-1-25+23-53-0.173 [info] 1631 /pub/flashplayer/update/current/sau/currentmajor.xml

2017-1-25+23-53-0.219 [warning] 1470 12175

2017-1-25+23-53-0.219 [warning] 1474 183

2017-1-25+23-53-0.219 [warning] 1475

2017-1-25+23-53-0.219 [info] 1432

2017-1-25+23-53-0.219 [info] 1612

2017-1-25+23-53-0.219 [info] 1620

2017-1-26+0-53-0.13 [info] 1628 flashupdate.domain.local

2017-1-26+0-53-0.44 [info] 1629 flashupdate.domain.local

2017-1-26+0-53-0.44 [info] 1614

2017-1-26+0-53-0.44 [info] 1615

2017-1-26+0-53-0.106 [info] 1618

2017-1-26+0-53-0.106 [info] 1619 1063

2017-1-26+0-53-0.122 [info] 1628 flashupdate.domain.local

2017-1-26+0-53-0.122 [info] 1629 flashupdate.domain.local

2017-1-26+0-53-0.122 [info] 1614

2017-1-26+0-53-0.122 [info] 1615

from the currentmajor.xml file

</version>

my clients are able to access the file via

https://flashupdate.domain.local/pub/flashplayer/update/current/sau/currentmajor.xml

Report · Jan 26, 2017

Thank you for posting the screenshots, very helpful. We are investigating further and I'll post back soon.

Report · Jan 27, 2017

Hi thanhn19432897

Can you please access https://flashupdate.domain.local/pub/flashplayer/update/current/sau/currentmajor.xml from the browser and check to see if there are https warnings?

Thank you.

--

Maria

Report · Jan 27, 2017

They are able to access https://flashupdate.domain.local/pub/flashplayer/update/current/sau/currentmajor.xml with no https warnings.

Report · Jan 27, 2017

Is flashupdate.domain.local the actual name of your server, or is that pseudo-name to obfuscate your actual local server name?

Report · Jan 27, 2017

It is just a pseudo-name to obfuscate your actual local server name.

Report · Jan 27, 2017

What OS versions, and browser versions are on the client systems?

Please also verify, and confirm that the Common Name (CN) of the ssl certificate is the same as your local server (flashupdate.domain.local).

Report · Jan 27, 2017

Yes it is the same.

Report · Jan 30, 2017

Can you please check that the CA that is associated with the self signed ssl certificate is not installed correctly for use by services? The section titled "To add the Certificates snap-in to an MMC for a service" at

https://technet.microsoft.com/en-us/library/cc754431(v=ws.11).aspx contains more information on this.

Adobe Community

flashplayer.log Warning codes 1474 and 1475