Excel 2007 ignores the roles configured on SSAS 2008

Hi,
I am facing a common problem for which I have found very useful threads but they didn't manage to help me.
My problem is on excel report, Dimension data is not filtering correctly when I connect with user credentials for which a role is configured on the cube. Excel 2007 ignores the roles configured on SSAS 2008 and I tested with 2 different users with the same
role configuration.
I ensured that the user doesn't fall in the server admin role and . I started up an SQL Profiler and I ensured no * in the list of roles of the user. I ensured also that there is no "built-in administrators group" configured (Security\BuiltinAdminsAreServerAdmin).
http://social.technet.microsoft.com/Forums/sqlserver/en-US/7052f751-8478-4ab2-aba8-d250a1606e07/deny-access-to-analysis-services-cube-from-excel-2007
Also I am planning to upgrade my Service Pack 1 to the cumulative pack Hot Fix 2710 ( KB969099 ) as it seems there are some known issues about dimension security on SSAS 2008. Do you really think it is a question of upgrade?
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4b4e6e3c-bebe-4f81-8462-b2d0bd61ad11/dimension-attribute-security-on-ssas-2008-not-working-but-works-fine-on-2005
However I managed to work around the issue on SSAS and on Excel as follow but it is the not the solution expected:
- On SSAS 2008 R2 cube browser, while testing using the role: Dimension values filtered correctly the required data
- On Excel: Unless the role is specified in the configuration of the connection then the data is not filtered.
http://kevin_s_goff.typepad.com/kevin_s_goff_weblog/2009/12/1242009---testing-ssas-roles-in-excel.html
It is really urgent,
Many thanks

Hello,
I'm experiencing exactly the same issue and I can't find any solution to it.
Were you able to solve it? If so, how did you do it?
Thanks!!!

Similar Messages

Import file from Excel and ignoring the headers

Hi all,
is it possible to import files(spreadsheets) from Excel and ignoring the first row that contains the headers? Since headers might contain special characters such as "\n", "&" and "/", i wonder if you can tell me how to load .xlsx files while ignoring the first line that contains description regarding the header.
Thanks

Put a filter on one of the fields on the source data store in your interface. It is likely that your header row will have some unique identifying attribute so filter on that e.g. if you are importing nmeric amount data it is unlikely that your header line contains a numeric value in the amount field but a decription such as "amount", put a filter testing if the value of that field is numeric or not

Bring Excel 2007 to the front when called from LabView v9 in Windows 7

I am building a duplicate system using Windows 7, LabView v9 and Excel v2007. The original system used WinXP, Excel 2007 and LabView v8.6. The issue is that the original system was able to bring Excel to the front when called from Labview using the property node -application-> visible. This new configuration runs Excel, loads the data, runs the macros but does not bring Excel to the front. The icon blinks in the Win7 taskbar and when selected displays over LabView. If I minimize the Labview window, Excel is there. This leads me to conclude that Excel is visible, as requested but will not come to the front until selected from the taskbar. The only differences, besides the versions, is the original system template files used the .xls extension in and was run in Excel in compatible mode. At the customers request, the new system uses the .xlsm extension on the Excel template files. I have tried using application.visible = True in the macro as well. Could be a setting in Labview? Could be a setting in Excel? Could be .xls vs. .xlsm? Or an issue with Windows 7 and the newer version of Labview.
HP workstation - Labview v9 - Windows 7 - Excel 2007 sp2
Thank you in advance
Stephen
Solved!
Go to Solution.

