Diese Seite mit anderen teilen ...

Informationen zum Thema:
WinDev Forum
Beiträge im Thema:
Erster Beitrag:
vor 1 Jahr, 3 Monaten
Letzter Beitrag:
vor 1 Jahr, 2 Monaten
Beteiligte Autoren:
steve erts, Frans, Fabrice Harari

AAF Spellcheck crashing word (solved)

Startbeitrag von steve erts am 13.03.2017 19:50


We recently migrated a client to a new server and since the migration the AAFSpellcheck function crashes Winword.exe. I don't really think this is a Windev issue but I'm hoping that it's maybe something someone have seen before and can offer some guidance.

We get an error that says:
This feature is not available Word is not installed properly on this computer.
Access to Selection Autmoation member
Error 800706BA

Problem signature:
Problem Event Name: APPCRASH
Application Name: WINWORD.EXE
Application Version: 15.0.4893.1000
Application Timestamp: 584f9853
Fault Module Name: wwlib.dll
Fault Module Version: 15.0.4893.1000
Fault Module Timestamp: 584f9857
Exception Code: c0000005
Exception Offset: 0010835f
OS Version: 6.3.9600.
Locale ID: 1033

Any advice would be greatly appreciated.



Re: AAF Spellcheck crashing word

Hi Steve,

your application is 32 bits ? Word is 32 bits ?

Best regards

von Fabrice Harari - am 13.03.2017 20:05

Re: AAF Spellcheck crashing word

Fabrice Harari
Hi Steve,

your application is 32 bits ? Word is 32 bits ?

Best regards

Hi Fabrice,

Our app is 32 bit and word on the new server (which is crashing) is 32 bit.

Interesting though, word on the OLD server was 64 bit and that is working.

Something to try though so thanks!


von steve erts - am 13.03.2017 20:21

Re: AAF Spellcheck crashing word

Hi Steve,

Our app is 32 bits, Word 32 bits (because otherwise wordmerge gives a problem) and the workstations are 64 bit.
Almost no problem.

von Frans - am 14.03.2017 10:38

Re: AAF Spellcheck crashing word

It appears that this was caused by Trust Center settings in Word. To fix all users trust center settings needed to be updated to allow Macros and all sessions of Word on server needed to be closed through Task Manager before error cleared itself up.

von steve erts - am 15.03.2017 03:52
After having the issue pop up occur it has been discovered that the issue was being caused by improper licencing of MS Office on my clients new server. e.g The server only had a one user license.

This can be cured by having users have an Office 365 ProPlus license which can be run locally and on a terminal server

von steve erts - am 21.03.2017 15:20
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.