SSRS 2016 - 'extension Name' is not valid - email

I am trying to set up a new subscription in SSRS 2016 and the Delivery options (E-Mail) aren't loading. Here is the error message:
Exception of type 'System.Web.HttpUnhandledException' was thrown.
The value of parameter 'extension Name' is not valid. (rsInvalidParameter)
I have the SMTP server setup in the Configuration Manager and have sent test emails with it. Is there another configuration I might have missed?

I ended up trying to add it using powershell and finally got a useful error message telling me my version of SSRS didn't support adding schedules.
Exception calling "ListSubscriptions" with "1" argument(s): "System.Web.Services.Protocols.SoapException: The feature: "Subscriptions to reports" is not supported in
this edition of Reporting Services.
I am using Web, but apparently I need the Standard version to proceed
https://learn.microsoft.com/en-us/sql/reporting-services/reporting-services-features-supported-by-the-editions-of-sql-server-2016

Related

Vertx Form Login Handler with Postgresql Failure

I am trying to authenticate user using FormLoginHandler and Postgresql Database with SqlAuthentication.
But I get the following error:
Jun 15, 2022 1:14:34 PM io.vertx.ext.web.RoutingContext
SEVERE: Unhandled exception in router
io.vertx.ext.web.handler.HttpException: Unauthorized
Caused by: io.vertx.core.impl.NoStackTraceThrowable: Invalid username/password
I am providing the right credentials.
The code snippet is:
SqlAuthenticationOptions sauthopts = new SqlAuthenticationOptions();
sauthopts.setAuthenticationQuery(AUTHENTICATE_QUERY);
SqlAuthentication authenticationProvider = SqlAuthentication.create(sqlClient, sauthopts);
router.route("/secure/*").handler(RedirectAuthHandler.create(authenticationProvider, "/login.html"));
FormLoginHandler formLoginHandler = FormLoginHandler.create(authenticationProvider);
router.route("/loginhandler").handler(formLoginHandler);
Please let me know if I am missing something here; or point me to a sample example.
Thanks in Advance.
Your setup doesn't show anything abnormal at first sight. For security reasons, we cannot "just" log the authentication data, as it would be a critical OWASP bug and security vulnerability.
My best guess is that probably is something not totally correct with the query, so this means you have now 2 options:
debug the application and see the query that is being sent + the arguments
prepare a small complete example that shows the bug and open an issue in vert.x so we can debug it further.
If you're upgrading from an older version, be aware that in vert.x 4.2.0 some changes were made to the base64 encoding to keep it consistent across modules. This could be a reason why authentication could fail as the encoded hashes may be slightly different. If you're just doing 4.3.0 from the start, then this would not be a problem.

JBPM7.XX: Error creating Task When Authentication via LDAP

I have integrated authentication jbpm with LDAP. But, When start process instance. I cannot create user task.
Here is log server, can anyone can help?
2021-05-14 17:18:39,683 ERROR [org.jbpm.services.task.wih.LocalHTWorkItemHandler] (default task-10) Fri May 14 17:18:39 ICT 2021: Error when creating task on task server for work item id 5. Error reported by task server: There are no known Business Administrators, task cannot be created according to WS-HT specification: org.jbpm.services.task.exception.CannotAddTaskException: There are no known Business Administrators, task cannot be created according to WS-HT specification
at org.jbpm.services.task.commands.UserGroupCallbackTaskCommand.doCallbackOperationForPeopleAssignments(UserGroupCallbackTaskCommand.java:298)
at org.jbpm.services.task.commands.AddTaskCommand.execute(AddTaskCommand.java:109)
at org.jbpm.services.task.commands.AddTaskCommand.execute(AddTaskCommand.java:53)
at org.jbpm.services.task.commands.TaskCommandExecutorImpl$SelfExecutionCommandService.execute(TaskCommandExecutorImpl.java:80)
at org.jbpm.services.task.commands.TaskCommandExecutorImpl$SelfExecutionCommandService.execute(TaskCommandExecutorImpl.java:65)
You need to create an "admin" group, for example
cn=admin,ou=Roles,dc=jbpm,dc=org
You may take a look at "LDAP structure" chapter and source code:
https://blog.kie.org/2021/02/migrating-jbpm-images-secured-by-ldap-to-elytron.html

Jaspersoft Studio/Server Report - Preview in Studio is Working, Server is throwing an Error when executing

