#1 2022-06-24 08:35:05

Johann
Member
Registered: 2022-05-30

How to access ReportServer file system

Is there a way to access the ReportServer file system from my own server file system? I am wondering where the files in the file system are actually stored and if it is possible to access and edit them from my server itself rather than having to login to ReportServer via the web.

Offline

#2 2022-06-24 08:39:57

eduardo
Administrator
Registered: 2016-11-01
Website

Re: How to access ReportServer file system

Hi Johann,

these are saved in the reportserver metadata database. You can access them via SFTP server:
https://reportserver.net/en/guides/admi … TP-Server/
https://reportserver.net/en/guides/conf … roperties/

4.11.8. Configuring the SFTP Server

Regards,
Eduardo

Offline

#3 2022-06-24 09:07:26

Johann
Member
Registered: 2022-05-30

Re: How to access ReportServer file system

Hi Eduardo,

Thanks for the quick reply. To clarify:

1. Are we supposed to generate hostkey by ourselves (e.g. using ssh-keygen) or should we leave the default value $generated there for the first time setting up the SFTP server? At the end of https://reportserver.net/en/guides/conf … roperties/, it is stated "If you do not want to start the SFTP server simply supply an invalid path or $generated..." so am a bit unsure regarding this. I have tried both ways but am getting the following error when trying to SSH using Windows MTPuTTY: https://ibb.co/Z2kMKYJ


2. I have ReportServer installed on a Linux system, but want to access it from my Windows, so would the value for the <keylocation> tag follow the Linux file path? In that case, where would the hostkey be generated (assuming I use $generate), otherwise what would be a good path to store the hostkey at? (assuming the key is manually generated)

Last edited by Johann (2022-06-24 09:09:13)

Offline

#4 2022-06-24 09:23:54

Johann
Member
Registered: 2022-05-30

Re: How to access ReportServer file system

Referencing this forum post https://forum.reportserver.net/viewtopic.php?id=715, I tried the following:

1. Use ssh-keygen to generate an ssh key pair
2. Copy the public key to a file named "hostkey.pem"
3. In reportserver /etc/misc/misc.cf, set the keylocation to "file:///C:Users/<<user>>/.ssh/hostkey.pem

After restarting reportserver, I got this error when using MTpuTTY to SSH: https://ibb.co/Z2kMKYJ

Offline

#5 2022-06-27 09:51:14

Johann
Member
Registered: 2022-05-30

Re: How to access ReportServer file system

Must the port 8022 be used? My default port for ReportServer 3.71 is 8024 instead of the 8022 mentioned in the documentation.

Offline

#6 2022-06-27 10:05:45

eduardo
Administrator
Registered: 2016-11-01
Website

Re: How to access ReportServer file system

Hi Johann,

you can configure ports as needed.

Regards,
Eduardo

Offline

#7 2022-06-27 10:49:55

Johann
Member
Registered: 2022-05-30

Re: How to access ReportServer file system

I am getting a BindException in the logs when I restart ReportServer: https://ibb.co/Hhb2G90

Is this an issue with the port? Not too sure what is going on here.

 
 |  __ \                     | |  / ____|                          |  ____|     | |                     (_)
 | |__) |___ _ __   ___  _ __| |_| (___   ___ _ ____   _____ _ __  | |__   _ __ | |_ ___ _ __ _ __  _ __ _ ___  ___
 |  _  // _ \ '_ \ / _ \| '__| __|\___ \ / _ \ '__\ \ / / _ \ '__| |  __| | '_ \| __/ _ \ '__| '_ \| '__| / __|/ _ \
 | | \ \  __/ |_) | (_) | |  | |_ ____) |  __/ |   \ V /  __/ |    | |____| | | | ||  __/ |  | |_) | |  | \__ \  __/
 |_|  \_\___| .__/ \___/|_|   \__|_____/ \___|_|    \_/ \___|_|    |______|_| |_|\__\___|_|  | .__/|_|  |_|___/\___|
            | |                                                                              | |
            |_|                                                                              |_|

