is it in principle possible to upload and run PDI jobs in bi server?
I have tried it, but always get this error in the user console:
Sorry. We really did try. Something went wrong. Please try again or contact your administrator.
in conjunction with this log file error message:
2014/08/02 14:04:43 - RepositoriesMeta - Reading repositories XML file: FromInputStream
14:04:43,384 ERROR [GeneratorStreamingOutput] Error generating content from content generator with id [viewer]
Could some give me a hint? Thanks!
Easy answer: That does not work in the CE edition. That functionality is available only in the EE edition.
I'm not sure that's by design, so I think you should open an issue at jira.pentaho.com.
In the meantime, you can run PDI jobs in the biserver CE if you use xactions or CDA.
Related
I am trying to set up replication between databases. I followed this tutorials:
https://learn.microsoft.com/en-us/sql/relational-databases/replication/tutorial-preparing-the-server-for-replication?view=sql-server-ver15
and after:
https://learn.microsoft.com/en-us/sql/relational-databases/replication/tutorial-replicating-data-between-continuously-connected-servers?view=sql-server-ver15
I went through first without any problems. Almost completed the second, but I stuck on step View the status of snapshot generation
When I try to strat snapshot agent, I get error:
Exception Message: An unspecified error had occurred in the native SQL Server connection component.
I tried to search on the internet MSSQL_REPL55012 (that's error code I get), but didn't succeed.
I tried to look in SQL Profiler, Jobs history, Replication Monitor, even ran failing job step from PowerShell, but couldn't get any more info on that.
What might be the issue? Anybody else stumbled upon that?
I am using:
SSMS version 15.0.18206.0
SQL Server engine 15.0.2000.5
I finally got it resolved. The issue was missing OLE DB driver.
I just downloaded latest driver. Then I got msoledbsqlr.rll driver in directory C:\Windows\SysWOW64\1033. Then I copied to C:\Program Files\Microsoft SQL Server\150\COM directory, so it can be found by snapshot.exe, which is executable run by Snapshot Agent.
Alternatvely, one can define environmental variable to point to C:\Windows\SysWOW64\1033 direcotry, so it will be found there.
Another issue might be that 64-bit SQL tries to use 32-bit drivers (msoledbsql.dll, msoledbsqlr.rll), but it wasn't issue in my case.
I know this question was answered but for future reference ,updating SQL server 2019 to latest CU solved for me.
One of the team member after upgrading the ADL tools for VS to version 2.3.4000.x, getting the below error..
Error : (-1,-1) 'E_CSC_SYSTEM_INTERNAL: Internal error!
The ObjectManager found an invalid number of fixups.
This usually indicates a problem in the Formatter.'
Compile failed!
Tried to downgrade back to version ( 2.3.3000.2 ), it didn't help much.
If encountered similar issue, found the reason and resolved it, please share it.
After trying out few unsuccessful options, decided to clean up the files in USQLDataRoot including localrunmetadata and catalog folder. Still, when I submit a job to create a database, there was no error, but it didn’t create the database.
We had some powershell scripts to setup the database and other objects. Ran the powershell script, which created the database and procedures. Then we were able to run the tests successfully. One more thing to double check, make sure build platform is set to “x64”.
Am trying to create Repository in Pentaho DI by using SQl server and Mysql, in that am facing a issue,
Please some one can help me to resolve that .
Repositary login failed.
Detailed cause:org.pentaho.di.core.exception,kettleException:
Error connecting to the repositary!The version of the repository is -1.-1.
This Kettle edition requires it to be at least version 5.0 and as such an upgrade is required.
To upgrade, backup your database and export the repository to XML for additional safety.
Then select the 'Edit' button followed by the 'Create or Upgrade' button.
Please consult the Upgrade Guide for eventually special instructions for this version.
Try following steps:
Check the existence of
"\data-integration\lib\mysql-connector-java-5.1.16-bin.jar
create a new database as repository,
select button [create|update], when select Dry run, please select N.
See dialog screenshot
I am newbie in Sql Server.I am trying to attach AdventureWorks database with Sql Server 2008(Window 7).following Error -
Can anyone tell me that how I can solve this problem?
Thanks in advance.
This is the installer package (msi). You must run it from explorer firstly.
You are trying to attach AdventureWorksDB.msi. First run this msi file, it will extract its contents somewhere. Then you will need to attach a file with extension .mdf.
For a few months we're developing an olap cube on SQL 2005. We deploy this cube on the local server which worked fine until a few weeks ago.
From that moment we got got an error while delpoying the cube.
"Error 1 File system error: Error opening file; \?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\SSAS_Funda.0.db\Dim Bron.0.dim.xml is not a disk file or file is not accessible. 0 0 "
The deployment proces should create these files, but that doesn't happen.
It looks like a permission problem. I check everything but couldn't find the problem. Either on Google I wasn't able to find the answer.
Any ideas?
Cheers,
Aart
I've fixed the problem.
I decided to patch and update SQL server.
I updated SQL server 2005 to SP2 using SQLServer2005SP2-KB921896-x86-ENU.exe and after that I installed a batch of patches which are available in 344806_intl_i386_zip.exe.
Then I followed the following steps which resulted into a succesfull cube generation:
- unprocess all dimensions;
- full process all dimensions;
- unprocess the cube(s);
- process the structure of the cube(s);
- process default the cube(s).
Finally it worked. I think a previous Windows Server 2003 patch or SQL server patch caused security issues on certain users. Like the "Servicce Account" I use all the time.
to fix this in the past, I have deleted the cube from the server and redeployed. This may not be an option in your situation. I would make a backup of the cube before trying this