I recently tried to add more Reports to our Jasper Server to distribute them to those who need them.
This worked with the first Report I uploaded, but when trying to upload new ones, on trying to execute them through the Server I get an Error message.
The following is what I've extracted from the log:
2021-03-19T12:56:31,694 ERROR AsyncJasperPrintAccessor,pool-5-thread-9:321 - Error during report execution com.jaspersoft.jasperserver.api.JSSecurityException: Ein Fehler ist aufgetreten. Wenden Sie sich an Ihren Systemadministrator. (6632)
Arguments:
at com.jaspersoft.jasperserver.api.security.validators.Validator.newSecurityException(Validator.java:544)
at com.jaspersoft.jasperserver.api.security.validators.Validator.validateSQL(Validator.java:533)
at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.createDatasource(JRTimezoneJdbcQueryExecuter.java:148)
at net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(JRFillDataset.java:1257)
at net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(JRFillDataset.java:726)
at net.sf.jasperreports.engine.fill.JRFillDatasetRun.evaluate(JRFillDatasetRun.java:249)
at net.sf.jasperreports.engine.fill.JRFillElementDataset.evaluateDatasetRun(JRFillElementDataset.java:259)
at net.sf.jasperreports.engine.fill.JRFillCrosstab.evaluate(JRFillCrosstab.java:678)
at net.sf.jasperreports.engine.fill.JRFillElementContainer.evaluate(JRFillElementContainer.java:383)
at net.sf.jasperreports.engine.fill.JRFillBand.evaluate(JRFillBand.java:548)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillSummaryNoLastFooterSamePage(JRVerticalFiller.java:1238)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillSummary(JRVerticalFiller.java:1189)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillReportEnd(JRVerticalFiller.java:297)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillReport(JRVerticalFiller.java:117)
at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:615)
at net.sf.jasperreports.engine.fill.BaseFillHandle$ReportFill.run(BaseFillHandle.java:135)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$SynchronousExecutor.execute(EngineServiceImpl.java:956)
at net.sf.jasperreports.engine.fill.BaseFillHandle.startFill(BaseFillHandle.java:181)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$AsynchronousReportFiller.fillReport(EngineServiceImpl.java:907)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:1842)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runWithDataSource(EngineServiceImpl.java:1159)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runReport(EngineServiceImpl.java:1100)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportRunnable.run(EngineServiceImpl.java:978)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
But since I am not using code to generate report I can't quite interpret the messages.
Can anybody tell me, why executing the report fails on the server, but is successful in the Jaspersoft Studio?
Both are running on the same Virtual Machine.
IT seems the developer handling this particular report started his queries with "which ..." which broke security rules set by Jaspersoft server by default, this has been changed, and reports do now properly generate when executed via the server

SharePoint Designer 2013 -> REST Service Connection -> SoapException

Hy
In SharePoint Designer 2013:
I'm adding a REST Service Connection to a REST Service hosted in my Intranet, which has Basic Authentication.
When I use this Data Connection as a DataList (for example on my SharePoint HomePage), i get the following Exception (in the Designer):
The Server returned a non-specific error when trying to get data from the data source.
When I look at the SharePoint Logs, I see the following Exception:
SOAP exception: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SharePoint.WebPartPages.DataFormWebPart.GetHierarchicalXPathNavigator(IHierarchicalDataSource ds) at Microsoft.SharePoint.WebControls.SingleDataSource.GetXPathNavigatorInternal() at Microsoft.SharePoint.WebControls.SingleDataSource.GetXPathNavigator() at Microsoft.SharePoint.SoapServer.WebPartPagesWebService.GetDataFromDataSourceControl(String dscXml, String contextUrl) 0152039d-7db3-20a8-718f-0c727b68e96b
When I open the REST URL in my Web-Browser, everything works fine.
By the way, I've already enabled the intranet-calls, so this isn't the problem:
$farm=get-spfarm
$farm.properties.disableintranetcalls=$false
$farm.properties.disableintranetcallsfromapps=$false
$farm.Update()
Thanks for your help!
Kind regards,
Peter

Crystal report 9.2, incorrect log on parameters

Background;
The Web application is developed for .Net framework 4.0. It has crystal report 9.2 integration. Application runs on Integrated Windows Authentication. The crystal reports are working fine when we execute, from solution running under Visual Studio 2010. When the same report are deployed to server (Web Server- OS: Windows Server 2003-SP2-32bit. DB Server- OS: Windows Server 2003-32bit) following error occurs, incorrect log on parameters. Crystal Report Runtime Engine for .net framework 4.0 has been installed in web server. Reports are configured to work on ODBC, System DSN with SQL Server driver. This drivers runs on SQL Server user account which has permission on database. There are no logon parameters passed from application. Just to verify, solution of passing the logon parameters from application is also tried, but the problem is not resolved.
Note: To resolve full access has been provided to IIS_WPG account on folder: C:\Windows\Temp, C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files and web application.
Server Error in '/XXXX' Application.
________________________________________
Error in File E:\WebApps\XXXX\Reports\CompanyStandard.rpt:
Unable to connect: incorrect log on parameters.
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: CrystalDecisions.CrystalReports.Engine.LogOnException: Error in File E:\WebApps\XXXX\Reports\CompanyStandard.rpt:
Unable to connect: incorrect log on parameters.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[LogOnException: Error in File E:\WebApps\XXXX\Reports\CompanyStandard.rpt:
Unable to connect: incorrect log on parameters.]
. N(String -, EngineExceptionErrorID 0) +582
. I(Int16 !, Int32 ") +277
CrystalDecisions.CrystalReports.Engine.FormatEngine.GetPage(PageRequestContext reqContext) +429
CrystalDecisions.ReportSource.LocalReportSourceBase.GetPage(PageRequestContext pageReqContext) +172
CrystalDecisions.Web.ReportAgent.|(Boolean Z) +223
CrystalDecisions.Web.CrystalReportViewer.OnPreRender(EventArgs e) +165
System.Web.UI.Control.PreRenderRecursiveInternal() +103
System.Web.UI.Control.PreRenderRecursiveInternal() +175
System.Web.UI.Control.PreRenderRecursiveInternal() +175
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2496
You need to change the profile IIS is running under to a domain account or change your web.config file to impersonate the user. Otherwise you will need to apply logoninfo for the report.