Problem described in kb article Q156484

[Guest Kin]

Hi there,

 

First time poster here and I hope that I post the question in the right group.

 

I am seeing the problem described in the kb article Q156484 on a Windows

2000 and Windows 2003 machines. However, the articule indicates the problem

applies to Windows NT 4.0. Does that mean the problem is fixed in Windows

2000 and later? If so, how can I determine which server pack contains the

fix? If not, how can I find the solutions for those 2 platforms?

 

Another input are welcome and thanks for your time in advance.

-Kin

[Guest Meinolf Weber]

Re: Problem described in kb article Q156484

 

Hello Kin,

 

It is not easy with this article to cmoply with your problems. Please describe

in detail when you are seeing it on your servers and if possible post the

complete error message and also errors from the event viewer.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Q156484

>

[Guest Kin]

Re: Problem described in kb article Q156484

 

Hi Meinolf,

 

Thanks for your reply.

 

Below is the code segment where I spawn a new process in my application:

 

=== code start

 

STARTUPINFO si;

SECURITY_ATTRIBUTES sa;

PROCESS_INFORMATION pi;

 

memset ((void*)&si, 0, sizeof (STARTUPINFO));

memset ((void*)&sa, 0, sizeof (SECURITY_ATTRIBUTES));

memset ((void*)&pi, 0, sizeof (PROCESS_INFORMATION));

 

sa.nLength = sizeof sa;

sa.lpSecurityDescriptor = NULL;

sa.bInheritHandle = TRUE;

 

si.cb = sizeof(STARTUPINFO);

si.dwFlags = STARTF_USESTDHANDLES | STARTF_USESHOWWINDOW;

si.lpDesktop = "";

si.wShowWindow = SW_HIDE;

 

CreateProcess (NULL, cmd, NULL, NULL, TRUE,

NORMAL_PRIORITY_CLASS | CREATE_NEW_CONSOLE,

NULL, NULL, &si, &pi);

 

=== code end

 

CreateProcess() returns true, but the new process was never started.

However, a valid process handle is stored in the pi.hProcess field. Calling

 

WaitForSingleObject (pi.hProcess, INFINITE);

 

returns immediately and the process return code (obtained by calling

GetExitCodeProcess()) is 128 (ERROR_WAIT_NO_CHILDREN). There is no error

event in the event log or error message being displayed anywhere.

 

Given the information I've in hand, I believe I'm experiencing the problem

described in the kb article, but only my app has that problem when running on

some Windows 2000/2003 machines. Hence, that leads to the questions in my

first post.

 

Thanks

-Kin

 

"Meinolf Weber" wrote:

> Hello Kin,

>

> It is not easy with this article to cmoply with your problems. Please describe

> in detail when you are seeing it on your servers and if possible post the

> complete error message and also errors from the event viewer.

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

> > Q156484

> >

>

>

>

[Guest Meinolf Weber]

Re: Problem described in kb article Q156484

 

Hello Kin,

 

Sorry, but better post in some programmers NG's.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hi Meinolf,

>

> Thanks for your reply.

>

> Below is the code segment where I spawn a new process in my

> application:

>

> === code start

>

> STARTUPINFO si;

> SECURITY_ATTRIBUTES sa;

> PROCESS_INFORMATION pi;

> memset ((void*)&si, 0, sizeof (STARTUPINFO));

> memset ((void*)&sa, 0, sizeof (SECURITY_ATTRIBUTES));

> memset ((void*)&pi, 0, sizeof (PROCESS_INFORMATION));

> sa.nLength = sizeof sa;

> sa.lpSecurityDescriptor = NULL;

> sa.bInheritHandle = TRUE;

> si.cb = sizeof(STARTUPINFO);

> si.dwFlags = STARTF_USESTDHANDLES | STARTF_USESHOWWINDOW;

> si.lpDesktop = "";

> si.wShowWindow = SW_HIDE;

