Biztalk Orchestration Monitor Error??

Hi!

I'm trying to monitor Biztalk Orchestrators with SCOM 2012. Some orchestrators are red and diagnostic task returns error message:

"

The process started at 13:06:58 failed to create System.PropertyBagData. Errors found in output: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 363945\37433\ApplicationArtifactProbeAction.vbs(126, 9) Microsoft VBScript runtime error: Type mismatch Command executed: "C:\Windows\system32\cscript.exe" /nologo "ApplicationArtifactProbeAction.vbs" "1 ........"

"

Error code is -2130771918

At the same time everything seems to be ok in Biztalk side.

Any thoughts?

Thanks,

August 21st, 2015 10:13am

Hi,

This may be a result of your AV-software blocking the scripts.
The first thing to do would be to exclude HealthService.exe and MonitoringHost.exe. If this doesnt work, try excluding the entire C:\Program Files\System Center Operations Manager\Agent\Health Service State directory.

Free Windows Admin Tool Kit Click here and download it now
August 28th, 2015 6:16am

Not sure which version of BizTalk you are monitoring but Bob has done some work on issues in the BizTalk 2010 management pack:

http://www.bictt.com/blogs/bictt.php/2012/04/12/scom-biztalk-2010-noise-reduction

Regards

Graham

August 28th, 2015 6:21am

AV is not issue here, thanks,
Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2015 3:26am

I have only 2 problematic orchestrators on Biztalk server and I want to understand why the problems appear.

The monitor configuration is in XML:

- <Configuration>

<IntervalSeconds>930</IntervalSeconds>

<ArtifactName>$Target/Property[Type="BTSLib!Microsoft.BizTalk.Server.2010.ApplicationArtifact"]/Name$</ArtifactName>

<ApplicationID>-1</ApplicationID>

<ArtifactType>1</ArtifactType>

<StartDateTime />

<EndDateTime />

<SuccessLimit>0</SuccessLimit>

<WarningLimit>10</WarningLimit>

<LogSuccessEvent>false</LogSuccessEvent>

<TimeoutSeconds>300</TimeoutSeconds>

</Configuration>

Can anybody explain, what it exactly does? Runs script ApplicationArtifactProbeAction.vbs? What this script does and why can error described above appear?

Thanks,

September 3rd, 2015 3:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics