> Hi All
>
> I have installed Windows Server 2003 and have installed one of my VS2008 SP1
> apps
>
> When I run the app, either from the desktop icon or .exe directly, the mouse
> icon changes for a second but the app doesn't start
>
> There are no log entries in the Event log and no error messages received
>
> I have installed VS2008 SP2 and run my app from within VS 2008 and it works
> fine
> If I double click the .exe file generated by VS the app doesn't run
>
> This is wierd
>
> Any ideas
>
> Regards
> Steve
>
>

"Mike" <unkn***@unknown.tv> wrote in message
news:%23EtLntY6JHA.2456@TK2MSFTNGP02.phx.gbl...
>I would download DEPENDS from MSDN if you don't have it already and load it
>from DEPENDS.
>
>      DEPENDS yourAPP.EXE
>
> Click START | PROFILES and see what happens.
>
> --
>
> Steve wrote:
>> Hi All
>>
>> I have installed Windows Server 2003 and have installed one of my VS2008
>> SP1 apps
>>
>> When I run the app, either from the desktop icon or .exe directly, the
>> mouse icon changes for a second but the app doesn't start
>>
>> There are no log entries in the Event log and no error messages received
>>
>> I have installed VS2008 SP2 and run my app from within VS 2008 and it
>> works fine
>> If I double click the .exe file generated by VS the app doesn't run
>>
>> This is wierd
>>
>> Any ideas
>>
>> Regards
>> Steve

> Hi Mike
>
> Thanks for the reply
>
> I ran Depends but am not sure what it is telling me
>
> See below
>
> Operating System: Microsoft Windows 2003 Server R2 (32-bit), version
> 5.02.3790 Service Pack 2
> Program Executable: c:\program files\osmont technologies\salon applications
> manager\SAM.EXE
> Program Arguments:
> Starting Directory: C:\Program Files\Osmont Technologies\Salon Applications
> Manager\
> Search Path:
> C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Program
> Files\Microsoft SQL Server\90\Tools\binn\
>
> Options Selected:
>      Log DllMain calls for process attach and process detach messages.
>      Hook the process to gather more detailed dependency information.
>      Log LoadLibrary function calls.
>      Log GetProcAddress function calls.
>      Log thread information.
>      Use simple thread numbers instead of actual thread IDs.
>      Log first chance exceptions.
>      Log debug output messages.
>      Use full paths when logging file names.
>      Log a time stamp with each line of log.
>      Automatically open and profile child processes.
> --------------------------------------------------------------------------------
>
> 00:00:00.000: Started "c:\program files\osmont technologies\salon
> applications manager\SAM.EXE" (process 0xB04) at address 0x00400000 by
> thread 1.  Successfully hooked module.
> 00:00:00.000: Loaded "c:\windows\system32\NTDLL.DLL" at address 0x7C800000
> by thread 1.  Successfully hooked module.
> 00:00:00.000: Loaded "c:\windows\system32\MSCOREE.DLL" at address 0x79000000
> by thread 1.  Successfully hooked module.
> 00:00:00.000: Loaded "c:\windows\system32\KERNEL32.DLL" at address
> 0x77E40000 by thread 1.  Successfully hooked module.
> 00:00:00.000: DllMain(0x77E40000, DLL_PROCESS_ATTACH, 0x00000000) in
> "c:\windows\system32\KERNEL32.DLL" called by thread 1.
> 00:00:00.000: DllMain(0x77E40000, DLL_PROCESS_ATTACH, 0x00000000) in
> "c:\windows\system32\KERNEL32.DLL" returned 1 (0x1) by thread 1.
> 00:00:00.016: Injected "c:\temp\depends22_x86\DEPENDS.DLL" at address
> 0x08370000 by thread 1.
> 00:00:00.079: DllMain(0x79000000, DLL_PROCESS_ATTACH, 0x00000000) in
> "c:\windows\system32\MSCOREE.DLL" called by thread 1.
> 00:00:00.094: DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in
> "c:\temp\depends22_x86\DEPENDS.DLL" called by thread 1.
> 00:00:00.094: DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in
> "c:\temp\depends22_x86\DEPENDS.DLL" returned 1 (0x1) by thread 1.
> 00:00:00.110: GetProcAddress(0x77E40000 [c:\windows\system32\KERNEL32.DLL],
> "FlsAlloc") called from "c:\windows\system32\MSCOREE.DLL" at address
> 0x79006079 and returned 0x77E6B49C by thread 1.
> 00:00:00.125: Exited "c:\program files\osmont technologies\salon
> applications manager\SAM.EXE" (process 0xB04) with code -1073740791
> (0xC0000409) by thread 1.
>
> What I can't understand is why the program runs OK in VS design env
>
> Regards
> Steve
>
>
> "Mike" <unkn***@unknown.tv> wrote in message
> news:%23EtLntY6JHA.2456@TK2MSFTNGP02.phx.gbl...
>> I would download DEPENDS from MSDN if you don't have it already and load it
>>from DEPENDS.
>>      DEPENDS yourAPP.EXE
>>
>> Click START | PROFILES and see what happens.
>>
>> --
>>
>> Steve wrote:
>>> Hi All
>>>
>>> I have installed Windows Server 2003 and have installed one of my VS2008
>>> SP1 apps
>>>
>>> When I run the app, either from the desktop icon or .exe directly, the
>>> mouse icon changes for a second but the app doesn't start
>>>
>>> There are no log entries in the Event log and no error messages received
>>>
>>> I have installed VS2008 SP2 and run my app from within VS 2008 and it
>>> works fine
>>> If I double click the .exe file generated by VS the app doesn't run
>>>
>>> This is wierd
>>>
>>> Any ideas
>>>
>>> Regards
>>> Steve
>
>

