www.InTouch.su

Всем доброго дня!
При попытке запуска Windowviewer выскакивает ошибка wwextalm "Are you running the right InTouch application"? InTouch 8 версии, Windows xp2.
[/img]

В логгере ошибки ссылаются на компонент "AlarmBuf"

xonyx писал(а):В логгере ошибки ссылаются на компонент "AlarmBuf"

Нужны точные логи.

Вот:

xonyx писал(а):Вот:

Много букв:
1. Cause Description: The CMethodDispatcher error occurs when an attempt is made to update an InTouch windows control or distributed alarm object if the window containing the object is not open or if there are multiple (wizard) objects with the same name.
--------------------------------------------------------------------------------
Resolution Summary: Correct the duplicate DAO names by changing one of the names. Each DAO in your application must have the a unique name.

2. "wzalmobj CMethodDispatcher::Method <SomeTag>/AddItem Unknown Object Name"

The message points to the alarm engine trying to address an Alarm Object in InTouch. The key part of the message is "Unknown Object Name."

This message commonly occurs under the following circumstances:

1) The alarm object name does not match the object name listed in the Alarm Query or Alarm Functions.
2) The window containing the Alarm Object is not open or loaded into memory when the Alarm Query or any alarm functions are called, especially in an Asynchronous Quick Function, when the time that it will run or the run timing between script precedence is indeterminate. The alarm queries and functions should always be called after the alarm display window has been completely opened.

Reference the correct windows control or distributed alarm object and make sure that the object is in memory.
For each window containing InTouch windows control or distributed alarm object(s), set a "flag" tag to 1 in the window "On Show" script, and reset the tag to 0 in the window "On Hide" script. Modify your scripts that are associated with these objects, adding IF . . . THEN logic to reference the windows control or distributed alarm object(s) only when the associated "flag" is set. You should also make sure that each of the objects are uniquely named.

3. Be sure that the object reference (Name) is correct if the script function is addressing a Windows Control. It is possible that object functions are being used in a script on an object that is not being displayed, loaded in memory, or does not exist.

The easiest way to troubleshoot this condition is to comment out various parts of the scripting that was added just prior to the Exception being thrown, until the offending function can be isolated. Occasionally, slightly delaying running the script with the function addressing the object in question will alleviate the issue, because the window displaying the object may not be fully loaded before the script was run.

Additionally, unchecking "Always Load Windows from Disk" may alleviate the problem if there is sufficient RAM available to store all the application windows, in addition to having sufficient amounts available for machine needs. By storing previously opened windows in memory, the calling function should therefore have access to the object on the window if the window was previously opened.

4. Make sure that the ControlName is spelled exactly the same as the object with the same case, and that the word Enabled is spelled with a capitol E.

5. Cause Description: Trying to control or request data from an Object but there is a syntax error in the dot field. Example: Incorrect: GetPropertyI(ALBOBJ_1.NumAlarm, IntTag); (singular Alarm) Correct: GetPropertyI(ALBOBJ_1.NumAlarms, IntTag);
--------------------------------------------------------------------------------
Resolution Summary: Verify that the syntax of the value passed is correct and that the correct function is called.
--------------------------------------------------------------------------------
Resolution Description: Verify: 1) the syntax of the value passed is correct. 2) the correct function is called. Use GetPropertyI() for Integers, D for Discretes, M for Messages. 3) the correct spelling of the dot field is used.

6. Buttons go behind animated object in runtime if WC Radio buttons are touching the animated object reviewed and closed. The only solution available is to avoid placing Windows Control(s) on top of other objects.

Всё эт хорошо, только вот ошибка появляется, даже если пустой проект без тегов и окон запустить в RT...

xonyx писал(а):Всё эт хорошо, только вот ошибка появляется, даже если пустой проект без тегов и окон запустить в RT...

Можно попробовать:
Resolution Summary: Remove the files wwextalm.dll and wwextalm.wdf files from the InTouch directory. (на флешку их). Но меня терзают смутные сомнения, что слетела регистрация каких то библиотек. Скорее всего дело пахнет переинсталляцией ПО вместе с ОС.

Нашёл вот что ещё:
On restore of the PC to an earlier date two files were &quot;missed&quot; on the recovery. These files had the same name as the DLL file but different extensions (.wdf and .wdo). The dll was on the HDD but the other two files were not. Речь о wzalmobj.dll

Klinkmann_Msk писал(а):

xonyx писал(а):Всё эт хорошо, только вот ошибка появляется, даже если пустой проект без тегов и окон запустить в RT...

Можно попробовать:
Resolution Summary: Remove the files wwextalm.dll and wwextalm.wdf files from the InTouch directory. (на флешку их). Но меня терзают смутные сомнения, что слетела регистрация каких то библиотек. Скорее всего дело пахнет переинсталляцией ПО вместе с ОС.

Нашёл вот что ещё:
On restore of the PC to an earlier date two files were &quot;missed&quot; on the recovery. These files had the same name as the DLL file but different extensions (.wdf and .wdo). The dll was on the HDD but the other two files were not. Речь о wzalmobj.dll

Дело пахнет переустановкой ОС ))

xonyx писал(а):

Klinkmann_Msk писал(а):

xonyx писал(а):Всё эт хорошо, только вот ошибка появляется, даже если пустой проект без тегов и окон запустить в RT...

Можно попробовать:
Resolution Summary: Remove the files wwextalm.dll and wwextalm.wdf files from the InTouch directory. (на флешку их). Но меня терзают смутные сомнения, что слетела регистрация каких то библиотек. Скорее всего дело пахнет переинсталляцией ПО вместе с ОС.

Нашёл вот что ещё:
On restore of the PC to an earlier date two files were &quot;missed&quot; on the recovery. These files had the same name as the DLL file but different extensions (.wdf and .wdo). The dll was on the HDD but the other two files were not. Речь о wzalmobj.dll

Дело пахнет переустановкой ОС ))

Ан нет. Удалил wwextalm.dll и все поехало!
Спасибо огромное.
Уважаемый Klinkmann_Msk, где почитать про эту библиотеку, для чего она?

всё, нашел, спасибо.