Problems with HPSUM when start from Insight Repository

[olmit]

Hello,

we use the HPSUM Utility from the Repository (Version Control Repository Manager). The command-line is:

\\\repository$\HPSUM.EXE /bundle:bp000569.xml /silent"

Since a few weeks we got an error for i386 based systems when we use the tool, x64 based systems are working fine. In the file OpMan.trace we get following lines:

"Target.cpp[767]: Target 0: Starting Component Discovery, Installable cp009538.exe
Target.cpp[673]: Target 0: Received Discovery Command: i fail 155:
"

When we use the GUI (hpsum.exe without options) then it displays
"loading" ...
"initializing" ...
Step 1 of 3 Inventory ...
Now we press "Next" (Local Host)
Step 2 of 3 Check System ...
an here an error "Status Discovery Failed" is displayed. In The OpMan.trace is the same Error (like described above).

Whe we start the cp009538 manualy on a i386 based system we get the following error:

"The Image file cp009538.exe is valid, but is for a machine type other then the current machine"

In the last weeks arrived some more files which produced this Problem an so we have to rename these files from the repository befor we can install the PSP on i386 based systems.

What can we do to eliminate this Problem?

[Cederberg]

well there are diffrent supportpacks for windows x64 and x86 so the later problem where you get that machinetype was wrong is probably because you are trying to install a x64 package on a x86 operating system or vice versa..

Would think that is the problem on the HPSUM problem as well.. but when you say that it had worked before it can't be...

[olmit]

Hello an thank you for your answer.

We have only one repository for all architectures and we use different xml-files for i386 (i.e. 569.xml) and x64 (i.e. 570.xml) based systems. But in every case the hpsum is trying to execute the file cp009538.exe. I don't know why the execution is startet, but that couldn't work because the package ist compiled for x64 systems. Other drivers-packages for x64 based systems are compiled in i386 format, they didn't produce an error. Maybe the hpsum should have a look at the file format before executing the packet....

And, yes, it worked fine for couple of years....

[GM Llewellyn]

Did you find a fix for this?

[olmit]

We use now the batch-files bp000xxx.cmd instead hpsum. Since a few weeks the repository manager didn't load down any of the problematic files, but we didn't try it out till now.