Jump to content

MS Word Error Message Not Detected


Recommended Posts

I have an error message from Microsoft word that says:

  • We're sorry. We can't open Filename because we found a problem with its contents.

The title is Microsoft Word but there is no text (you can see in the attached AuINFO information).

image.png.5daca522de970c8f67381d0593590bac.png

Can anyone help me how to deal with this error?

The other problem I have with this is that the Class is used for other errors to, so I cannot just used this class.

Does anyone have an idea how to click on the "OK" when detected?

We're Sorry.txt

Link to comment
Share on other sites

kind of cheesy, but, any chance this error window is a different size than all the rest you deal with?

LibreOffice UDF  ; Scite4AutoIt Spell-Checker Using LibreOffice

Spoiler

"Life is chiefly made up, not of great sacrifices and wonderful achievements, but of little things. It is oftenest through the little things which seem so unworthy of notice that great good or evil is brought into our lives. It is through our failure to endure the tests that come to us in little things, that the habits are molded, the character misshaped; and when the greater tests come, they find us unready. Only by acting upon principle in the tests of daily life can we acquire power to stand firm and faithful in the most dangerous and most difficult positions."

 

Link to comment
Share on other sites

 

This wonderful site allows debugging and testing regular expressions (many flavors available). An absolute must have in your bookmarks.
Another excellent RegExp tutorial. Don't forget downloading your copy of up-to-date pcretest.exe and pcregrep.exe here
RegExp tutorial: enough to get started
PCRE v8.33 regexp documentation latest available release and currently implemented in AutoIt beta.

SQLitespeed is another feature-rich premier SQLite manager (includes import/export). Well worth a try.
SQLite Expert (freeware Personal Edition or payware Pro version) is a very useful SQLite database manager.
An excellent eBook covering almost every aspect of SQLite3: a must-read for anyone doing serious work.
SQL tutorial (covers "generic" SQL, but most of it applies to SQLite as well)
A work-in-progress SQLite3 tutorial. Don't miss other LxyzTHW pages!
SQLite official website with full documentation (may be newer than the SQLite library that comes standard with AutoIt)

Link to comment
Share on other sites

On 3/13/2024 at 1:05 PM, Nine said:

What have you tried so far ?  Any chance you attempt creating a secondary process to kill those windows ?

Hi Nine,  I'm sorry I'm not 100% sure what you mean here... My application (AutoIT) runs constantly to check for possible error message on the screen and needs to deal with it when it finds one. But this error message is NOT detectable. As it has no Visible Text, not special title and the class is a general class.

My AutoIT knowledge stops there - That's my only knowledge I have and that's the extent I tried - Find the window in any particular way, but I don't see a way, because as I attached I don't know how else I could find that error, because AutoIT cannot "see it"... 

 

On 3/13/2024 at 3:17 PM, donnyh13 said:

kind of cheesy, but, any chance this error window is a different size than all the rest you deal with?

Yeah... MAYBE not a bad idea... The only problem is if I have another error that has the same size, it could be "handled" wrongly, which is the reason why, the first time I tried with the CLASS (because it was the only thing I could think of) failed because I think the Print window uses the same CLASS and I ending up cancelling the print job from time to time (or something of the sort ;) )

Link to comment
Share on other sites

On 3/13/2024 at 3:17 PM, donnyh13 said:

kind of cheesy, but, any chance this error window is a different size than all the rest you deal with?

The other problem with this one, is that the window Size may change due to the file name XD 

Link to comment
Share on other sites

@jchd I'm sorry this is not an option.

Unfortunately this is an automated system, not a system that we actually manage files. So I wouldn't go through the whole process of fixing the file.

If the file has a problem I want the error to go away, the Rendering does not happen, and customers are getting an error that it didn't work. This way they can fix the file, or contact us to check what's happening.

Link to comment
Share on other sites

I was thinking the same as @donnyh13.  But I suspect the Print Window does have readable content right ?  So any window of that size with no content could be considered as error message ?  Another solution would be to use OCR to read the window. Look at :

 

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...