"Mike" <unkn***@unknown.tv> wrote in message
news:%23x0muKg6JHA.2656@TK2MSFTNGP05.phx.gbl...
> HI,
>
> So DEPENDS exits without starting your app?
>
> I suggested DEPENDS because it understands how to load a .NET applet like
> the VS IDE does so its useful when you don't have the IDE on the target
> machine as a quick/fast check.  So if there was any missing, like SxS
> stuff or anything else odd, it might show it. In some similar cases with
> us, running the app directly would not start as you describe. DEPENDS
> helped show us why.
>
> It would of been nice to turn on some of the other profile options, like
> the DLL MAIN calls, GetProcXXXX and exceptions if not already on.
>
> But it seems it didn't get too far once it got to SAM.EXE and within .015
> seconds, it exited.
>
> It looks like the SAM.EXE program exited with a code 0xC0000409.
>
> I swagging now, but googling
>
>     .NET C0000409
>
> brings up a bunch of stuff.  See if any of these hits apply to you or
> makes sense to your application.
>
> Quick suggestions:
>
> 1) Try turning off the VS hosting process. See if you duplicate it under
> the IDE. Even running it in non-debug release mode.
>
> 2) See if you put in a MSGBOX or DEBUG.WRITELINE  at the very beginning as
> a quick test run on Window 2003.
>
> DEBUG.WRITELINE is useful with a debug trace window.
>
> See http://msdn.microsoft.com/en-us/library/system.diagnostics.debug.aspx
>
> Download DBGVIEW.EXE so u can run it on the target machine.
>
> http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
>
> DBGVIEW.EXE allows you to popup a window to see traces from applications.
> Doing a trace, is a wrapper over the OutputDebugString(string) C/C++
> function which in VB.NET is
>
>    Debug.Writelin("Step 1 - starting")
>    ...
>    Debug.Writelin("Step 2 - doing something else")
>
> now, the beauty is that you can keep these in code and it is only compiled
> when you compile in DEBUG mode or with the /D:DEBUG=TRUE switch.
>
> I suspect u are not even getting to step 1, if so, it meas this is
> something in your application that is causing it to exit prematurely.
>
>
> --
>
>
> Steve wrote:
>> Hi Mike
>>
>> Thanks for the reply
>>
>> I ran Depends but am not sure what it is telling me
>>
>> See below
>>
>> Operating System: Microsoft Windows 2003 Server R2 (32-bit), version
>> 5.02.3790 Service Pack 2
>> Program Executable: c:\program files\osmont technologies\salon
>> applications manager\SAM.EXE
>> Program Arguments:
>> Starting Directory: C:\Program Files\Osmont Technologies\Salon
>> Applications Manager\
>> Search Path:
>> C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Program
>> Files\Microsoft SQL Server\90\Tools\binn\
>>
>> Options Selected:
>>      Log DllMain calls for process attach and process detach messages.
>>      Hook the process to gather more detailed dependency information.
>>      Log LoadLibrary function calls.
>>      Log GetProcAddress function calls.
>>      Log thread information.
>>      Use simple thread numbers instead of actual thread IDs.
>>      Log first chance exceptions.
>>      Log debug output messages.
>>      Use full paths when logging file names.
>>      Log a time stamp with each line of log.
>>      Automatically open and profile child processes.
>> --------------------------------------------------------------------------------
>>
>> 00:00:00.000: Started "c:\program files\osmont technologies\salon
>> applications manager\SAM.EXE" (process 0xB04) at address 0x00400000 by
>> thread 1.  Successfully hooked module.
>> 00:00:00.000: Loaded "c:\windows\system32\NTDLL.DLL" at address
>> 0x7C800000 by thread 1.  Successfully hooked module.
>> 00:00:00.000: Loaded "c:\windows\system32\MSCOREE.DLL" at address
>> 0x79000000 by thread 1.  Successfully hooked module.
>> 00:00:00.000: Loaded "c:\windows\system32\KERNEL32.DLL" at address
>> 0x77E40000 by thread 1.  Successfully hooked module.
>> 00:00:00.000: DllMain(0x77E40000, DLL_PROCESS_ATTACH, 0x00000000) in
>> "c:\windows\system32\KERNEL32.DLL" called by thread 1.
>> 00:00:00.000: DllMain(0x77E40000, DLL_PROCESS_ATTACH, 0x00000000) in
>> "c:\windows\system32\KERNEL32.DLL" returned 1 (0x1) by thread 1.
>> 00:00:00.016: Injected "c:\temp\depends22_x86\DEPENDS.DLL" at address
>> 0x08370000 by thread 1.
>> 00:00:00.079: DllMain(0x79000000, DLL_PROCESS_ATTACH, 0x00000000) in
>> "c:\windows\system32\MSCOREE.DLL" called by thread 1.
>> 00:00:00.094: DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in
>> "c:\temp\depends22_x86\DEPENDS.DLL" called by thread 1.
>> 00:00:00.094: DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in
>> "c:\temp\depends22_x86\DEPENDS.DLL" returned 1 (0x1) by thread 1.
>> 00:00:00.110: GetProcAddress(0x77E40000
>> [c:\windows\system32\KERNEL32.DLL], "FlsAlloc") called from
>> "c:\windows\system32\MSCOREE.DLL" at address 0x79006079 and returned
>> 0x77E6B49C by thread 1.
>> 00:00:00.125: Exited "c:\program files\osmont technologies\salon
>> applications manager\SAM.EXE" (process 0xB04) with code -1073740791
>> (0xC0000409) by thread 1.
>>
>> What I can't understand is why the program runs OK in VS design env
>>
>> Regards
>> Steve
>>
>>
>> "Mike" <unkn***@unknown.tv> wrote in message
>> news:%23EtLntY6JHA.2456@TK2MSFTNGP02.phx.gbl...
>>> I would download DEPENDS from MSDN if you don't have it already and load
>>> it from DEPENDS.
>>>      DEPENDS yourAPP.EXE
>>>
>>> Click START | PROFILES and see what happens.
>>>
>>> --
>>>
>>> Steve wrote:
>>>> Hi All
>>>>
>>>> I have installed Windows Server 2003 and have installed one of my
>>>> VS2008 SP1 apps
>>>>
>>>> When I run the app, either from the desktop icon or .exe directly, the
>>>> mouse icon changes for a second but the app doesn't start
>>>>
>>>> There are no log entries in the Event log and no error messages
>>>> received
>>>>
>>>> I have installed VS2008 SP2 and run my app from within VS 2008 and it
>>>> works fine
>>>> If I double click the .exe file generated by VS the app doesn't run
>>>>
>>>> This is wierd
>>>>
>>>> Any ideas
>>>>
>>>> Regards
>>>> Steve
>>

> Hi Mike
>
> Great work
>
> I turned off the VS Hosting process and now I get errors related to not
> finding dlls
> I have an app.config file with
> <probing privatePath="DLLs" /> which is the folder the .dlls are stored
>
> The error states ...
>
> LOG: Initial PrivatePath = NULL
>
> LOG: No Application configuration file found
>
> I have a configuration file in the bin folder, SAM.exe.config which has the
> probing section so I am lost
>
> Keep in mind the program runs fine on XP and Vista. Its only Windows 2003
> Server I am having problems with
>
> Any ideas
>
> Regards
>
> Steve

"Mike" <unkn***@unknown.tv> wrote in message
news:%23G4Rn1i6JHA.1716@TK2MSFTNGP03.phx.gbl...
> Glad you are zooming in on the issue. :-)
>
> Unfortunately, you reached a point where I have not caught up yet with
> .NET.  I'm still learning it and have not dealt with distribution issues,
> manifest and assemblies and DLL dependencies.  I'm sure others here with
> products already in .NET can provide further assistance with this.  I
> would if I knew. :-)
>
> The only thing I have left about this is that when you run .net
> applications on share drive, .NET acts weird and I've seen both silent
> runs to exceptions with erroneous messages being thrown.
>
> --
>
> Steve wrote:
>> Hi Mike
>>
>> Great work
>>
>> I turned off the VS Hosting process and now I get errors related to not
>> finding dlls
>> I have an app.config file with
>> <probing privatePath="DLLs" /> which is the folder the .dlls are stored
>>
>> The error states ...
>>
>> LOG: Initial PrivatePath = NULL
>>
>> LOG: No Application configuration file found
>>
>> I have a configuration file in the bin folder, SAM.exe.config which has
>> the probing section so I am lost
>>
>> Keep in mind the program runs fine on XP and Vista. Its only Windows 2003
>> Server I am having problems with
>>
>> Any ideas
>>
>> Regards
>>
>> Steve