Windows NT Prevent Window Popup

  • Thread starter Thread starter Webbert
  • Start date Start date
W

Webbert

I just got involved in a production issue and believe that there is a popup
window that is preventing the system from running until someone presses "OK".

The only indication that I have at this point is a screen shot of an event
log that shows
Source: Application Popup
Category: None
Type: Information
Event ID: 26
User: N/A

No other information is available.

I thought that there was a way with Dr. Watson to prevent any and all popups
from displaying on a server that expects no UI. Can anyone point me in the
right direction to prevent the popups from occuring?

Thanks,
Dave
 
Try to verify if there really is a popup window, and which
application or service created it.
Most likely, it's on the console of the server.
If you are running 2003, connect to the console session with
mstsc /console.
If you are running W2K, you'll have to logon to the physical
console of the server.

If the popup is created by a 3rd party application, there's
probably not much that you can do. If the application isn't TS
compatible, it's possible that it has hardcoded the popup to always
appear in the console session. Contacting the developer of the
application is then your only chance.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?V2ViYmVydA==?=
<webbertsolutions@hotmail.com.REMOVE.THIS> wrote on 01 aug 2007 in
microsoft.public.windows.terminal_services:

> I just got involved in a production issue and believe that there
> is a popup window that is preventing the system from running
> until someone presses "OK".
>
> The only indication that I have at this point is a screen shot
> of an event log that shows
> Source: Application Popup
> Category: None
> Type: Information
> Event ID: 26
> User: N/A
>
> No other information is available.
>
> I thought that there was a way with Dr. Watson to prevent any
> and all popups from displaying on a server that expects no UI.
> Can anyone point me in the right direction to prevent the popups
> from occuring?
>
> Thanks,
> Dave
 
It is a 2003 box.
Once, I connect to the console session with RDC what do I do?

Thanks,
Dave

"Vera Noest [MVP]" wrote:

> Try to verify if there really is a popup window, and which
> application or service created it.
> Most likely, it's on the console of the server.
> If you are running 2003, connect to the console session with
> mstsc /console.
> If you are running W2K, you'll have to logon to the physical
> console of the server.
>
> If the popup is created by a 3rd party application, there's
> probably not much that you can do. If the application isn't TS
> compatible, it's possible that it has hardcoded the popup to always
> appear in the console session. Contacting the developer of the
> application is then your only chance.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?V2ViYmVydA==?=
> <webbertsolutions@hotmail.com.REMOVE.THIS> wrote on 01 aug 2007 in
> microsoft.public.windows.terminal_services:
>
> > I just got involved in a production issue and believe that there
> > is a popup window that is preventing the system from running
> > until someone presses "OK".
> >
> > The only indication that I have at this point is a screen shot
> > of an event log that shows
> > Source: Application Popup
> > Category: None
> > Type: Information
> > Event ID: 26
> > User: N/A
> >
> > No other information is available.
> >
> > I thought that there was a way with Dr. Watson to prevent any
> > and all popups from displaying on a server that expects no UI.
> > Can anyone point me in the right direction to prevent the popups
> > from occuring?
> >
> > Thanks,
> > Dave
>
 
Hi Dave,

What Vera meant was that if the popup is occuring on the console (i.e. not a
remote session) then you will see it if you connect using the /console
switch (this is like physically being at the console) however you are still
going to have to wait until the message appears though or cause the app to
recreate it's problem.

If this is the case it's known as an hard error, or hard message and there
might not be a lot you can do about it other than go back to the developer
of the application.

Out of curiosity, what is the issue - what is making you think you need to
click OK on something before you can continue?

Thanks,
Jon

-----




