Getting a Crystal Report Viewer error on a Windows 7 machine - windows-7

We've got an old VB6 app which uses Crystal Reports XI Release 2 to run reports against a SQL Server 2005 database. This has worked well over the years. Also, for the last upteen years we've used Windows XP. Well, we're beginning to migrate to Windows 7. Well, now one of the users on Windows 7 cannot run the report. It gives him an error of “Logon failed. Details: [Database Vendor Code: 6]”. All of the Crystal Reports used in this application use an system ODBC connection. I've verified, twice, that the system DNS properly authenticates against the SQL Server database. However, when the user attempts to run any of the reports in the VB6 app, they all give that same error. The weird thing is we've got another old VB6 app, which also uses Crystal Reports, and that app's reports work fine. But that app runs against a local Microsoft Access database, not against SQL Server.
So the question is, are there any known issues involving SQL Server, Crystal Reports XI Release 2 and Windows 7?
Something else we just noticed. On the 2 user machines that are exhibiting this problem, both are 64-bit Windows 7 machines. So, could it instead be an issue of a 64-bit version of Windows, SQL Server and Crystal Reports XI Release 2?

Crystal Report 11.5 does run on 64 bit windows. Minimum req.ment is CR11 R2 SP6 to run on 64 bit.

Related

Oracle Forms and Reports for Windows 10

While installing forms and reports for Oracle 11g R2 I am facing the following error:
Checking operating system certification status failed.
I am using Windows 10 x64, forms and reports version is 11.1.2.2.0. During the web search, I found that Windows 10 is not included in any Certification Matrix of forms and reports. Is there any solution or I must switch to some other OS version ?
You should have an oraparam.ini or param.ini file in the installation directory. Within that file, there should be a Certified Versions section with something like:
Windows=4.0,5.0,5.1,5.2
You can try adding ,10.0* or just ,10.0 to the end, save the file, and restart the installation and it should finish installing. But that doesn't necessarily mean it'll work. I never had much success getting Forms Builder to work on Windows 7 and always had to revert to XP Mode.

Powerbuilder 11.2 has stopped working Windows 64 bit

I am running and supporting a PowerBuilder 11.2 application running in windows 7 64bit environment. The previous version of this program ran without a problem, and 99% of this new program runs without a problem. However, when I run a specific bit of functionality, at times the program throws an exception "Sybase PowerBuilder 11.0 has stopped working" Problem event name APPCRASH Application Name PB110.EXE, Fault Module Name PBSHR110.dll, Exception code c0000005 in the dev environment. In the compiled version running on the client machine the error "A breakpoint in an application indicates a program error. After this dialog is dismissed, the application will continue to run, but it may be in an unstable state" and the program closes
There are shared PBL files throughout this whole application. It is a framework that supports 6 MDI programs. I have performed a full build on the main objects and it compiles without error. The other programs that in the framework that use these common objects to not have this problem. I have tried to step through the code doing a debug, but when I step through the code, it does not crash.
I have re-installed PB 11.0 and the PB 11.2 upgrade again and of course rebooted numerous times. I am at a loss here. I have tried everything that worked before and have spent over a week trying to find something online, so I am now appealing to the group. Any help at all will be so very much appreciated. Until then, I'll keep trying.
Thanks.
John
It could be that PB 11.2 is not listed as being supported on Windows 7. A lot of times you can get lucky, and most applications will still work on unsupported OS's. Yet, an update may be released that breaks something. You may want to try downloading the latest release of PB which is 12.6 and migrate a copy of your application to that version. You will at least be able to rule out if that is the issue or not.
Enclosed is Sybase PowerBuilder Enterprise version 11.2, which is
compatible with the following platform and operating system
configurations:
Microsoft Windows XP with Service Pack 2
Microsoft Windows XP Tablet PC Edition with Service Pack 2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows Vista Business Edition
PowerBuilder 11.2 builds 32-bit applications, but supports deployed
applications in both 32-bit and 64-bit environments on the Vista
operating system. For more information about using PowerBuilder on the
Vista operating system, see “Vista Support” in the online Help. For a
list of issues that have been found on the Vista operating system, see
“Vista issues”.
Microsoft Windows 2000 with Service Pack 4 is supported for deployment
only. All support for this platform will be discontinued in future
releases of PowerBuilder.

