![]() ![]() Start-Process "2017/vc_redist.圆4.exe" -Wait -NoNewWindow -ArgumentList '/install /passive /norestart' \ Start-Process "2017/vc_" -Wait -NoNewWindow -ArgumentList '/install /passive /norestart' \ Since I also use an xml data source I include java and the CR xml piece. I included both the x32 and 圆4 for all components or just remove x32 or 圆4 pieces if not needed. I also tested with the 2017 C runtime and it works fine. It looks like in the latest images we do not need to add the dll's any longer. Start-Process msiexec.exe -Wait -NoNewWindow -ArgumentList '/i C:\CRRuntime_64bit_13_0_9.msi /quiet /qn /lie! c:/msi_install.log' Start-Process msiexec.exe -Wait -NoNewWindow -ArgumentList '/i C:\vcredist.msi /quiet /qn /lie! c:/msi_install.log' \ RUN copy C:\Installs\oledlg32.dll c:\windows\system32\oledlg.dll \Ĭ:\windows\system32\regsvr32.exe c:\windows\system32\oledlg.dll \Ĭopy C:\Installs\oledlg64.dll c:\windows\syswow64\oledlg.dll \Ĭ:\windows\syswow64\regsvr32.exe c:\windows\syswow64\oledlg.dll \ So in total, my Dockerfile for installing Crystal Reports Runtime looked like: Useful information about dependencies for older versions of the runtime can be found here: (Mine did.)įor the record, I got oledlg32.dll from my Windows 10 Enterprise install system32 and SysWOW64 folders (renamed them 32 and 64 so I could store them in the same docker context folder) and to get the Crystal Reports Runtime installed, I also had to install (You can use the volume mapping feature of Docker to get that file in there.)įrom your mounted directory, you can then simply then. ![]() (or extracted from the installation media). So if you want to continue, knowing the potential pitfalls, I'd start the container with a volume containing oledlg.dll from a full install of Windows Server Now, you're probably not interested in using functionality that would end up calling these OLE APIs. This is understandable because these APIs Turns out, pageobjectmodel.dll requires oledlg.dll (which isn't included in Windows Server 2016 Server Core). I extracted the DLL from the MSI and looked at its dependencies. NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win64_圆4\pageobjectmodel.dllįailed to register. Module C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for. MSI (s) (24:94) : Product: SAP Crystal Reports runtime engine for. I reproduced this issue, here's a snippet from the MSI installation log (msiexec /i x.msi /l*v log.txt): ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |