csdn右侧菜单不能展开，提示错误automation服务器不能创建对象

最新推荐文章于 2024-07-23 15:13:55 发布

原创最新推荐文章于 2024-07-23 15:13:55 发布 · 3.5k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#服务器 #object #bugs #server #microsoft #internet

本文提供了解决“Automation Server Can't Create Object”错误的方法，通常由于MSXML版本冲突引起。建议重新注册msxml3.dll文件来修复该问题。

提示以下的错误：

Automation server can't create object

解决方法：

regsvr32 msxml3.dll

参考以下资料地址

http://blogs.msdn.com/jledgard/archive/2004/08/23/automation-server-can-t-create-object-and-other-vs-2002-2003-start-page-problems-issues-and-bugs.aspx

原文：

"Automation server can't create object" and other VS 2002/2003 Start Page Problems, Issues, and Bugs

Yes, I was one of the testers for the Start Page in Visual Studio 2002 and 2003. There are a LOT of good reasons we are scrapping it and starting over with a new Start Page for VS 2005. Our redesign certainly takes into account the comments left here and countless other places we've looked for feedback. You'll see a renewed focus on simplicity and the main purpose of launching your recent projects. But this post isn't meant to be about the new start page. This is a brain dump of the known problems I've seen with the existing start page and how you can potentially solve them.

The "Automation Sever Can't Create Object" error message.

There may be a problem with the installed version of the Windows Scripting component. See KB323885.

Sometimes there are problems with different versions of MSXML being registered on the machine. The VS.NET start page uses the msxml3 object to render content in the start page. There have been a few known issues where installs of different versions ( there are a few!) of the msxml object will stomp on the previously installed versions ( link). Here is how I have fixed it on some machines:

Bring up a command prompt (cmd.exe)
in the command prompt “cd c:/windows/system32” (no quotes)
Then “xmlinst –u”
“regsvr32 msxml3.dll”
Close cmd prompt

Sometimes this is caused by aggressive anti-virus software that blocks the scripting components from launching. I talk about this extensively here.

Update: If you are unable to create projects.

I recently helped someone work with support to track down another issue and fix. Here are some steps that may help your problem. Essentially there are three registry keys that can get in a funky state where they have no owner of thier permissions...

Apparently, the Scripting.FileSystem object could not be accessed by Visual Studio.Net when trying to create a project. We figured that out by having me use regmon when sharing my desktop and trying to create a project. There were three keys I couldn't access or change permissions on: Scripting.Dictionary, Scripting.Encode and Scripting.FileSystemObject. However, I discovered through regedit that no owner assigned to the keys. I updated the security permissions after changing the owner and now I can create projects in Visual Studio.Net.

"You must be connected to the internet to use this feature."

The new start page will simply be polling it's online content from RSS feeds, but the old page polls a more proprietary XML standard down from MSDN servers to populate with content. The start page simply does a transform of the XML into the standard it prefers. We connect to this XML by using the

Try clearing your internet cache.

Try changing your selected help filter and re-loading the page.

Verify, with your internet connection you can connect to this page and see the XML there. ( http://msdn.microsoft.com/vsdata/vsdata.asp?tab=vs_online_community) If you can't, then there is an issue with your internet connect or firewall/proxy settings.

We use the "Microsoft.XMLHTTP" object to connect to and pull down this content. There are some issues with some versions of this object that cause it not to work properly through a proxy. You can see if you have this problem by downloading this file ( www.winisp.net/scooblog/ietest.zip), extracting the results and opening the "test.htm" file. (You'll have to enable script in the security settings for XP SP2 as it kindly blocks the test for you.) If the results look like the "good.txt" you don't have this problem. If they look like the "bad.txt" you have this problem. The problem is actually with the XMLHTTP object and, as far as I know, the IE team does not yet have a QFE or fix for this. Hey, check out the developer centers if you want good content. :-)

Filed under: Microsoft, Visual Studio

Comments