Error 1904
I have a package which im are unable to install unatennded.(Crystal Report for SAP B1)
GUI mode works perfectly but when trying to run the package silent i get this message
Error 1904. Module xxxxxx\EnterpriseFramework.dll failed to register. HRRESULT -2147024770. Contact your support personell
Read something that this have to do with the self Reg Table. But this is a vendor msi and i prefer not to mess with it
I have tried searching for the dll in that table also but did not find it
Any idea how to solve this?
GUI mode works perfectly but when trying to run the package silent i get this message
Error 1904. Module xxxxxx\EnterpriseFramework.dll failed to register. HRRESULT -2147024770. Contact your support personell
Read something that this have to do with the self Reg Table. But this is a vendor msi and i prefer not to mess with it
I have tried searching for the dll in that table also but did not find it
Any idea how to solve this?
0 Comments
[ + ] Show comments
Answers (15)
Please log in to answer
Posted by:
ekniranjan
14 years ago
you are getting error when you run silently, right ?
what type of switch you tried like ..../s /?
I face this on for Photoshop Elements old version.
what type of switch you tried like ..../s /?
I face this on for Photoshop Elements old version.
Posted by:
anonymous_9363
14 years ago
You almost certainly have a missing dependency. Google 'sap enterpriseframework.dll'.
Posted by:
Bankeralle
14 years ago
switch you tried
im using msiexec /i crystalreport.msi INSTALLDIR=%SYSTEMDRIVE%\Apps\Crystal /qb!
If im using the same command without /qb! it works fine
Posted by:
mekaywe
14 years ago
Is that entry present in SelfReg Table then take the Wisecomcapture of the DLL and add the registries to respective component and delete the SelfReg entry
Posted by:
anonymous_9363
14 years ago
Sorry, Kaare, I completely missed the part of your post where you said that GUI mode runs OK but silent does not.
I suspect that the MSI contains a CA which is attempting to register that DLL but, for whatever reason, the CA isn't being executed in UI mode. If you log the install, it will identify the rogue CA for you, if you can't identify it by eye. Once you know which it is, you can condition it out (using 'If 0=1', or something like that) in your tansform. That transform will obviously also contain the COM information for the DLL.
I suspect that the MSI contains a CA which is attempting to register that DLL but, for whatever reason, the CA isn't being executed in UI mode. If you log the install, it will identify the rogue CA for you, if you can't identify it by eye. Once you know which it is, you can condition it out (using 'If 0=1', or something like that) in your tansform. That transform will obviously also contain the COM information for the DLL.
Posted by:
ramsudheer
13 years ago
@Bankeralle
Posted by:
anonymous_9363
13 years ago
- Have you installed all the pre-requisites?
- Have you tried to find whether or not a Custom Action is responsible for trtuing to register that DLL?
- Have you tried to find whether or not a Custom Action is responsible for trtuing to register that DLL?
Posted by:
ramsudheer
13 years ago
@VBScab: There are no pre-requisites for this application (SAP Crystal Reports 12.0).
I compared both the log files i.e Installation with UI and Silent installation. In silent installation, it struck at the Action SelfRegModules (EnterpriseFramework.dll). I even tried to get the registry information using WiseComCapture for this DLL but no luck.
Could you pls suggest any other approaches. Thanks
I compared both the log files i.e Installation with UI and Silent installation. In silent installation, it struck at the Action SelfRegModules (EnterpriseFramework.dll). I even tried to get the registry information using WiseComCapture for this DLL but no luck.
Could you pls suggest any other approaches. Thanks
Posted by:
anonymous_9363
13 years ago
You don't think that, perhaps, a reporting tool which is designed for SAP might require - at the very least - a SAP client? You know best...
EDIT:
What happens when you load that DLL into Dependency Walker? How many yellow or red triangles does DW display? THOSE are the dependencies for that DLL. Without them, you'll never register the DLL [shudder...] or extract COM information from it.
EDIT:
What happens when you load that DLL into Dependency Walker? How many yellow or red triangles does DW display? THOSE are the dependencies for that DLL. Without them, you'll never register the DLL [shudder...] or extract COM information from it.
Posted by:
pjgeutjens
13 years ago
GUI mode works perfectly but when trying to run the package silent i get this message
When you say GUI mode, do you mean a straight msiexec of the msi with UI, or the SAP setup.exe program?
Reason why I ask is that this reminds me of an issue I had installing SAP Business Objects XI without using SAP's setup, which would throw very similar errors.
Reason was (I decided) that the setup.exe actually handles some of the DLL registrations that are prerequisite for the DLLs in the actual MSI.
If it's straight msiexec GUI mode, try laying the UI and Execution action sequences next to each other and look for missing CAs
PJ
Posted by:
ramsudheer
13 years ago
Thanks for your replies.
@VBScab: There are there DLLs which were showing in red color. I searched those dll files in the media folder, but I couldnt find those files. Let me re-check again on this and let you know.
@PJ: I am running through MSIEXEC, it was installing fine in UI mode but not through Silent install.
I have commented out SelfRegModules Action in ExecuteImmedaite mode and installed the application, though the application is installed successfully but lot of files were not installed.
@VBScab: There are there DLLs which were showing in red color. I searched those dll files in the media folder, but I couldnt find those files. Let me re-check again on this and let you know.
@PJ: I am running through MSIEXEC, it was installing fine in UI mode but not through Silent install.
I have commented out SelfRegModules Action in ExecuteImmedaite mode and installed the application, though the application is installed successfully but lot of files were not installed.
Posted by:
joseph
13 years ago
Hi,
When we install the application in QB! then only we are getting this error, that means it is not installing all the required files or dlls , this causes an error . So, before registering any dll files those files should be there ,otherwise it will throw an error. we had the same issue with this application.So we added the property ADDLOCAL=ALL in mst , installed using QB! . it worked. Then while installing it will install the dll and then it will try to register the DLL.
Thanks,
R.Joseph.
When we install the application in QB! then only we are getting this error, that means it is not installing all the required files or dlls , this causes an error . So, before registering any dll files those files should be there ,otherwise it will throw an error. we had the same issue with this application.So we added the property ADDLOCAL=ALL in mst , installed using QB! . it worked. Then while installing it will install the dll and then it will try to register the DLL.
Thanks,
R.Joseph.
Posted by:
ramsudheer
13 years ago
@Joseph: Thanks for your reply.... I implemented the same thing.. it worked perfectly..
Posted by:
anonymous_9363
13 years ago
Aaaaahhhhhhhh....the penny drops....
I'd wager that the features or components which don't get installed are conditioned using UILevel, or another property which is set using UILevel.
I'd wager that the features or components which don't get installed are conditioned using UILevel, or another property which is set using UILevel.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.