Windows Defender not compatible with FoxPro or DonorPerfect?

[Guest]

We recently installed Windows Defender and found we now get error messages
when doing Microsoft Word merges via DonorPerfect. Computer that do not have
Windows Defender installed work great and can merge without problems.

Once Windows Defender has been installed, uninstalling it again does not
help the DonorPerfect error messages. Thus, Windows Defender must not
uninstall correctly or else monkies with Windows XP settings.

Anyone have any ideas? What does Windows Defender all modify that it would
not uninstall correctly?

 

[Bill Sanderson]

I've got Windows Defender installed on about a dozen machines which also
have DonorPerfect installed--not the absolute newest release, but one back.
I haven't needed to do such a merge since the 14th when the app was
released, but I think it is unlikely that no one else has, and I haven't
heard this complaint.

I have seen one or two other messages relating to odd FoxPro messages and
Windows Defender--I'd love to have you post the error messages as accurately
as possible, and also any system event log messages related to them if
possible.

 

[Guest]

Thanks for your response, Bill. Here is what happens in DonorPerfect v8:

1) We go into a donor record and hit the printer button on the button
toolbar. We then choose "Merge a Letter...".

2) On computers with Windows Defender installed, we get the following two
error messages in a row:

"There has been an error. If you do not understand this message, call your
DonorPerfect Representative. Pressing Cancel will exit you from the system.
ERROR CODE: 11. Function argument value, type, or count is invalid.. /
unlisted program / 0"

"There has been an error. If you do not understand this message, call your
DonorPerfect Representative. Pressing Cancel will exit you from the system.
ERROR CODE: 12. Variable 'MERROR' is not found.. / unlisted program / 0"

The merge then does not work. The template Word doc will come up, but not
one with the proper merge fields filled in. This happens with all merges
when merging from donor records within DP. Other kinds of merges work just
fine, just not this kind.

Everything worked just fine before Windows Defender was installed.

The only event viewer errors I show are under "System". A DCOM error
happens about every minute or two. Event ID is 10009 and error is: "DCOM was
unable to communicate with the computer LIFE2 using any of the configured
protocols."

- Matt.

 

[Bill Sanderson]

Is Life2 a server? Is there an HP printer installed on this machine? If
so, what model?

My client is on 7.0--but there's a new version for one of our two databases
sitting awaiting "the right moment" to update it.

It's quite possible that the DCOM error is relevant to the issue that you
are seeing--not sure, though.

I don't have any immediate suggestions, but let me know about the
questions --and I'm still pondering.

--

 

[Guest]

Thanks again for your responses, Bill. Yes, LIFE2 is our Novell NetWare 6
server. Model is an older Compaq Proliant 800. We run DonorPerfect through
our workstations, but the main DPW32 directory is on the LIFE2 network
storage. Yes, almost all staff have HP laser printers attached ranging from
HP 5P - new HP 1012 models.

I don't know of anything that changed the week DonorPerfect stopped merging
except installing Windows Defender on all workstations. You'd think
uninstalling it would restore things back to the way they were.

- Matt.

 

[Bill Sanderson]

On a couple of workstations with the small--"breadbox" sized HP printers, I
was seeing DCOM errors every 30 seconds.

The info in this cut and paste from www.eventid.net is what cleard them for
me:
-----------------------------------------------------
In my case, this problem occurred between two Windows 2000 Professional SP4
workstations and an HP Print Server Appliance 4200, which is joined to a
Windows 2000 AD Domain. HP LaserJet 1320 Toolbox miss-registered itself
during standard install, caused two DCOM errors every 35 seconds.
To fix the problem, at a command window from the directory \windows\system32
run the command:
hpbpro.exe -RegServer
If the problem persists then run the following command:
hpbpro.exe -Service.
See the link to "HP LaserJet and LaserJet AiO Printers - DCOM Error Message"
for additional information on this problem.
----------------------------------------------------
Check systems seeing these dcom errors for hpbro.exe--and execute those two
commands on them. You'll probably find you need that fix on most systems
with the particular models of HP laserprinters involved.

Indeed--uninstalling should put everything back the way it was. I haven't
had any reports of issues with our (7.x) DonorPerfect databases, and I
believe we do this kind of merge pretty regularly.

I didn't actually get into that office in person this week except for a few
hours on Friday afternoon--will be there more next week and try to dig
deeper, and maybe run the upgrade to the new version.


--

 

[Bill Sanderson]

Whoops - typo--look for

HPbpro.exe.



--

On a couple of workstations with the small--"breadbox" sized HP printers,
I was seeing DCOM errors every 30 seconds.

