Application Error: CiceroUIWndFrame

1 May 2006 11:10 PM

Marty Cruise

Everything has been running like a dream, until I performed my last one-click
deployment. Now on application close, users get:

==================
Application Error
The instruction at "0x30cb0a4f" referenced memory at "0x00000000". The
memory could not be written.
==================

Strangely, while developing the latest version, I must have ran the app a
hundred times through VS Studio and did not encounter this error. I
installed the app on my development machine and now get the error as the
users do. When I run it through VS Studio, same thing. The only difference
when I run through VS Studio is that the Application Error indicates
CiceroUIWndFrame in the title.

I've even tried running previous versions, which themselves did not throw an
error, and I now get the same thing.

What the heck can be going on? One of the latest MS updates maybe?

2 May 2006 11:17 AM

Russel Trojan

I've gotten this error as well, and I found that this is a known issue in
Microsoft Office 2003. To get rid of the error message, uninstall the
Alternate User Input components in Microsoft Office. Since I don't use
handwriting or voice recognition, the removal didn't affect anything useful,
but the error magically disappeared.

Show quoteHide quote

"Marty Cruise" <MartyCru***@discussions.microsoft.com> wrote in message
news:3A208D23-8910-4274-AF9D-1F85DBDDE68B@microsoft.com...
> Everything has been running like a dream, until I performed my last
> one-click
> deployment. Now on application close, users get:
>
> ==================
> Application Error
> The instruction at "0x30cb0a4f" referenced memory at "0x00000000". The
> memory could not be written.
> ==================
>
> Strangely, while developing the latest version, I must have ran the app a
> hundred times through VS Studio and did not encounter this error. I
> installed the app on my development machine and now get the error as the
> users do. When I run it through VS Studio, same thing. The only
> difference
> when I run through VS Studio is that the Application Error indicates
> CiceroUIWndFrame in the title.
>
> I've even tried running previous versions, which themselves did not throw
> an
> error, and I now get the same thing.
>
> What the heck can be going on? One of the latest MS updates maybe?
>

3 May 2006 2:40 PM

Marty Cruise

Looks like the cause is a bug in the mso.dll, which is used by the web
browser control. Remove the web browser control and the error disappears.