Monday, February 15, 2010

Cannot Open or Find File when installing visual basic application .Please insert disk'. (vb6) Could not open the file named: drive/filename

Sometimes when trying to install a visual basic application the following error message may occur according to the version of vb

in vb4

Could not open the file named: :\

If you are using vb5

Cannot find the source file ':\\' to install.

In vb6

Cannot find file ':\. Please insert disk'.

The reason for this error messages are the drive from which installation filename is running does not support long filenames. This problem is common in CD-ROM drives whose driver is out of date and does not offer support for longer filenames. However this problem can occur in any drives

To resolve the problem do any of the following

1. Obtain and install an updated driver that adds support for long filenames on the device in question.

2. Modify the project such that no long filenames are used by any of the project's files, and then re-deploy.

3. Copy the entire contents of the setup from the CD (or network drive) to a folder on the local hard drive. Rename all files in this directory that currently have short filenames but originally contained long filenames. The correct long filenames can be determined by viewing the [FILES] and/or [BOOTSTRAP] sections of the SETUP.LST file. Finally, run SETUP.EXE from this local folder.

Sunday, February 14, 2010

Riched20.dll error message in outlook 2003

On start of outlook 2003 you may receive the following error messages

Outlook.exe caused an 'access violation' fault in module riched20.dll at 014f:4802bc95.


Outlook caused an Invalid Page Fault in riched20.dll.

And when you trying to create a new email message the following error message will occur

Unable to load "riched20.dll". You may be out of memory, out of system resources, or missing a .dll file.

The reason for this error message is Riched20.dll on your computer is damaged or missing

To resolve this error search in the computer to check whether riched20.dll exists in the computer. If exists then rename the riched20.dll the file. Follow the following steps

1. Click start -> Search

2. In the search box type "riched20.dll". Select search all files and folders

3. Start search

4. If search resuls showing file called "riched20.dll" then right click - > rename
and type another name for the file

5. Then you have repair the outlook 2003

Start outlook 2003

in the help menu select "Detect and Repair"

Follow all the instructions

Saturday, February 13, 2010

Cannot start Microsoft Office Outlook Cannot open Outlook window microsoft outlook 2007, Regsvr32.exe VBScript.dll

When starting outlook 2007 first time you may receive the following error message

Failed to register a VB Script DLL. Reinstall or run Regsvr32.exe VBScript.dll to self register.


Cannot start Microsoft Office Outlook. Cannot open Outlook window

The reason for this error is the username contains unicode characters. When you run Outlook 2007 for the first time, Outlook does not translate user names that are stored as part of the user profile path in the registry from Unicode to ANSI correctly.

To resolve this error restart the computer. And try to open outlook 2007

Thursday, January 21, 2010

Error Accessing the System Registry VB6 vb vba

When trying to access the reference dialog box in VB6 or vba the following error message may come.

Error Accessing the System Registry

The cause of this problem is a full/Clean Installation of Crystal Reports
In crystal reports this problem will not come in or higher.

To correct rgis problem follow the following steps

1. Use REGEDT32.exe to scan for keys that are dimmed in HKEY_CLASSES_ROOT\TypeLib and HKEY_CLASSES_ROOT\CLSID.

2. Use the RegMon utility from Run the filtering processes for Visual Basic, and then try accessing the References dialog box in Visual Basic. When the error occurs, switch to RegMon and make note of the last keys which were successfully read or written. (These should be from HKEY_CLASSES_ROOT\TypeLib or HKEY_CLASSES_ROOT\CLSID.)

To fix the permission problem follow the following steps

1. Load REGEDT32 and locate the keys that are dimmed from the preceding step 1, or the keys that you noted from step 2. (Note: If you used step 2, once you locate the key, look at the key or sub-key that immediately follows it in the Registry. If you did not have the appropriate permissions to access the key, it would not have even been logged through the RegMon utility and, as such, the entry you noted in step 2 will be the last successful read/write. Therefore, the one that followed it caused the error to occur.

2. On the Security menu, give the appropriate permissions to the key so that you, and Visual Basic, can access it:
Administrators - Full Control
Everyone - Read
System - Full
Users - Read
Modify the user list to suite your needs.

3. Sometimes REGEDT32 is not able to access the key, and it gives you an error stating that the security account information cannot be retrieved or found. You can fix this in the following ways:

a. On the Control Panel, double-click the Services icon.

b. Type the following command to schedule a new command prompt:AT 13:10 /Interactive cmd.exe

c. Change 13:10 to whatever time you want the cmd.exe (command prompt) to run: for example, one or two minutes from your current time.

d. Wait until this new command prompt starts. (Note: The window caption is similar to C:\Winnt\System32\MSTask.exe.) If the command prompt fails to start, please see Knowledge Base article 193852 ( ) "Task Scheduler May Fail to Run Job When Scheduled"

e. From the new command prompt, type the following, and then press enter: REGEDT32.EXE Because you start this process from the SYSTEM command prompt, REGEDT32 is also running under the SYSTEM security context.

f Repeat the preceding step 2, and then reset the permissions.

Wednesday, January 20, 2010

System files are out of date vb installation visual basic 6

When installing visual basic 6 on a computer running windows xp,vista or windows 2000 you may receive the following error message

Setup cannot continue because some system files are out of date on your system. Click OK if you would like setup to update these files for you now. You will need to restart Windows before you can run setup again. Click cancel to exit setup without updating system files.

This error is comming when the setup is trying to install newer version of the files which is already there and is protected by windows file protection system. When the setup is running the setup program compares the version of the files in the system. If the files in the system are older than the files in the setup the program will replace those files.

To resolve this problem follow the following steps

1. Apply latest visual basic service pack

2. Remove the commonly redistributed system files from the setup package

3. System files that should be excluded from your redistributable package

Happy Programming