# Required ActiveGate version needed for 2.0 extension

**URL:** <https://community.dynatrace.com/t/required-activegate-version-needed-for-2-0-extension/43015>\
**Category:** Extensions\
**Tags:** extensions\
**Created:** [December 4, 2023, 3:50pm UTC](https://community.dynatrace.com/t/required-activegate-version-needed-for-2-0-extension/43015 "2023-12-04T15:50:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sivart\_89](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@sivart\_89](https://community.dynatrace.com/u/sivart_89)\
**Post date:** [December 4, 2023, 3:50pm UTC](https://community.dynatrace.com/t/required-activegate-version-needed-for-2-0-extension/43015/1 "2023-12-04T15:50:45Z")

</div>

Within I believe the last week version 2.0.0 of the Microsoft SQL Server 2.0 extension was released. Upon trying out this extension in our sbx env I am seeing the error below. Are extensions really being released before the required ActiveGate version is even available? Or is there something I am missing here. The latest&nbsp;available AG version I am seeing is 1.277. Could we not wait until the requirement is satisfied before releasing the version to the public?

Failed to assign monitoring configuration to ActiveGate. Reason: The monitoring configuration requires ActiveGate version 1.279.0 or later that supports data source sqlServer and belongs to group “Extensions”

From the yaml

 ![sivart_89_0-1701704975007.png](https://global.discourse-cdn.com/dynatrace/original/2X/e/e2517495f9709be8f801a6628e2aa2668fc5073c.png)

---

<div class="post-metadata">

**Author:** ![Mike\_L](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/mike_l/32/11717_2.png) [@Mike\_L](https://community.dynatrace.com/u/Mike_L)\
**Post date:** [December 4, 2023, 4:46pm UTC](https://community.dynatrace.com/t/required-activegate-version-needed-for-2-0-extension/43015/2 "2023-12-04T16:46:36Z")

</div>

There are tenants on early versions so we sometimes have extensions before it is public. We are working on a way to block upgrades before a compatible OA/AG version is present in the environment.

---

<div class="post-metadata">

**Author:** ![sivart\_89](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@sivart\_89](https://community.dynatrace.com/u/sivart_89)\
**Post date:** [December 4, 2023, 4:53pm UTC](https://community.dynatrace.com/t/required-activegate-version-needed-for-2-0-extension/43015/3 "2023-12-04T16:53:18Z")

</div>

Thank you Mike, this makes sense. Hope to have that feature enabled but if not I’ll just make a mental note to check the yaml before upgrading to ensure we have the needed version.

---

<div class="post-metadata">

**Author:** ![jmccullough3](https://avatars.discourse-cdn.com/v4/letter/j/aeb1de/32.png) [@jmccullough3](https://community.dynatrace.com/u/jmccullough3)\
**Post date:** [July 24, 2024, 6:42pm UTC](https://community.dynatrace.com/t/required-activegate-version-needed-for-2-0-extension/43015/4 "2024-07-24T18:42:56Z")

</div>

Is there a problem running MS SQL extension v1.2.5 on ActiveGate v1.293?&nbsp; We upgraded AG and started having widespread issues with metric collection.