I have a file that someone else send to me. He is able to open the Power Pivot model on his computer, but the same file fails to open on my computer. I also tried on other computers, and it is not working.
I am able to open other Power Pivot file, but not this one.
We are using the same version of Excel (2010) and Power Pivot (SQL 2012 SP2).
I always get this error:
Has anyone any recommendation?
This might be a issue of vertipaq, did you have access engine install or vertipaq, if access engine try to uninstall it and install vertipaq, disable and enable the power pivot addin and try once.
Related
Whenever I try to make a database connection in transaction Pentaho, be it oracle or postgreSQL, although everything is correct in the last part, the test button does not show anything instead of saying the connection is complete. The necessary JDBC files are installed, can you help me?
enter image description here
I tried all the JDBC files, and I even prepared the file path for JDBCs, but nothing changed.
The test button doesn't work because you should download pentaho from https://www.hitachivantara.com/en-us/products/dataops-software/data-integration-analytics/pentaho-community-edition.html. Don't downloaded it from sourceforge, if you downloaded from here try the 8.3 version.
Tip:If the marketplace doesn't appear install pentaho 8.3 version.
We just started noticing this. It used to work, and now it doesn't. The crash happens on all of our computers. We right click on a database, select Script Database..., choose to script the entire database and SSMS crashes. No information in the Event Logs. We've found that if we script all tables, it works. If we also script all stored procedures and functions, it crashes. All of our databases are in Azure. Haven't tried local DBs. Any ideas how to troubleshoot?
Thank you,
Mike
It might be a bit late to answer but it might help someone;
I had the same issue recently, upgraded to the latest version 18.12.1 and it now works fine;
Check Download SSMS 18.12.1
Click on "Free Download for SQL Server Management Studio (SSMS) 18.12.1"
and run the installed file "SSMS-Setup-ENU.exe" as an administrator and follow the wizard.
I am trying to use pentaho which I downloaded from sourceforge (pentaho files). I run the schema-workbench shell correctly and a window opens with the interface, but I still haven't been able to connect to the admin console on http://localhost:8080/pentaho.
Any ideas on which this doesn't seem to work for me?
Best regards
You have a start-pentaho.sh which launches (after a long the first time) the pentaho server on port 8080.
That is, if you have downloaded the correct package, because Pentaho contains many packages: one is the server, another one is the client-tools which contains the schema-workbench as well as the pdi (Pentaho Data Integrator), and the prd (Pentaho Report Designer) as well as few others.
You are running the wrong file. To open the pentaho console, you need to download the PNTAHO SERVER and run 'start-pentaho.sh'
Pentaho by default will start PuC Pentaho USer Console on http://localhost:8080/pentaho once server is up and running. For getting the data integration i.e Spoon interface go to
For Windows : Pentaho install directory>> design-tools>> data-integration>>spoon.bat
For Linux/Mac:Pentaho install directory>> design-tools>> data-integration>>spoon.sh
I hope this helps.
We have a task where we need to automatically convert an excel file to a csv to prep it for loading into a SQL database. The developers built this process into a SSIS package. For the conversion, they initially tried to have a task in the SSIS package execute a VBscript to convert the file. When they were running this on there local machines, this worked correctly. When they ran the package manually through VS on the server, it ran correctly. When they ran the package manually via the Integration Catalog it ran correctly. We did this both as our accounts and as the service account and got the same results. However, when we scheduled it as a job it would hang on the part of the process that executed the VBScript. No errors, it would just hang until you killed the job.
The job was executing as the service account which has full admin access on the server, explicit full access to the share where the files are stored and converted (which is on the same server) and full admin access to SQL. The job owner is set to sa which uses the service account. And all the job does is execute the package from the integration catalog which works if you run it independently of a job. When we compared the ssisdb execution report for the manual run in the integration catalog using the service account to the job run they looked the same except the job hung on the conversion task and the other did not.
After spending some time trying to figure this out, the developers tried a different solution. They changed the conversion script from using VBScript to using C#. They ran the package from there local machine and once again the package worked. This time when they ran it manually on the server it failed. When we ran it from the integration catalog it failed and when we ran it from a job it failed.
The error we keep getting is "Create CSV file: Error: Exception has been thrown by the target of an invocation" After spending several hours looking into this error nothing suggested seems to be working.
We also tried these same solutions on a newly built server to make sure we weren't dealing with an odd configuration setting that could have been changed (It is a Dev server) and it still failed there.
At this point, we are pretty lost at what is happening. The first solution worked, but for some reason would never work as a job. The 2nd solution works everywhere except when ran on the server.
We are looking at some other solutions to try to get around this. The next thing may be trying to using powershell to convert the file, but not sure if that will bring us back to the same issue. Any suggestion you guys have will be greatly appreciated
Also, we are using SQL Server 2012 dev edition, VS 2012 pro, Windows Server 2012 R2
This might be because of a bug that Excel has when trying to run jobs (that use Excel) and no user is logged on a specific machine. This might affect also the excel library. The solution is to create the following 2 folders:
C:\Windows\SysWOW64\config\systemprofile\Desktop
C:\Windows\System32\config\systemprofile\Desktop
and then restart the machine. :)
(Edited to show that a restart is needed. thanks for Dustin for checking this)
I have two scheduled tasks on my computer. They both open Excel files and run a macro & are pretty similar in what they do. They both work on my computer. However I moved the scheduled tasks onto a colleague's computer. One worked the other didn't.
The one that didn't work opened Excel but had an error saying:
"programmatic access to visual basic project is not trusted".
Like I say, both Excel files are very similar. The one that didn't work does reference two additional projects the other one does not. They are,
Microsoft Visual Basic for Applications Extensibility 5.3
Microsoft Windows Common Controls-2.6.0 (SP6)
I have never come across this error before.
File -> Options -> Trust Center -> Trust Center Setttings -> Macro Settings -> Trust Access to the VBA Project object model.
This is usually needed if you are referencing Extensibility library.
Mac Version - In the past there was no setting for this on the Mac version. You did get always a dialog saying the thing.
But now, at least with version 16.30, not sure how long ago, the Mac Users have the same setting available.
BTW, it is under security, not under trust.
HTH
Its very easy to do this in Python using the pywin32 module by Mark Hammond.
What the above post by #user2140173 does actually is to change some registry values. This can be programmatically accomplished by the pywin32 module as follows:
import win32api
import win32con
key = win32api.RegOpenKeyEx(win32con.HKEY_CURRENT_USER,
"Software\\Microsoft\\Office\\16.0\\Excel"
+ "\\Security", 0, win32con.KEY_ALL_ACCESS)
win32api.RegSetValueEx(key, "AccessVBOM", 0, win32con.REG_DWORD, 1)
Ref:
http://docs.activestate.com/activepython/2.4/pywin32/win32api__RegSetValueEx_meth.html
http://docs.activestate.com/activepython/2.4/pywin32/win32api__RegOpenKeyEx_meth.html