Is there a way to solve error of pentaho unable to open a pprt file? - mysql

I am attempting to open a .pprt file with Pentaho report designer but it keeps returning the error of unable to open the file as valid report definition. I also went far to extract the file locally (I use a Linux Ubuntu) then tried to open the different .XML files but is of no use if I can get my specific MySQL queries. I'd appreciate some help on how to attack this error.
Find the screenshot below

Related

Error while importing bacpac file to Azure SQL Database (SSISDB.catalogues is not supported in this version of SQL)

We are facing an issue when we are importing a bacpac file to azure SQL Datatbase. When we digged into the issue we have found out that the bacpac file which we are receving from past 5 days has the script which has "Execute ssisdb" related things in the model xml file of bacpac. However the older bacpac files does not have the script which has ssisdb in the model xml file. I think this is due to the fact that the bacpac which we started receiving contatins the ssis integration catalogue due to which the ssisdb script was generated. Can some one explain this error?
We have no clue on what this error means. So would be great if some one can assist on this
Error Screenshot
Previous bacpac file which does not have ssisdb in script
New Bacpac which contatins ssisdb in the script

How can I see which dataset is throwing me an error about a missing parameter?

I'm getting a Server Error when trying to view a report on a remote server - it looks as though the deploy may have failed, because it works fine on my dev environment. The error I'm getting is:
An attempt was made to set a data set parameter '#shopName' that is not defined in this data set.
However there are a large number of datasets associated with this report. How can I narrow it down to only the offending dataset; so that I can properly debug this?
The best way to see which dataset is causing the problem is to open the Report Server Service log file. This can be found at C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\LogFiles for SQL Server 2014.
Open the newest .log file in the directory, and find the error message you saw earlier.
Above it you will see the name of the dataset causing the problem:
An exception has occurred in data set 'getShopAddress'

Cannot connect to database via JDBC in Pehtaho Report Designer

So, while trying to connect to Pentaho in Pentaho Report Designer, I am getting an error which says:
Communication failure during handshake. Is there a server running on the host host_name?
using class org.gjt.mm.mysql.Driver
I have now included the jar file mentioned in the first answer and the connection says OK. But, when I preview or use a query using that connection, again I get the same error.
I am absolutely new to Pentaho. I got a few errors before which I could resolve. But, I have been stuck on this one for 2 days now. Cannot find anything regarding this.
May be Mysql connector is not there i think.
=> Before creating jdbc connection. Go to these location Eg:- C:\report-designer-3.9.1\lib and then check mysql-connector-java-5.1.26.jar file is their or not. If it's not their goto these (http://dev.mysql.com/downloads/connector/j/) location and download jar file and copy that file and paste it in C:\report-designer-3.9.1\lib location.
=> Restart Pehtaho Report Designer again and check it now.
=> May be you have lower version of mysql jar file remove old mysql jar file and paste higher version of mysql jar.
I think your problem will be solved.
Thank you..

Symfony2 Doctrine2 MS SQL Server connection on WHM/CPanel

SEE UPDATE BELOW:
I'm using Symfony2/Doctrine2 on CPanel and I need to make a connection to a MS SQL Server database. I keep getting an error saying
could not find driver
I've tried to install FreeTDS on WHM/CPanel following these instructions:
http://forums.cpanel.net/f5/definitive-freetds-installation-instuctions-88561.html
I also added an additional option to the PHP compilation (all_php5) so it looks like this:
--with-mssql=/usr/local/freetds --with-pdo-dblib=/usr/local/freetds
I then also added an entry to my php.ini file (/usr/local/lib/php.ini) that says:
extension= "mssql.so"
I rebuilt Apache/PHP after making all these changes but I still get the error saying the driver cannot be found. Anybody have this setup and know what I'm missing?
UPDATE:
So, instead of compiling FreeTDS, I found some packages through yum which I installed. I did, however, compile .so files for both mssql.so and pdo_dblib.so. They are now both referenced in my php.ini that I know is getting loaded. I can successfully use the mssql_* functions but PDO is still not working for me. I still get the the "could not find driver" error. I no longer have an all_php5 file since I don't think I need it anymore since I just compiled the .so files. Is this correct? What else can I do to get PDO working? Here is a screenshot of my phpinfo() page:

ASP Weird Unspecified Error - 80004005

I had to work on an already made website, just adding some small module
While i was updating, there was many files called myDB.mdb in the different subfolders
i wanted to make sure that my app is connecting the right database
so i started renaming subfolder...at one of those subfolders, i refreshed,the main site and mine stopped working
i renamed back to the correct name.. refresh... refresh... refresh.. i am still refreshing and i started another browser.. it is giving a connection problem :S
Provider error '80004005'
Unspecified error
/new/conn.asp, line 13
any idea about his :S
would appreciate any help !
I have had the same problem. The first time I loaded a page it worked well, but if I loaded the page again quickly, then I got this error. If I waited for a while then I didn't get the error. It must be because when you call objConnection.Close it takes some time to actually close the mdb file, so if you try and open it again you get the "File already in use type error". Strangely adding a mode to the connection sorted this problem out for me. It doesn't have to be read only, read / write works as well.
objConnection.Mode = 1 ' read only
Microsoft OLE DB Provider for ODBC
Drivers error '80004005'
[Microsoft][ODBC Microsoft Access
Driver] The Microsoft Jet database
engine cannot open the file
'(unknown)'. It is already opened
exclusively by another user, or you
need permission to view its data.
or
Microsoft OLE DB Provider for
ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access
Driver] '(unknown)' isn't a valid
path. Make sure that the path name is
spelled correctly and that you are
connected to the server on which the
file resides.
or
Microsoft OLE
DB Provider for ODBC Drivers error
'80004005' [Microsoft][ODBC Microsoft
Access 97 Driver] Couldn't use
'(unknown)'; file already in use.
From: http://tutorials.aspfaq.com/8000xxxxx-errors/80004005-errors.html
Whatever happened, it is resulting in an 80004005 error, so the problem is definitely a permission issue.
Depending on the configuration of the web server, it may not be the IUSR account that needs the access. I find it's best to fire up FileMon, filter it to the name of my database (with wildcards), and check out the properties of the error that shows up. Viewing the properties will show you the user that is actually trying to access the file.
For Access databases, you want to make sure that you're modifying the permissions of the folder and not the file. You'll need Modify permissions on the folder so that the .ldb file can be created.
Check that the IUSR account has permissions on the Access database and the folders/sub-folders containing it. I've found that on occasion if you rename or compact an access database it loses IUSR priviledges so appears in use / locked
I had the same error on Access DB :
Provider error '80004005'
Unspecified error
Reason was that one of the pages included files was not in the right format (UTF-8) but ANCI
When I changed that file to UTF-8 , everything woked right !
greeting otto
Googled in but the issue was spaces in the filename for my situation. Remove them and no problems. I hope that will help someone else.