Sometimes Symantec Endpoint Protection and other MSI system errors can be related to problems in the Windows registry.
I have a Symantec Corporate Edition 10.01 since 2006 and the definitions stopped updating the first week of July 2013.
JDB file (and perhaps preceeding updates), that was not updating the 64 bit clients.
JDB files from 2010-03-18 and beyond work just fine updating both the 32 and 64 bit clients.
Additional Clarification: The Intelligent Updater files are designed to update client installs for SEP or SAV only.
Even though I was skeptical of your advice, I went ahead and performed the steps described in your knowledgebase article (short of the full reintstall*) and they did not help at all; the March 16h definition update simply does not populate the 64-bit folder with any data.
* In addition, I had So since prior definition packages worked just fine on these systems, and since the problem has cropped right back up on this newly installed SEPM instance, I would infer that another full reinstall would be nothing more then a time consuming stop-gap measure, and that the SEPM jdb files themselves are somehow corrupt.
clients and the x86 executable file for 32-bit client installations is used for Symantec Anti Virus Scan Engine for Windows(again, is this same as Symantec Scan Engine?
)Could someone tell me if I've been using the i32 executable definition for 32-bit client installations all along and then try to run the x86 executable definition for 32-bit client installations would that cause a problem?