Home All Groups Group Topic Archive Search About

Vb Win app crashes on start

Author
21 Jul 2006 10:17 PM
UnkleVo
When I start the dotnet program it crashes on start with the message
"<myprog>.exe has encountered a problem and needs to close.  We are
sorry for the inconvenience."

There are no errors in window error log.

I tried to debug it at run time using mdbg.exe and it generates the
floowing error:

MDbg (Managed debugger) v2.0.50727.42 (RTM.050727-4200) started.
Copyright (C) Microsoft Corporation. All rights reserved.

For information about commands type "help";
to exit program type "quit".

mdbg> run docimageindex
STOP: Unhandled Exception thrown
Exception=System.TypeInitializationException
        _typeName="DocImageIndex.modStart"
        _className="System.TypeInitializationException"
        _exceptionMethod=<null>
        _exceptionMethodString=<null>
        _message="The type initializer for 'DocImageIndex.modStart'
threw an exc
eption."
        _data=System.Collections.ListDictionaryInternal
        _innerException=System.Exception
        _helpURL=<null>
        _stackTrace=array [24]
        _stackTraceString=<null>
        _remoteStackTraceString=<null>
        _remoteStackIndex=0
        _dynamicMethods=<null>
        _HResult=-2146233036
        _source=<null>
        _xptrs=0
        _xcode=-532459699

This is unhandled exception, continuing will end the process
Error: No current frame


This is an urgent issue for us. Please help us out. I hope Microsoft
support guys could help out on this. The program runs fine under the
admin accounts. Only one user out of many can run this program with no
problems. User accounts configurations are identical.

It is version 2.0 dotnet framework. It is installed properly.

Any suggestions are greatly appreciated.

Thank you,

Author
22 Jul 2006 8:08 AM
tommaso.gastaldi
Hello UnkleVo

from your description, it sounds like a permisssion problem.
Have you tried playing aroud with permissions to see if it solves the
problem?

-tom

UnkleVo ha scritto:

Show quoteHide quote
> When I start the dotnet program it crashes on start with the message
> "<myprog>.exe has encountered a problem and needs to close.  We are
> sorry for the inconvenience."
>
> There are no errors in window error log.
>
> I tried to debug it at run time using mdbg.exe and it generates the
> floowing error:
>
> MDbg (Managed debugger) v2.0.50727.42 (RTM.050727-4200) started.
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> For information about commands type "help";
> to exit program type "quit".
>
> mdbg> run docimageindex
> STOP: Unhandled Exception thrown
> Exception=System.TypeInitializationException
>         _typeName="DocImageIndex.modStart"
>         _className="System.TypeInitializationException"
>         _exceptionMethod=<null>
>         _exceptionMethodString=<null>
>         _message="The type initializer for 'DocImageIndex.modStart'
> threw an exc
> eption."
>         _data=System.Collections.ListDictionaryInternal
>         _innerException=System.Exception
>         _helpURL=<null>
>         _stackTrace=array [24]
>         _stackTraceString=<null>
>         _remoteStackTraceString=<null>
>         _remoteStackIndex=0
>         _dynamicMethods=<null>
>         _HResult=-2146233036
>         _source=<null>
>         _xptrs=0
>         _xcode=-532459699
>
> This is unhandled exception, continuing will end the process
> Error: No current frame
>
>
> This is an urgent issue for us. Please help us out. I hope Microsoft
> support guys could help out on this. The program runs fine under the
> admin accounts. Only one user out of many can run this program with no
> problems. User accounts configurations are identical.
>
> It is version 2.0 dotnet framework. It is installed properly.
>
> Any suggestions are greatly appreciated.
>
> Thank you,
Author
25 Jul 2006 3:34 PM
UnkleVo
Tom,

Thank you for your response.

Yes, it definitely looks like permissins problem.
We are now trying to play with different set of permissions.

All the best,

Unkle

tommaso.gasta***@uniroma1.it wrote:
Show quoteHide quote
> Hello UnkleVo
>
> from your description, it sounds like a permisssion problem.
> Have you tried playing aroud with permissions to see if it solves the
> problem?
>
> -tom
>
> UnkleVo ha scritto:
>
> > When I start the dotnet program it crashes on start with the message
> > "<myprog>.exe has encountered a problem and needs to close.  We are
> > sorry for the inconvenience."
> >
> > There are no errors in window error log.
> >
> > I tried to debug it at run time using mdbg.exe and it generates the
> > floowing error:
> >
> > MDbg (Managed debugger) v2.0.50727.42 (RTM.050727-4200) started.
> > Copyright (C) Microsoft Corporation. All rights reserved.
> >
> > For information about commands type "help";
> > to exit program type "quit".
> >
> > mdbg> run docimageindex
> > STOP: Unhandled Exception thrown
> > Exception=System.TypeInitializationException
> >         _typeName="DocImageIndex.modStart"
> >         _className="System.TypeInitializationException"
> >         _exceptionMethod=<null>
> >         _exceptionMethodString=<null>
> >         _message="The type initializer for 'DocImageIndex.modStart'
> > threw an exc
> > eption."
> >         _data=System.Collections.ListDictionaryInternal
> >         _innerException=System.Exception
> >         _helpURL=<null>
> >         _stackTrace=array [24]
> >         _stackTraceString=<null>
> >         _remoteStackTraceString=<null>
> >         _remoteStackIndex=0
> >         _dynamicMethods=<null>
> >         _HResult=-2146233036
> >         _source=<null>
> >         _xptrs=0
> >         _xcode=-532459699
> >
> > This is unhandled exception, continuing will end the process
> > Error: No current frame
> >
> >
> > This is an urgent issue for us. Please help us out. I hope Microsoft
> > support guys could help out on this. The program runs fine under the
> > admin accounts. Only one user out of many can run this program with no
> > problems. User accounts configurations are identical.
> >
> > It is version 2.0 dotnet framework. It is installed properly.
> >
> > Any suggestions are greatly appreciated.
> >
> > Thank you,