On our main installation (win98 machine) we can no longer view reports.
I have completely uninstalled, reinstalled, and added the latest maintenance release. I am hoping that I can avoid reinstalling windows to get it to work again.
I can choose any report, it will give me the report options, but instead of bringing up the report i get this error message:
Logon failed. Detail: ADo Error Code: ox80040e21; source: microsoft ole db provider for visual foxpro; description: invalid path or file name; native error 295. After this i get another error screen that mentions a error log file. Here is an excerpt from the log:
Fatal error: Exception code=C0000005 @ 02/17/2005 08:31:09 PM. Error log file: C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\VFP\VFP8Rerr.log
Called from - crystal2.destroy line 21 {c:\pc90source\crystal\crystal2.vct c:\pc90source\crystal\crystal2.vct}
Called from - app.closeallforms line 14 {c:\pc90source\pcapp.vct c:\pc90source\pcapp.vct}
Called from - pcshutdown line 363 {C:\PowerChurch\PCPLUS9\pc.prg c:\powerchurch\pcplus9\pcplus9.exe}
Called from - ON... line 0 { }
Called from - pc line 162 {C:\PowerChurch\PCPLUS9\pc.prg c:\powerchurch\pcplus9\pcplus9.exe}
I am having a similar problem viewing reports in V9. I have an XP Pro system.
My error code is:
Crystal Report Viewer
Logon failed.
Details: Error Code: 0x800a0e7a
Source: ADODB. Connection
Description: Provider cannot be found. It may not be properly installed.
As for your Logon Failed error. Did you run NetSetup9 on the workstation having the problem to see if one of the necessary files got corrupted? Have you run ScanDisk and Defrag on the system? I am still unable to reproduce this problem in house. I've dedicated a computer for this task and installed all the printers known to cause this type of problem. What other common programs might be influencing if a DLL is properly installed and registered? What Anti-Virus do you have running? Do you have any Registry checking software? Have you looked for SpyWare installed on the workstation? What percentage of system resources are available after the computer at the desktop and ready to work on, if this is lower than 60% you probably have something running on the computer that might be causing this problem.
In regards to the C5, the log is helpful, I might be able to find away to prevent that.
Tracy wrote:Did you call Tech Support for a response?
Don't I have to pay for phone support?
The computer it runs on is not connected to the internet, so there is no spyware. It is running AVG antivirus v7. We have other installations of powerchurch plus that also have avg and they are working fine. I had a couple of programs in the startup, but removed them while I was trying to figure out the problem. There isn't much running on this machine except powerchurch. There are only 5 or 6 apps in the task list when you do a ctrl-alt-del. I manually shut them down one at a time during testing as well. System resources are normal on that system, above 60 for sure after a reboot. No registry checker is installed on the machine, and a scandisk has been done. We have an old dot matrix pinter on that computer for printing checks. We recently installed a module in our laser copier that allows us to print to it.
Is running netsetup9 different then reinstalling? I didn't try that if its different.
As an upgrade to PowerChurch 9, you received 45 days of support. It starts with the first support call. If you would like to check your current support status, call, ask the receptionist. This is support, are you not taking my time away from other tasks? Should the company compensated for the time I take to answer questions on this forum?
NetSetup9 installs the runtime files (DLL’s) on to the system. Installing from CD overwrites the executable and report files, backing out any maintenance releases (MR). Are you on the latest MR?
Make sure the anti-virus program is not scanning DBF, FPT, and CDX extension system wide. We do use the current windows user’s temp folder.
Was the dot matrix printer the default printer before the problem started, and now the copier is the default printer?
The part of the log you pasted was for that specific error; that explained to me where the problem is happening, nothing in that log will explain why it is happening.
I will check the antivirus software. I don't think either printer is the default printer. So the default printer hasn't changed. I will have to check to be sure, and I am not at the church at the moment.
Ok so I asked someone at the church to take a look. We did change the default printer from HPDeskjet 520 to Panasonic FP-D350 (the copier). When we change it back we still get the initial error the first time we run a report, but instead of crashing it allows us to try to run the report again, and it works the second time around. So its not perfect, but it makes the system useable.
I made the mistake of answering you in my last post when I was frustrated about a different problem I'm working on here. I did not mean to sound harsh in my response about support.
NetSetup9 is located in the program directory.
Sometimes the problem will be corrected by updating the drivers. Try a PowerChurch restart, then a system restart with the HPDeskjet 520 left as the default printer, to see if it helps first.
Logon Failed problems have been traced to a few of things.
1) Microsoft Data Access Controls (MDAC)
2) DLL not registered - usually see a "Provider not found" message
3) Printer driver, changing to a different printer driver, even installing the HP Laser Jet III and send to File as a test to see the problem go away. A work around to this problem is to set this working printer as the Windows Default. Preview of the reports can now be done, to Print use the "Save As" feature to send to Word or PDF and print from there. Until this problem can be reproduced here, it will be very difficult to determine what the real problem is and properly solve it. Part of this is directly out of my hands, as the problem is within the third party reporting tool "Crystal Reports".
We resolved the issues by upgradeing the computer to xp. Although now we have a problem that we can't print cheques on our tractor feed dot matrix printer.
Open the PowerChurch V9 manual to page 26. The Note: under Setting up your tractor printer paper size.
Note: Due to differences in defining a custom paper size, tractor printing is not suppored in PowerChurch Plus on a Windows NT 4, Windows 2000, Windows XP or later operating systems.
Tracy wrote:Open the PowerChurch V9 manual to page 26. The Note: under Setting up your tractor printer paper size.
Note: Due to differences in defining a custom paper size, tractor printing is not suppored in PowerChurch Plus on a Windows NT 4, Windows 2000, Windows XP or later operating systems.
I saw that. So I am faced with going back to win98 and living with crashes, and the inability to print to various printers, or go to xp to resolve those issues but no longer able to print out cheques. I suppose I will have to go back to win98. We may set the old printer as a network printer on a win98 machine an see if we can get it to print though the network. This is frustrating.