> CreateProcess (NULL, cmd, NULL, NULL, TRUE,

> NORMAL_PRIORITY_CLASS | CREATE_NEW_CONSOLE,

> NULL, NULL, &si, &pi);

> === code end

>

> CreateProcess() returns true, but the new process was never started.

> However, a valid process handle is stored in the pi.hProcess field.

> Calling

>

> WaitForSingleObject (pi.hProcess, INFINITE);

>

> returns immediately and the process return code (obtained by calling

> GetExitCodeProcess()) is 128 (ERROR_WAIT_NO_CHILDREN). There is no

> error event in the event log or error message being displayed

> anywhere.

>

> Given the information I've in hand, I believe I'm experiencing the

> problem described in the kb article, but only my app has that problem

> when running on some Windows 2000/2003 machines. Hence, that leads to

> the questions in my first post.

>

> Thanks

> -Kin

> "Meinolf Weber" wrote:

>

>> Hello Kin,

>>

>> It is not easy with this article to cmoply with your problems. Please

>> describe in detail when you are seeing it on your servers and if

>> possible post the complete error message and also errors from the

>> event viewer.

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> Q156484

>>>

[Guest Kin]

Re: Problem described in kb article Q156484

 

Hi Meinolf,

 

Thanks for your reply. I will do that.

 

-Kin

 

"Meinolf Weber" wrote:

> Hello Kin,

>

> Sorry, but better post in some programmers NG's.

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

> > Hi Meinolf,

> >

> > Thanks for your reply.

> >

> > Below is the code segment where I spawn a new process in my

> > application:

> >

> > === code start

> >

> > STARTUPINFO si;

> > SECURITY_ATTRIBUTES sa;

> > PROCESS_INFORMATION pi;

> > memset ((void*)&si, 0, sizeof (STARTUPINFO));

> > memset ((void*)&sa, 0, sizeof (SECURITY_ATTRIBUTES));

> > memset ((void*)&pi, 0, sizeof (PROCESS_INFORMATION));

> > sa.nLength = sizeof sa;

> > sa.lpSecurityDescriptor = NULL;

> > sa.bInheritHandle = TRUE;

> > si.cb = sizeof(STARTUPINFO);

> > si.dwFlags = STARTF_USESTDHANDLES | STARTF_USESHOWWINDOW;

> > si.lpDesktop = "";

> > si.wShowWindow = SW_HIDE;

> > CreateProcess (NULL, cmd, NULL, NULL, TRUE,

> > NORMAL_PRIORITY_CLASS | CREATE_NEW_CONSOLE,

> > NULL, NULL, &si, &pi);

> > === code end

> >

> > CreateProcess() returns true, but the new process was never started.

> > However, a valid process handle is stored in the pi.hProcess field.

> > Calling

> >

> > WaitForSingleObject (pi.hProcess, INFINITE);

> >

> > returns immediately and the process return code (obtained by calling

> > GetExitCodeProcess()) is 128 (ERROR_WAIT_NO_CHILDREN). There is no

> > error event in the event log or error message being displayed

> > anywhere.

> >

> > Given the information I've in hand, I believe I'm experiencing the

> > problem described in the kb article, but only my app has that problem

> > when running on some Windows 2000/2003 machines. Hence, that leads to

> > the questions in my first post.

> >

> > Thanks

> > -Kin

> > "Meinolf Weber" wrote:

> >

> >> Hello Kin,

> >>

> >> It is not easy with this article to cmoply with your problems. Please

> >> describe in detail when you are seeing it on your servers and if

> >> possible post the complete error message and also errors from the

> >> event viewer.

> >>

> >> Best regards

> >>

> >> Meinolf Weber

> >> Disclaimer: This posting is provided "AS IS" with no warranties, and

> >> confers

> >> no rights.

> >> ** Please do NOT email, only reply to Newsgroups

> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >>> Q156484

> >>>

>

>

>