I will try the windowstate change. Were these done in succession? (i.e. property node -> property node -> property node) Or were they done along the way such as call the ActiveX open and a property node then in a worksheet modification area etc. so there was some time between calls?
I am not sure about the API since the discussion there is with regard to DDE. (Taken from the link document: If you want to call a DLL that contains ActiveX
objects, use the Automation
Open VI with the Property
Node and the Invoke
Node.). I am calling Excel as an application not as a library call unless I am mistaken, which I could certainly be. Are you thinking that once Excel is active through the Automation Open VI that a DLL call to set the application visible would work? I may be trying this already but in Excel through the use of the macro I call from LabView. It contains application.visible = True at the beginning before reading files and plotting data.
I may try sprinkling Property node with application->visible in various locations in the LabView diagram as I do update cells after the call to the plot macro. The puzzle for me is the blinking Excel icon in the task bar. This means active and running but not visible or something wrong as well. There are a few #VALUE cells if not all test in the system are run. Again not a problem in Excel 2007-WinXP-LV8.6
Thank you again one and all.

MS Excel cannot read the Roles definition on Analysis Service cube

Hello,
While using Analysis Service connection via Excel, apparently it does not automatically provide Roles or EffectiveUserName in the connection string based on username/password we provide. We must manually edit the connection string.
Does this thing already defined as bugs, or there is other explanation ? Is there any related with this ?
Thanks.

Hi Prayijana,
In your scenario, you said that you need to manually edit the connection string for different users to connect to SQL Server Analsysi Services Multidimensional database, right?
When using excel to interact with a SSAS cube, we can use the default settings "Use the authenticated user's account". In this case, excel will use the current account to connect SSAS cube. If the account has a matched role on the databse,
then he can access to the cube.
If this is not what you, please provide us more informantion, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Enable Excel 2007 format export on Crystal Reports Server 2008 - Sharepoint

I'm trying to use Sharepoint's excel services to post some charts from an exported Crystal report to sharepoint. However Crystal Reports Server 2008 only exports excel 97-2003 format. How can I update the Crystal Reports Server 2008 components to support Excel 2007 format. Has anyone done this before?
Thanks,
Dominic

Unfortunately what you are looking for is not possible (At least as far as I know). Crystal is limited to the formats that it already has - and it is not possible to add additional export formats.
Sorry
Shawn

Excel 2007 accessing PivotItem.Visible gives error if the field item value is a DATE

I have VBA code to manipulate the content of a pivot table - essentially it hides all but the first N items in a pivotfield. Under Excel 2003 the code works fine, as expected irrespective of the data content of the pivot field item. Under Excel
2007, if the data content is a date, the VBA code generates one of several error conditions.
pivotItems(i).Visible = True
Generates error 1004 - Unable to set the visible property of the pivot class
If pivotItems(i).Visible = True then...
Trying to test the visibility generates error 13 - type mismatch
?pivotItems(i).Visible
Trying to determine the visibility of the pivot item in the VBA immediate window, this generates error 2042
I have an illustrative spreadsheet which permits the code to process two different pivot tables, one using a field containg dates; the other a field containing text. Under Excel 2003, the code works on both pivot tables. Under Excel 2007 it works
on the text field table, but fails on the date field table.
I have looked for answers on numerous support forums including answers.microsoft but found not found any answers... only the same or similar unanswered question.

Hi Herbert,
Thank you for your continued interest; please find a revised illustration of the problem here -
http://www.mediafire.com/download.php?zc6ty9ctl1n7yd9
I have made the following changes / additions to the problem illustrator:-
Adopted the use of lists for the data source of the pivot table
Removed reference to '(blank)' as a reserved item not hidden by the VBA code to avoid the possibility of hiding all items
In respect of my original code (MK1), utilised a 'real' item name to be the
reserved item
Added a new (MK2) macro to alter the number of visible items which
hides all but one of the VisibleItems collection
makes the first N items in the collection visible
checks that there are only N items visible (the position of the reserved item
might be greater than N)
The code still executes as expected under 2003, but fails (the same as before) under 2007 when the data type of the PivotItem is date.
The MK1 code fails when testing the current visibility of the Item before trying to set the visibility with:- RTE 1004 Unable to
get the PivotItems property of the PivotField Class
The MK2 code fails when trying to set the visibility with:- RTE 1004 Unable to
set the Visible property of the PivotItem Class as reported above. Note - given that MK2 avoids trying hide invisible items or unhide visible items, I no longer believe that this error is due to the attempt
to set visibility to current state as seen under Excel 2003. I am deeply confused by this now!
I observe with care the different CLASSES on which these failures are reported even though in each case the operations are on the PivotItem.Visible property - MK1 queries it / MK2 attempts to alter it.
Just in case you have been wondering where this is going, this spreadsheet has no prupose beyond illustrating the Excel 2003 / 2007 problem being encountered elsewhere when manipulating pivot table items whose value are dates. The requirement
is to provide a simple user interface to a complex managing reporting spreadsheet consisting of a significant number of pivot tables and charts - altering one cell causes the VBA code to modify the collection of pivot tables to deliver a revised view of the
data. All works fine for 2003 users of the model, but not 2007 users. I need one spreadsheet which will work correctly on both 2003 & 2007.
Regards.

Excel-2007 cannot connect to Oracle ODBC data source, Control Panel can.


I cannot make an ODBC connection from Exce-2007 to Oracle work. I am an expert Excel and VBA user (since 1994) and I have frequently used Excel to access ODBC databases, including Oracle (I have done this with Excel-2003 both with worksheet queries and have written VBA ADO-connection routines). And even though in Excel-2007 a worksheet ODBC query is supposed to be easier to create than in previous version of Excel, my connection fails. Any suggestions and all help are welcome and much appreciated.
DETAILS


1) What is my system? I am using Excel-2007 on Windows Vista x64 and Oracle server v.11g on my computer (all this is on my computer, no network issues).
2) Why use Excel with Oracle at all? I use Excel-2007 to access Oracle rather than Access-2007 (or any other application like TOAD, etc.) because I do engineering calculations with the data stored in Oracle. These calculations are easier done in Excel (I suppose that one alternative to this could be to use some sql or Access to get the data from the database, then store it as plain vanilla CSV file, then open this file in Excel, then do the math (the math involves complex optimisation algorithms), then save the results as CSV, then use some sql or Access to put the data back into the database. Howwever this does not strike me as a quick or neat solution. And after all Excel has been designed to access ODBC databases, so why not use it?)
3) What do I do in Excel-2007 that won't work? I create an ODBC link to Oracle that does not work. In Excel-2007 this is straightforward:

<ul>
<li>define an ODBC connection (Data tab --> From other sources --> From data connection wizard);</li>
<li>define a query on the worksheet -- that's it, this is all!</li>
</ul>

I start with creating an ODBC connection:
a) I choose an ODBC data source type: ODBC DSN
b) Excel-2007 displays the list of the available ODBC data sources. I see in it my Oracle database name and I select it.
c) Excel-2007 displays the Data Link Properties:
- the "Provider" has a list of the OLE DB drivers with preselected "Microsoft OLE DB Provider for ODBC Drivers". I keep this default selection.
- the "Connection" tab has a connection string "DSN=<my database name>" which I keep, it also has fields for the user name and the password, which I fill with the correct credentials.
- Finally there is a button "Test Connection", which when I click produces the following error message:
"Test connection failed because of an error in initializing provider. 
Unespecified error"

4) Additional food for thought:
a) In the above walk-through the only data, which I type, are the user name and password, everything else is selected from lists offered by Excel-2007, hence any possibility of typos being the cause of the problem can safely be discarded.
b) I can test the ODBC driver in the Control Panel and it shows that it can connect to the Oracle database:
- in Control Panel --> Admin Tools --> Data Sources (ODBC) on the "User DSN" tab I can see the list of the available ODBC data sources (same list as in Excel-2007, point 3b above) with the name of my database in it;
- selecting the name of my database from the list of the sources and clicking "Configure" button opens a tab with Data Source Name (same as in Excel-2007), TNS Service Name and User ID. I enter <user name>/<password> and click "Test Connection" button. A message "Connection successful" appears (just for a test I enter incorrect user credentials and "Unable to connect" message appears)
BOTTOM LINE


