Tips and Tricks: Automate Open Relay Checking

We’ve been working hard non-stop for last the year to improve our customer support experience, and we have made some amazing progress.  That being said, it is so exciting to see how our customers help each other too.  The quality and quantity of user-to-user support that’s happening inside Kaseya Connections is nothing short of awesome!

With such passionate and talented users helping each other, it becomes a great resource for Kaseya admins as they solve problems, and improve their service delivery day in and day out.   Don’t worry, we’re not going to hold hands in a circle and sing Kumbyah.  Instead I’d like to highlight an solution posted to our Knowledge Exchange inside the community.

From user, jdvuyk, here is a way to automate open relay checking on exchange servers. He inlcuded some great steps in the agent procedure to check for store.exe and then another check in case port 25 isn’t open.

Thanks to jdvuyk!

2 thoughts on “Tips and Tricks: Automate Open Relay Checking

  1. the link is not working… Get a SQL error!!!

    Please fix.

    Server Error in ‘/’ Application.
    ——————————————————————————–

    Index was outside the bounds of the array.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.IndexOutOfRangeException: Index was outside the bounds of the array.

    Source Error:

    The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

    1. Add a “Debug=true” directive at the top of the file that generated the error. Example:

    or:

    2) Add the following section to the configuration file of your application:

    Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

    Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

    Stack Trace:

    [IndexOutOfRangeException: Index was outside the bounds of the array.]
    System.Collections.Generic.Dictionary`2.FindEntry(TKey key) +10377269
    System.Collections.Generic.Dictionary`2.ContainsKey(TKey key) +9
    Telligent.DynamicConfiguration.Components.ConfigurationDataBase.GetProperty(String propertyName) +379
    Telligent.DynamicConfiguration.Components.ConfigurationDataBase.GetValue(String propertyName, String defaultValue) +27
    Telligent.DynamicConfiguration.Components.ConfigurationDataBase.GetStringValue(String propertyName, String defaultValue) +20
    ASP.utility_headerfragments_core_groupnavigation_ascx.OnInit(EventArgs e) +259
    System.Web.UI.Control.InitRecursive(Control namingContainer) +143
    System.Web.UI.Control.AddedControl(Control control, Int32 index) +271
    Telligent.Common.Web.UI.Controls.ExtendedControlCollection.Add(Control child) +38
    CommunityServer.Components.ExternallyImplementedHeaderFragmentBase.AddContentControls(Control control) +102
    CommunityServer.Controls.HeaderFragmentsBase.CreateChildControls() +804
    System.Web.UI.Control.EnsureChildControls() +146
    CommunityServer.Controls.HeaderFragmentsBase.OnInit(EventArgs e) +24
    System.Web.UI.Control.InitRecursive(Control namingContainer) +143
    System.Web.UI.Control.InitRecursive(Control namingContainer) +391
    System.Web.UI.Control.InitRecursive(Control namingContainer) +391
    System.Web.UI.Control.InitRecursive(Control namingContainer) +391
    System.Web.UI.Control.InitRecursive(Control namingContainer) +391
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1477

    ——————————————————————————–
    Version Information: Microsoft .NET Framework Version:2.0.50727.4211; ASP.NET Version:2.0.50727.4209

Leave a Reply

Your email address will not be published. Required fields are marked *