In some circumstances, messages will become stuck in the Outbox folder
according to WinMail (even though no message may exist in the outbox
directory of eml files). These stuck messages prevent WinMail from being
able to send any messages.

Previously the only solution was to wipe out the database. I've now added a
button to my WMUtil program (http://www.oehelp.com/WMUtil/Default.aspx).
Clicking on the "Clear Outbox" button will remove all references in the
database to outbox messages. This should then enable the user to send
messages again, but since I haven't had the problem, I haven't been able to
test if it will work for those who are experiencing it.



steve

"Steve Cochran" <scochran@oehelp.com> wrote in message
news:14A87C0D-07EA-42EB-8C80-F4A4C78FEBC9@microsoft.com...
> In some circumstances, messages will become stuck in the Outbox folder
> according to WinMail (even though no message may exist in the outbox
> directory of eml files). These stuck messages prevent WinMail from being
> able to send any messages.
>
> Previously the only solution was to wipe out the database. I've now added
> a button to my WMUtil program (http://www.oehelp.com/WMUtil/Default.aspx).
> Clicking on the "Clear Outbox" button will remove all references in the
> database to outbox messages. This should then enable the user to send
> messages again, but since I haven't had the problem, I haven't been able
> to test if it will work for those who are experiencing it.

I don't need it myself, yet, but thanks in advance for putting in the
effort.
Cheers.

"Julian" <Julianlzb87@gmail.com> wrote in message news:E5AE8DE4-E404-4314-BB86-6C721CDC0B48@microsoft.com...
> "Steve Cochran" <scochran@oehelp.com> wrote in message news:14A87C0D-07EA-42EB-8C80-F4A4C78FEBC9@microsoft.com...
>> In some circumstances, messages will become stuck in the Outbox folder according to WinMail (even though no message may exist
>> in the outbox directory of eml files). These stuck messages prevent WinMail from being able to send any messages.
>>
>> Previously the only solution was to wipe out the database. I've now added a button to my WMUtil program
>> (http://www.oehelp.com/WMUtil/Default.aspx). Clicking on the "Clear Outbox" button will remove all references in the database
>> to outbox messages. This should then enable the user to send messages again, but since I haven't had the problem, I haven't
>> been able to test if it will work for those who are experiencing it.
>
> I don't need it myself, yet, but thanks in advance for putting in the effort.
> Cheers.

Likewise. I'll make sure to recommend this utility to anyone
suffering from the stuck message in the Outbox problem.
--
Gary VanderMolen

I'm waiting to see what happens for the users with the problem.

The WinMail.exe process has to be ended to enable the button. And it takes
a while to go through and fix things. If there are actually messages in the
outbox directory of eml files, then those messages are not deleted. Only
the database is cleared of references to outbox messages.

steve

"Gary VanderMolen" <gary@NoMail.invalid> wrote in message
news:u%23Xg86RjHHA.3792@TK2MSFTNGP04.phx.gbl...
> "Julian" <Julianlzb87@gmail.com> wrote in message
> news:E5AE8DE4-E404-4314-BB86-6C721CDC0B48@microsoft.com...
>> "Steve Cochran" <scochran@oehelp.com> wrote in message
>> news:14A87C0D-07EA-42EB-8C80-F4A4C78FEBC9@microsoft.com...
>>> In some circumstances, messages will become stuck in the Outbox folder
>>> according to WinMail (even though no message may exist in the outbox
>>> directory of eml files). These stuck messages prevent WinMail from being
>>> able to send any messages.
>>>
>>> Previously the only solution was to wipe out the database. I've now
>>> added a button to my WMUtil program
>>> (http://www.oehelp.com/WMUtil/Default.aspx). Clicking on the "Clear
>>> Outbox" button will remove all references in the database to outbox
>>> messages. This should then enable the user to send messages again, but
>>> since I haven't had the problem, I haven't been able to test if it will
>>> work for those who are experiencing it.
>>
>> I don't need it myself, yet, but thanks in advance for putting in the
>> effort.
>> Cheers.
>
> Likewise. I'll make sure to recommend this utility to anyone
> suffering from the stuck message in the Outbox problem.
> --
> Gary VanderMolen
>

I'm still waiting to see if it works.

Thanks!

steve

"Julian" <Julianlzb87@gmail.com> wrote in message
news:E5AE8DE4-E404-4314-BB86-6C721CDC0B48@microsoft.com...
> "Steve Cochran" <scochran@oehelp.com> wrote in message
> news:14A87C0D-07EA-42EB-8C80-F4A4C78FEBC9@microsoft.com...
>> In some circumstances, messages will become stuck in the Outbox folder
>> according to WinMail (even though no message may exist in the outbox
>> directory of eml files). These stuck messages prevent WinMail from being
>> able to send any messages.
>>
>> Previously the only solution was to wipe out the database. I've now
>> added a button to my WMUtil program
>> (http://www.oehelp.com/WMUtil/Default.aspx). Clicking on the "Clear
>> Outbox" button will remove all references in the database to outbox
>> messages. This should then enable the user to send messages again, but
>> since I haven't had the problem, I haven't been able to test if it will
>> work for those who are experiencing it.
>
> I don't need it myself, yet, but thanks in advance for putting in the
> effort.
> Cheers.

"Steve Cochran" wrote:

> I'm still waiting to see if it works.
>
> Thanks!
>
> steve


Steve, I downloaded the WUtil and when I went to run the clear outbox I got
an error message saying "Unhandled exception has occured in your
application.........
Unable to load DLL @scxout.dll@ the application has failed to start because
it's side by side configuration is incorrect......"

What does this mean?

Create a directory on the Desktop. Then extract the two files from the zip
file into that directory. Then open that directory and click on the
WMUtil.exe file to open the program. See if that fixes the problem.

steve

"benjibogs" <benjibogs@discussions.microsoft.com> wrote in message
news4705C78-1DD2-4081-A25F-6FC4765A98E5@microsoft.com...
>
>
> "Steve Cochran" wrote:
>
>> I'm still waiting to see if it works.
>>
>> Thanks!
>>
>> steve
>
>
> Steve, I downloaded the WUtil and when I went to run the clear outbox I
> got
> an error message saying "Unhandled exception has occured in your
> application.........
> Unable to load DLL @scxout.dll@ the application has failed to start
> because
> it's side by side configuration is incorrect......"
>
> What does this mean?

By directory you mean folder? - sorry not all that clever with these pc wotsits

"Steve Cochran" wrote:

> Create a directory on the Desktop. Then extract the two files from the zip
> file into that directory. Then open that directory and click on the
> WMUtil.exe file to open the program. See if that fixes the problem.
>
> steve
>
> "benjibogs" <benjibogs@discussions.microsoft.com> wrote in message
> news4705C78-1DD2-4081-A25F-6FC4765A98E5@microsoft.com...
> >
> >
> > "Steve Cochran" wrote:
> >
> >> I'm still waiting to see if it works.
> >>
> >> Thanks!
> >>
> >> steve
> >
> >
> > Steve, I downloaded the WUtil and when I went to run the clear outbox I
> > got
> > an error message saying "Unhandled exception has occured in your
> > application.........
> > Unable to load DLL @scxout.dll@ the application has failed to start
> > because
> > it's side by side configuration is incorrect......"
> >
> > What does this mean?
>

Yes. Directory = Folder

"benjibogs" <benjibogs@discussions.microsoft.com> wrote in message
news:F1DBA1C0-5D51-4630-90C9-3EC61ACD4E79@microsoft.com...
> By directory you mean folder? - sorry not all that clever with these pc
> wotsits
>
> "Steve Cochran" wrote:
>
>> Create a directory on the Desktop. Then extract the two files from the
>> zip
>> file into that directory. Then open that directory and click on the
>> WMUtil.exe file to open the program. See if that fixes the problem.
>>
>> steve
>>
>> "benjibogs" <benjibogs@discussions.microsoft.com> wrote in message
>> news4705C78-1DD2-4081-A25F-6FC4765A98E5@microsoft.com...
>> >
>> >
>> > "Steve Cochran" wrote:
>> >
>> >> I'm still waiting to see if it works.
>> >>
>> >> Thanks!
>> >>
>> >> steve
>> >
>> >
>> > Steve, I downloaded the WUtil and when I went to run the clear outbox
>> > I
>> > got
>> > an error message saying "Unhandled exception has occured in your
>> > application.........
>> > Unable to load DLL @scxout.dll@ the application has failed to start
>> > because
>> > it's side by side configuration is incorrect......"
>> >
>> > What does this mean?
>>

Hi guys,

I've read all the messages and have downloaded the fix, and I'm STILL STUCK,
( I did not understand the whole moving process, because it's kind of
muddled, no matter how many times you explain it, something I'm doing isn't
right. ) however this is what I'm getting when I try to run the tool:

Unhandled exception has occurred in your application. If you click continue,
the application will ignore this error and attempt to continue. If you click
Quit, the application will close immediately.

When you click on Details in the box, this is what you get:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.DllNotFoundException: Unable to load DLL 'scxout.dll': The
application has failed to start because its side-by-side configuration is
incorrect. Please see the application event log for more detail. (Exception
from HRESULT: 0x800736B1)
at WMUtil.MWMUtil1.XOut(IntPtr pszLogPath, IntPtr pszName,
XoutCallbackProc x)
at WMUtil.frmWMUtil1.btnXOut_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WMUtil
Assembly Version: 1.5.0.0
Win32 Version: 1.5.0.0
CodeBase: file:///C:/Users/Heather/Desktop/Mail%20Help/wmutil/WMUtil.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.






I'm very, very frustrated with a lot of things with VISTA--but this has been
by far the most annoying.