Automation server cannot create an object solution

Automation server cannot create 6 solution for Object!

　　Method One:

Start-run: regsvr32 scrrun.dll

　　Method Two:

Copy the following statement to Notepad, save as a. cmd file, and run it. Of course it's OK to run the next sentence in the command line.

Echo is being repaired, this process may take several minutes, please wait ...

rundll32.exe Advpack.dll/delnoderundll32%systemroot%system32dacui.dll

rundll32.exe Advpack.dll/delnoderundll32%systemroot%catrooticatalog.mdb

REGSVR32/S Comcat.dll

REGSVR32/S Asctrls.ocx

REGSVR32/S Oleaut32.dll

REGSVR32/S shdocvw.dll/i

REGSVR32/S Shdocvw.dll

REGSVR32/S Browseui.dll

REGSVR32/S browseui.dll/i

REGSVR32/S Msrating.dll

REGSVR32/S Mlang.dll

REGSVR32/S Hlink.dll

REGSVR32/S Mshtml.dll

REGSVR32/S Mshtmled.dll

REGSVR32/S Urlmon.dll

REGSVR32/S Plugin.ocx

REGSVR32/S Sendmail.dll

REGSVR32/S mshtml.dll/i

REGSVR32/S ScrObj.dll

REGSVR32/S Corpol.dll

REGSVR32/S Jscript.dll

REGSVR32/S Msxml.dll

REGSVR32/S Imgutil.dll

REGSVR32/S Cryptext.dll

REGSVR32/S Inseng.dll

REGSVR32/S iesetup.dll/i

REGSVR32/S Cryptdlg.dll

REGSVR32/S Actxprxy.dll

REGSVR32/S Dispex.dll

REGSVR32/S Occache.dll

REGSVR32/S Iepeers.dll

REGSVR32/S urlmon.dll/i

REGSVR32/S Cdfview.dll

REGSVR32/S Webcheck.dll

REGSVR32/S Mobsync.dll

REGSVR32/S Pngfilt.dll

REGSVR32/S Licmgr10.dll

REGSVR32/S Hhctrl.ocx

REGSVR32/S Inetcfg.dll

REGSVR32/S Trialoc.dll

REGSVR32/S Tdc.ocx

REGSVR32/S msr2c. Dll

REGSVR32/S Msident.dll

REGSVR32/S Msieftp.dll

REGSVR32/S Xmsconf.ocx

REGSVR32/S Ils.dll

REGSVR32/S Msoeacct.dll

REGSVR32/S Wab32.dll

REGSVR32/S Wabimp.dll

REGSVR32/S Wabfind.dll

REGSVR32/S Oemiglib.dll

REGSVR32/S Directdb.dll

REGSVR32/S Inetcomm.dll

REGSVR32/S Msoe.dll

REGSVR32/S Oeimport.dll

REGSVR32/S Msdxm.ocx

REGSVR32/S Dxmasf.dll

REGSVR32/S Laprxy.dll

REGSVR32/S L3CODECX.AX

REGSVR32/S ACELPDEC.AX

REGSVR32/S MPG4DS32.AX

REGSVR32/S Danim.dll

REGSVR32/S Daxctle.ocx

REGSVR32/S Lmrt.dll

REGSVR32/S Datime.dll

REGSVR32/S Dxtrans.dll

REGSVR32/S Dxtmsft.dll

REGSVR32/S Wshom.ocx

REGSVR32/S Wshext.dll

REGSVR32/S Vbscript.dll

REGSVR32/S Scrrun.dll Mstinit.exe/setup

REGSVR32/S Msnsspc.dll/sspccreatesspireg

REGSVR32/S Msapsspc.dll/sspccreatesspireg

Echo.

Echo.

echo Repair Successful! Any key exit!

Pause>nul

Is the component registration problem, my problem is solved in this way.

　　Method Three:

I've been using a good vs.net editor, and suddenly one day when I create a new project, halfway through, pop-up "Automation server cannot create objects", and then stop.

I went to the csdn on the "Automation" keyword to consult the C # version of the problem, found that a lot of friends have met, and the answer to most of the friends to ask the questioner is IE parsing the XML file when the error.

See a few answer this kind of question, have met this problem friend, their answer is: Reload vs.net all have no function, finally reinstall the operating system to solve this problem.

It's killing me to install the operating system, so I have been using copy & Paste Engineering documents to achieve the purpose of the new project.

Until one day, I accidentally dot vs_setup.msi to add vs.net Help document (later know should point Setup.exe to add). Vs_setup.msi to half, also error, a look at debugging results, is FileSystemObject create failure (thank God, here's the error message is finally friendlier).

Vs.net Error "Automation server cannot create object" is this the cause?

I suddenly remembered that a few months ago on the internet to hear can prohibit the use of FileSystemObject objects, I forgot how to operate, anyway, a fiddling, concrete how to operate I also forget, from that I have never in my program used FileSystemObject. Search on Google, found that there are 2 ways to prohibit FileSystemObject

The first method: Modify the registry ([Hkey_local_machinesoftwareclassesclsid{0d43fe01-f093-11cf-8940-00a0c9054228}progid]

@= "Scripting.FileSystemObject"), change the FileSystemObject to an arbitrary name, and only users who know the name can create the object. I check the registry, where the name is Scripting.FileSystemObject.

Then why can't I use the FSO? It suddenly occurred to me that I was using

The second method: "Run Regsvr32 scrrun.dll/u, all users cannot create FileSystemObject". It was a bit harsh at the time. Run Regsvr32 Scrrun.dll quickly. I tried to create a project with Vs.net, a progress hint, no more damn "Automation server cannot create object"

Therefore, the friend who meets this kind of question, thinks carefully whether to move this "FileSystemObject" this cheese, should all be able to solve through this method. Otherwise, you really need to reinstall your operating system and reinstall Vs.net.

　　Method Four:

Open user accounts in Control Panel and select the "Automation server cannot create an object" error prompt when "Change the way users log on or off" is selected. (If this error message occurs when you perform another operation, you can also resolve it in the following way, for the same reason.) ）

Solution: Mainly Scripting.FileSystemObject (FSO text file read and write) was shut down, open the FSO function, in the "Run" in the implementation of Regsvr32 scrrun.dll.

Special method: Perform regsvr32 shimgvw.dll in "Run"

　　Method Five:

There is no need to reinstall the operating system and vs.net, but some scripts require Microsoft's MSXML controls to enter. When you use the default safe mode of IE version 5, you are prompted to accept the MSXML control and, if accepted, MSXML is automatically installed on your machine (it may take a few minutes). If the automatic installation is unsuccessful, you can download and install MSXML 3.0 yourself. If the "Automation server cannot create objects" error is still present after MSXML 3 is installed, because your machine prohibits all ActiveX, it typically sets IE's safe mode to "medium"

　　Method VI:

My machine used the above method to not solve the problem, use the following method to solve the problem, you may wish to try: Open Internet Explorer, "Tools" menu bar, the "Options" column, click the "Security" bar, the "Custom Level" tab, the third item " Initialize and script ActiveX controls that are not marked as safe are set to Enabled.