ActiveX component can't create object occurred in w3wp.exe - iis

I am currently having an issue with a classic ASP application I am working on and from what I can tell it might be due to something related to IIS.
It started out with me getting the error:
"An unhandled exception ('ActiveX component can't create object') occurred in
w3wp.exe[XXXX]."
I tried googling, but failed to find anything that could solve my issue.
So I tried to create a small .vbs application. To see if it had anything to do with the component that is used for the "createObject()" method.
dim test
set test = createObject("System.Collections.Sortedlist")
test.add 1, "value 1"
test.add 2, "value 2"
MsgBox(test(1))
And the file ran as it should.
I've tried running the application using both Visual Studio 2015 and 2017.
After I noticed that it sad "Occurred in the w3wp.exe" I tried reinstalling IIS to see if that would change anything, but sadly it has not had any effect.
Update: I am using Windows 10 personally and running the site of my own PC for testing purposes.
"Access Denied" errors and applications with COM activation fail after installing July 2018 Update

Related

IIS problems after installing July'18 Updates

We are experiencing the following problems after installing the July'18 updates in our servers running Windows 2012 and Windows 2016:
1) We can no longer restart the www service. The service locks in "stopping" mode forever.
2) We can no longer instantiate .NET .DLLs (interop) in classic ASP using server.createobject. We receive the error 0x800A01AD "ActiveX component can't create object". I've read some workarounds at other forums to change IIS Anonymous Authentication to "Application pool identity" but it didn't resolve the problem.
We could only fix both problems after uninstalling ALL the July'18 KB's: KB4284815, KB4338815, KB4338424, KB4338419, KB4054566.
Other questions I found here did not solve or even mention the www restart problem, that also started after the July updates.
Microsoft is aware of the .NET DLL access denied errors and is still working on a solution: https://support.microsoft.com/am-et/help/4345913/access-denied-errors-after-installing-july-2018-security-rollup-update
Yesterday Microsoft finally published a resolution for the "ActiveX component can't create object" error: https://support.microsoft.com/en-us/help/4345913/access-denied-errors-after-installing-july-2018-security-rollup-update. I tested it in Windows Server 2012 R2 and Windows 2016 and it worked OK.

Microsoft Visual Studio 2012 has stopped working (solutions on Stack Overflow not working)

Error message:
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.
This was the error message I got when I tried to launch Visual Studio 2012 on my Windows 8.1 system. There is no other information to act upon other than this, which is rather the same as "We don't know what's wrong. We will tell you if we know (but I don't think we do)". It was actually working before it just decided to stop.
The last configuration I made before it began to show this error was that I selected the option to load the last solution whenever I launch Visual Studio, and this was done in the options dialog. I don't think that could have caused Visual Studio to suddenly crash. The previous error message included something that had to with a change in configuration.
I have checked that ActivityLog.xml file in.
There were basically four errors:
Construction of frame content failed. Frame identifier: ST:0:0:{74946827-37a0-11d2-a273-00c04f8ef4ff} Frame caption: Exception details: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) at Microsoft.VisualStudio.Shell.Interop.IVsShell5.LoadPackageWithContext(Guid& packageGuid, Int32 reason, Guid& context) at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.GetPackage() at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.ConstructContent()
SetSite failed for package [Visual Studio Component Model Host Package]
End package load [Visual Studio Component Model Host Package]
End package load [Microsoft.VisualStudio.Editor.Implementation.EditorPackage]
I have searched on Stack Overflow, Bing and Google. The solutions I got from there didn't work. Some had to do with registry settings, deleting keys, etc. I even disabled all the extensions from the registry. There was a time it was showing another message that "Object reference was not set to ...".
I don't know what to do. The only solution I have not tried is the one that I should download the updates. Update 4 is about 2 GB. That will take me, at least a week to download. Is there anything I can do?
PS: I tried to uninstall it. It does absolutely nothing. From the Control Panel, there's only the option to change. Clicking it seems to do something but nothing appears. I tried running from the set up from the .iso file. It shows nothing, too. How can I fix this problem?
There's probably nothing we can help you with here, my view is that you need to reinstall VS. If you cannot uninstall or repair it then you should contact Microsoft.
I am able to fix this problem by installing latest version of of .NET Framework. May be helpful for others as well.