Version: RS3.7.1-6048 2021-11-08-13-44-40
Code Version: 2021-11-08-11-18-29
Java Version: Oracle Corporation OpenJDK 64-Bit Server VM 25.181-b13 (1.8)
VM Args: -Djava.util.logging.config.file=/opt/tomcat/apache-tomcat-9.0.27/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses=true -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Dignore.endorsed.dirs= -Dcatalina.base=/opt/tomcat/apache-tomcat-9.0.27 -Dcatalina.home=/opt/tomcat/apache-tomcat-9.0.27 -Djava.io.tmpdir=/opt/tomcat/apache-tomcat-9.0.27/temp
rs.configdir: Not Configured

### DB Config ###
hibernate.dialect: net.datenwerke.rs.utils.hibernate.MySQL5Dialect (OK)
hibernate.connection.driver_class: com.mysql.cj.jdbc.Driver (OK)
hibernate.connection.url: jdbc:mysql://localhost:3306/reportserver (OK)
hibernate.connection.username: omc
hibernate.connection.password: **********
hibernate.default_schema:

Connection Test: OK
Schema Version: RS3.0-20

27-Jun-2022 18:46:34.955 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
27-Jun-2022 18:46:44.867 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.AdminResource
27-Jun-2022 18:46:44.867 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.AdminResource
27-Jun-2022 18:46:44.867 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.BasicRepositoryResource2
27-Jun-2022 18:46:44.868 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.BasicRepositoryResource2
27-Jun-2022 18:46:44.868 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.DataSourceResource
27-Jun-2022 18:46:44.868 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.DataSourceResource
27-Jun-2022 18:46:44.868 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.ExporterResource
27-Jun-2022 18:46:44.868 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.ExporterResource
27-Jun-2022 18:46:44.868 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.FilterRepositoryResource
27-Jun-2022 18:46:44.869 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.FilterRepositoryResource
27-Jun-2022 18:46:44.869 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.InfoResource
27-Jun-2022 18:46:44.869 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.InfoResource
27-Jun-2022 18:46:44.869 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.License
27-Jun-2022 18:46:44.869 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.License
27-Jun-2022 18:46:44.870 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.OlapDiscoverResource
27-Jun-2022 18:46:44.870 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.OlapDiscoverResource
27-Jun-2022 18:46:44.870 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.Query2Resource
27-Jun-2022 18:46:44.870 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.Query2Resource
27-Jun-2022 18:46:44.870 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.SessionResource
27-Jun-2022 18:46:44.871 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.SessionResource
27-Jun-2022 18:46:44.871 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.SaikuI18nResource
27-Jun-2022 18:46:44.871 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.SaikuI18nResource
27-Jun-2022 18:46:44.871 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.StatisticsResource
27-Jun-2022 18:46:44.871 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.StatisticsResource
27-Jun-2022 18:46:45.191 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rsenterprise.main.service.RsEnterpriseModule.configureServlets SAP Crystal libraries not present
27-Jun-2022 18:46:50.168 WARNING [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfigFailsafe Configfile scheduler/scheduler.cf could not be loaded. Default values are in effect.
27-Jun-2022 18:46:50.171 WARNING [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfigFailsafe Configfile exportfilemd/pdfexport.cf could not be loaded. Default values are in effect.
27-Jun-2022 18:46:50.173 WARNING [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfigFailsafe Configfile exportfilemd/pdfexport.cf could not be loaded. Default values are in effect.
27-Jun-2022 18:46:50.351 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.saiku.service.saiku.ThinQueryServiceImpl.<init> loaded thinqueryservice
27-Jun-2022 18:46:50.581 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.core.service.i18ntools.RemoteMessageServiceImpl.<init> Loading messages...
27-Jun-2022 18:47:02.933 INFO [https-jsse-nio-0.0.0.0-8443-exec-27] net.datenwerke.rs.core.service.i18ntools.RemoteMessageServiceImpl.<init> Available locales: de, hi, lo, pt, lt, hr, lv, hu, zh-CN, hy, uk, id, mk, mn, af, uz, ms, el, mt, en, is, it, my, es, et, eu, vi, ja, ne, ro, nl, no, be, fi, ru, bg, keys, bn, fr, jw, bs, ka, si, sk, sl, ga, gd, ca, sq, sr, kk, km, sv, ko, zh-TW, ta, cs, th, lb, tl, pl, da, tr
27-Jun-2022 18:47:22.326 INFO [Thread-163] net.datenwerke.rs.core.service.jarextension.hookers.ReportServerExtenderHooker.initialize Start loading ReportServer extensions.
27-Jun-2022 18:47:22.336 INFO [Thread-163] net.datenwerke.rs.core.service.EnvironmentAfterStartupInformation.initialize

Application Server: Apache Tomcat/9.0.27

### PAM Configuration ###
Static PAM configuration: net.datenwerke.rs.authenticator.service.pam.UserPasswordPAMAuthoritative
Finalized PAM configuration: class net.datenwerke.rs.authenticator.service.pam.UserPasswordPAMAuthoritative


27-Jun-2022 18:47:25.981 SEVERE [Thread-163] org.apache.sshd.common.util.logging.LoggingUtils.error bind(0.0.0.0/0.0.0.0:8024) - failed (BindException) to bind: Address already in use
27-Jun-2022 18:47:25.982 WARNING [Thread-163] net.datenwerke.rs.remoteaccess.service.RemoteAccessStartup$1.initialize Failed to start SFTP Server
        java.net.BindException: Address already in use
                at sun.nio.ch.Net.bind0(Native Method)
                at sun.nio.ch.Net.bind(Net.java:433)
                at sun.nio.ch.Net.bind(Net.java:425)
                at sun.nio.ch.AsynchronousServerSocketChannelImpl.bind(AsynchronousServerSocketChannelImpl.java:162)
                at org.apache.sshd.common.io.nio2.Nio2Acceptor.bind(Nio2Acceptor.java:81)
                at org.apache.sshd.common.io.nio2.Nio2Acceptor.bind(Nio2Acceptor.java:171)
                at org.apache.sshd.server.SshServer.start(SshServer.java:340)
                at net.datenwerke.rs.remoteaccess.service.sftp.SftpServiceImpl.start(SftpServiceImpl.java:163)
                at net.datenwerke.rs.remoteaccess.service.RemoteAccessStartup$1.initialize(RemoteAccessStartup.java:33)
                at net.datenwerke.gf.service.lateinit.LateInitStartup$1.run(LateInitStartup.java:62)
                at java.lang.Thread.run(Thread.java:748)
27-Jun-2022 18:47:26.897 INFO [Thread-163] net.datenwerke.rs.search.service.search.SearchServiceImpl.rebuildIndex Rebuilding search index...
27-Jun-2022 18:47:29.671 INFO [Thread-163] net.datenwerke.gf.service.lateinit.LateInitStartup$1.run Startup completed

Offline

#8 2022-06-27 15:37:11

eduardo
Administrator
Registered: 2016-11-01
Website

Re: How to access ReportServer file system

Hi Johann,

you have to select different ports for your SFTP server and your reportserver, can you pls check this ?

Regards,
Eduardo

Offline

#9 2022-06-28 01:15:18

Johann
Member
Registered: 2022-05-30

Re: How to access ReportServer file system

Hi Eduardo,

Yup. I have tried 8024 which is different from the port reportserver is on. When I run

 netstat -ap | grep 8022 

I see that the port  is open when I restart reportserver.

Regards,
Johann

Last edited by Johann (2022-06-28 01:15:38)

Offline

#10 2022-07-21 08:45:02

Johann
Member
Registered: 2022-05-30

Re: How to access ReportServer file system

This issue seems to be resolved after upgrading ReportServer to 4.2.0.

Offline

Board footer

Powered by FluxBB