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)

Solomon Issues

(0) ShareShare
ReportReport
Posted on by 235

We just upgraded to SL 2011. We're currently experiencing printing issues. Some users can print 1 check then go back and ROI.exe will crash. I was told that the ROI.exe hotfix was installed last night.

Other users will try and print get this error message: System Message 6201. Report Execution failed. Error = 56029. Error printing report. The printer specified can not be found. It may not be accessible in the current security context.

The IT Director claims that within Solomon there is no where to set permissions or access to printers.

There are no details from the System Message 6201

The details from the ROI.exe crash are below:

Description:
  Stopped working
 
Problem signature:
  Problem Event Name:                      CLR20r3
  Problem Signature 01:                     roi.exe
  Problem Signature 02:                     8.0.0.0
  Problem Signature 03:                     4fa196d2
  Problem Signature 04:                     Solomon.Kernel
  Problem Signature 05:                     8.0.0.0
  Problem Signature 06:                     4eb954b5
  Problem Signature 07:                     1bf
  Problem Signature 08:                     0
  Problem Signature 09:                     PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
  OS Version:                                       6.1.7601.2.1.0.18.10
  Locale ID:            1033
 
We are being told by the Director  that it's a local issue on our Terminal server (the users RDP into the server and access Solomon). This is what we've done to test it: 
1) connected the check printer to each computer and attempted to print through the redirect while connected to TS. This worked once and then we got the ROI.exe crash.
2) logged directly into the TS as the given user and sent a test print to the printer, printed fine.
3) We are currently sharing the printers on the TS and connecting users computers to them via the share
 
Why would the printers work one time and then ROI crash? How can we avoid ROI crashing if the hotfix has been installed?
 
 

*This post is locked for comments

I have the same question (0)
  • Carolyn Kolpien Profile Picture
    on at

    Hi Todd231,

    On the workstation, in SL, click on the Application icon and go to Printer Setup.  Check Use Windows Default Printer and also check Save as Default.  This will save the printer in the Solomon.ini file so that SL will always find the printer.  Let's see if that resolves the issue.  Let me know how it goes.

  • todd231 Profile Picture
    235 on at

    The users use an MSI package that actually logs them into a TS server and they use the software from the server. It's not installed on their computers other than a RDP session.

    Other than that area, is there any other printer setup within Solomon on the back end? I'm by no means an SL admin but I need to get this fixed.

    We've tried matching printer drivers between the server and the workstations, we've tried sending print jobs to other printers and we're still getting the ROI.exe crash.

    It's very strange.

  • Adam Leonard Profile Picture
    2,151 on at

    Hi Todd,

    I see you mentioned that the printers are being installed locally on the terminal server.  Do you know if the users are using ANY redirected printers?

    I would start by making the changes in this KB article (similar to what Carolyn mentioned above):

    952385

    How to configure Microsoft Dynamics SL to use the local Windows default printer

    mbs.microsoft.com/.../KBDisplay.aspx

    Have the users set a printer installed locally to the TS as their windows default printer then go into SL and tell it to "use windows default" and "save as default".  

    All printer info is stored in the solomon.ini file.  The above settings should tell the solomon.ini file to use the windows default printer (no matter what it is).  Try that and let us know if the issue persists.

  • todd231 Profile Picture
    235 on at

    Adam, I installed the printers locally and set Solomon to "use Windows default" which did not work. I've matched drivers specifically for the HP model of printer we are using as well as matched them with the HP Universal print driver.

    Again, concerning the ROI.exe crash:

    Our Solomon admin(s) think that it's a permissions issue within Active Directory. I don't think it is because these same users didn't have problems in the last version of Solomon.

    We did install Solomon 2011 on a new TS server which is 2008 R2. The old TS server is just 2008.

    One of our guys called MS support last night and they seemed to think it was a .NET issue. He upgraded .NET to 4.0 and killed the SL client on our TS. After a quick reinstall today, the ROI.exe crash is back. (Not sure if the install completed due to the crash last night. From what our guy said, it installed fine.)

    I really appreciate all of you guys help with this, and as an Network Admin it helps having a sounding board because right now, I'm not getting much of a response from our SL admins other than "It's a permissions issue, fix it".

    Thank you,

    Todd

  • todd231 Profile Picture
    235 on at

    One other thing, this TS server that Solomon is on is part of a cluster.

    It's virtual...

    Could that be an issue?

  • Suggested answer
    Community Member Profile Picture
    on at

    Hello Todd,

    I am running into the same error on a workstation and on the TS server for various users.  The client is also using Server 2008 R2.  I have also tried the default printer fix suggested.  It fixes some of the users but any batch reports automatically printed on release is getting this error.  My error is slightly different than yours:

    System Message 6201

    Report execution failed. Error = 56029

    There was an error running the report.  Make sure Crystal Reports 2008 has been updated to Service Pack 4 or later.

    Class not registered = ICRReportPrinterPageRange.

    I have applied the Crystal 2008 SP3.1 that came with the installation software.  But I can't find SP4.

    Did you get this issue resolved?

  • HolliV Profile Picture
    235 on at

    Todd,

    Did you ever fix your problem?  I have the same issue with process manager.

  • Community Member Profile Picture
    on at

    Support pointed me to a "redistributable" that fixed the problem.  Here is the link.

    mbs2.microsoft.com/fileexchange

    Apply it to all workstations, if you receive this error message about SP4.

  • lgroskopf Profile Picture
    5 on at

    I am also having this issue.  The link for the "redistributable" is not complete.  Can you complete it?

    Thanks!

  • Ajit Kannan Profile Picture
    1,246 on at

    Hi Todd231,

    The DLL file “u2lsol4.dll” may missing in \WRKSTN\Windows\Crystal under SL  root folder

    • Browse the “u2lsol4.dll” file under the SL installation files and place it in to the above mentioned path.
    • Register the DLL

    Refer the beneath link more detail

    ajitkannan-erp.blogspot.in/.../report-roi-has-stop-working-in-dynamics.html

    Thanks,

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