gettign stright to problem.
have written an code for service which do not works for one PC.
gives error at system event log for exe has not ended properly.
observation is
1. Start of service will start 5 chield EXEs.
2. Stop of service will stop all 5 EXEs and then close the service.
3. at the start & stop of main() I have printed logs saying Entry &
Exit points
4. from main servicemain() is called which start & stops the chield(5)
processes
5. logs for individual chield start & stop is also printed.
6. confirmation of start & stop of chield is done via
GetExitCodeProcess()
Observation of the logs printed on both the PC are exectly the same.
On the PC where it works when I click on Stop service,
observation of Task Manager shows closer of all the service within 1
sec or so.
On the PC where I get error in Event viewer
observation of Task Manager shows closer of all the chield within 1
sec or so.
where by service task still going on. after 2-3 seconds error is
shown in the event viewer.
Logs of both the PC compared and found exectly same.
I am quite confused as to what & where can be the problem...
-----------------------------------------
Error details
-----------------------------------------
Error generating application service.exe, version 0.0.0.0,
error generating module unknown, version 0.0.0.0,
error generating address 0x00000000
Please refer to http://go.microsoft.com/fwlink/events.asp for detailed
information.
-----------------------------------------
if any one have any view point please share with me... so as i can
resolve this problem.
Sp the PC where it is not working... (suppose to be the End Client
PC...)
Thanks in advance.
Bipin Mistry.
It looks like the service doesn't handle some error condition (possibly
related to a corrupt user profile or too small Registry heap size) which
causes it to try to run code at 0.
The most appropriate way to find out what's wrong would be to debug the
service (precede ImagePath with your debugger and make service interactive
or, if the service has a switch to make it runnable as a normal application,
use it.
If you don't want to install a debugger on the workstations you can use
remote debugging over a LAN or so.
Of course, you could also verify that all errors are handled properly in the
code. You may also enable drwtsn32 and try to figure out something from the
output (preferably with a debug build of the service). The fact that it took
time to get the error also makes me think that drwatson already did create a
log file.
- Sten
- Sten
Hi sten
thanks for the degugger info, will try it right away...
mean while I tried on other 2 PCs and found the result OK
this makes me think there is some environmental issue related to this
problem.
If you have any idea please do get back... mean while will try for the
drwtsn32.
- Bipin