Control Compliance Suite

When I run the latest CCS v10.0 Reporting and Analytics PCU 2010-4, getting an error:

Unable to continue the setup.

Unable to find Setup.Config For Patch Pre-Copy. Patch install will exit.

This happens just after the extraction phase completes and enters into the Setup screen.

I can see the files extracted onto e: and can see a Setup.Config file in there as well. 

Earlier today, I ran the Data Collection PCU 2010-4 successfully, although I had to change the %ProgramFiles% environment variable from c:\Program Files to E:\Program Files in order to get it to run.  (All CCS component files are installed onto the E: drive.)

Anyone experience anything like this?  I'm on the phone with support now but not getting too far very fast.

Thanks,

Aaron

I have the installs downloaded but have not tried to run the R&A PCU 2010-4 yet . I did kick off the Data Collection one off on my local machine and that came up to the install area fine.

Do you still have the old installation files for the PCU 2010-3 (or earler) on the server where you are trying to install the 2010-4? This is just a bit of a each but I'm wondering if there is something in the pre-installation that is looking for previous files of the software / upgrade data before it kicks off the newest installation?

If you get the issue solved on the phone with Symantec I'd be real interested in finding out what the cause of the problem and the solution is since I'll be running through an 2010-4 update within the next 30 days.

Good luck

It would be intresting to look at the  install logs from Start-Run-%temp%. Could you post it here?

Thank you for the solution - This has helped me overcome this issue

Last night, I looked for a log file in the %temp% folder but no logs were created there.  I found that all CCS logs are in the %ALLUSERSPROFILE%\Application Data\Symantec.CSM\Logs folder (on a Win2003 server).  For installs the logs are in this path under the Installs folder. 

Before resolving the issue, the only log file created before the update errored out was CSIInstallLog_datetime.txt which I found in the above path Installs folder.  But...the log just cuts off right after identifying the OS info without specifying any errors.  I believe the setup is probably trying to locate the original install media cache folder where it's expecting to find the original Setup.Config file to determine what has been installed.  But, it doesn't look like the update program was coded to produce error results in the log when it cannot locate the file.  It should at least let us know the path that it cannot find the specific Setup.Config file in. 

First, I'll show the only log file contents when I got the initial "unable to continue..." error then I'll show a portion of the log file contents after successfully installing the PCU.   

Entire log file from failed PCU install attempt:
01/27/2011 19:20:55.875 Setup.exe            Entering SetupApp::TempPath
01/27/2011 19:20:55.875 Setup.exe               TempPath: e:\Temp\1\
01/27/2011 19:20:55.875 Setup.exe               SetupApp::TempPath completed successfully.
01/27/2011 19:20:55.875 Setup.exe            Leaving SetupApp::TempPath
01/27/2011 19:20:55.875 Setup.exe            Entering SetupApp::MediaDir
01/27/2011 19:20:55.875 Setup.exe               Entering SetupApp::ModuleFilename
01/27/2011 19:20:55.875 Setup.exe                  SetupApp::ModuleFilename completed successfully.
01/27/2011 19:20:55.875 Setup.exe               Leaving SetupApp::ModuleFilename
01/27/2011 19:20:55.891 Setup.exe               SetupApp::MediaDir completed successfully.
01/27/2011 19:20:55.891 Setup.exe            Leaving SetupApp::MediaDir
01/27/2011 19:20:55.891 Setup.exe            Processing config file: e:\temp\1\CSMSetup\media.2010-4\Setup.Config
01/27/2011 19:20:55.891 Setup.exe            Entering SetupApp::MediaDir
01/27/2011 19:20:55.891 Setup.exe               Entering SetupApp::ModuleFilename
01/27/2011 19:20:55.891 Setup.exe                  SetupApp::ModuleFilename completed successfully.
01/27/2011 19:20:55.891 Setup.exe               Leaving SetupApp::ModuleFilename
01/27/2011 19:20:55.906 Setup.exe               SetupApp::MediaDir completed successfully.
01/27/2011 19:20:55.906 Setup.exe            Leaving SetupApp::MediaDir
01/27/2011 19:20:55.906 Setup.exe            Entering SetupApp::CreateFolder
01/27/2011 19:20:55.906 Setup.exe            Leaving SetupApp::CreateFolder
01/27/2011 19:20:55.906 Setup.exe            Entering SetupUtil::DetectOS
01/27/2011 19:20:55.906 Setup.exe            Leaving SetupUtil::DetectOS
01/27/2011 19:20:55.922 Setup.exe            Entering OSDetector::GetInputData
01/27/2011 19:20:55.922 Setup.exe            Leaving OSDetector::GetInputData
01/27/2011 19:20:55.922 Setup.exe            Detected [ProcessorArchitecture = x86]
01/27/2011 19:20:55.922 Setup.exe            Detected [ProcessBitness = 32bit]
01/27/2011 19:20:55.922 Setup.exe            Detected [MajorVersion = 5]
01/27/2011 19:20:55.922 Setup.exe            Detected [MinorVersion = 2]
01/27/2011 19:20:55.922 Setup.exe            Detected [BuildNumber = 3790]
01/27/2011 19:20:55.938 Setup.exe            Detected [PlatformId = WIN32_NT]
01/27/2011 19:20:55.938 Setup.exe            Detected [ServicePackMajor = 2]
01/27/2011 19:20:55.938 Setup.exe            Detected [ServicePackMinor = 0]
01/27/2011 19:20:55.938 Setup.exe            Detected [ProductType = SERVER]
01/27/2011 19:20:55.938 Setup.exe            Unknown suitemask value: 272
01/27/2011 19:20:55.938 Setup.exe            Detected [SuiteMask = BACKOFFICE]
01/27/2011 19:20:55.938 Setup.exe            Detected [SysMetricsIndex = ]
01/27/2011 19:20:55.938 Setup.exe            Entering InputReader::Read
01/27/2011 19:20:55.953 Setup.exe            Leaving InputReader::Read
01/27/2011 19:20:55.953 Setup.exe            [TRUE ][OSMap : NTPlatform : PlatformId=WIN32_NT]
01/27/2011 19:20:55.953 Setup.exe            [FALSE][OSMap : NTLessThan4 : NTPlatform & (MajorVersion < 4)]
01/27/2011 19:20:55.953 Setup.exe            [FALSE][OSMap : Minor1 : MinorVersion=1]
01/27/2011 19:20:55.953 Setup.exe            [FALSE][OSMap : Win7 : Major6 & Minor1 & Workstation]
01/27/2011 19:20:55.953 Setup.exe            [FALSE][OSMap : W2k8R2 : Major6 & Minor1 & Server]
01/27/2011 19:20:55.969 Setup.exe            [FALSE][OSMap : Minor0 : MinorVersion=0]
01/27/2011 19:20:55.969 Setup.exe            [FALSE][OSMap : W2k8 : Major6 & Minor0 & Server]
01/27/2011 19:20:55.969 Setup.exe            [FALSE][OSMap : WVista : Major6 & Minor0 & Workstation]
01/27/2011 19:20:55.969 Setup.exe            [TRUE ][OSMap : Minor2 : MinorVersion=2]
01/27/2011 19:20:55.985 Setup.exe            [TRUE ][OSMap : Server : (ProductType=SERVER) | (ProductType=DOMAIN_CONTROLLER)]
01/27/2011 19:20:55.985 Setup.exe            [TRUE ][OSMap : Major5 : MajorVersion=5]
01/27/2011 19:20:55.985 Setup.exe            [TRUE ][OSMap : W2k3Server : Major5 & Minor2 & Server]
01/27/2011 19:20:55.985 Setup.exe            [FALSE][OSMap : HomeServer : SuiteMask=WH_SERVER]
01/27/2011 19:20:55.985 Setup.exe            [FALSE][OSMap : WHomeServer : W2k3Server & HomeServer]
01/27/2011 19:20:55.985 Setup.exe            [FALSE][OSMap : ServerR2 : SysMetricsIndex=SERVERR2]
01/27/2011 19:20:56.000 Setup.exe            [FALSE][OSMap : W2k3R2 : W2k3Server & ServerR2]
01/27/2011 19:20:56.000 Setup.exe            [TRUE ][OSMap : W2k3 : W2k3Server & (!WHomeServer & !W2k3R2)]
01/27/2011 19:20:56.000 Setup.exe            [TRUE ][OSMap : OSMap :  WNT4 | W2k | WXP | WXPx64 | WHomeServer | W2k3R2 | W2k3 | WVista | W2k8 | W2k8R2 | Win7 | (!NTPlatform) | NTLessThan4]
01/27/2011 19:20:56.000 Setup.exe            [TRUE ][OS : OS : ((ProductType == SERVER) | (ProductType == DOMAIN_CONTROLLER)) & (((MajorVersion == 5) & (MinorVersion >= 2)) | (MajorVersion > 5))]

Portion of log file from successful PCU install up to detecting :
01/27/2011 20:03:24.502 Setup.exe            Entering SetupApp::TempPath
01/27/2011 20:03:24.502 Setup.exe               TempPath: e:\Temp\1\
01/27/2011 20:03:24.502 Setup.exe               SetupApp::TempPath completed successfully.
01/27/2011 20:03:24.502 Setup.exe            Leaving SetupApp::TempPath
01/27/2011 20:03:24.502 Setup.exe            Entering SetupApp::MediaDir
01/27/2011 20:03:24.518 Setup.exe               Entering SetupApp::ModuleFilename
01/27/2011 20:03:24.518 Setup.exe                  SetupApp::ModuleFilename completed successfully.
01/27/2011 20:03:24.518 Setup.exe               Leaving SetupApp::ModuleFilename
01/27/2011 20:03:24.518 Setup.exe               SetupApp::MediaDir completed successfully.
01/27/2011 20:03:24.518 Setup.exe            Leaving SetupApp::MediaDir
01/27/2011 20:03:24.518 Setup.exe            Processing config file: e:\temp\1\CSMSetup\media.2010-4\Setup.Config
01/27/2011 20:03:24.534 Setup.exe            Entering SetupApp::MediaDir
01/27/2011 20:03:24.534 Setup.exe               Entering SetupApp::ModuleFilename
01/27/2011 20:03:24.534 Setup.exe                  SetupApp::ModuleFilename completed successfully.
01/27/2011 20:03:24.534 Setup.exe               Leaving SetupApp::ModuleFilename
01/27/2011 20:03:24.534 Setup.exe               SetupApp::MediaDir completed successfully.
01/27/2011 20:03:24.534 Setup.exe            Leaving SetupApp::MediaDir
01/27/2011 20:03:24.534 Setup.exe            Entering SetupApp::CreateFolder
01/27/2011 20:03:24.534 Setup.exe            Leaving SetupApp::CreateFolder
01/27/2011 20:03:24.549 Setup.exe            Entering SetupUtil::DetectOS
01/27/2011 20:03:24.549 Setup.exe            Leaving SetupUtil::DetectOS
01/27/2011 20:03:24.549 Setup.exe            Entering OSDetector::GetInputData
01/27/2011 20:03:24.549 Setup.exe            Leaving OSDetector::GetInputData
01/27/2011 20:03:24.549 Setup.exe            Detected [ProcessorArchitecture = x86]
01/27/2011 20:03:24.549 Setup.exe            Detected [ProcessBitness = 32bit]
01/27/2011 20:03:24.565 Setup.exe            Detected [MajorVersion = 5]
01/27/2011 20:03:24.565 Setup.exe            Detected [MinorVersion = 2]
01/27/2011 20:03:24.565 Setup.exe            Detected [BuildNumber = 3790]
01/27/2011 20:03:24.565 Setup.exe            Detected [PlatformId = WIN32_NT]
01/27/2011 20:03:24.565 Setup.exe            Detected [ServicePackMajor = 2]
01/27/2011 20:03:24.565 Setup.exe            Detected [ServicePackMinor = 0]
01/27/2011 20:03:24.565 Setup.exe            Detected [ProductType = SERVER]
01/27/2011 20:03:24.581 Setup.exe            Unknown suitemask value: 272
01/27/2011 20:03:24.581 Setup.exe            Detected [SuiteMask = BACKOFFICE]
01/27/2011 20:03:24.581 Setup.exe            Detected [SysMetricsIndex = ]
01/27/2011 20:03:24.581 Setup.exe            Entering InputReader::Read
01/27/2011 20:03:24.581 Setup.exe            Leaving InputReader::Read
01/27/2011 20:03:24.581 Setup.exe            [TRUE ][OSMap : NTPlatform : PlatformId=WIN32_NT]
01/27/2011 20:03:24.596 Setup.exe            [FALSE][OSMap : NTLessThan4 : NTPlatform & (MajorVersion < 4)]
01/27/2011 20:03:24.596 Setup.exe            [FALSE][OSMap : Minor1 : MinorVersion=1]
01/27/2011 20:03:24.596 Setup.exe            [FALSE][OSMap : Win7 : Major6 & Minor1 & Workstation]
01/27/2011 20:03:24.596 Setup.exe            [FALSE][OSMap : W2k8R2 : Major6 & Minor1 & Server]
01/27/2011 20:03:24.596 Setup.exe            [FALSE][OSMap : Minor0 : MinorVersion=0]
01/27/2011 20:03:24.612 Setup.exe            [FALSE][OSMap : W2k8 : Major6 & Minor0 & Server]
01/27/2011 20:03:24.612 Setup.exe            [FALSE][OSMap : WVista : Major6 & Minor0 & Workstation]
01/27/2011 20:03:24.612 Setup.exe            [TRUE ][OSMap : Minor2 : MinorVersion=2]
01/27/2011 20:03:24.612 Setup.exe            [TRUE ][OSMap : Server : (ProductType=SERVER) | (ProductType=DOMAIN_CONTROLLER)]
01/27/2011 20:03:24.612 Setup.exe            [TRUE ][OSMap : Major5 : MajorVersion=5]
01/27/2011 20:03:24.612 Setup.exe            [TRUE ][OSMap : W2k3Server : Major5 & Minor2 & Server]
01/27/2011 20:03:24.627 Setup.exe            [FALSE][OSMap : HomeServer : SuiteMask=WH_SERVER]
01/27/2011 20:03:24.627 Setup.exe            [FALSE][OSMap : WHomeServer : W2k3Server & HomeServer]
01/27/2011 20:03:24.627 Setup.exe            [FALSE][OSMap : ServerR2 : SysMetricsIndex=SERVERR2]
01/27/2011 20:03:24.627 Setup.exe            [FALSE][OSMap : W2k3R2 : W2k3Server & ServerR2]
01/27/2011 20:03:24.627 Setup.exe            [TRUE ][OSMap : W2k3 : W2k3Server & (!WHomeServer & !W2k3R2)]
01/27/2011 20:03:24.627 Setup.exe            [TRUE ][OSMap : OSMap :  WNT4 | W2k | WXP | WXPx64 | WHomeServer | W2k3R2 | W2k3 | WVista | W2k8 | W2k8R2 | Win7 | (!NTPlatform) | NTLessThan4]
01/27/2011 20:03:24.627 Setup.exe            [TRUE ][OS : OS : ((ProductType == SERVER) | (ProductType == DOMAIN_CONTROLLER)) & (((MajorVersion == 5) & (MinorVersion >= 2)) | (MajorVersion > 5))]
01/27/2011 20:03:40.877 CSIExec              1:Main Ap...n Thread Verbose                                    ===== Log generated by CSI version 10.0.63.10200 =====
01/27/2011 20:03:40.893 CSIExec              1:Main Ap...n Thread Verbose                                    File log started: C:\Documents and Settings\All Users\Application Data\Symantec.CSM\Logs\Installs\CSIInstallLog_20110127200324.txt
01/27/2011 20:03:40.893 CSIExec              1:Main Ap...n Thread Verbose                                    Command line option: /StartFromSetup
01/27/2011 20:03:40.893 CSIExec              1:Main Ap...n Thread Verbose                                    Command line option: /LogFilename=C:\Documents and Settings\All Users\Application Data\Symantec.CSM\Logs\Installs\CSIInstallLog_20110127200324.txt
01/27/2011 20:03:40.893 CSIExec              1:Main Ap...n Thread Verbose                                    Command line option: /PatchMode=1
01/27/2011 20:03:40.909 CSIExec              1:Main Ap...n Thread Verbose                                    Command line option: /PatchProduct=Symantec Control Compliance Suite - R and A
01/27/2011 20:03:40.924 CSIExec              1:Main Ap...n Thread Verbose                                    User Cache size requirement is 664 MB
01/27/2011 20:03:40.924 CSIExec              1:Main Ap...n Thread Verbose                                    Creating WizardHost
01/27/2011 20:03:41.049 CSIExec              1:Main Ap...n Thread Verbose                                    Creating UIController
01/27/2011 20:03:41.049 CSIExec              1:Main Ap...n Thread Verbose                                    Executing UIController
01/27/2011 20:03:41.065 CSIExec              1:Main Ap...n Thread Verbose                                    Entering WizardHost.set_State: Changing wizard host state from Waiting to Waiting
01/27/2011 20:03:41.081 CSIExec              1:Main Ap...n Thread Verbose                                    Leaving WizardHost.set_State
01/27/2011 20:03:41.081 CSIExec              1:Main Ap...n Thread Verbose                                    Entering WizardHost.LoadPage: Loading Page: Preparing Installer; State: Begin; Direction Next
01/27/2011 20:03:41.096 CSIExec              1:Main Ap...n Thread Verbose                                       Loading CSIUserControl on Thread: 1:Main Application Thread
01/27/2011 20:03:41.159 CSIExec              1:Main Ap...n Thread Verbose                                       Entering WizardHost.set_State: Changing wizard host state from Waiting to Begin
01/27/2011 20:03:41.159 CSIExec              1:Main Ap...n Thread Verbose                                          Entering WizardHost.PageStateChangedEventHandler: Changing page state to NotStarted
01/27/2011 20:03:41.159 CSIExec              1:Main Ap...n Thread Verbose                                          Leaving WizardHost.PageStateChangedEventHandler
01/27/2011 20:03:41.159 CSIExec              1:Main Ap...n Thread Verbose                                       Leaving WizardHost.set_State
01/27/2011 20:03:41.174 CSIExec              1:Main Ap...n Thread Verbose                                       Entering CSIUserControl.OnControlEnter: Page: CSI.InstallInitializationPageActivity; Command: Next
01/27/2011 20:03:41.174 CSIExec              1:Main Ap...n Thread Verbose                                       Leaving CSIUserControl.OnControlEnter
01/27/2011 20:03:41.174 CSIExec              1:Main Ap...n Thread Verbose                                       Entering WizardHost.PageStateChangedEventHandler: Changing page state to Blocking
01/27/2011 20:03:41.174 CSIExec              1:Main Ap...n Thread Verbose                                       Leaving WizardHost.PageStateChangedEventHandler
01/27/2011 20:03:41.174 CSIExec              1:Main Ap...n Thread Verbose                                    Leaving WizardHost.LoadPage
01/27/2011 20:03:41.190 CSIExec              3:                   Verbose                                    Reading CSI manifests
01/27/2011 20:03:41.206 CSIExec              3:                   Verbose                                    Entering CSIUtil.ReadCSIManifests: Reading application activity manifest
01/27/2011 20:03:41.206 CSIExec              3:                   Verbose                                       Entering DigitalSignValidation...
01/27/2011 20:03:41.221 CSIExec              3:                   Verbose                                       Config file: e:\Temp\1\CSMSetup\Media\Setup.Config
01/27/2011 20:03:44.659 CSIExec              3:                   Verbose                                       Exiting Successfully DigitalSignValidation...
01/27/2011 20:03:51.143 CSIExec              3:                   Verbose                                       The License name: CCS_Core, License type:Mandatory
01/27/2011 20:03:52.424 CSIExec              3:                   Verbose                                       The License name: CCS_Core, License type:Optional
01/27/2011 20:03:56.674 CSIExec              3:                   Verbose                                       The License name: BV PM ISO Server add-on, License type:Mandatory
01/27/2011 20:03:56.784 CSIExec              3:                   Verbose                                       The License name: BV PM ISO Server add-on, License type:Mandatory
01/27/2011 20:03:57.237 CSIExec              3:                   Verbose                                       The License name: BV PM ISO Server add-on, License type:Mandatory
01/27/2011 20:03:58.018 CSIExec              3:                   Verbose                                       The License name: BV PM ISO Server add-on, License type:Mandatory
01/27/2011 20:03:58.737 CSIExec              3:                   Verbose                                       The License name: BV PM ISO Server add-on, License type:Mandatory
01/27/2011 20:03:58.737 CSIExec              3:                   Verbose                                       The License name: BV PM ISO Server add-on, License type:Mandatory
01/27/2011 20:04:14.565 CSIExec              3:                   Warning     XMLPackageReader                  Unrecognized XML element while parsing XML Activity Manifest: XmlProperty
01/27/2011 20:04:14.565 CSIExec              3:                   Warning     XMLPackageReader                  Unrecognized XML element while parsing XML Activity Manifest: File
01/27/2011 20:04:14.581 CSIExec              3:                   Warning     XMLPackageReader                  Unrecognized XML element while parsing XML Activity Manifest: Conditions
01/27/2011 20:04:14.581 CSIExec              3:                   Warning     XMLPackageReader                  Unrecognized XML element while parsing XML Activity Manifest: Scope
01/27/2011 20:04:18.643 CSIExec              3:                   Verbose                                       Entering CSIUtil.RegisterSnapinManifests: Reading Snap-in activity manifest
01/27/2011 20:04:18.784 CSIExec              3:                   Verbose                                       Leaving CSIUtil.RegisterSnapinManifests
01/27/2011 20:04:18.799 CSIExec              3:                   Verbose                                    Leaving CSIUtil.ReadCSIManifests
01/27/2011 20:04:18.815 CSIExec              1:Main Ap...n Thread Verbose                                    Manifests read successfully.
01/27/2011 20:04:18.909 CSIExec              3:Sequenc....OnBegin Verbose     ExecutionEngine                Executing Sequence: CSI.Anchor.OnBegin
01/27/2011 20:04:18.987 CSIExec              3:Sequenc....OnBegin Verbose     Condition                         Evaluating Condition: [Empty Condition] = True
01/27/2011 20:04:18.987 CSIExec              3:Sequenc....OnBegin Verbose     ExecutionEngine                   Running Activity: CSI.Anchor.OnBegin::CSI.DetectInstalledSuiteVersion
01/27/2011 20:04:19.002 CSIExec              3:Sequenc....OnBegin Verbose                                       Entering InstallInitializationPage.Status_StatusChanged: Install initializing
01/27/2011 20:04:19.002 CSIExec              1:Main Ap...n Thread Verbose                                    Entering InstallInitializationPage.Status_StatusChanged: Install initializing
01/27/2011 20:04:19.002 CSIExec              1:Main Ap...n Thread Verbose                                    Leaving InstallInitializationPage.Status_StatusChanged
01/27/2011 20:04:19.018 CSIExec              3:Sequenc....OnBegin Verbose                                       Leaving InstallInitializationPage.Status_StatusChanged
01/27/2011 20:04:19.065 CSIExec              3:Sequenc....OnBegin Verbose                                       Entering RegistriesOpActivity.Run: Registry OP Activity
01/27/2011 20:04:19.065 CSIExec              3:Sequenc....OnBegin Information                                      Start the Registry operation: Reg_ReadValue.
01/27/2011 20:04:19.065 CSIExec              3:Sequenc....OnBegin Information                                      There are 1 Registries entry to be operated.
01/27/2011 20:04:19.065 CSIExec              3:Sequenc....OnBegin Verbose                                          Entering RegistriesOpActivity.InitializeRegistryDescriptor:
01/27/2011 20:04:19.424 CSIExec              3:Sequenc....OnBegin Verbose                                          Leaving RegistriesOpActivity.InitializeRegistryDescriptor
01/27/2011 20:04:19.424 CSIExec              3:Sequenc....OnBegin Information                                      Regsitries to be Oped: 1.
01/27/2011 20:04:19.440 CSIExec              3:Sequenc....OnBegin Information                                      The installed version is: 10.0.863.10000.
01/27/2011 20:04:19.440 CSIExec              3:Sequenc....OnBegin Verbose                                          csikey[CSI.InstalledVersion]value[10.0.863.10000]
01/27/2011 20:04:19.440 CSIExec              3:Sequenc....OnBegin Verbose                                       Leaving RegistriesOpActivity.Run
01/27/2011 20:04:19.456 CSIExec              3:Sequenc....OnBegin Verbose     ExecutionEngine                   Activity execution succeeded: CSI.DetectInstalledSuiteVersion
01/27/2011 20:04:19.456 CSIExec              3:Sequenc....OnBegin Verbose     Condition                         Evaluating Condition: [Empty Condition] = True
01/27/2011 20:04:19.456 CSIExec              3:Sequenc....OnBegin Verbose     ExecutionEngine                   Running Activity: CSI.Anchor.OnBegin::CSI.DetectSpecialFolders
01/27/2011 20:04:19.471 CSIExec              3:Sequenc....OnBegin Verbose                                       Entering DetectSpecialFolders.Run: Detecting special folders
01/27/2011 20:04:19.471 CSIExec              3:Sequenc....OnBegin Verbose                                          Entering Helper.GetProductUserCacheDirectory: Quering product user cache folder
01/27/2011 20:04:19.471 CSIExec              3:Sequenc....OnBegin Verbose                                             Looking for key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Symantec Control Compliance Suite - R and A
01/27/2011 20:04:19.471 CSIExec              3:Sequenc....OnBegin Verbose                                             User Cache Path: E:\Temp\Reportcache
01/27/2011 20:04:19.487 CSIExec              3:Sequenc....OnBegin Verbose                                          Leaving Helper.GetProductUserCacheDirectory
01/27/2011 20:04:19.487 CSIExec              3:Sequenc....OnBegin Verbose                                          User Cache Path - E:\Temp\Reportcache
01/27/2011 20:04:19.487 CSIExec              3:Sequenc....OnBegin Verbose                                       Leaving DetectSpecialFolders.Run
01/27/2011 20:04:19.487 CSIExec              3:Sequenc....OnBegin Verbose     ExecutionEngine                   Activity execution succeeded: CSI.DetectSpecialFolders
01/27/2011 20:04:19.487 CSIExec              3:Sequenc....OnBegin Verbose     Condition                         Evaluating Condition: [Empty Condition] = True
01/27/2011 20:04:19.502 CSIExec              3:Sequenc....OnBegin Verbose     ExecutionEngine                   Running Activity: CSI.Anchor.OnBegin::CSI.DetectInstallMode
01/27/2011 20:04:19.502 CSIExec              3:Sequenc....OnBegin Verbose                                       Entering DetectInstallMode.Run: Detecting Install Mode

