Kaseya Community

Home » Discussion Forums » Reporting & InfoCenter - VSA » report generation

Learn more about how AuthAnvil can protect and enhance your Kaseya experience

Similar Posts

A custom Report doesn't run

by
on Oct 30, 2020
  • Not Answered

Report: Number of computers in each machine group

by
on Jun 3, 2011

General Purpose SQL Queries - Post them here!

by
on Jan 26, 2011

Executive Reports and Drive Scores

by
on Feb 1, 2012
  • Not Answered

German report templates needed!!

by
on Feb 21, 2011
  • Suggested Answer
Details
  • 4 Replies
  • 3 Subscribers
  • Postedover 9 years ago

report generation

  • lightnindjo
    Posted by
    on Nov 4, 2011 3:51 PM

    hi, 

    everytime i am running a report. i kaseya send me back this error : 

    System.Web.Services.Protocols.SoapException: The operation you are attempting requires a secure connection (HTTPS). ---> Microsoft.ReportingServices.Diagnostics.Utilities.SecureConnectionRequiredException: The operation you are attempting requires a secure connection (HTTPS). at Microsoft.ReportingServices.WebServer.ReportExecution2005Impl.SetExecutionCredentials(DataSourceCredentials[] Credentials, ExecutionInfo2& executionInfo) at Microsoft.ReportingServices.WebServer.ReportExecutionService.SetExecutionCredentials(DataSourceCredentials[] Credentials, ExecutionInfo& executionInfo)
    Thank you for your help.
  • lightnindjo
    Posted by
    on Nov 9, 2011 9:12 AM

    up! Is it someone who know how to fix this error?
  • Chad Gniffke
    Posted by
    on Nov 9, 2011 5:14 PM

    Lightnindjo,  if you haven't already, I would put a ticket in with support.
  • zippo
    Posted by
    on Nov 9, 2011 5:34 PM

    And, you might want to follow the instructions in this SQL Reporting Services Setup Guide:

    community.kaseya.com/.../63709.aspx
  • lightnindjo
    Posted by
    on Nov 18, 2011 10:45 AM

    Hi, I've finally solve that problem.

    I have modified the SQL Reporting services xml configuration file : rsreportserver

     <Add Key="SecureConnectionLevel" Value="2" />

    I put a 0 in this value. Now this SQL reporting don't require a secure concection (https) to generation a repport.