The procedure for using an ODBC connection from Excel is very simple, in the past I have created and used such connections numerous times with Excel-2003 and earlier on Win-XP and earlier. But now on Excel-2007 and Vista-x64 I cannot make it work.
Also, testing an ODBC connection driver is really easy and simple to be done in the Control Panel. There testing the same ODBC connection, which fails in Excel-2007, results in success.
I am frustrated by the simplicity of the problem and yet the persistant error. I have lost now two full days in failed attempts to make the simple procedure work and in searching the internet for answers.
All help is highly appreciated <img class="emoticon" src="images/emoticons/happy.gif" border="0" alt="" width="16" height="16" />,
Plamen


Did you find the solution to your problem?
If not, I think I may know.
Excel 2007 is a 32-bit application.
When installing 32-bit applications in a 64-bit environment, the "default" location is:
C:\Program files (x86)\...
Excel then launches from this location.
However, when it connects to Oracle and passes the name of the calling program, Oracle attempts to "interpret" the value of (x86) as if
the value within the parenthesis are being passed as a reference. Of course, iOracle doesn't find anything, so the result is (),
and then it cannot return the connection info back to the calling application.
I corrected it by installing Excel in C:\Program Files\, and once launched from that location, it works the same as on the 32-bit machines.
However, at my location, they are FORCING Excel to be installed in the(x86) location.
What I'm trying to discover now is:
Is it possible to flag Oracle to NOT process the embedded variables?
Or, is it possible to assign a variable in Oracle such that x86 = "(x86)", so that the end result is viable?
Have you had any luck with your installation?
thanks,
Paul

Warning message when exporting a Financial Report to Excel 2007

Excel 2007 users that attempt to export a fully formatted Financial Report into Excel 2007 get the following error message:
"The file you are trying to open, 'FileName.xls', is in a different format than specified by the file extension. Verify that the file is not corrupted and is from a trusted source before opening the file. Do you want to open the file now?"
I am still researching the behavior that users get when they click through the message, but would ideally like for the message not to appear without updating the client machine registries. Has anybody else run across this?
Excel 2007
BI Plus version: 9.3.1.0.0.248

It looks like this is a known issue addressed in Bug 7359171 - EXPORT TO EXCEL 2007 CAUSES FILE FORMAT WARNING:
The current design does not allow you to open HTML content from a web site in Excel unless the extension of the URL is .HTM/.HTML/.MHT/.MHTML. So ASP pages that return HTML and set the MIME type to something like XLS to try to force the HTML to open in Excel instead of the web browser (as expected) will always get the security alert since the content does not match the MIME type. If you use an HTML MIME type, then the web browser will open the content instead of Excel. So there is no good workaround for this case because of the lack of a special MIME type for HTML/MHTML that is Excel specific. You can add your own MIME type if you control both the web server and the client desktops that need access to it but, otherwise the best option is to use a different file format or alert your users of the warning and tell them to select Yes to the dialog.
Another Workaround :
Client Configuration of Extension Hardening.
Client desktops can change the default behavior of the security check using a registry key. The following registry key can be set to alter the behavior ofthe Excel 2007 client in the following ways:
Key: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\SecurityValue: (DWORD)"ExtensionHardening" = [0 = Disable check; 1 = Enable check and prompt; 2 = Enable check, no prompt deny open]Default setting if value not present is 1 (enable and prompt).
The client can configure the site to disable the check by setting ExtensionHardening = 0. This will stop the prompt from appearing, but it will also disable any future checks for the file content validity. This does not (in itself) lower your security. The check is part of a defense-in-depth strategy to prevent malicious users from crafting files of a different type than its extension (or MIME type), which could then be used to trick users into opening a file of a type they did not expect. This warning is designed to let the user know of this potential threat and given them an option of canceling the open if they wish.

BPC and Excel 2007

