Ошибка в деплое

[mak]

Подрубаюсь к GR, установленной на другой машине. Все работает отлично.
Подрубаюсь чуть позже, сразу сообщение: "Connect to Galaxy: Could not access File Repository share on GR node: HostName",
далее спрашивает пароль в GR, успешно входим и, кажись, все нормально.
Но при delpoy объекта пишет во что:




На обоих машинах OC Win2003.Пользователи одинкавые. Переустанавливали ОС, ошибка тоже оставалось. версия IAS3.0+IT10.0.

[Klinkmann_Msk]

To mak:

Сорри за английский:
1. I would try undeploying the GR Node, re-running the OS Configuration Utility on both machines, re-running change network account on both machines, rebooting, redeploying the GR Node, then trying to redeploy the platform to the other PC.

2. I once ran into a similar issue. App Server versions were the same, all OSConfig stuff was applied but it still didn't work.

It turned out that the firewall was blocking file sharing between the computers and there was also something about the Kerberos authentication that was blocking the deploy. Test if you can mount a shared folder from the GR on the client and vice versa and make sure that you use the ArchestrA network account credentials. This has to be possible for the deployment to work. Also, have a look in the Windows logs at the time of deploy. In our case there was Kerberos error messages in the application log (or was it in system?). We resolved the issue by changing the configuration of firewall and router.

3. Можно ещё воспользоваться технотой 461.

[mak]

To mak:

Сорри за английский:
1. I would try undeploying the GR Node, re-running the OS Configuration Utility on both machines, re-running change network account on both machines, rebooting, redeploying the GR Node, then trying to redeploy the platform to the other PC.

2. I once ran into a similar issue. App Server versions were the same, all OSConfig stuff was applied but it still didn't work.

It turned out that the firewall was blocking file sharing between the computers and there was also something about the Kerberos authentication that was blocking the deploy. Test if you can mount a shared folder from the GR on the client and vice versa and make sure that you use the ArchestrA network account credentials. This has to be possible for the deployment to work. Also, have a look in the Windows logs at the time of deploy. In our case there was Kerberos error messages in the application log (or was it in system?). We resolved the issue by changing the configuration of firewall and router.

3. Можно ещё воспользоваться технотой 461.

в логах нашел запись:

Отказано в доступе. (80070005) caught at line 290 in AlarmPrimitiveRuntimeImpl.h (in Z:\MagellanDev\src\AlarmHistory\AlarmPrimitive\AlarmRuntimeServer\..\..\Common\).

Вариант с Firewall подходит. На клиентской машине стоит NodeSecurity со своим Eset Personal Firewall. Попробую отключить.

Но вот есчо, сообщение: "Connect to Galaxy: Could not access File Repository share on GR node: HostName",
появлялась и тогда когда 2-ая машина подключалась к 1-ой! т.о. сообщение появлялось на той машине, которая выступала в роли клиента GR.

[Klinkmann_Msk]

To mak:

Это может быть опять-таки связано с фаерволом, который "отбивает" ICM-Ping запросы.