"Webbert" <webbertsolutions@hotmail.com.REMOVE.THIS> wrote in message
news:060DA2EB-CCED-47C7-BFE8-A28E63F43276@microsoft.com...
> It is a 2003 box.
> Once, I connect to the console session with RDC what do I do?
>
> Thanks,
> Dave
>
> "Vera Noest [MVP]" wrote:
>
>> Try to verify if there really is a popup window, and which
>> application or service created it.
>> Most likely, it's on the console of the server.
>> If you are running 2003, connect to the console session with
>> mstsc /console.
>> If you are running W2K, you'll have to logon to the physical
>> console of the server.
>>
>> If the popup is created by a 3rd party application, there's
>> probably not much that you can do. If the application isn't TS
>> compatible, it's possible that it has hardcoded the popup to always
>> appear in the console session. Contacting the developer of the
>> application is then your only chance.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?V2ViYmVydA==?=
>> <webbertsolutions@hotmail.com.REMOVE.THIS> wrote on 01 aug 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > I just got involved in a production issue and believe that there
>> > is a popup window that is preventing the system from running
>> > until someone presses "OK".
>> >
>> > The only indication that I have at this point is a screen shot
>> > of an event log that shows
>> > Source: Application Popup
>> > Category: None
>> > Type: Information
>> > Event ID: 26
>> > User: N/A
>> >
>> > No other information is available.
>> >
>> > I thought that there was a way with Dr. Watson to prevent any
>> > and all popups from displaying on a server that expects no UI.
>> > Can anyone point me in the right direction to prevent the popups
>> > from occuring?
>> >
>> > Thanks,
>> > Dave
>>
 
By the error message that it is an application popup and that the service
fails to restart. The service is setup to continuously restart. The only
reason I can think of is that something is preventing it from exiting all the
way so that it can't restart (i.e. a message box )

Thanks,
Dave

"Jon Wallace" wrote:

>
> Hi Dave,
>
> What Vera meant was that if the popup is occuring on the console (i.e. not a
> remote session) then you will see it if you connect using the /console
> switch (this is like physically being at the console) however you are still
> going to have to wait until the message appears though or cause the app to
> recreate it's problem.
>
> If this is the case it's known as an hard error, or hard message and there
> might not be a lot you can do about it other than go back to the developer
> of the application.
>
> Out of curiosity, what is the issue - what is making you think you need to
> click OK on something before you can continue?
>
> Thanks,
> Jon
>
> -----
>
>
>
>
> "Webbert" <webbertsolutions@hotmail.com.REMOVE.THIS> wrote in message
> news:060DA2EB-CCED-47C7-BFE8-A28E63F43276@microsoft.com...
> > It is a 2003 box.
> > Once, I connect to the console session with RDC what do I do?
> >
> > Thanks,
> > Dave
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Try to verify if there really is a popup window, and which
> >> application or service created it.
> >> Most likely, it's on the console of the server.
> >> If you are running 2003, connect to the console session with
> >> mstsc /console.
> >> If you are running W2K, you'll have to logon to the physical
> >> console of the server.
> >>
> >> If the popup is created by a 3rd party application, there's
> >> probably not much that you can do. If the application isn't TS
> >> compatible, it's possible that it has hardcoded the popup to always
> >> appear in the console session. Contacting the developer of the
> >> application is then your only chance.
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?V2ViYmVydA==?=
> >> <webbertsolutions@hotmail.com.REMOVE.THIS> wrote on 01 aug 2007 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > I just got involved in a production issue and believe that there
> >> > is a popup window that is preventing the system from running
> >> > until someone presses "OK".
> >> >
> >> > The only indication that I have at this point is a screen shot
> >> > of an event log that shows
> >> > Source: Application Popup
> >> > Category: None
> >> > Type: Information
> >> > Event ID: 26
> >> > User: N/A
> >> >
> >> > No other information is available.
> >> >
> >> > I thought that there was a way with Dr. Watson to prevent any
> >> > and all popups from displaying on a server that expects no UI.
> >> > Can anyone point me in the right direction to prevent the popups
> >> > from occuring?
> >> >
> >> > Thanks,
> >> > Dave
> >>
>
>
>
 
The following registry setting may help in your situation:

HKLM\SYSTEM\CurrentControlSet\Control\Windows

ErrorMode REG_DWORD 0x00000002

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/29991.mspx?mfr=true

-TP

Webbert wrote:
> I just got involved in a production issue and believe that there is a
> popup window that is preventing the system from running until someone
> presses "OK".
>
> The only indication that I have at this point is a screen shot of an
> event log that shows
> Source: Application Popup
> Category: None
> Type: Information
> Event ID: 26
> User: N/A
>
> No other information is available.
>
> I thought that there was a way with Dr. Watson to prevent any and all
> popups from displaying on a server that expects no UI. Can anyone
> point me in the right direction to prevent the popups from occuring?
>
> Thanks,
> Dave
 
