Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 17 SEP 2007 02:24:24PM Gray Cunningham wrote:

Last week I upgraded a customer (whom I just inerited) from OI 3.7.5 all the way to OI 8.0.1. Now when they try to print reports that had been generated with REPORTER, they encounter a "Could not connect to OI. Check your User Name and Password" error messgae. I realize that Reporter is no longer supported…in fact I have never used it, but I was under the impression that existing reports would most likely still work. Back in 2004, Jim Vaughan had posted a similar issue and Sean had asked Jim to email him directly as he had a possible solution. Jim subsequently posted that it had worked. I am at my customer's site right now, Sean is teaching a class this week and no one else currently in the office at Revelation is familiar with this. Jim are you out there? Or does anyone else have any suggestions?

Thanks,

Gray Cunningham


At 17 SEP 2007 02:46PM Jim Vaughan wrote:

At the time the fix that I was sent was a new oinsight.exe; but that was back in 2004.


At 17 SEP 2007 02:50PM Gray Cunningham wrote:

Bummer! I was hoping it might be more generic than that. Thanks for your quick response.


At 17 SEP 2007 02:54PM Jim Vaughan wrote:

How are you running the report?

This is the code I use:

Subroutine [/color]Run_Report_Tactic(Report_Name) 
[/color]****************************************************** 
****************************************************** 
[/color]$insert [/color]CMCommon 
[/color]Declare Function [/color]Utility, Drive 
[/color] 
[/color]* if . use full install path  
[/color]If [/color]Report_Name[/color]1[/color],[/color]1[/color]=[/color]"." [/color]Then 
    [/color]Install_Path=Drive() 
    [/color]If [/color]Install_Pathlen(install_Path),[/color]1[/color]=[/color]'\' [/color]Then 
      [/color]Report_Name=Install_Path:report_Name[/color]3[/color],[/color]10000[/color] 
    [/color]End Else 
      [/color]Report_Name=Install_Path:report_Name[/color]2[/color],[/color]10000[/color] 
    [/color]End 
End 
[/color] 
[/color]* do nothing if no report, this will be true when called from callback 
[/color]If [/color]Report_Name # [/color]"" [/color]Then  
  [/color]Mssg=[/color]'Loading Report' 
  [/color]Call [/color]Msgx(mssg,[/color]''[/color],[/color]''[/color],[/color]''[/color]) 
  [/color]Call [/color]Wait() 
  Callback=[/color]"" 
  [/color]* Modality 
  [/color]Callback1] [/color]= [/color]1 
  [/color]Callback2] [/color]= [/color]"Run_Report_Tactic" 
  [/color]* With Null Paramater So That No Report Runs 
  [/color]Callback3] [/color]= [/color]"" 
  [/color]Status=Utility([/color]'RUNWIN'[/color],Drive():[/color]'\REPORTER.EXE /AP=w_Tactic /UN=w_Tactic /RP=[/color]:Report_Name:[/color]' /RE=0 /PV=1 /QU'[/color], Callback) 
  [/color]Call [/color]Msgx([/color]""[/color]) 
[/color]End 
Return[/color][/color][/size]         
               

At 17 SEP 2007 03:48PM Gray Cunningham wrote:

They are executing a pre-defined report right from a menu item quickevent.


At 17 SEP 2007 04:51PM Gray Cunningham wrote:

Here's a new and very interesting tidbit of information: Prior to the upgrade, all of the workstations were running XP Home. The hardware guys wanted to go to XP Pro and tried to upgrade the workstations. All but one of the workstations didn't like the upgrade (they were cheap store-bought HPs) and so they were wiped clean and received a fresh install of XP Pro. The one workstation that allowed the upgrade (a clone) does not have any REPORTER related problems and all the others do.


At 17 SEP 2007 05:11PM Karen Oland wrote:

Have you tried installing the old version again (on the "new" xp installs), then upgrading right along.

Sounds like an unregistered ocx/dll or registry issue.


At 17 SEP 2007 05:19PM Sean FitzSimons wrote:

Gray,

Karen has an idea. However, try reinstalling the Client Install alone. A clean system would not have the Client DLLs necessary to run Reporter.

Sean


At 17 SEP 2007 05:39PM Jim Vaughan wrote:

A clean install of OI 8 does not work with reporter, you need to install an old version that supported reporter.exe and upgrade it to OI 8.


At 17 SEP 2007 06:08PM Gray Cunningham wrote:

This one is an upgraded one.


At 17 SEP 2007 06:40PM Gray Cunningham wrote:

I may have led you astray…it appears that the workstation had nothing to do with it. What does happen is that the user will encounter the "Could not connect to OI. Check your User Name and Password" error message on their first use of REPORTER. If they click "OK" and then close the application error that follows, they can then use REPORTER all they want until they log out of OI. Once they log out and back in, they return to the point where they encounter the error on the first use of REPORTER. Obviously, my customer is hoping for a more elegant solution and so am I…but at least we have a temporary work-around. So far, my only other solution is to go back to OI 4.1.3.

We did have to run the old Client Install on the newly loaded workstations.

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/3c0f7dc7eb0983998525735900651c64.txt
  • Last modified: 2024/01/04 20:57
  • by 127.0.0.1