I've had my PC since Sept 2014 and really want to use Power Pivot in Excel. I have Windows 8.1 64bit running stand alone Excel 2013 32bit (purchased Sept 2014)
I have never been able to get Power Pivot to load, the Add-in appears on the ribbon but only produces the errors described below.
I have MySQL installed, Visual Studio 2010 for Office Runtime (x64), Open Office with text only enabled.
I've run the Configuration Analyzer Tool (OffCAT) which only showed a problem with Outlook which is fine ( I think! ) as I don't use it and reinstalled both Excel and the add-in.
If anyone can shed some light on or solve this problem it would be greatly appreciated. I've read somewhere (forgot to bookmark) about editing script in one of the config files as there could be an accidental 'space' in the code, if I could find where I read that maybe that would help or solve this. I see somebody posted the exact same error elsewhere a few months back but received no answer so maybe this can't be rectified.
Here are the errors I recieve:
"We couldn't get data from the Data Model. Here's the error message we got:
The type initializer for 'Microsoft.Analysis.Services.XmlaClient' threw an exception.
Configuration system failed to initialize.
Root element is missing. (C\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine\config)
Root element is missing."
When I close this error another box appears:
Sorry, PowerPivot can't openthe Data Model because there was a COM exceptionwhile opening.
You might be opening a workbook on a corrupt installation of excel. Click Details for more information.
When I click 'Details' this appears:
============================
Error Message:
============================
Object reference not set to an instance of an object.
============================
Call Stack:
============================
at Microsoft.Office.PowerPivot.ExcelAddIn.InProcServer.CannotUpgrade(GeminiWorkbook geminiWb, WorkbookConnection wbConn, String& message)
at Microsoft.Office.PowerPivot.ExcelAddIn.InProcServer.LoadSandboxAfterConnection(String errorCache)
at Microsoft.Office.PowerPivot.ExcelAddIn.InProcServer.LoadSafeSandboxAfterConnection(String errorCache)
at Microsoft.Office.PowerPivot.ExcelAddIn.InProcServer.LoadOLEDBConnection(Boolean raiseCompleteEvent, String errorCache)
============================
I received a pointer from someone called 'scottsen' over at Mr.Excel who suggested I re-installed Microsoft.Net 4 framework.
So that's what I did and now it works just fine (til I find a way to break it!).
Case solved.
Related
I have written some VBA code which works fine on my machine and sent it to someone for testing. When they attempt to run the code on their machine they get an error message stating: "Could not load some objects because they are not available on this machine."
Some research has revealed the likely issue is the fact that I am using a Date Picker object in a userform, which supposedly doesn't work on all versions of excel. However this person is running excel 2010 32 bit just like me, so I don't understand why it wouldn't work.
Is there anything I can do to ensure my code will run on any machine running excel 2010 32 bit? Or do I have to revert to using textboxes D:
thanks for your thoughts.
I have a problem to open the treeview in MS Access. I think it's since the last windows update.
I'm getting an error message when I start the program:
"There is no object in this control element. Runtime error 438: Object
does not support this property or method."
The debugger marks one line yellow in the vba code: CreateTree TreeView0.Nodes.
I didn't change anything since the last time. There it has still worked.
I did the following steps, but they all didn't help:
reinstalled MS Access
repaired MS Access
exchanged the C:\Windows\SysWOW64\MSCOMCTL.ocx, unregistered and registered it
updated VB6 to the latest version
added the database again
I hope that someone can help me!
This is a known new bug in mscomctl.ocx in many localisations - if not all, including English.
From one of the reportings:
Now they are experiencing the problem also with MSI installations of
Office 2016 which have been updated by the Windows update of Aug 1. On
these systems mscomctl.oxc seems to not have been updated as it still
showed version 6.1.98.46.
They had to disinstall the update of Aug 1
(KB4011051 -> no mention there of this issue) to get rid of the
problem.
There is at this moment no info from MS when and how it will be corrected.
This may be a better long term solution for you.
https://www.access-treeview.com/
Wish you the best
Another alternative TreeView control is here: http://www.vbforums.com/showthread.php?698563-CommonControls-(Replacement-of-the-MS-common-controls)
This is because you have 64bit version of MS Office installed. Install 32bit version and you'll see TreeView and others again.
I have added my macro to a already existing excel file with macros (build on lower version of excel). It is working fine on my system as well as other systems with same excel version. But when the excel file is opened in other versions, it either crashes or gives error messages like unexpected error occurred(32809)/ compile error. I am using Excel 2010 14.0.7143.500. Can any body tell me how to resolve this issue?
The Telemetry Log displays some simple information about the recorded events. Each record displayed in the Telemetry Log contains a title and lists the severity of the event displayed. For errors, the records also include a description of the error together with steps to address the issue. Keep in mind that not all of the records displayed represent errors caused by Office solutions; the Telemetry Log also shows when solutions and files are loaded or closed successfully.
For example, the issue titled "OM Hidden: Comment.Initial Property" appears if a solution or macro-enabled file opened in Word 2013 attempts to get the initials of a commenter who is associated with a comment. Word 2013 features an improved commenting experience that does not display commenter initials by default. The APIs associated with the older commenting model have been hidden in the Word 2013 object model but remain available for backwards-compatibility. The "OM Hidden: Comment.Initial" issue in the indicates the file that attempted to use the API, the application that raised the event (Word 2013), the time and date of the event, and short description about the error and how to fix it.
I am running Windows 8 with Office 2013 (64-Bit). I am trying to continue developments in VBA in Excel that I started with Office 2010 (32-Bit). I am aware of the necessary 64-Bit alterations however I am receiving confusing configuration errors.
Here is the problem:
If I create a new Excel file and VBA project; all my VBA code functions correctly. No problems.
If I open and use a macro from a file that was developed/used in Office 2010 previously, I receive a "File Not Found: VBA6.dll" error message.
Once I start receiving the message, I receive it on all VBA macro's; even the new ones that (not more than 30 seconds) previously worked fine.
If I then re-create a new Excel file and new VBA Project, that individual piece of new code works fine. No problems - until I run code in one of the 'error files'. The fault then spreads into my new developments.
It's as if Excel is getting its references confused but every time I check them (on good or bad files) they are always exactly the same.
Note:
None of my references are missing.
I don't have VBA6.dll on my system; I have VBA7 and the 'Visual Basic for Application' reference refers too 'C:\Windows\SysWOW64\msvbvm60.dll'
There are two other 'Visual basic for Application' references on the list but it wont let me change them
It works on new files without VBA6.dll so I assume it isn't required?
I have checked for and installed all the latest Windows updates.
What should I do to troubleshoot this problem?
If you think I need VBA6.dll, is that because the referenced libraries use it?
If so then why are they not using VBA7?
And why does it work correctly before opening an old VBA6 file? Does Excel suddenly decide all files must use VBA6 just because one file did previously?
Anything to cure me of my confusion is much appreciated,
Best regards
EDIT: I almost forgot to mention;
When I try to debug the error after receiving it, Excel crashes (every time).
I also sent a 'bad file' to a colleague who [with the same system configuration] hasn't yet received this problem - and they also received the error. Suggesting it is something wrong with the files?
EDIT 2:
The problem is not yet resolved. I hope the downvote will not hinder my chances of an answer.
I have also tried re-registering libraries but nothing has changed.
If I open a 'bad file' I can add new Macros and they work fine; but the second I run an existing Macro and receive the error, the new Macros do not work either.
The error was caused during Office 2013 (64-bit) installation. The VBA7 DLL was not registered correctly so I had to open regedit and manually input the correct filepath in both
HKEY_CLASSES_ROOT\TypeLib{000204EF-0000-0000-C000-000000000046}\
6.0\9\win32
4.2\9\win32
Replacing the 'C:\Windows\SysWOW64\msvbvm60.dll' data value (mentioned in the question) for Visual Basic for Applications to the VBA7 DLL filepath. Which on my system is:
C:\Program Files\Common Files\Microsoft Shared\VBA\VBA7.1\VBE7.dll
All files now work; I hope this solves the problem for anyone else in the future.
I recently reset my whole laptop. After the reset, I installed all of my programmes, including Visual Studio 2013 (I had 2012 on my last build). I then dumped my projects into the projects folder of 2013 and...I COULDN'T RUN MY PROJECT!!! I can view the code and the designer but I can't run it.
The error is from Application.Designer.vb and it is a "System.InvalidOperationException" error. Under additional information, it says "An error occured creating the form. See Exception.InnerException for details. The error is: Object reference not set to an instance of an object. Highlighted is Me.MainForm = Global.MyApplicationName.Form1
I have checked msdn for answers about System.InvalidOperationException but haven't found any fixes that work.
I really don't know what to do and don't want to lose my application as I've spent a fair bit of time on it.
I have 2 suggestions to try
Open Application.Designer.vb and just delete the word Global.
Exclude (not delete) the mainform (Form1, apparently) from the project. Save it. Then include it again and go to Project Properties and make it the startup form again.
I've had similar issues (without the exception) when reorganizing pieces of large solutions into other namespaces. Often, I need to drill into the designers to change a ref to get it to run and it is usually removing 'Global' and/or adding the new Namespace ref. In your case, it sounds like a similar reference in the project did not get updated from 2012.
If that is the case, the second way should get VS to write back all the files in a manner that it likes.