Can someone tell me what version/service pack of BPC is needed in order to run properly in Excel 2007?
Thanks!
Anthony

Anthony,
I am using BPC Sp3 so V.5.0.502.03 and I discovered problems in the Admin with Excel 2007!
As an admin I would not recommend yet to install Excel 2007, except if all admins are using it!
Just to let you know:
Here is a log I put on SAP Support Portal about this problem:
Short Text
Excel 2007 saving files in 2007 format but with an xls ext
Long Text
I have upgraded my Excel to 2007, but the default file format is in
Excel 2003 format. When I make changes to dimensions the file is being
saved as an xls (as opposed to an xlsx) file, but it is being saved in
the Excel 2007 format. This means that 2003 users can't open the file.
I have deliberately kept the default file version in excel to the 2003
format so that I don't have compatibility issues, but BPC seems to be
ignoring this settting and using the 2007 format anyway.
I can work around this by opening the file from Excel and resaving it,
but obviously this is a nuisance to keep having to do this. I do not
want to revert back to Excel 2003 just to avoid this problem
I am running BPC version 5.1 SP3
Steps for Reconstruction
Install Excel 2007, make the default file type Excel 97-2003. Use BPC
admin to make a change to a dimension, then try to make a change to the
same dimension on a machine that is running Excel 2003
Here is the answer they gave me:
Dear customer,
Thank you for contacting SAP Support Centre.
The problem is a known issue which has been reproted the dev team.
It will be fixed on bpc 7m.
The current workaround is:
1. Install 'Compatibility Pack for the 2007 Office system' file on
client has Office2003.
2. Change file extension 'xls' or 'xlt' to 'xlsx'.
3. Opent template
I wish this could be helpful to you.
Even in installing the compatibility pack did not solve this problem but it is only this problem i found and only in the Admin... but as an admin it is a major problem!!
So when you ask, the version of BPC working "properly"... i dont really know what to answer. Make your own opinion
Nic

Error - using MS Excel 2007

Hi All,
Very recently I have upgraded my system to MS Excel 2007 from MS Excel 2003. Now when I try to refresh a workbook the system throws an error message saying " Run time error '13' - Type mismatch ". And then gets disconnected from the BW system.
Please help.
Thanks & Regards,
Surjit P

Hi Surjit,
Hi,
See SAP Note 1040856 - Business Explorer 3.X on Windows Vista / Excel
2007 below:
The *Business Explorer (SAP BW 3.x)3 programs are not yet released for
Windows Vista, that means, BEx Query Designer (SAP BW 3.x),*BEx Analyzer
(SAP BW 3.x), 3BEx Web Application Designer (SAP BW 3.x), *BEx Download
Scheduler (SAP BW 3.x)* and BEx Browser (SAP BW 3.x) are not released.
*Likewise, the BEx Analyzer (SAP BW 3.x) for Excel 2007 is not released for
other versions of Microsoft Windows.
Other terms
BEx Analyzer, BEx Query Designer, BEx Web Application Designer, WAD,
Microsoft Windows Vista, 3.x Frontend, Excel 2007, Office 2007
Reason and Prerequisites
We are currently evaluating the usage. Tests have shown that the productive
use of Business Explorer cannot be supported fully at the moment.
Due to changes in the Microsoft Windows and Office environment, problems may
occur when displaying Business Explorer programs (SAP BW 3.x).
Solution
Microsoft Vista and Excel 2007 will be supported officially as of the next
BW 3.5 Frontend patch. These patches should be available by the end of
September 2007.
- BW 3.5 for SAP GUI 6.40: Frontend Patch 13 (see Note 1073426)
- BW 3.5 for SAP GUI 7.10: Frontend Patch 2 (see Note 1006943)
Known problems:
- Microsoft Vista and BEx Query Designer: See Notes 1050174, 1039191,
1013139 and 1050174.
- Microsoft Excel 2007, Vista and BEx Analyzer: see Notes 1045244,
1052761 and 1054250.
- Excel 2007 and BW precalculation servers: You cannot use Microsoft
Excel 2007.
Make sure all the criteria given above are accomplished..
assign points if helpful.
Thanks and Best Regards
lasitha