In my (humble) opinion, I believe the original CCS R&A install process is the actual culprit and should change to not store the media cache and/or the Setup.Config from the original install in a %Temp% folder.  Instead, it should store the files in the same path as the RMS/BV install does which is by default set to C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Control Compliance Suite- Data Collection\MediaCache or similar path.

Also, the PCU install should identify this error in the log file when it cannot find the Setup.Config file it's looking for. 

Aaron

Martin,

Hey, that's great!  I'm glad this helped. 

Aaron

Thanks, Kevin for the reply.

We implemented directly onto v10.0 in July last year and believe the Symantec SE did not install the PCU 2010-3. Unfortunately, even after attending a great v9.0 training class in early December, there wasn't any mention of maintenance to the product and I'm just now finding out about the PCUs and Patch Assessment updates that have to be ran.

Actually, not long after posting this original issue and only about 15 minutes after hanging up with the Symantec Technical Support rep last night, I resolved the issue on my own.  But...it was a strange issue, one that I hope Symantec might try to change, and one others may be interested in.

Here's what I found and the solution which I sent the Symantec Technical Support rep last night as well.

Looks like the PCU update may be looking for a Setup.Config file in another temporary media cache location (other than the one that's created by the PCU extraction process).  A separate media cache folder is automatically created during the original installation of CCS R&A.  This folder might be called Reportcache and may be in your %temp% location at the time of the originall CCS install.

To find this, I first went into Add/Remove Programs just to verify R&A components were installed (even though I could run the R&A console just fine) but I got an error that Windows could not find the uninstall program.

I then checked the Windows uninstall registry within HKEY_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Uninstall\Symantec Control Compliance Suite - R and A.  The UninstallPath string value was E:\Temp\Reportcache and the UninstallString string value was E:\Temp\Reportcache\CSIExec.exe.  This path/structure did not currently exist.  The E: drive is where all CCS component program files were installed to.  I remember that during the Symantec SE's original installation of v10 (in July), his first attempts failed because the media cache copy process of the install could not complete (ran out of disk space on C:).  It was trying to copy the entire CCS DVD to the default %ALLUSERSPROFILE% and %TEMP% paths which was still set to C: drive.  Most servers are configured these days with a smaller OS system drive with all application program files and data stored on a separate, much larger partition/drive.  Back then, I had to modify the %ALLUSERSPROFILE% and %TEMP% variables to get the install to work.  This may be why these uninstall reg entries were set to E: - but is not a good practice, in my opinion, for Symantec if follow up installs or upgrades rely on the media cache location to still remain in a "temp" folder.  

Anyway, after finding out the uninstall location values in the registry did not exist, next I ran the original CCS installation setup.exe from the CD (or download) and did a Repair on just Reporting and Analytics.

During the repair, a Reportcache folder was automatically created in E:\Temp.  Along with 664MB+ files in the E:\Temp\Reportcache folder was also another Setup.Config file.

After the repair completed, I ran the Reporting & Analytics PCU 2010-4 install which completed successfully.  I am not certain if the PCU install process was looking for specific contents in this Setup.Config specific file in the Reportcache folder or possibly just reads the uninstall registry key to find where the previous Setup.Config file was located?  It's my guess that it's the latter.

Overall, in my opinion, if all PCU updates are designed to look for the original installation media cache within any "Temp" folder, it's very possible the PCU update may fail. I'd suggest to Symantec to change this for the Reporting and Analytics install so the media cache copies to the %ALLUSERSPROFILE% location instead.  This is what the CCS Data Collection install does.  At least that location may not be as likely to get cleaned out periodically by the server admin via automated or manual processes.

I'm curious if anyone else has this Reportcache folder already prior to you running the v10.0 Reporting and Analytics PCU 2010-4.  If it does not exist and the install fails, try these steps above.

Hope this helps.

Aaron