Lee can you help, people are starting to have probelms with the DNN installler not working.  Mine started when I migrated to IIS6.   This is the error I am now getting

-2147467259 (0x80004005).

Someone on the DDN forum said they solved the problem by repairing .Net 2.0 , I even went to the degree of unistalling 2.0 and reinstalling it.  No Joy.

I think it is something in the 6.0 Installation. The one thing I  noticed from my new machine to the old, is that the old IIs manger had a tab called server extensions and the new one dosent. 

Thanks

Mark

 

hi Mark,

I'm afraid I don't have any information covering this, I am using IIS5 and have not used IIS6 - let us know if you find a solution.

Thanks,

Hey:  This is definitely a .NET 2.0 issue.  Which version of DNN are you using?  What OS are you using?  If it's W2K3 server and DNN 4.x, then you were on the right track in repairing .NET.  Uninstalling and reinstalling .NET 2 can create other issues, however, since the GUIDs in the registry will change, which could create havoc.  This is something you should probably contact (I know, dealing w/Microsoft can be an unrecoverable maze) Microsoft about.  I've had this error before when installing some M$ updates.  The way I fixed it was to go to Start->Control Panel->Add/Remove Programs, then select .NET Framework 2.0 and click 'Repair', then rebooting.

But it sounds like you're way past this, unfortunately.  Are you creating a new site?  Which DNN installer are you using?  I would get rid of any sign of DNN, restart the machine, then click Start, then right click on 'My Computer' and select 'Manage'.  Look at you application and system Events.  This will help you see what is happening *before* the .NET 2.0 error is happening that might be the root cause of the problem. 

A great site, if you really don't want to deal with Microsoft, is www.eventid.net.  It costs like 9 bucks a month to get full informationm, but even if you don't pay, you can find a lot of good information by entering the Event ID and category and reading what others recommend for this issue.

This ended up to be a 2.0 issue.  I found a utility in the microsoft knowledge base.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

This fixed the problem on my local machine (developement).  We are trying to set DNN 4.41?  the latest version up on our server and keep getting Global error.   Again, my research points to a permisions problem for the .ASPNet user.  However we have not been able to resolve the issues.   We are running 2000 on the server and are starting to wonder if thats the problem and an upgrade to 2003 is in order.

Sorry for completness sake, my developement maching runs XP pro. The commucicatiosn error happened becuase 2.0 was loaded before IIs. Load IIS first then 2.0 and things work better that way. If things get our of wack try running the utility above.

Hey Mark:

Thanks for returning and posting that.  I have an idea that I will be needing to use that at some point. ;-)  But I appreciate when people who post issues also post how they resolved it.  You are a good man!