Another Solution Of Active X Problem

ActiveX Control cannot create object" Error showing in opning any module in server machine
Symptoms
When you use Microsoft Access related applications, you receive the following error message: ActiveX...
When you use Microsoft Access, you receive the following error message:
ActiveX component can't create object
This article describes some common causes for this error message and offers methods that you can use to resolve the issue.
cause
This behavior can occur if any of the following conditions are true: Data Access...
This behavior can occur if any of the following conditions are true:
Data Access Objects (DAO) is not properly registered.
-or-
One or more references are missing.
-or-
There is a utility database reference that is not valid.
-or-
You do not have the required permissions for required libraries.
-or-
There is a damaged wizard file.
Resolution
Cause 1: DAO is not properly registered
1. On the computer that hosts Microsoft Windows Terminal Server or the computer on which Microsoft Access is installed, click Start, and then click Run.
2. Type regsvr32 followed by the path to your DAO file. Enclose this path in quotation marks. For example, to register the DAO 3.6 library, use the following command:
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL"


Cause 2: There is a damaged wizard file
1. Use Windows Explorer to locate the following wizard files: Acwzmain.mde, Acwztool.mde and Acwzlib.mde.
2. Change the file name extension of each file to "old." For example, change Acwzmain.mde to Acwzmain.old.
3. Reinstall Access to restore the files.

Active X component Can Not Create Object Problem in Win 2003 server

Reason:The Problem may be due to curruption of installation files of MDAC.
Solution:
1. Click on Start > Programs > Accessories > Notepad.
2. Click on File > Save As to save the blank document.
3. Browse to the root of the C:\ drive.
4. Name the file: MDACRdMe.htm, click Save.
5. Close Notepad.
6. In Windows Explorer, open the c:\Windows\Inf folder.
7. Right-click the Mdac.inf file, and then click Install.
8. You will be prompted for multiple files during the installation.
9. At each prompt, click on browse and navigate to the appropriate file (see list
below), click on Open then Retry.
10. There will be no notification when the installation is complete.
Files and Corresponding Locations
• File Name: adcjavas.inc
• Location: C:\Program Files\Common Files\System\msadc
• File Name: adojavas.inc
• Location: C:\Program Files\Common Files\System\ado
• File Name: msdadc.dll
• Location: C:\Program Files\Common Files\System\ole db
• File Name: dao360.dll
• Location: C:\Program Files\Common Files\Microsoft shared\dao
• File Name: handler.reg
• Location: C:\Program Files\Common Files\System\msadc
• File Name: MDACRdMe.htm
• Location: C:\
• File Name: oledbvbs.inc
• Location: C:\Program Files\Common Files\System\ole db
• File Name: oledbjvs.inc
• Location: C:\Program Files\Common Files\System\ole db

How to Manually Uninstall SQL Server 2005

Sometimes, you may find that, though you can't see any SQL Server 2005 instance in the programs list and when you try to install SQL Server 2005, you get a messages saying that there is already a SQL Server instance or some components such as SQL Server Management Studio installed. The reason for this is the existence of corrupted SQL Server instance and you need to remove the SQL Server instance manually.

To do this run the following command from the command prompt:

"%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\ARPWrapper.exe /Remove"

Uninstall the SQL Server components one at a time until all the SQL Server components are uninstalled.

Note: Add or Remove Programs also runs the ARPWrapper.exe program by using the /Remove option. However, the reference to the ARPWrapper.exe program may have been deleted. Make sure that all the services (if they exists) relevant to this SQL Server instance is stopped.