crdb_oracle.dll could not be loaded in Crystal Reports 2008

I have installed crystal reports studio 2008 on win server 2012. when i try to run a report in crystal, i get following error:
The database connector crdb_oracle.dll could not be loaded. The correct version of the database client for this database type might not be installed.
I don't even see Oracle in the list of possible data sources in crystal reports. And Oracle driver was selected during crystal reports installation.
Oracle 11.2.0 client is installed. TNSping is working, all DLL's are in place. The same set of products (except on win-7 x86) is working just fine, so oracle and crystal should match.
Please see attahced screens. Advices i found on the Internet didn't help at all. Please advise.
screens-1
screens-2
I have figured out what was the issue.
As CrystalReports was 32-bit app, and windows server was 64-bit, i was missing 32-bit oracle client (just 64-bit version was installed). After i have installed 32-but oracle client, crystal worked fine.

Visual FoxPro (9.0) issue on Microsoft Windows Server 2003 R2

We have been running a Visual FoxPro (version 9) application on a Server under Microsoft Windows Server 2003 Operating system for a number of years now. We are now trying to migrate it to a different Server running under Microsoft Windows Server 2003 R2 and the application crashes. The problem occurs when it is trying to create HTML files from the FoxPro reports it has just created. To do this is uses the system variable _ReportOutput and aborts with the message “ox is not an object”. The application resides on the Network in a directory accessible to both Servers. Since hitting this problem I have changed the program to use the Htmllistener class within _ReportListener and get the same problem (works on one not on the other (R2)). Wait windows have been inserted to gain additional information but they only show that the object has not been created returning a data type of .Logical. It appears to me the problem is with the R2 version of the operating system, has anybody any ideas.
Have you installed ReportOutput.APP in the same folder as the application?

Anybody seen this behavior with Sql Server Reporting Services, a 64bit OS and an Oracle datasource?

I'm working on a Sql Server Reporting Services solution that queries across both a Sql Server data source and an Oracle 10g data source. My dev box is Windows 7 64bit with Sql Server 2008R2 and I'm hosting IIS7 and SSRS on that system for development; using VS.NET for designing the reports.
I have been having errors when running the report where SSRS complains about loading the 32 bit Oracle client in a 64bit process. There a number of threads out there about how to solve that. The thing is, they all come down to making sure you have the 64bit Oracle, client which I do. The weird chain of events I have goes like this:
Create initial Oracle datasource and wire up report (it works)
Edit Oracle datasource connection (it stops working with BadImageFormatException 32bit/64bit error message)
uninstall and reinstall Oracle client (it works)
Edit Oracle connection again (it stops working with BadImageFormatException 32bit/64bit error message)
So short of reinstalling the client every time I change the connection string I am at a complete loss. Has anybody seen this sort of behavior? And if so what the heck am I doing wrong?
Originally answered here: SSRS report with 32-bit Oracle Client Not working in 64-Bit Environment
This is the second time I configure a similar server, and the second time I spend hours figuring this one out. If for nobody else, I am writing this for the future me. This is for a Windows Server 2012 R2 64bit, 8GB RAM, 300+GB HDD, Intel Xeon CPU E5620 # 2.40GHz, that is running Microsoft SQL Server Reporting Services 2012 64bit and IIS 7.0 with web applications that use the Oracle Client 32bit connection System.Data.OracleClient
Install the 64bit client
Change the name of the Oracle inventory directory # "C:\Program Files\Oracle" to "C:\Program Files\Oracle64"
Restart computer and test for connection from SSRS to Oracle
Install the 32bit client and specify a different location for its home directory
Restart computer and test connection from SSRS to Oracle and from Web Applications to Oracle
I hope this helps my future self and others :)
You need to install 64 bit Oracle Client. Beware, i had bad experience on having both oracle 32 bit and 64 bit client. I ended up uninstalling 64 bit oracle client and trying to figure out installing SSRS in 32 bit mode on 64bit win7.

Resources