The info in this cut and paste from www.eventid.net is what cleard them
for me:
-----------------------------------------------------
In my case, this problem occurred between two Windows 2000 Professional
SP4 workstations and an HP Print Server Appliance 4200, which is joined to
a Windows 2000 AD Domain. HP LaserJet 1320 Toolbox miss-registered itself
during standard install, caused two DCOM errors every 35 seconds.
To fix the problem, at a command window from the directory
\windows\system32 run the command:
hpbpro.exe -RegServer
If the problem persists then run the following command:
hpbpro.exe -Service.
See the link to "HP LaserJet and LaserJet AiO Printers - DCOM Error
Message" for additional information on this problem.
----------------------------------------------------
Check systems seeing these dcom errors for hpbro.exe--and execute those
two commands on them. You'll probably find you need that fix on most
systems with the particular models of HP laserprinters involved.

Indeed--uninstalling should put everything back the way it was. I haven't
had any reports of issues with our (7.x) DonorPerfect databases, and I
believe we do this kind of merge pretty regularly.

I didn't actually get into that office in person this week except for a
few hours on Friday afternoon--will be there more next week and try to dig
deeper, and maybe run the upgrade to the new version.

 

[Guest]

I appreciate the followup, thanks.

The printer connected to my PC is an HP LaserJet 1012 which is fairly decent
sized. The events viewer didn't show anything relating to HP. It seemed
like my PC is failing to contact the LIFE2 server for some reason and it
involves DCOM, although it isn't affecting my day to day work on this
machine. The DCOM errors happen even when I'm not running DonorPerfect
version 8.

- Matt.

 

[Bill Sanderson]

The DCOM errors really are caused by software associated with the
printer--follow these steps to eliminate the errors:
----------------------------------------------------
Try re-registering the component HPBPRO.EXE. I had a problem with the
component re-attempting to run every 60 seconds. I tried the sugggestions in
message c00098371 "DCOM Error Message" pertaining to hpbpro.exe, and it
solved the problem.

To quote,
"To register the component properly, open a command prompt window by
clicking Start then Run. Enter cmd.exe in the Run window.

Change to the System 32 folder by typing "cd\winnt\system32" for Win2K or
"cd\windows\system32" for WinXP.

Run the command "hpbpro.exe -RegServer".
Then run the command "hpbpro.exe -Service".

Then type "Exit" and then restart your PC.
------------------------------------------

This is well worth doing--those DCOM errors fill up the files fast.
However, it isn't related to the DonorPerfect issue at all, as far as I can
tell.


--

 

[Guest]

I ran the following and the DCOM errors no longer appear:

http://www.grc.com/dcom/

But DonorPerfect will still not merge on computers with Windows Defender
installed or previously installed.

- Matt.

 

[Bill Sanderson]

Hmm - well--that is one way to prevent the error message, but simply
re-registering the HP code should have done the job. I'm unclear on exactly
when DCOM is needed--and I don't trust Steve Gibson to tell me.

I'll be spending some time with the folks I work with who use DonorPerfect
tomorrow. I'll see whether we can get the newer version installed, and
whether they are having any trouble with your specific merge type.

--

 

[Bill Sanderson MVP]

Matt--are you still seeing this issue? Have you been in touch with the
DonorPerfect folks about it?

I've now got the new version installed for about a week, and we've seen some
teething problems with it--an export to CheckFree or some similar service
failed, and was quickly repaired by support. I've got a specific complaint
from a user about an export issue, but it involves phone numbers, which I
know have changed significantly in the new version.

I'll go back through the thread, but if you can give me a quick step-by-step
for the type of export that is failing, I'm now in a position to try to
replicate.

--

 

[Guest]

Thanks for the followup, Bill. I do appreciate it.

I did find a solution that seems to help. I find that if I log in as the
network administrator and then back on as the user again on the workstation
experiencing trouble, I find they can then export just fine to Word via
DonorPerfect 8. The same goes for writing Adobe Acrobat PDF documents to the
network (writing PDF's locally worked fine, but writing them to the network
gave a log error before).

It makes me wonder if the recent Novell NetWare client upgrades I did to
version 4.91 SP2 was the culprit after all. I did do these around the same
time as Windows Defender.

As far as upgrading from version 7 to version 8 goes, yes, we did experience
a lot of problems with things breaking including EFT w/ Checkfree and various
reports we run. But support was able to clear those problems up once we
contacted them. They usually suggest updating to the newest update via their
website.

- Matt.

 

[donorperfect]

My name is Mike Sernoff and I'm the Vice President of Client Services for SofterWare, the company that provides DonorPerfect. I just came across this thread and wanted to reply, even though the issue was posted several years ago. I did want to note that any time a DonorPerfect user is experiencing an issue of this nature, I would encourage them to contact our support department for assistance, either by telephone or via the Clients area of our website, www.donorperfect.com (login required). Our technical support staff are happy to assist with troubleshooting these types of issues. Thank you and Happy Holidays.