Welcome to the Sage 300 Support Group on Community Hub! Available 24/7, the Forums are a great place to ask and answer product questions, as well as share tips and tricks with Sage peers, partners, and pros.
On Windows Server 2012 R2, after installing Sage 300 2017 and Crystal Reports Pro 2016, some Crystal Reports dlls (such as u2lcapw.dll) are not accessible from Crystal Reports Designer, so custom reports don't run in the Designer.
The dlls were installed (by the Sage300 installation program?) in SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86. In previous Accpac/Sage300 Revisions, they were installed in windows\crystal, but not so in this instance.
Sage 300 was installed to C:\Sage300\Programs. Crystal Reports Pro (purchased from Sage) was installed to the default location set by the CR Pro installation program.
What is the correct procedure for making this dll (and others) available? We used to be instructed to copy the dlls from c:\windows\crystal to c:\windows\system32, but in this case they have not been installed in windows\crystal.
This has now happened on two Sage 300 2017 installs which we have in progress.