Exchange 2013 CAS Template Error

I’m trying to set up a new Application Service using the exchange template f5.microsoft_exchange_2010_2013_cas.v1.2.0 and i’m running to the following error. Currently running 11.1.0 Build 2481.0 Hotfix HF10.

Error parsing template:can’t eval proc: “script::run” 01020036:3: The requested unknown (avr) was not found. while executing “tmsh::get_config sys provision $args” (procedure “iapp_get_provisioned” line 32) invoked from within “iapp_get_provisioned avr” invoked from within “tmsh::run_proc f5.iapp.1.1.0.cli:iapp_get_provisioned avr” (procedure “script::run” line 1) invoked from within “script::run” line:1

Oscar, just a thought as I’ve not seen this before. In the iApp template have you enabled Analytics? If so does the iApp work if you don’t select it?

Do you have AVR provisioned on the box?

N

Try toggling the AVR enabled state under System/Provisioning. i.e. if it is enabled, disable it and vice versa.

If that does not do it, and you cannot wait until support gives you a solution, do the following:

Go under iApps/Templates, click on the template to edit it. Then in the Implementation section use Ctrl-F to find: iapp_get_provisioned avr

Comment that line out and add another under it like this:

set avr_provisioned [iapp_get_provisioned avr]
set avr_provisioned 0   

 Or

set avr_provisioned 1

set it to 0 or 1 depending on whether or not you want the AVR configuration added to your exchange.

Thx for the response. I receive the error as soon as I select the template from the dropdown list on the Template Selection screen. It never loads a form like it does when I select f5.http for example. And I don’t believe I have AVR enabled as it’s a test system with a basic config.

I tried 0 then 1 but no change, same error message. I will try modifying the template outside of the f5 and importing it with a different name.

No luck modifying the template..

Under Presentation, try taking out these two lines:

choice analytics_provisioned tcl { expr { [tmsh::run_proc \
        f5.iapp.1.1.0.cli:iapp_get_provisioned avr] ? "yes":"no" }}

See below.

I received additional errors (undefined references to analytics) after removing those two lines. I had to go through and remove all sections referencing analytics for the template to save without errors and now when creating the App Service it chokes at apm… It feels like I’m missing something else. Error parsing template:can’t eval proc: “script::run” 01020036:3: The requested unknown (apm) was not found. while executing “tmsh::get_config sys provision $args” (procedure “iapp_get_provisioned” line 32) invoked from within “iapp_get_provisioned apm” invoked from within “tmsh::run_proc f5.iapp.1.1.0.cli:iapp_get_provisioned apm” (procedure “script::run” line 1) invoked from within “script::run” line:1

Hi Oscar, I apologize for the difficulties you’re having with the iApp template. The error you’re seeing is actually caused by tmsh commands in a shared library (f5.iapp.1.1.0), so editing the iApp template itself will probably not help.

There may be an error in the support matrix for this template (it may not be supported for versions of BIG-IP earlier than v11.2, for example). We will discuss this with the iApp development team and provide you with a recommended course of action.

thanks

Mike

Thanks Mike. If there’s a way to import that library it would be a great short-term solution.

Hi again Oscar,

I was unable to repro this error on a v11.1.0 HF10 BIG-IP. Would you be able to post the sanitized contents of your bigip_script.conf file here, using the preformatted code option to make it more readable?

Also, I’m not sure which hardware platform you’re on, but if possible we recommend upgrading to at least BIG-IP v11.2.1. There was an issue with versions 11.0 and 11.1 that causes problems with monitors that were created by an iApp: 404 Page not found | BIG-IP Documentation

Mike

Is there a solution for this problem? We have a BIG-IP with the latest supported version 11.1.0 Build 2481.0 Hotfix HF10. It’s not possible to install 11.2.1.

AFAIK, the only solution is to upgrade. You can create a regular LTM monitor per the SOL3813 as a workaround.