Home› General
ReportBuilder 22.04 now available including Delphi 12.1 support!
New Blog Post: Helper Routines

Re: Previous issue with shutting down D6 with RB 6.01

rbuserrbuser
edited September 2001 in General
The problem I thought went away after I uninstalled D6 and all of the add
on's including RB 6.01. However, what I found is this. Until I run my
first report D6 with RB 6.01 shuts down normally. After I try and print my
first report that generated the breakpoint I have mentioned elsewhere in
this NG, it will no longer shut down properly. It hangs at 100% cpu usage
and will not close. Nor will it let me change projects. If I remove RB
6.01, then it works normally. I don't know if it is due to something in my
report or the fact that I am running on Windows 2000 Server with SP2 and a
host of MS security patches.

Has anyone else encountered this problem? I am running D6 E, Infopower 3000
Pro latest version, ABC components, latest version and RB 6.01 Pro.

--
Regards,

John

www.barjohn.com
johng@barjohn.com

Comments

  • rbuserrbuser
    edited September 2001
    After spending several hours I was finally able to track down the problems
    once I found that I could not duplicate the problem on a second server set
    up with very similar software and all of Delphi 6 and the add on's being
    identical. Here is the source of the problem for anyone else that might
    experience these strange problems.

    Delphi 6 not shutting down and hanging at 100% cpu usage was due to
    configsafe running on the system. It has an applet that detects when you
    are adding a new program or removing a program to allow you to get a
    snapshot of the system state. Apparently it and RB did not get along and it
    would keep D6 from closing when RB was loaded.

    The problem with the strange breakpoints is caused by not having a printer
    driver that RB likes set as the default printer. I have two network
    printers, and HP1100 running on another Win2k server and an HP4500 running
    on a third server. I had the default set to the HP1100 and it caused this
    problem. If I selected the HP4500 the problem goes away. If I select a
    dummy local printer with its port set to file (an HP4050) it works OK. It
    just doesn't like the HP1100 even though it has the proper Win2kDriver
    installed. This bug should be documented and hopefully fixed.

    --
    Regards,

    John

    www.barjohn.com
    johng@barjohn.com
This discussion has been closed.