microsoft.public.dotnet.framework

Jesse Hansen

4/17/2008 5:26:00 PM

I should also have noted that I have isolated the problem to this specific
component. A plain vanilla Windows Forms project with this component dropped
in will create the same error.

"Jesse Hansen" wrote:

> We have an in-house developed application that uses a 3rd party COM control.
> We recently upgraded the application to .Net 3.5. Everything runs smoothly on
> Windows XP. We had previously tried the .Net 2.0 version on Windows Vista,
> and it runs just fine as long as you have not. However, when we upgrade the
> same machine to .Net 3.5 (preperatory to upgrading the application) the .Net
> 2.0 version will not run. It fails with this error:
>
> Exception Source: atEmulatorCtrl2k2
> Exception Type: System.Runtime.InteropServices.COMException
> Exception Message: Object variable or With block variable not set
> Exception Target Site: Apply
>
> ---- Stack Trace ----
> atemu2k2.AccuTermClasses.Settings.Apply(flags As Int32)
> Insight.exe: N 00000
> atemu2k2.ControlWrapper.atEmulatorDotNet.set_InitialSettings(Value As
> PropBag)
> Insight.exe: N 00116
> Insight.AccuTermTabbedDocument.InitializeComponent()
> Insight.exe: N 01117
> Insight.AccuTermTabbedDocument..ctor()
> Insight.exe: N 00019
> Insight.OrbitInsight.InitializeComponent()
> Insight.exe: N 00168
> Insight.OrbitInsight..ctor()
> Insight.exe: N 00224
> Insight.Program.Main()
> Insight.exe: N 00047
>
> I have searched everywhere and cannot find anything that seems to match my
> situation. I'm especially confused that the combination of Vista and .Net 3.5
> seems to be the trigger. With 2.0 on Vista or 3.5 on XP the application runs
> just fine.
>
> Note:
> I have run the application as both a limited user and administrator. Our
> application is deployed currently to people with limited user accounts on XP.