HP Version Control Repository Manager issues with HP Smart Update Manager

[Alexx_B]

Hi all
I have Windows 2003 server with HP SIM 5.2 and VCRM 2.1 installed
If I use SMHP -> VCA to upgrade rather software and firmware - everything is OK. But if I try to run setup exe directly from repository share (like \\\repository\setup.exe) - I get a error

Some times ago when I ran setup.exe - HP Smart Update Manager stared and first step - Build inventory of available updates - went normally. Now at this step progress bar reaches 100% and I see "Inventory finished" and then I get a error:
=============================
Header: HP Smart Update Manager
Message: Fatal Error - aplication will exit
=============================

Event log shows 2 events correlated with this error:

=============================
1)Event Source: Application Error
Event ID: 1000
Description: Faulting application SourceClient.exe, version 1.5.0.0, faulting module SourceClient.exe, version 1.5.0.0, fault address 0x00057065.

2)Event Source: DrWatson
Event ID: 4097
Description: The application, \\hpsim\Repository\SourceClient.exe, generated an application error The error occurred on 02/16/2009 @ 15:54:37.900 The exception generated was c0000005 at address 00457065 (SourceClient)
=============================

I think that this problem is related with my repository database after one of the automatically updates. Maybe XML descriptions for updates or something else.

If I run VCRM I see:
=============================
Warning: The catalog is currently being validated, some components might appear missing.
=============================
in the Catalog page

I try to run "rescan the repository and rebuild the catalog" tool and check the log but there are no errors in it (informational message "Catalog validation completed.")

At this time I have next Proliant Support Packs added to the repository:
ProLiant Support Pack for Microsoft Windows Server 2003 Version 7.91A (English (US), Japanese)
ProLiant Support Pack for Microsoft Windows Server 2003 Version 8.00A (English (US), Japanese)
ProLiant Support Pack for Microsoft Windows Server 2003 Version 8.10A (English (US), Japanese)
ProLiant Support Pack for Microsoft Windows Server 2003 x64 Editions Version 8.00A (English (US), Japanese)
ProLiant Support Pack for Microsoft Windows Server 2003 x64 Editions Version 8.11A (English (US), Japanese)
ProLiant Support Pack for Microsoft Windows Server 2003 Version 8.11A (English (US), Japanese)
ProLiant Support Pack for Microsoft Windows Server 2003 Version 8.15A (English (US), Japanese)
ProLiant Support Pack for Microsoft Windows Server 2003 x64 Editions Version 8.15A (English (US), Japanese)
ProLiant Support Pack for Microsoft Windows Server 2003 Version 8.15B (English (US), Japanese)
ProLiant Support Pack for Microsoft Windows Server 2003 x64 Editions Version 8.15B (English (US), Japanese)


How can I repair my repository? Of course I can remove all the PSPs added but I'm not sure that this can solve my problem forever. So does anyone know how to find corrupted repository item?

[Edward Latzko]

Use hpsum.exe instead of setup.exe.

[Alexx_B]

I try to run hpsum with same result :(

[Edward Latzko]

What version of the VCRM are you running? The current version of the VCRM is 2.2.0.820 . If not try updating to this version. let me know.....

[TechGuru]

Hi Alexx_B,

error generated while executing setup.exe [Sourceclient.exe] is not related to VCRM,

Just download the latest PSP from Internet, extract the psp in some test folder & check if setup.exe or hpsum.exe is working fine.

if it works fine, just copy & overwrite the extracted files into repository folder.

[fazil_1]

Could you not share the local SIM VCRM folder and connect to it as an share and run the setup ?

[Alexx_B]

>What version of the VCRM are you running?
My version was 2.1.10 with SIM 5.2.1. Now I have updated it to 2.2.0.820 (VCRM) and SIM 5.3.0

After update there is no any difference - error still occurs and VCRM catalog rebuild option still does not show any error

>error generated while executing setup.exe [Sourceclient.exe] is not related to VCRM,
I'm afraid you are not quite right. If I just run setup.exe from common PSP - there is no "catalog build" step executed. So even if I just copy all files from a newer PSP to a older with replace (save only updates from old version) - I still can't choose what version of PSP I can use.
So VCRM changes some files (xml I think) to allow possibility of using different PSP's versions

Of course I tried to do next thing: backup repository folder and move lastest PSP files into folder. Catalog builds normally but after target selection I see an error "discovery failed" on "select items to be installed" page so I can't just replace files as you advise.

I know than I can delete all the repository files, download all PSP's I use and add them into repository manually. But I want to use automatic repository update, this is so logically I think :)
So If next PSP update will break repository again - Will I have to do these steps again? Ha-ha, noway.
And that's why I want to know how can I clean repository to fix the bug

[TechGuru]

I am sure about what i say, trust me.

executing setup.exe will start the HPSUM & it will scan the current folder(Any folder with PSPs, no need to be a VCRM repository folder.) for updates, time taken for "build inventory of available updates" step is directly proportional to number of bundles available in folder.

i think the problem is, VCRM downloads the PSPs automatically but dose not replace the files which are already present in repository folder[like setup.exe, hpsum.exe etc.], hence they are not updated to the latest.

VCA & VCRM don't use setup.exe or hpsum.exe for deploying the components, windows smart components and bundles are deployed directly using VCA.

[Alexx_B]

OK. You say that HPSUM scans all updates in current folder. So why if I copy files from newest PSP to older one (with replace) I cannot choose PSP version to use?

>VCA & VCRM don't use setup.exe or hpsum.exe for deploying the components,
I knew it. When I said about VCRM I meant that seems like it modifying some components (XML?) and HPSUM searches other PSP versions components. I think that it is because I try to combine 2 PSP's and nothing happens :(

>i think the problem is, VCRM downloads the PSPs automatically but dose not replace the files which are already present in repository folder[like setup.exe, hpsum.exe etc.], hence they are not updated to the latest.
Maybe, maybe. But how I can correct it? Replace only setup.exe and hpsum.exe files or something else? As I wrote I try to copy all the newest PSP contents to VCRM folder and still an error exists

[Ramesh Upadhyayula]

I had the same issue with SourceClient.exe.
After trying numerous reinstalls what finally worked was cleaning out all the files in the temp directory.
Hopefully this works for others as well.

[Jorge Delgado S.]

Hi everybody,
We noticed at the page for downloading the PSP, there is also an update for HP Version Control Agent; it doesn't say anything about this error. We wrote down the package at wich the error comes up and it was this HP-VCA package. We tried download it manually and it failed in one of our machines. Once we got it, we include it in the PSP folder and ran it once again and this time the process completed.

Cheers,