Root element is missing when trying to Publish

It has been a while since I've published my app to Azure. During that time frame, I've upgraded my system from 32-bit to 64-bit meaning a fresh install of Windows and Visual Studio. And Visual Studio Update 3 came out and was applied. When I went to publish an update today, I received the following:
The following exception was thrown trying to publish: Root element is missing.
My web.config file looks fine so I don't think it's this issue.
The app works fine in debug mode so I don't think it's any of the .lsml files as is mentioned here.
And I tried this procedure to hand edit the .ls3proj file but it didn't seem to help.
I previously had an issue trying to publish when I upgraded from the standalone LightSwitch 2011 to Visual Studio 2012. I was able to overcome that issue using the method described in this thread.
Attempting to use this same method resulted in my new project has a full screen error saying "There are critical errors in the application definition metadata..." and 210 individual errors (max errors reached).
The first error, "Cannot create unknown type '{http://schemas.microsoft.com/LightSwitch/2010/xaml/model}GlobalAttributeGroup'." Doesn't make sense because that line in the .lsml is identical from the old project to the new project.
The second error, "Could not find any application definition in the project." Which I do not understand at all.
I am able to publish a simple "Hello, world" style app to my Azure account.
What could be causing this? How can I get more information about exactly which element is causing the issue? The log produced by running devenv /log was not helpful.
Matt Thalman was able to solve my problem over in the Microsoft Forums. The ServiceConfiguration.cscfg and ServiceDefinition.csdef were missing from the project when checked out of version control. Copying those over from a new project restored my ability to publish.

VisualStudio 2012 crashes on opening web-based project - Windows 7 - Windows error message

Everything had beed working great, but suddenly something happened and every time I try to open any web-based project (either MVC or just 'Open Web Site', any others are just fine), Visual Studio 2012 crashes with Windows environment message:
MyProject - Microsoft Visual Studio (Administrator): devenv.exe - System error
Exception Processing Message 0xc0000005 Parameters 0x000007FEFD4A718C 0x000007FEFD4A718C 0x000007FEFD4A718C 0x000007FEFD4A718C
ОК
I did not notice exact moment when it stopped working. And obviously I have different extensions etc. But I believe, I did not install any big soft these days.
I've installed Windows 8 though, but separatly - on separate volume to try it. Theoretically, it might affect my situation, but I don't know how is that possible - at least I don't know any explanations.
I've tried to refresh Visual Studio 2012 installation, even removed and installed it again.
However, at the same time, I have Visual Studio 2010 previously installed, and it opens web-based projects without any problems.
Mentioned error message above is, as I understand, some generic error message - googling did not help on its recognizing, so don't know what to do - don't really want to reinstall Windows because of that.
Does anyone have any thoughts? Thanks!
I really don't know what was the cause of the problem, but after all other tries I've applied all pending updates of Windows Update service and everything works well after that.

Microsoft Test Manager - An error occurred with the diagnostic data adapter IntelliTrace

I get the following error message when I attempt to run a test in Microsoft Test Manager.
This adapter will not be used for this
test run. The following error
occurred: The element 'StartupInfo' in
namespace
'urn:schemas-microsoft-com:visualstudio:tracelog'
has invalid child element
'DeleteLogOnClose' in namespace
'urn:schemas-microsoft-com:visualstudio:tracelog'.
Looking in the event log on the (agent and controller - same box) server I see the following error shortly before the above one:
(QTDCAgent32.exe, PID 2700, Thread 7)
Data collector
'datacollector://microsoft/TestImpact/1.0'
logged the following error: This
adapter will not be used for this test
run. The following error occurred:
Object reference not set to an
instance of an object.
I've searched for a solution but cannot find anyone else who encountered this issue.
Anyone have any ideas?? I'm getting desperate!
Thanks
JP
For at least the first error it looks like you have an invalid Collection Plan. Have you modified them at all? Did you change Visual Studio versions at all?
Check both:
Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\DataCollectors\Microsoft.VisualStudio.TraceCollector.dll.config and
Microsoft Visual Studio 10.0\Team Tools\TraceDebugger Tools\en\CollectionPlan.xml
I would at least try removing that node 'DeleteLogOnClose' altogther to start with.
I had this issue with VS 2010. I was able to resolve it by applying vs 2010 sp1.

Resources