SAP GUI 7.10 Repack
Hi all
First time poster, long time reader :)
Having some issues with SAP GUI 7.10, my client basically demands everything in MSI format so having to repack SAP GUI 7.10 using WISE Packaging Studio 7 SP2.
As far as I can tell the SAP GUI doesn't have a vendor MSI so am running a setup capture but when I go to execute the SAP installer it does nothing, the process is running in task manager but the setup wont launch while WISE is installed.
I have tested by running the installer on a clean Windows XP Pro SP3 VM and it installs fine but as soon as WISE is installed the SAP installer will no longer run properly.
Anyone have any ideas on what could be causing the problem?
First time poster, long time reader :)
Having some issues with SAP GUI 7.10, my client basically demands everything in MSI format so having to repack SAP GUI 7.10 using WISE Packaging Studio 7 SP2.
As far as I can tell the SAP GUI doesn't have a vendor MSI so am running a setup capture but when I go to execute the SAP installer it does nothing, the process is running in task manager but the setup wont launch while WISE is installed.
I have tested by running the installer on a clean Windows XP Pro SP3 VM and it installs fine but as soon as WISE is installed the SAP installer will no longer run properly.
Anyone have any ideas on what could be causing the problem?
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Posted by:
spartacus
15 years ago
Would your client consider using a wrapper MSI that deploys the source files and calls the vendor's original installer executable rather than repackaging the whole thing? The consensus (as I see it from reading the Package KnowledgeBase and related posts) seems to be that this might be a better approach in this case.
Regards,
Spartacus
Regards,
Spartacus
Posted by:
smallbytes
15 years ago
Posted by:
RJ
15 years ago
Posted by:
DLL_HELL
15 years ago
Does anybody ever search the forum for an answer before posting???
The SAP.710 source contains 3 runtime .msi These are special vendor supplied .msi designed to install to areas monitored by windows file protection. Normal .msi CAN NOT install to these areas.
Install these on your clean build before capturing SAP7.10
SAP will then work.
I really do not understand what the big issue is regarding SAP7.10 and why everyone seems to be so hung up over it. It can be packaged just like most other applications.
read my post here.http://www.appdeploy.com/messageboards/printable.asp?m=31883
SAP7.10 really does seem to separate the men from the boys!
The SAP.710 source contains 3 runtime .msi These are special vendor supplied .msi designed to install to areas monitored by windows file protection. Normal .msi CAN NOT install to these areas.
Install these on your clean build before capturing SAP7.10
SAP will then work.
I really do not understand what the big issue is regarding SAP7.10 and why everyone seems to be so hung up over it. It can be packaged just like most other applications.
read my post here.
SAP7.10 really does seem to separate the men from the boys!
Posted by:
anonymous_9363
15 years ago
ORIGINAL: DLL_HELLThose with grey matter between the ears do. The rest would rather you do all the work for them. I no longer respond, not even to tell 'em to use Google. See the request for a script to check free disk space posted today? God help me...
Does anybody ever search the forum for an answer before posting???
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.