I have an Excel 2013 Add-in.
I can't figure out why it won't load through Remote Desktop gateway if the user haven't first logged in through a normal RDP connection.
When looking into the registry on the server it seems office is missing some entries that used to be there such as:
CURRENT_USER\Software\Microsoft\Office\Excel\Addins\
I only got
CURRENT_USER\Software\Microsoft\Office\15.0\Excel\
Related
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.
we've got a Windows Server 2012 R2 with SSIS 2015 installed, and also SAP BO BI 4.2. There is also Office 2016, and we first tried (and then uninstalled) Microsoft Office Access Redistributable 2010 32bit (which had some problems with BO), and then we successfully installed Microsoft Office Access Redistributable 2016 32bit.
Before the redistributable, the SSIS couldn't even see the Excel component in the data flow. We are accessing with some users in RD to the machine, and there is a user which is administrator.
So, the administrator made all the install/uninstall. If we open a SSIS solution with the administrator, and we open a DTSX with an Excel connection, it hangs. If we try to make a new SSIS to point to a new Excel, when we try to open the table we get "Could not retrieve the table information for the connection manager ‘Excel Connection Manager’". That also happens to some of my collegues.
What is extremely strange, is that this doesn't happen to my user. I can connect to the RD, open the SSIS solution, and all the metadata is loaded. I can create a new DTSX, point to the same Excel on the server, and I see the sheets to choose. Somehow, I guess, my user is the only one which is loading correctly the dlls for Access 2016 (if I try to set a different driver, it doesn't load).
I'll try when I get back to work to see if the suggestion here to read from SQL and see if I get the same error from the other users is always the same...but still I need to get why my user is working.
https://mariussqlbi.wordpress.com/2013/09/06/extracting-data-from-excel-with-ssis/
Any help would be appreciated...
Daniele
I have a web application in c# in VS2010, that uses Microsoft.Interop.Excel 12 to export data to an Excel Spreadsheet.
The application works well on Windows Server 2003, and also on Windows Server 2008 R2 in debug mode from VS2010.
When I run the application on iis7.5, I get Exception from HRESULT: 0x800AC472.
I have used dcomcnfg to give permissions to the appPool identity user on Microsoft Excel Application,
and created Desktop folder in C:\Windows\SysWOW64\config\systemprofile and in C:\Windows\System32\config\systemprofile, with permissions to the same user.
The server I'm using is Virtual Windows Server 2008 R2 (on top of Windows Server 2012).
Can anyone help ?
Thanks a lot
I have a client who is upgrading parts of their Windows server infrastructure to Windows 2012. They have a MOSS 2007 installation on the same network currently.
Assuming that the WFEs and app servers (which run SharePoint Services) remain on Windows 2008 installations will the app servers be able to continue to run the AD imports successfully? Will adjustments need to be made? Or will it be outright incompatible?
I understand the best answer is to upgrade SP to 2010 or 2013 but am trying to understand all options. Thanks very much.
I recently setup a sharepoint server 2013 on our company and have found really good examples how you can override the suitbar with custom links.
Now that I'm trying to implement those examples i get to that point where Visual Studio 2012 and Office development tools is installed.
When i choose to start a new project I select New Project > Templates > Visual C# > Office/SharePoint > SharePoint Solutions > SharePoint 2013 Empty Project hit ok and i get an error that says Sharepoint not installed?
Am I supposed to install VS 2012 and develop om my Sharepoint 2013 server directly?
A very common way to develop SharePoint applications is to run a virtual machine (hyper-v under windows 8 for example) on your development workstation.
You can also dual-boot into a vhd file.
You can also install Windows Server 2012 and use one of the many desktop conversion techniques to use it as your primary operating system on your workstation.
Another often seen technique is to have a virtual machine hosted in the cloud or a datacenter, running both SharePoint Server and Visual Studio. Then connect to that machine using Remote Desktop.
With some trickery, you could have the SharePoint 2010 installer install om a workstation OS. This no longer works on SharePoint 2013. The reason this support was removed is due to the inclusion of Boot from VHD and Hyper-v into Windows 8.
It is my experience that if you just want to build your application and not run or debug it, that just having the assemblies copied over from an actual SharePoint Server will allow you to do that. I haven't found an updated document for SharePoint 2013 yet.
Yes. You have to develop on the sharepoint server directly using Visual Studio as Sharepoint server GAC has the required server object models to work programatically with sharepoint server object model.
You can aslo develop on client machine using Client Object Model or WCF Data Services Framework.