As a follow up. If I wrote a .NET application such as

using System
using System.Collections.Generic
using System.Text

namespace CreateException
{
.. class Program
.. {
.. static void Main( string[] args )
.. {
.. throw new ApplicationException( "This is just a test" )
.. }
.. }
}


A Microsoft Error Dialog Box pops up and says
.. CreateException has stopped working
.. A problem caused the program to stop working correctly.
.. Windows will close the program and notify you if a solution is available.
.. [Debug] [Close program]

Looking at the task manager the program is still running waiting for
me to click on one of the buttons. I'm shooting in the dark as "I"
personnally
don't have access to the production machine, so I can't poke around.

I did find a way to disable the UI for the Windows Error Reporting
(DontShowUI)
http://msdn2.microsoft.com/en-us/library/bb513638.aspx

Any and all thoughts are greatly appreciated.

Dave






"Jon Wallace" wrote:

>
> Hi Dave,
>
> What Vera meant was that if the popup is occuring on the console (i.e. not a
> remote session) then you will see it if you connect using the /console
> switch (this is like physically being at the console) however you are still
> going to have to wait until the message appears though or cause the app to
> recreate it's problem.
>
> If this is the case it's known as an hard error, or hard message and there
> might not be a lot you can do about it other than go back to the developer
> of the application.
>
> Out of curiosity, what is the issue - what is making you think you need to
> click OK on something before you can continue?
>
> Thanks,
> Jon
>
> -----
>
>
>
>
> "Webbert" <webbertsolutions@hotmail.com.REMOVE.THIS> wrote in message
> news:060DA2EB-CCED-47C7-BFE8-A28E63F43276@microsoft.com...
> > It is a 2003 box.
> > Once, I connect to the console session with RDC what do I do?
> >
> > Thanks,
> > Dave
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Try to verify if there really is a popup window, and which
> >> application or service created it.
> >> Most likely, it's on the console of the server.
> >> If you are running 2003, connect to the console session with
> >> mstsc /console.
> >> If you are running W2K, you'll have to logon to the physical
> >> console of the server.
> >>
> >> If the popup is created by a 3rd party application, there's
> >> probably not much that you can do. If the application isn't TS
> >> compatible, it's possible that it has hardcoded the popup to always
> >> appear in the console session. Contacting the developer of the
> >> application is then your only chance.
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?V2ViYmVydA==?=
> >> <webbertsolutions@hotmail.com.REMOVE.THIS> wrote on 01 aug 2007 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > I just got involved in a production issue and believe that there
> >> > is a popup window that is preventing the system from running
> >> > until someone presses "OK".
> >> >
> >> > The only indication that I have at this point is a screen shot
> >> > of an event log that shows
> >> > Source: Application Popup
> >> > Category: None
> >> > Type: Information
> >> > Event ID: 26
> >> > User: N/A
> >> >
> >> > No other information is available.
> >> >
> >> > I thought that there was a way with Dr. Watson to prevent any
> >> > and all popups from displaying on a server that expects no UI.
> >> > Can anyone point me in the right direction to prevent the popups
> >> > from occuring?
> >> >
> >> > Thanks,
> >> > Dave
> >>
>
>
>
 
Gave it shot on my machine "Vista Business" using the code as a test

using System
using System.Windows.Forms

namespace CreateException
{
.. class Program
.. {
.. static void Main( string[] args )
.. {
.. MessageBox.Show( "Some text", "Error Caption",
MessageBoxButtons.OK, MessageBoxIcon.Hand )
.. throw new ApplicationException( "This is just a test" )
.. }
.. }
}

With ErrorMode=2 and then with NoInteractiveServices=1, this produce no
noticable results.
Both the popup and error message was still seen. May be a "Vista" thing
though.

I will try it on a server once I get a virtual up and running.

Thanks for the suggestion.

Dave


"TP" wrote:

