Hello
I can confirm that they could not reproduce it in CU2...But they did have some fix releated in version 2018
Here is a workaround listed in the bug 32187 (this is the HF for the CU1 bug)
Execute the following command in a command Window running as administrator
c:\Windows\Microsoft.NET\Framework\v4.0.30319\regasm.exe "c:\Program Files (x86)\Common Files\Microsoft Shared\DynamicsSL\Microsoft.Dynamics.SL.ObjectModel.dll"
The assembly, Microsoft.Dynamics.SL.ObjectModel.dll who’s typical location is
c:\Program Files (x86)\Common Files\Microsoft Shared\DynamicsSL needs to be registered with COM for the Object Model to work properly. The Client Installation for Microsoft Dynamics SL 2015 did not do that properly. The CU1 update was not capable of registering the file, so this HotFix was created.
To accomplish that registration, the REGASM tool is used. It is installed with Microsoft.Net so is already available on the machine. Its typical location is…
c:\Windows\Microsoft.NET\Framework\v4.0.30319
------------------------------------------------------------
You might look at this below regarding the bug mentioned
The latest comments regarding this bug (the HF request submitted for CU2) are:
After creating the application and setting it to target the 32-bit configuration (rather than AnyCPU), the app loaded parent fine. After applying CU1 to the SL 2015 install, it did encounter a problem - as expected - but installing CU2 then fixed the issue.
I also was able to launch the Dynamics SL parent and application from Microsoft Excel after installing the 32-bit version of Excel. Apparently Object Model runs only under the 32-bit version.
Per comments below, this is not reproducible after the manual registration step provided with Bug 32187 is applied. The code hotfix for that bug has been included in CU2.
This is that workaround for manual registration
Execute the following command in a command Window running as administrator
c:\Windows\Microsoft.NET\Framework\v4.0.30319\regasm.exe "c:\Program Files (x86)\Common Files\Microsoft Shared\DynamicsSL\Microsoft.Dynamics.SL.ObjectModel.dll"
The assembly, Microsoft.Dynamics.SL.ObjectModel.dll who’s typical location is
c:\Program Files (x86)\Common Files\Microsoft Shared\DynamicsSL needs to be registered with COM for the Object Model to work properly. The Client Installation for Microsoft Dynamics SL 2015 did not do that properly. The CU1 update was not capable of registering the file, so this HotFix was created.
To accomplish that registration, the REGASM tool is used. It is installed with Microsoft.Net so is already available on the machine. Its typical location is…
c:\Windows\Microsoft.NET\Framework\v4.0.30319
In order to access the object model from Excel, the 32-bit version of Excel/Office must be installed. For an application to successfully access the Object Model, the app must be built with a target environment of x86.
Thank you
Jana MacDonald
Microsoft Dynamics Support
