When I launch Excel 2016 using Runas I am not able to log into Excel. The version we are using is in this path "C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE". It appears as a subscription product Microsoft 365 Apps for enterprise. This is corporate Excel and I do not have an individual license key.
When Excel launches it needs to be signed in or it won't work. I can input my corporate email and when I click [Next] the app freezes. It appears to have a modal dialog box "pop-under" that is not visible. If I kill the app it warns there is a dialog box but I cannot switch to it. I cannot input the password because the dialog box is not visible.
Does anyone know a trick to get this to work? Log into Excel after launching with Runas?
TIA
Related
Just faced with strange behavior on Outlook for Mac. When a user creates an event, add attendees, save and close, then select it and press the button "Forward" it opens a new message window with disabled my Outlook Add-In (open Add-in button is disabled). When I do the same on Outlook for Window the Add-in button is enabled and Add-in works fine.
What is the reason to change behavior on Mac and Windows? Is it an issue?
Stable repro, I use the same o365 account (there is no difference between the Add-in manifest then), Outlook for Mac 16.36 (20030502), Outlook for Windows 2006 (build 13001.20384 Click-to-Run) Current chanel.
Thanks in advance.
Sorry for confusion earlier. We do not support add-ins in the event forward scenario by design in Outlook Mac.
However, read mode add-ins are supported in event forward scenario (with the exception of item.getBody APIs) in the New Outlook for Mac, which is currently available in our Insiders program. You can get access to it by signing up for the Insiders program here.
I have written an add-in for Microsoft Excel. The add-in works great on the web-based Excel, but I get the error below when I try to run it in the desktop version
This happens when the plugin tries to authenticate the user using a popup window. Anyone encountered this issue ?
Thanks
Matteo
Had an issue with excel 2013 invoked with scheduled task via powershell.
I added "Desktop" directory on C:\Windows\SysWOW64\config\systemprofile. (for 32 bits too)
Now i can read excel file but i can't save excel file.
Windows server 2019.
Excel 2013.
It was working on 2008 R2.
Thanks for help.
Ok, I've found a trick.
Microsoft said that automation on server side is not supported by devs.
https://support.microsoft.com/en-us/help/257757/considerations-for-server-side-automation-of-office
Solution is here :
https://social.msdn.microsoft.com/Forums/office/en-US/66afe200-0bff-41f5-a2ca-e43007ad8f31/excelapplication-powershell-script-error-running-from-scheduled-task?forum=exceldev
Open comexp.msc.
Navigate to DCOM config and find Microsoft Excel Application. Right clic and properties
Identity tab >> This user and choose a user who has a profile on this computer.
You do not need Desktop folders on systemprofile dirs.
I have a ASP.NET application which uses Microsoft intrope assemblies to read, write and modify excel files and it uses Excel 2013 on server machine. Application works fine if i am logged in to server machine as administrator but when i am logged out the application is unable to to initialize excel application. Here is the exception.
System.Runtime.InteropServices.COMException (0x8000401A)
Application is running on Windows Server 2008R2 with MS Excel 2013 32-bit I am not being able to figure out the reason of this behavior. Is this about COM objects security options or it has something to do with IIS permissions?
The InteropServices class opens an (invisible) Excel instance to get its work done. Excel cannot run as a Windows service and needs to be instanciated by a logged on user.
"Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment."
See this page for more information: Office support: Considerations for server-side Automation of Office
If you still want to keep the interop service, try change it to run as an interactive user:
Open Component Services (Start -> Run -> MMC comexp.msc /32)
Find Component Services -> Computers -> My Computer -> DCOM Config -> Microsoft Excel Application
Right click, choose properties
Go to the Identity tab and choose Interactive user
If this is not working, you can try to manually enter the user credentials
Of course, you could also switch to another framework to read the file. SO: How to read an excel file in C# without using Microsoft.Office.Interop.Excel libraries
I had the same problem after migrating from 2008r2 to 2012. My solution:
Find Component Services -> Computers -> My Computer -> DCOM Config -> Microsoft Excel Application
Right click, choose properties
Go to the Identity tab and choose This user (input user & password)
Macros refuse to run for me in Excel 2007 on Windows Server 2003.
The macro and visual basic icons on the ribbon are grayed out.
If I open a workbook with a macro, I get the warning: " This workbook has lost its VBA project, ActiveX controls and any other programmability-related features."
If I try to make a new excel template in VSTO (Excel is closed at the time), I get the error: "Programmatic access to the Microsoft Office Visual Basic for Applications project system could not be enabled. . ."
I checked that VBA was installed (originally it wasn't, I added it via office setup). I also tried uninstalling and reinstalling office and VBA, no dice.
I made a macro-enabled workbook.
I set the workbook's location to trusted.
I configured all of the security settings available under Excel Options/Trust Center to allow-everything-no-prompts.
I set "Enable all macros" and "Trust access to the VBA object model".
I downloaded the group policy admin templates and verified none of this is being set via group policy.
That's everything I can find in Google to try, but clearly there is another place that VBA can be turned off. Where else can I look?
Are you sure there isn't a system policy in place that inhibits VBA?
Edit: Some reading, if you've not already seen these:
http://support.microsoft.com/kb/282847/en-us
http://support.microsoft.com/kb/287567
http://support.microsoft.com/kb/281954/en-us - Applies to earlier versions, but some/all may still be relevant to 2k7
Alt+F11 in excel and see if there is an option in there that you can change....