From: Brandon on 06/30/2000
SomeBody PlEaSe HeLp Me!!!!!!!!!!!
I seem to crash several times a day! And its almost always OLEMAINTHREADWNDNAME! what the heck is it and how can i fix it???????
Sometimes i cant even shut down properly to fix the problem.....it takes several tries to stay up long enuff to shut down properly so i can go back online.
| |
Votes:
Rating: 0
Delete: 0
|
|
--- Replies to this Problem ---
From: Brandon on 06/07/2000
THANK YOU KEN! =-):
: from Microsoft: : SUMMARY
: If an application makes a SQLConnect or SQLDriverConnect call to ODBC Desktop Drivers 3.x, and if the application is idling after SQLConnect or SQLDriverConnect has returned, any other application that broadcasts a DDE message (message broadcasters) may hang. Once the application disconnects from the database, the hanging application works normally. : MORE INFORMATION
: When SQLConnect or SQLDriverConnect is called, ODBC DeskTop Drivers initialize OLE using threads that they create internally. As a result of OLE initialization, three hidden windows--DDEServerWindow, OLEChannelWnd, and OLEMainthreadwndname--are created. : If the thread that made the database connection is idle, then the hidden windows will not respond to any broadcast DDE messages sent by other applications. For example, if an application broadcasts a message such as WM_DDE_INITIATE to all windows, the SendMessage hangs until all the top- level windows have received the message. Because the thread that created the hidden windows is idle and does not respond, the application hangs. This is a known OLE issue in mutithreaded applications. : I use Norton Crashguard to get rid of the window - but I still don't know how to stop it.
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Brandon on 06/07/2000
:
: from Microsoft: : SUMMARY
: If an application makes a SQLConnect or SQLDriverConnect call to ODBC Desktop Drivers 3.x, and if the application is idling after SQLConnect or SQLDriverConnect has returned, any other application that broadcasts a DDE message (message broadcasters) may hang. Once the application disconnects from the database, the hanging application works normally. : MORE INFORMATION
: When SQLConnect or SQLDriverConnect is called, ODBC DeskTop Drivers initialize OLE using threads that they create internally. As a result of OLE initialization, three hidden windows--DDEServerWindow, OLEChannelWnd, and OLEMainthreadwndname--are created. : If the thread that made the database connection is idle, then the hidden windows will not respond to any broadcast DDE messages sent by other applications. For example, if an application broadcasts a message such as WM_DDE_INITIATE to all windows, the SendMessage hangs until all the top- level windows have received the message. Because the thread that created the hidden windows is idle and does not respond, the application hangs. This is a known OLE issue in mutithreaded applications. : I use Norton Crashguard to get rid of the window - but I still don't know how to stop it.
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Ken on 06/01/2000
from Microsoft:SUMMARY
If an application makes a SQLConnect or SQLDriverConnect call to ODBC Desktop Drivers 3.x, and if the application is idling after SQLConnect or SQLDriverConnect has returned, any other application that broadcasts a DDE message (message broadcasters) may hang. Once the application disconnects from the database, the hanging application works normally. MORE INFORMATION
When SQLConnect or SQLDriverConnect is called, ODBC DeskTop Drivers initialize OLE using threads that they create internally. As a result of OLE initialization, three hidden windows--DDEServerWindow, OLEChannelWnd, and OLEMainthreadwndname--are created. If the thread that made the database connection is idle, then the hidden windows will not respond to any broadcast DDE messages sent by other applications. For example, if an application broadcasts a message such as WM_DDE_INITIATE to all windows, the SendMessage hangs until all the top- level windows have received the message. Because the thread that created the hidden windows is idle and does not respond, the application hangs. This is a known OLE issue in mutithreaded applications. I use Norton Crashguard to get rid of the window - but I still don't know how to stop it.
| |
Votes:
Rating: 0
Delete: 0
|
|
|
