ROI has stopped working

(0) Share

Report

Posted on by Community Member

I have been chasing an ROI has stopped working issue with SL 2011 now for a couple of weeks and I am hoping someone might have a suggestion beyond the no printer recognized cause. This is happening at a client with any new installs of the SL client even though prior installs of that client are not getting the error. It happens when setting up the printer to a local printer or to a network printer that other functional workstations that do not have the problem are using or even using the Windows XPS printer. The user has local admin rights and the client was installed using run as administrator. I have refreshed the contents of the WRKSTN folder from my contents (just in case one of the files was corrupted or missing). I have created debug.tlb file in the main folder so I could track the ROI progress and it gets through the RI-Where, the RI_Replace, the RIPARAMS and the Number of Entries in steps before aborting. so, it is aborting just before it would present the "Number of entries in RIPARAMS = xxx step. What it is actually doing at that time remains a mystery. It does seem, based on the debug displays, that it is failing before even determining the printer.

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

Butch Adams 4,763 on at

Like (0)

Report

I've dealt with that twice on 2011 RTM. Both times it came down to bringing Windows updates current. The caveat being, I had attempted a number of things, so I am not sure that alone did it.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Butch,

Thanks for your response. Unfortunately, all the workstations at this client are built from the same Windows 7 image and I checked and the working and non-working workstations are at the same build level.

I forgot to mention in my original post that these are 64-bit Windows 7 workstations but since the functional ones are as well, that does not seem to help. What is puzzling is that the client installs on the functional workstations were done over a year ago and the failing client installs were done less than a month ago.

Was this reply helpful? Yes No
Butch Adams 4,763 on at

Like (0)

Report

Rick,

I wonder if you could talk them into doing a scratch install of Windows 7 and then SL to see if it would work. Worse case is they just reimage the machine.

...b

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Butch,

That was a good thought but we already built a virtual machine with a clean Windows 7 install and got the same error. I am going to have them build a 32-bit Windows virtual machine just to make sure that is not the issue as well (I don't think so since they have other 64-bit Windows boxes working and I have other client using 64-bit Windows without the error).

My next step[ is to run a SQL trace with the debug.tlb file set on a working workstation and then on a failing workstation tracking ROI and see if I can determine the last SQL request that was made by ROI before it failed. Kind of a long short but it is the only bullet left in my holster at this point. I see several posts out their within the forum and outside the forum with people having this issue but most of them either have no resolution or they are the standard no printer issue. A couple seem to even be misleading as they talk about registering various DLLs some of which are not one that regsvr32 or regsvr64 can even register because they have no entry point..

Was this reply helpful? Yes No
brent_quick 180 on at

Like (0)

Report

Default report and no modifications on grouping or sort via Template? If yes the skip to last sentence.

I had huge problems (2015) with ROI not responding and it was that the 7.0FP1 report templates were changing sorts and groups in invalid ways. Did modified versions for the specific use case (based of Detail GL report) and made grouping and sorts work (or default) and no issue since.

Sorry to not help directly, but the ROI processor is a black box mostly when it craps out.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Brent,

In my client's case ROI is aborting on any report in any module (I did not make that clear) but thanks for the response. Yes, templates carried forward from prior releases, primarily those built when SL was using VB6 (e.g. version 6.5) to SL using VB.NET typically have to be dropped and recreated. And yes, ROI is a "black box" and is one of the protected code segments of SL. I am a long-time Solomon partner going back to the pre-Microsoft days and purchased source code listings from Solomon but SWIM and ROI were not included in those listings back then either. Error messages like this are sometimes very hard to determine the cause when the message is generic and the details are of no help (except to someone who has the code) and no event log is generated with additional information. We simply rely on other users who have had the issue and stumbled into a solution to share their solution. But. like Butch stated, when you shotgun a problem, many times you are not sure what change or changes actually ended up taking care of the problem.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Problem was finally resolved. Some time back, hot fix BUG24224ALL had been installed on the server to correct the ability to print AP checks in name order. That hot fix included an updated version of swimapi.dll that goes on the workstation but it does not replace that dll as part of the workstation setup so the hot fix has to be run on each new workstation after the standard client is installed. This hot fix is a collection of fixes so it brings along "friends".

The way this was determined was to look at the build number of ROI.EXE and then run down what hot fix replaced it. Then look for other dlls that are workstation dlls that were part of that hot fix.

I know there have been several posts about "ROI.EXE has stopped working" and many of those posts never included a resolution so I hope this might help someone else in the future.

Was this reply helpful? Yes No
Butch Adams 4,763 on at

Like (0)

Report

Nice detective work!

Was this reply helpful? Yes No