> The following registry setting may help in your situation:
>
> HKLM\SYSTEM\CurrentControlSet\Control\Windows
>
> ErrorMode REG_DWORD 0x00000002
>
> http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/29991.mspx?mfr=true
>
> -TP
>
> Webbert wrote:
> > I just got involved in a production issue and believe that there is a
> > popup window that is preventing the system from running until someone
> > presses "OK".
> >
> > The only indication that I have at this point is a screen shot of an
> > event log that shows
> > Source: Application Popup
> > Category: None
> > Type: Information
> > Event ID: 26
> > User: N/A
> >
> > No other information is available.
> >
> > I thought that there was a way with Dr. Watson to prevent any and all
> > popups from displaying on a server that expects no UI. Can anyone
> > point me in the right direction to prevent the popups from occuring?
> >
> > Thanks,
> > Dave
>
 
Hi Dave,

Did you write the code for the service that is having the
problem? If yes then it is best to troubleshoot the cause(s)
of why the service is crashing and/or refusing to shutdown
gracefully.

The ErrorMode setting will not intercept all messagebox calls
if that is what you are thinking.

For a service there should not be any user-interface related
code such as forms, messagebox.show, etc.

I don't think your test code approximates the scenario. Did
you run it as a service? I think that using pinvoke to call
the MessageBox function with MB_SERVICE_NOTIFICATION
for the uType parameter *may* be closer, however, I have not
tested it.

Also keep in mind that code that you run under Vista Business
as a normal application will not run in session 0 (like a service
or app running on the console of 2003 would) and it will not be
running under the SYSTEM account.

-TP

Webbert wrote:
> Gave it shot on my machine "Vista Business" using the code as a test
>
> using System
> using System.Windows.Forms
>
> namespace CreateException
> {
> . class Program
> . {
> . static void Main( string[] args )
> . {
> . MessageBox.Show( "Some text", "Error Caption",
> MessageBoxButtons.OK, MessageBoxIcon.Hand )
> . throw new ApplicationException( "This is just a test" )
> . }
> . }
> }
>
> With ErrorMode=2 and then with NoInteractiveServices=1, this produce
> no noticable results.
> Both the popup and error message was still seen. May be a "Vista"
> thing though.
>
> I will try it on a server once I get a virtual up and running.
>
> Thanks for the suggestion.
>
> Dave
 
You said "The ErrorMode setting will not intercept all messagebox calls
if that is what you are thinking." Yes this is what I was thinking.

I am also aware of the differences between services and applications. The
demo was just something quick and dirty to try.

The code is not mine and I am debugging in the dark. Trying to find any
information that I can pass on to help fix the issue.

Appreciate the help.

Dave


"TP" wrote:

> Hi Dave,
>
> Did you write the code for the service that is having the
> problem? If yes then it is best to troubleshoot the cause(s)
> of why the service is crashing and/or refusing to shutdown
> gracefully.
>
> The ErrorMode setting will not intercept all messagebox calls
> if that is what you are thinking.
>
> For a service there should not be any user-interface related
> code such as forms, messagebox.show, etc.
>
> I don't think your test code approximates the scenario. Did
> you run it as a service? I think that using pinvoke to call
> the MessageBox function with MB_SERVICE_NOTIFICATION
> for the uType parameter *may* be closer, however, I have not
> tested it.
>
> Also keep in mind that code that you run under Vista Business
> as a normal application will not run in session 0 (like a service
> or app running on the console of 2003 would) and it will not be
> running under the SYSTEM account.
>
> -TP
>
> Webbert wrote:
> > Gave it shot on my machine "Vista Business" using the code as a test
> >
> > using System
> > using System.Windows.Forms
> >
> > namespace CreateException
> > {
> > . class Program
> > . {
> > . static void Main( string[] args )
> > . {
> > . MessageBox.Show( "Some text", "Error Caption",
> > MessageBoxButtons.OK, MessageBoxIcon.Hand )
> > . throw new ApplicationException( "This is just a test" )
> > . }
> > . }
> > }
> >
> > With ErrorMode=2 and then with NoInteractiveServices=1, this produce
> > no noticable results.
> > Both the popup and error message was still seen. May be a "Vista"
> > thing though.
> >
> > I will try it on a server once I get a virtual up and running.
> >
> > Thanks for the suggestion.
> >
> > Dave
>
 
Back
Top