SAPgui 6.20
I have repackaged the SAPgui 6.20 client application using AdminStudio but I am unable to resolve ICE33 errors using the conflict wizard. There are 140 registry entries which have not been captured in the relevant tables (ProgID) etc.
The problem is that these registry entries conflict with another existing .msi application and result in a repair of SAPgui when the other application is launched, much to everyones confusion.
How do I resolve the ICE33 errors in my SAPgui.msi so that it no longer conflicts with the other .msi application?
The problem is that these registry entries conflict with another existing .msi application and result in a repair of SAPgui when the other application is launched, much to everyones confusion.
How do I resolve the ICE33 errors in my SAPgui.msi so that it no longer conflicts with the other .msi application?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
MSIMaker
20 years ago
If the registry entries are referencing DLL's then move the dll's into the SAP Program folder and remove the reg keys and try it. SAP will locate the files it needs without the keys.
You can also create a .local file for all of the exe files so that they look for their dependant files in the apps main folder.
You can also create a .local file for all of the exe files so that they look for their dependant files in the apps main folder.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
