web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

CR conflicting versions running SL2015 and another app

(0) ShareShare
ReportReport
Posted on by 719

We have SL2015 with Crystal Reports 2008 sp5 (12.5.0.1190), and also have Sage Fixed Assets with CR on the same Windows 10 workstation. The two Crystal Runtime installations coexisted until an update from Sage was installed that updated Crystal  Runtime for .NET to version 13.0.9.1312. That update broke both program's ability to run Crystal reports; SL began returning an ROI error for any report.

Sage required an additional update for reports to print, but it is working now. SL is still returning an ROI error when attempting to run any Crystal report. A full installation of the Crystal version provided with Solomon was performed on the workstation, but nothing changed; SL reports still return an ROI error when opened. The Crystal Reports designer installation from the SL media is working.

Has anyone else found how to get these Crystal reports installations to coexist?

*This post is locked for comments

I have the same question (0)
  • Butch Adams Profile Picture
    4,763 on at

    Have you tried repairing the SL install? SL installs its CR runtimes, not the CR Designer software, so maybe an SL reinstall will fix it up.

  • Brian_IL Profile Picture
    719 on at

    Thanks for the suggestion. I tried removing and reinstalling the SL2015 cu1 client with no change in the Crystal Reports ROI error. The Sage Fixed Assets installation of Crystal was fixed by installing an update for MS Visual C++ 2015 (x86). Version 14.0.24123 is now installed. The SL client installed MS Visual C++ 2012 (x86) 11.0.60610.

    I installed the latest Visual Studio update 4 for VS2012, it is now running C++ 2012 version 1.0.61030, but nothing changed with the ROI error running reports from SL. Any other suggestions?

  • Butch Adams Profile Picture
    4,763 on at

    Have you looked in your Windows Event Log for clues?

    And just so we don't overlook the most common reason for the error - Have you double checked that you have assigned a valid printer?

  • Brian_IL Profile Picture
    719 on at

    Hi Butch,

    The printer setup is valid and tested working for other apps. It worked from SL until the other program appears to have updated a shared setting or a shared file in Windows.

    The Win10 Application Event log reports a .NET error, followed by an Application Error recorded by ROI.EXE. The detailed XML from the log is below.

    Log Name:      Application

    Source:        .NET Runtime

    Date:          2/2/2018 1:13:58 PM

    Event ID:      1026

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:     xxxxxxxxxxxx.local (not the actual computer name)

    Description:

    Application: ROI.EXE

    Framework Version: v4.0.30319

    Description: The process was terminated due to an unhandled exception.

    Exception Info: System.InvalidCastException

      at ROI.My.MyApplication.MyApplication_UnhandledException(System.Object, Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.raise_UnhandledException(System.Object, Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnUnhandledException(Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnUnhandledExceptionEventAdaptor(System.Object, System.Threading.ThreadExceptionEventArgs)

      at System.Windows.Forms.Application+ThreadContext.OnThreadException(System.Exception)

      at System.Windows.Forms.Control.WndProcException(System.Exception)

      at System.Windows.Forms.Control+ControlNativeWindow.OnThreadException(System.Exception)

      at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

      at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageA(MSG ByRef)

      at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)

      at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)

      at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])

      at ROI.My.MyApplication.Main(System.String[])

    Event Xml:

    <Event xmlns="schemas.microsoft.com/.../event&quot;>

     <System>

       <Provider Name=".NET Runtime" />

       <EventID Qualifiers="0">1026</EventID>

       <Level>2</Level>

       <Task>0</Task>

       <Keywords>0x80000000000000</Keywords>

       <TimeCreated SystemTime="2018-02-02T19:13:58.427110000Z" />

       <EventRecordID>33297</EventRecordID>

       <Channel>Application</Channel>

       <Computer>xxxxxxxxxxxxx.local</Computer>

       <Security />

     </System>

     <EventData>

       <Data>Application: ROI.EXE

    Framework Version: v4.0.30319

    Description: The process was terminated due to an unhandled exception.

    Exception Info: System.InvalidCastException

      at ROI.My.MyApplication.MyApplication_UnhandledException(System.Object, Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.raise_UnhandledException(System.Object, Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnUnhandledException(Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnUnhandledExceptionEventAdaptor(System.Object, System.Threading.ThreadExceptionEventArgs)

      at System.Windows.Forms.Application+ThreadContext.OnThreadException(System.Exception)

      at System.Windows.Forms.Control.WndProcException(System.Exception)

      at System.Windows.Forms.Control+ControlNativeWindow.OnThreadException(System.Exception)

      at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

      at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageA(MSG ByRef)

      at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)

      at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)

      at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()

      at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])

      at ROI.My.MyApplication.Main(System.String[])

    </Data>

     </EventData>

    </Event>

  • Community Member Profile Picture
    on at

    We hit the same problem that hit you.  The solution from Sage is that SL and Sage Fixed Assets cannot reside on the same machine. A VM (Virtual Machine) will work.  

    Unable to cast COM object of type 'CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass' to interface type 'Crystal Decisions.ReportAppServer.Controllers.ISCRReportSource'.

    Products
    Sage Fixed Assets 2018

    Description

    • Sage Fixed Assets 2018.1
    • Sage Fixed Assets Crystal runtime 13.0.21
    • 3rd party applications using crystal runtime
    • IQMS
    • IQMS Crystal runtime 13.0.13.1597
    • Error when running reports in 3rd party application after upgrade to Sage Fixed Assets 2018.1
    • Error running reports after upgrade to 2018.1
    • Unable to cast COM objects
    • CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass
    • CrystalDecisions.ReportAppServer.Controllers.ISCRReportSource
    • No such interface supported
    • The document has not been opened.
    • Epicore
    • Skyline
    • Heritage Financial
    • MS Dynamics
    • Automaster Systems AMS2000
    • Blackbaud
    • The Financial Edge
    • Vista Viewpoint
    • Sage X3 Version 6.5 Workstation Client and earlier versions



    Cause

    Crystal runtime version conflict between 3rd party software and Sage Fixed Assets 2018.1.

    Sage Fixed Assets 2018.1 does use Crystal Runtime version 13.0.21

    The 3rd party applications that conflicts in crystal runtime with Sage Fixed Assets 2018.1:

    • IQMS
    • Epicore
    • Skyline
    • Heritage Financial
    • Automaster Systems AMS2000
    • Blackbaud
    • The Financial Edge
    • Vista Viewpoint
    • MS Dynamics
    • SysPro
    • Sage X3 Version 6.5 Workstation Client and earlier versions



    Resolution

    The two products are unable to generate reports when installed on same machine. Install Sage Fixed Assets 2018.1 onto a separate machine (VM is possible).

     

  • Community Member Profile Picture
    on at

    We can now add Vertex software to the list that breaks Crystal Reports.   Vertex version 13.0.23.2819 is latest and part of regular monthly update.   

  • Suggested answer
    Tny Profile Picture
    10 on at

    In case of Vertex's In-direct Returns, I have a fix.  Create ROI.exe.config in the same folder as ROI.exe.  The config file needs to contain assembly redirects for each Crystal reports assembly.  You have to make sure every client machine that runs Dynamics has the 13.0.23.2819 version of Crystal Reports installed.

    The newVersion number should be confirmed by going to C:\Windows\assembly\GAC_MSIL\CrystalDecisions.CrystalReports.Engine.  The first part of the next sub folder is the version number.

    Who at Microsoft has to be blackmailed to get a CU3 with current version of Crystal Reports?  Even better would be if all the assemblies where side by side and not GAC'd.

    <?xml version="1.0" encoding="utf-8"?>

    <configuration>

    <startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/></startup>

    <runtime>

     <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.CrystalReports.Engine" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportSource" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>    

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.Shared" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.Web" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.Windows.Forms" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.ClientDoc" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.CommonControls" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.CommonObjectModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.Controllers" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.CubeDefModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.DataDefModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.DataSetConversion" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>    

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.ObjectFactory" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.Prompting" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.ReportDefModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

       <dependentAssembly>

         <assemblyIdentity name="CrystalDecisions.ReportAppServer.XmlSerialize" publicKeyToken="692fbea5521e1304" culture="neutral"/>

         <bindingRedirect oldVersion="0.0.0.0-13.0.2000.0" newVersion="13.0.3500.0"/>

       </dependentAssembly>

     </assemblyBinding>  

    </runtime>

    </configuration>

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans