"Слет" DASMBTCP

[ToRRo2002]

В процессе работы в ArchestrA SMC "исчезает" DASMBTCP. (Был установлен DASMBTCP 1.1), Переустановка DASMBTCP 1.1, затем переустановка InTouch (9.5) и опять DASMBTCP 1.1 - результатов не приносят.
В Log после приведенных выше манипуляций:
17274 KPC-Z005 25.11.2008 10:56:32 015 0 2964 3116 mmc Warning DAServerManager
и сообщение:
CoCreateInstanceEx for DASAgent failed - System: (null), hr = 8000401A

Кто сталкивался - в чем причина?
Помогает ли установка DASMBTCP 1.5+SP2?

[dk]

Добрый день!

Недавно столкнулись с аналогичной ситуацией. Проблема заключается в том, что пароль общей учетной записи для продуктов wonderware (например эту учетную запись необходимо указать при установки InTouch) слишком короткий или вообще пустой. Необходимо поменять пароль или переназначить общую учетную запись при помощи утилиты от wonderware: Start -> Run -> aaAdminUser.

Инфо на английском:

1:
Error: "CoCreateInstanceEx for DASAgent failed - System: (NULL), HR = 8000401A is in Logger". DAServer doesn't show in SMC, the LogViewer is available however.

Cause:
The Network Account has an empty or very short password.

Resolution:
Use the "Change Network Account" utility to change the account password to be at least 8 characters long.

2:
All inter-platform communications in an ArchestrA galaxy uses the network account to communicate to each other. These accounts should never be modified or removed as it will break the system. Problems with these accounts can also slow down system response.

If the account already exists:
•Ensure that it is set to never expires
•Ensure that the user is prevented from changing the password
•Ensure that the user is a member of the local PC’s administrator group.

Run the “Change network account” utility (Start | Run | aaAdminUser). If the account is local and does not exist, select “Create Local Account”. Supply the credentials and click OK – it forces a reboot (no choice is given). In a domain environment, it is desirable to use a domain account.

Local network accounts work just as well as Domain accounts. The problem with local accounts is that it is difficult to manage. If someone changed a password of one of these local accounts, all the machines in the system will behave strangely and finding the culprit machine is sometimes difficult – one usually has to change all the machine’s network accounts separately to make sure the problem is resolved.
A domain account provides better security and a single password to manage. Remember to make the domain account a member of the local Administrators groups.

С уважением,
Дмитрий.