VS 2013 crashes on opening Worker Role configuration

After creating a cloud project using Azure SDK for .NET 2.4 then Visual Studio 2013 (update 3) crashes when I attempt to edit the Role Configuration via the UI by double clicking the [Cloud Project] -> Roles -> [Worker Role Name] in Solution Explorer.
The event details as text looks like this.
Application Error
Log Name: Application
Source: Application Error
Date: 12-09-2014 10:33:59
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: [removed].[removed].com
Description:
Faulting application name: devenv.exe, version: 12.0.30723.0, time stamp: 0x53cf6f00
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0xe0434352
Fault offset: 0x0000c42d
Faulting process id: 0x1f54
Faulting application start time: 0x01cfce63c98e92fb
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 8a86cb32-3a57-11e4-857a-0026b9e0fb6f
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-09-12T08:33:59.000000000Z" />
<EventRecordID>213664</EventRecordID>
<Channel>Application</Channel>
<Computer>[removed].[removed].com</Computer>
<Security />
</System>
<EventData>
<Data>devenv.exe</Data>
<Data>12.0.30723.0</Data>
<Data>53cf6f00</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.18409</Data>
<Data>53159a86</Data>
<Data>e0434352</Data>
<Data>0000c42d</Data>
<Data>1f54</Data>
<Data>01cfce63c98e92fb</Data>
<Data>C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe</Data>
<Data>C:\Windows\syswow64\KERNELBASE.dll</Data>
<Data>8a86cb32-3a57-11e4-857a-0026b9e0fb6f</Data>
</EventData>
</Event>
.NET Runtime
Log Name: Application
Source: .NET Runtime
Date: 12-09-2014 10:33:59
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [removed].[removed].com
Description:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AggregateException
Stack:
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__4(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-09-12T08:33:59.000000000Z" />
<EventRecordID>213663</EventRecordID>
<Channel>Application</Channel>
<Computer>[removed].[removed].com</Computer>
<Security />
</System>
<EventData>
<Data>Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AggregateException
Stack:
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__4(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
</Data>
</EventData>
</Event>
Just prior to the crash...
...it seems like VS 2013 is attempting to log me in to a company server (active directory?). Regardless of my action (providing my login credentials or cancelling the login) VS 2013 then proceeds to crash.
My other computers
On my private laptop that connects to the internet via a private internet connection, the same type of project loads the configuration page w.o. issues (same VS and SDK configuration).
Others have this issue as well
There is also a thread about this on SO, although without a solution:
Visual Studio 2013 crashes when opening up service configuration for edit
Can anybody provide any help about how to solve this, please?
Br,
Claus

Hi Will
Thanks for your answer - I have added my findings below:
The problem apparently stems from the authentication process.
If you are using your company email as username on Azure, the inherent domain name will cause the authentication method to redirect you to your company's Active Directory.
The problem can be solved by choosing a different email as username on Azure.
The problem can also be replicated by setting up a website with authentication using Azure Active Directory. During login through Azure AD, the exact moment you enter the domain name in your username, the login screen redirects you from the Azure AD to the
AD at sts.[email domain name] - and consequently, the login fails. Using a different username the Azure AD authentication works flawlessly.
Br,
Claus

ALV to EXCEL-2007 issue

We are in the midst of changing over from Excel 2003 to Excel 2007.
We are seeing an issue in Excel 2007 with the use of the Microsoft Excel View option from the ALV output.
When the Excel view comes up, the Send button is grayed out. The users have to save the file to their PC and then re-open it before they can e-mail it. The Send button works for those that are still using Excel 2003.
If they use List-Export-Spreadsheet-Table-Microsoft Excel the Send button is there, but not all of our ALV report have this as an option.
Are there any thoughts on how to activate the Send button when using the Microsoft Excel View?

Before contacting OSS, search for notes. there are a number related to Excel 2007.
Rob

Errors opening Excel 2007 spreadsheets in Excel 2010

When I try to open spreadsheets created in Excel 2007 with Excel 2010, I get the error: "Excel found unreadable contenct in 'file name'. Do you want to recover the contents of this workbook? If you trust the source of this workbook, click
Yes". Then a Repairs dialog box comes up saying: "Excel completed file level validation and repair. Some parts of this workbook may have been repaired or discarded.    Removed Part: Print options." File then opens fine.
We receive Excel 2007 from various sources. One of my problem is that we are just starting to migrate people to Windows 7 and Office 2010, with most people still on Office XP. The file format converter for Excel 2002/2003 does not work with these
Excel 2007 files. The other problem is that we have macros that are used to open Excel files and import data into other Excel files. Pretty hard to modify these macros to allow for some files that are going to pop up this error, and others that
do not.
What is causing this problem, and what fix is available? We have asked that people save the Excel files in Excel 97-03 format before sending to us, with mixed results.

Hi,
Thank you for using Excel IT Pro Discussions forum.
Are you using Office 2010 RTM version? If it is trial version or beta version, I suggest upgrading it to the RTM version.
First, please check if this KB article helps:
Error message when you try to open a workbook in Excel 2007: "Excel found unreadable content in Book_Name"
http://support.microsoft.com/kb/929766
Note: The steps are for Excel 2007. The steps in Excel 2010 are similar.
If the problem persists, let’s also check the following settings in Excel 2010.
========
1.
In Excel 2010, click File > Options > Trust Center > File block settings.
2.
Check the checkboxes before:
Excel 2007 and later Wordbooks and Templates
Excel 2007 and later Macro-Enabled Workbooks and Templates
Excel 2007 and later Add-in Files
Excel 2007 and later Binary Workbooks
Then, try to open the Excel 2007 file in Excel 2010 and check the results again.
Best Regards,
Sally Tang
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
[email protected]

Excel 2007 csv file formatting issue

Our users create .csv files for upload to SAP. Their habit is to include a number of blank lines in excel to make it more readable.
In Excel 2003, blank lines were handled as, literally, blank lines, and opening in a text editor shows exactly that, a blank line (with a CR-LF character to terminate the row).
In Excel 2007 however, the blank line consists of a number of commas equal to the no. of columns, followed by the CR-LF termination. Hope that makes sense.
While the 2003-generated .CSVs are fine, the 2007 versions cause SAP to throw an exception ("Session never created from RFBIBL00") and the upload fails. The question therefore is, has anyone ever come across anything similar, or is anyone aware of any remediation that might be possible? Haven't been able to find any documentation on this Excel 2003-2007 change sonot able to address the issue through Excel config.
Thanks!
Duncan

Hello
Please refer to the consulting note 76016 which will provide information on the performance of the standard program
RFBIBL00.
Regards.

Excel 2007 query problems

Has anyone else noticed problems with Excel 2007 when doing webqueries? We have someone who wrote a bunch of VBA in an excel document (excel 2003) that does 7 web queries, and then creates pivot tables on the results.
Because of the row limitations in older excel version (1million+ rows in Excel 2007), we upgraded. However, now the Excel queries take forever. In TOAD, the queries run in 5 seconds, but take hours upon hours in Excel 2007. The PC where Excel runs is adequately powered (CPU, RAM, etc) to handle the load.
I'm assuming some type of ODBC problem? Maybe an incompatibility with Oracle 9iR1 drivers?
We're running 9.2.0.1 here for now.
Any help would be appreciated!
Thanks!
-Mike

turns out the Excel 2007 VBA engine is extremely slow. THe query returns very quickly, but Excel 2007 is taking much much longer to use the result set.

Excel 2007 ignores the roles configured on SSAS 2008

Similar Messages

Maybe you are looking for