Problem policy ADSPI-DNS_LogDNSPagesSec (995 Views)
Reply
Frequent Advisor
Marat Zalotdinov
Posts: 61
Registered: ‎04-07-2011
Message 1 of 13 (995 Views)
Accepted Solution

Problem policy ADSPI-DNS_LogDNSPagesSec

Hello!

OMW v9.0.

I have upgrade Windows 2008 r2 from version 8.6 to 11.0 and now have some problems.

In node gote error everytime: No opcmon value received and reached max waiting intervals
for policy ADSPI-DNS_LogDNSPagesSec_2K8+. Kill the external program and do a restart. (OpC30-3404)

Thanks.

Honored Contributor
Ram_21
Posts: 3,655
Registered: ‎04-30-2003
Message 2 of 13 (986 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

Hello

 

This is a known defect with the way the agent handles the vbscript being called within the policy's two conditions. From what I understand the agent lab is working on addressing this issue and there is no workaround/solution at this time.

 

Hope this helps.
Regards
Ram

Frequent Advisor
Marat Zalotdinov
Posts: 61
Registered: ‎04-07-2011
Message 3 of 13 (975 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

Thanks.

It's true.

 The response from suuport HP:

"I am glad to inform you that the issue you are seeing is a defect on the Operations Agent (not on the ADSPI) which had already reported to us by a couple of other customers. Our Agent Lab is working on addressing it. I will contact the developer engineer in charge of this case to check what the investigation status is and I will let you know."

Honored Contributor
KAKA_2
Posts: 1,444
Registered: ‎05-26-2007
Message 4 of 13 (970 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

Hello,

 

Send me a PM and i will give you the modified script which fix the problem. 

 

Thank You.

-KAKA-

Frequent Advisor
Marat Zalotdinov
Posts: 61
Registered: ‎04-07-2011
Message 5 of 13 (960 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

my e-mail:
marat.zalotdinov@icl.kazan.ru

Thaks a lot!
Honored Contributor
KAKA_2
Posts: 1,444
Registered: ‎05-26-2007
Message 6 of 13 (955 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

I have no access to personal emails so check your forum Inbox.
Member
amberite
Posts: 3
Registered: ‎12-15-2010
Message 7 of 13 (926 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

I have the same issue, could I have a copy of the amended script please.

gareth.foy@royallondongroup.co.uk

Honored Contributor
KAKA_2
Posts: 1,444
Registered: ‎05-26-2007
Message 8 of 13 (924 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

i am waiting for results from marat and Maf. once they confirm i will pass it to you as well.

Thank You.
-KAKA-
Frequent Advisor
Marat Zalotdinov
Posts: 61
Registered: ‎04-07-2011
Message 9 of 13 (921 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

ok.

Honored Contributor
KAKA_2
Posts: 1,444
Registered: ‎05-26-2007
Message 10 of 13 (917 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

Marat- ok means it woked?? Or yet to be test and confirm?
Honored Contributor
Ram_21
Posts: 3,655
Registered: ‎04-30-2003
Message 11 of 13 (913 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

Hello

 

Just a suggestion - make sure that the updated vbscript that is being discussed in this thread has a different name and you call that script in the ADSPI policy. This way you won't run into any problem if HP releases a newer version of the script and it just simply overwrites what you have used.

 

Regards
Ram

Honored Contributor
KAKA_2
Posts: 1,444
Registered: ‎05-26-2007
Message 12 of 13 (911 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

RAM- Thanks for Suggestion. I logged Case a Year before and Case was closed with the Solution that Support Not able to reproduce the issue in House.

You See Many Users are having the same issue then why cant Support See ?

Anyway if hp Release a bug Free Script then it does Not matter if it overwrite the Script or Not, but yes it matters if hp dont Rectify the Problem and Release it.

-KAKA-
Valued Contributor
maf
Posts: 110
Registered: ‎11-11-2010
Message 13 of 13 (884 Views)

Re: Problem policy ADSPI-DNS_LogDNSPagesSec

Small update. I have got a hotfix from HP Support to address this issue. And a correction - the problem is in AD SPI and not the agent.  The problem is that this policy shares a script with another policy, and that script has a bug in calling command line opcmon.

 

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.