Query Engine Error

Visual Studio Version = 2005

Crystal Report Version = 9.2

Effect of the error message = The report viewer is fully blank. You cannot see the Crystal Report logo.

Error message from the exception = Query engine error.

Solution:

a). Install the following files:

cr90dbexwin_en.exe

CRRedist2005_x86.msi

CTL Crystal Reports 9.2 Distribution.msi

If you installed the above files before, please choose to repair them.

How I know the problem is fixed?

1). The report viewer should at least display the Crystal Report logo now. If you still encounter no record printed, please check your dataset row count.

The request could not be submitted for background processing.

If you hit the above error message when trying to load the Crystal Report in Visual Studio .NET 2005, then you may try to follow the steps below to resolve the problem:

a). Add the NETWORK SERVICE user into the security of the following folders:

C:\WINDOWS\Microsoft.NET

C:\WINDOWS\Microsoft.NET\Framework

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

b). End the asp_net process in the Task Manager.

c). Recompile your source code.

Cannot open Oracle 10g OEM in the internet browser?

If you cannot open the Oracle 10g OEM in the internet browser, and Windows is giving you this error:

The OracleDBConsole<SID> service terminated with service-specific error 2 (0x2).

Then, the following details might be able to resolve your problem.

    1. Make sure the PATH, ORACLE_HOME and ORACLE_SID are defined correctly in Control Panel -> System -> Advanced -> Environment Variables -> User variables for Administrator.

    2. Make sure the following folders are exist in D:\oracle\product\10.2.0\db_1\oc4j\j2ee

        OC4J_DBConsole_<COMPUTER_IP>_<SID>
        OC4J_DBConsole_<COMPUTER_NAME>_<SID>

    3. Make sure the following folders are exist in D:\oracle\product\10.2.0\db_1

        <COMPUTER_IP>_<SID>
        <COMPUTER_NAME>_<SID>

    4. You might need to restart your Windows after the above changes.


For more information, please refer to http://forums.oracle.com/forums/thread.jspa?threadID=309223

DataSource in ListBox and ComboBox

In VB.NET, both ComboBox and ListBox controls allow the software developer to define the DataSource.

However, there might be some errors occur if the way to define the DataSource is not correct.

Sequence to define DataSource and columns name

You are recommended to define the DataSource by the following sequence.

.DisplayMember = mstrDisplayMember

.ValueMember = mstrValueMember

.DataSource = objDS.Tables(0)

Beside that, always make sure that the value for .DisplayMember and .ValueMember are pointing to the correct columns name.


What happen if the sequence is wrong and the ValueMember is pointing to incorrect column name?

Some software developers prefer to put ".DataSource = objDS.Tables(0)" at the first line. If the value of the .ValueMember is incorrect, then VB.NET will prompt you an error message.

Example:

.DataSource = objDS.Tables(0)

.DisplayMember = mstrDisplayMember

.ValueMember = "Incorrect Column Name"

Error message = "Cannot bind to the new value member. Parameter name: value"


What happen if the sequence is correct but DisplayMember and ValueMember are pointing to incorrect columns name?

VB.NET will not prompt you any error message but the result in the controls will be displayed as "System.Data.DataRowView".

Example:

.DisplayMember = mstrDisplayMember

.ValueMember = "Incorrect Column Name"

.DataSource = objDS.Tables(0)

Result = System.Data.DataRowView (if the result returned 3 records, then VB.NET will show you 3 "System.Data.DataRowView")

Visual Studio 2003 Setup faild

There might be a lot of reasons why Visual Studio 2003 setup failed on your machine.

So, the best practice to trace the error is always refer to the "Installation_Log.txt".

If you found something like the following error message:

RunMSI.exe exited with return value 1601.
Error code 1601 for this component means "The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance.


Then, you must do the following to resolve this error:

a). Install the Windows Installer 3.1 or Windows Installer 4.5

b). Redo the Visual Studio 2003 setup

Microsoft Security Advisory: Vulnerability in Microsoft Video ActiveX control could allow remote code execution

The following products are required to apply the latest fix from Microsoft in order to patch the security issue for video activex control:

• Microsoft Windows Server 2003 Service Pack 2, when used with:
• Microsoft Windows Server 2003, Standard Edition (32-bit x86)
• Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
• Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
• Microsoft Windows Server 2003, Web Edition
• Microsoft Windows Server 2003, Datacenter x64 Edition
• Microsoft Windows Server 2003, Enterprise x64 Edition
• Microsoft Windows Server 2003, Standard x64 Edition
• Microsoft Windows XP Professional x64 Edition
• Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
• Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
• Microsoft Windows XP Service Pack 2, when used with:
• Microsoft Windows XP Home Edition
• Microsoft Windows XP Professional
• Microsoft Windows XP Service Pack 3, when used with:
• Microsoft Windows XP Home Edition
• Microsoft Windows XP Professional

How Do I Apply This Fix?

1. Go to http://support.microsoft.com/kb/972890

2. Click the "Enabled Workaround - Fix It" button. You will required to download a msi file.

3. After complete the download, just run the msi file to install the fix in your computer.

4. After that, restart your computer (even the fix does not asking for it).

How to fax by using Windows XP?

It is a very good idea to fax by using computer. Please click the link below to show the article from Microsoft:

http://www.microsoft.com/windowsxp/using/setup/learnmore/crawford_02october21.mspx