Login :: Register
General Topics
2005 IIS MVPs
Other IIS Sites
Microsoft Sites
Subscribe to the IIS Answers Newsletter  Subscribe to the IIS Answers Newsletter 

Subscribe to one of the best sources of information about IIS on the net. Written by Brett Hill, IIS MVP and Steve Schofield ASP.net MVP with a lot of help from the IIS community, the weekly newsletter contains useful tips, the latest news, and links of interest to those who administer IIS and related technologies. You'll recieve no spam and it's free. You can find more information and archives at http://www.iisanswers.com/newsletter Also available in RSS at http://lyris.iislists.com/read/rss?forum=iisanswers&rev=0.92


IIS FAQ Recent Articles and News

Current Articles | Categories | Search | Syndication

Friday, July 23, 2004
21 Tasks when Migrating to IIS 6 - by Brett Hill
By Brett Hill (brett) @ 5:12 PM :: Custom Articles :: 2 Comments :: 12563 Views

This new article lists 21 things to do when you migrate IIS 5 applications to IIS 6. The list includes several “gotchas” that can be difficult to troubleshoot if overlooked as well as some best practices for configuring IIS 6. If you need a shortcut to avoiding problems during your migration, this is it.


By Ben 'benjilloyd' Lloyd @ 7/29/2004 7:40 AM
I am still having problem migrating a conventional ASP application to 2003.

The problem I am having is a .asp script trying to instantiate an object, reporting: ActiveX component can't create object

My situation is complicated by the fact that the object I am trying to instantiate is not a true COM object but a .NET component that also has the interface for a COM component. I have created a deployment project to get the DLL and dependant files onto the 2003 server from my 2000 development machine. The component can be instantiated successfully from a conventional exe application on the 2003 but not from the asp script.

I have tried adding the component to the Web Extensions within IIS6 but this has had no effect.

I'd love to hear from the author of the article referenced in this post as he is obviously aware of the issues that are likely to occur. The article is a brilliant resource, one that I hope can be built on to become a definative list.

Hope to hear from 'someone' :-)


By Brett 'brett' Hill @ 7/30/2004 9:40 AM
Intresting problem. Almost always, failures to instantiate an object are permissions proboblems. I would use Regmon to see if the user context in use for the app pool has the necessary rights on the object. Also, be careful if your .net framework and the .asp code are running in different app pools you are likely to have problems since one must talk to the other.
-brett hill

Post a Comment
You must be logged in to post a comment. You can login here.

More Stuff

 This site and its contents are Copyright 1999-2004 by IISFAQ Microsoft Corporation in no way endorses or is affiliated with IISFAQ